Setting Connection Destination Identifiers for B2B Queues

5-10 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter

8. Click Save and Activate Changes.

5.6 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. 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: There should be no breaks in lines between the different -D parameters. Do not copy or paste the text from above to your Administration Consoles arguments text field. This may result in HTML tags being inserted in the Java arguments. The text should not contain other text characters than those included the example above. Note: You must ensure that these variables are passed to the managed server correctly. They should be reflected in the server’s output log. Failure of the Oracle Coherence framework can prevent the soa-infra application from starting. 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. Extending the Domain for SOA Components 5-11

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

Messaging node.

3. Click JMS Modules, and then SOAJMSModule.

4. Click Lock and Edit.

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

then click Advanced. 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: ■ dist_B2B_OUT_QUEUE_auto : jmsb2bB2B_OUT_QUEUE ■ dist_B2B_IN_QUEUE_auto : jmsb2bB2B_IN_QUEUE ■ dist_B2BBroadcastTopic_auto : jmsb2bB2BBroadcastTopic ■ dist_XmlSchemaChangeNotificationTopic_auto : jmsfabricXmlSchemaChangeNotificationTopic

8. Click Save and Active Changes.

5.7 Disabling Host Name Verification for the WLS_SOAn Managed Server