Configure Oracle Coherence for the Oracle Service Bus Result Cache

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

7. Click Save and activate the changes.

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

5.14.9 Configure Oracle Coherence for the Oracle Service Bus Result Cache

The default configuration for the Coherence infrastructure that Oracle Service Bus result cache uses is multicast. Oracle recommends using unicast communication for the Oracle Service Bus result cache. To enable unicast for the Oracle Service Bus result cache Coherence infrastructure: 1. Log into Oracle WebLogic Server Administration Console. In the Change Center, click Lock Edit.

2. In the Domain Structure window, expand the Environment node.

3. Click Servers.

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-170 Oracle Fusion Middleware High Availability Guide

4. Click the name of the server represented as a hyperlink in the Name column of

the table. The settings page for the selected server appears.

5. Click the Server Start tab.

6. Enter the following for WLS_OSB1 on a single line, no carriage returns: -DOSB.coherence.localhost=osbhost1vhn1 -DOSB.coherence.localport=7890 -DOSB.coherence.wka1= osbhost1vhn1 -DOSB.coherence.wka1.port=7890 -DOSB.coherence.wka2= osbhost2vhn1 -DOSB.coherence.wka2.port=7890 For WLS_OSB2, enter the following on a single line, no carriage returns: -DOSB.coherence.localhost=osbhost2vhn1 -DOSB.coherence.localport=7890 -DOSB.coherence.wka1= osbhost1vhn1 -DOSB.coherence.wka1.port=7890 -DOSB.coherence.wka2= osbhost2vhn1 -DOSB.coherence.wka2.port=7890 7. Save and activate the changes. You must restart Oracle Service Bus servers for these changes take effect.

5.14.10 Setting Connection Destination Identifiers for B2B Queues