In the Change Center, click Activate. In the Domain Structure window, expand the Environment node. Click Servers. The Summary of Servers page appears. Click the name of the server represented as a hyperlink in the Name column Click the Server Start tab.

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

c. At the bottom of the View Details page, click Edit.

d. If there is a cluster address in the endpoint URI, add the new server to the cluster address. e. On the Edit a Proxy Service - Summary page, click Save. f. Repeat the previous steps for each remaining proxy service that uses JMS endpoints with cluster addresses.

g. In the Change Center, click Activate.

h. Restart the managed server. The proxy services are now configured for operation in the extended domain. 6. Update the Oracle Service Bus result cache Coherence configuration for the new server: a. Log into Oracle WebLogic Server Administration Console. In the Change Center, click Lock Edit.

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

c. Click Servers. The Summary of Servers page appears.

d. 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.

e. Click the Server Start tab.

f. Enter the following for WLS_OSBn on a single line, without a carriage returns: -DOSB.coherence.localhost=osbhost1vhnn -DOSB.coherence.localport=7890 -DOSB.coherence.wka1= osbhost1vhn1 -DOSB.coherence.wka1.port=7890 -DOSB.coherence.wka2= osbhost2vhn1 -DOSB.coherence.wka1.port=7890 g. Save and activate the changes this change requires the Oracle Service Bus servers to be restarted to be effective. 7. Create JMS Servers and persistent stores for OSB reportinginternal destinations on the new managed server. a. Use the Oracle WebLogic Server Administration Console to create a new persistent store for the new WseeJMSServer and name it, for example, OSB_ rep_JMSFileStore_N. Specify the path for the store. This should be a directory on shared storage, as recommended in Section 5.14.1.3, Shared Storage Prerequisites : Note: The above configuration assumes that servers WLS_OSB1 and WLS_OSB2 are running when WLS_OSBn is started. This will enable WLS_OSBn to join the coherence cluster started by either WLS_OSB1 or WLS_OSB2 using the WKA addresses specified. Also, make sure WLS_OSB1 and WLS_OSB2 are started before WLS_OSBn is started when all three servers are restarted. This will ensure WLS_OSBn join the cluster started by one of WLS_OSB1 or WLS_OSB2. If you want to have a configuration where the order in which the servers are started does not matter, you must add the host and port for WLS_OSBn as WKA for WLS_OSB1 and WLS_OSB2, and also add WLS_OSBn as WKA for WLS_OSBn. 5-196 Oracle Fusion Middleware High Availability Guide ORACLE_BASE adminDOMAIN_NAMEcluster_namejmsOSB_rep_JMSFileStore_N b. Create a new JMS Server for OSB, for example, OSB_rep_JMSServer_N. Use the OSB_rep_JMSFileStore_N for this JMSServer. Target the OSB_rep_ JMSServer_N Server to the recently created Managed Server WLS_OSBn. c. Update the SubDeployment targets for the jmsresources OSB JMS Module to include the recently created OSB JMS Server. To do this, expand the Services node and then expand the Messaging node. Choose JMS Modules from the Domain Structure window of the Oracle WebLogic Server Administration Console. The JMS Modules page appears. Click jmsResources represented as a hyperlink in the Names column of the table. The Settings page for jmsResources appears. Click the SubDeployments tab. The subdeployment module for jmsresources appears. Click on the wlsbJMSServerXXXXXX subdeployment and update the targets to include the new OSB_rep_JMSServer_n server. 8. Create JMS Servers, persistent stores and destinations for OSB JAX-RPC on the new managed server.

a. Use the Oracle WebLogic Server Administration Console to create a new