Setting Connection Destination Identifiers for B2B Queues

Configuring High Availability for Oracle Fusion Middleware SOA Suite 5-115

7. Click Save and activate the changes.

8. This change requires the SOA servers to be restarted.

5.13.9 Setting Connection Destination Identifiers for B2B Queues

Oracle B2B uses specific JMS Destination Member calls, and requires setting the Create Destination Identifier CDI for these calls to succeed. To set up the CDI: 1. Log into the Oracle WebLogic Server Administration Console.

2. In the Domain Structure window, expand the Services node, and then the

Messaging node.

3. Click JMS Modules, and then SOAJMSModule.

4. In the Change Center, click Lock Edit.

5. Click the dist_B2BEventQueue_auto, Configuration, and the General tab, and

then click Advanced. Note: The Coherence cluster used for deployment uses port 8088 by default. This port can be changed by specifying a different port for example, 8089 with the -Dtangosol.coherence.wkan.port and -Dtangosol.coherence.localport startup parameters. For example: WLS_SOA1 enter the following into the Arguments field on a single line, without a carriage return: -Dtangosol.coherence.wka1=soahost1vhn1 -Dtangosol.coherence.wka2=soahost2vhn1 -Dtangosol.coherence.localhost=soahost1vhn1 -Dtangosol.coherence.localport=8089 -Dtangosol.coherence.wka1.port=8089 -Dtangosol.coherence.wka2.port=8089 WLS_SOA2 enter the following into the Arguments field on a single line, without a carriage return: -Dtangosol.coherence.wka1=soahost1vhn1 -Dtangosol.coherence.wka2=soahost2vhn1 -Dtangosol.coherence.localhost=soahost2vhn1 -Dtangosol.coherence.localport=8089 -Dtangosol.coherence.wka1.port=8089 -Dtangosol.coherence.wka2.port=8089 Note: The multicast and unicast addresses are different from the ones used by the WebLogic Server cluster for cluster communication. SOA guarantees that composites are deployed to members of a single WebLogic Server cluster even though the communication protocol for the two entities the WebLogic Server cluster and the groups to which composites are deployed are different. Do not copy the text from above to your Administration Console’s arguments text field, which can result in HTML tags being inserted in the Java arguments. The text should not include any text or characters other than the ones shown above. 5-116 Oracle Fusion Middleware High Availability Guide

6. In the Create Destination Identifier field, add the following jndi name for the

queue: jmsb2bB2BEventQueue 7. Repeat these steps, creating the following Create Destination Identifiers for the queues listed below: ■ B2B_OUT_QUEUE : jmsb2bB2B_OUT_QUEUE ■ B2B_IN_QUEUE : jmsb2bB2B_IN_QUEUE ■ B2BBroadcastTopic : jmsb2bB2BBroadcastTopic ■ XmlSchemaChangeNotificationTopic : jmsfabricXmlSchemaChangeNotificationTopic

8. Click Save and Activate Changes.

5.13.10 Starting the System in SOAHOST1