My Oracle Support Banner

SOA Domain Silent Domain Creation Fails Using Custom Server Names and targetting of JMS artifacts fails as well (Doc ID 2817873.1)

Last updated on OCTOBER 28, 2021

Applies to:

Oracle SOA Suite - Version 12.2.1.4.0 and later
Information in this document applies to any platform.

Symptoms

On : 12.2.1.4.0 version, Fabric

ACTUAL BEHAVIOR
---------------
SOA Domain creation Issue

While using attached scripts for SOA domain creation for 12.2.1.4.0 version documented on
https://docs.oracle.com/en/middleware/fusion-middleware/12.2.1.4/insoa/configuring-product-domain.html#GUID-081C1379-157C-4EC5-B52C-7461A19985F4
The architecture is one Linux OS on which we have hosted 1 admin , 1managed and one node manager.
The Issue is we customer wants to create one Managed server with name SOA_MS1.
The script is executed successfully but we can see a extra managed server with name "soa_server1" by default created.
Also we can see below jms server created which is not expected.



EXPECTED BEHAVIOR
-----------------------
We expected only BPMJMSServer , SOAJMSServer ,UMSJMSServer jmsserver to be created which should be targeted to SOA_MS1 managed server which we are creating.
please suggest how to avoid creating the default managed server soa_server1
and for all the JMS servers to be created using custom names

STEPS
-----------------------
Run script from documentation changing the names of the server managed for custom ones

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.