Use the Oracle WebLogic Server Administration Console to create a new In the Change Center, click Lock and Edit. Click New. Select Queu Click Next. Click Next.

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

persistent store for the new WseeJMSServer and name it, for example, Wsee_ rpc_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 : ORACLE_BASE adminDOMAIN_NAMEcluster_namejmsWsee_rpc_JMSFileStore_N b. Create a new JMS Server for OSB JAX-RPC, for example, OSB_rpc_JMSServer_ N. Use the Wsee_rpc_JMSFileStore_N for this JMSServer. Target the OSB_rpc_ JMSServer_N Server to the recently created Managed Server WLS_OSBn. c. Update the WseeJMSModule OSB JMS Module with destinations and 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 Note: This directory must exist before the managed server is started or the start operation fails. Note: This subdeployment module name for destinations is a random name in the form of wlsbJMSServerXXXXXX resulting from the Configuration Wizard JMS configuration for the first two servers WLS_OSB1 and WLS_OSB2. Note: WebLogic Advanced Web Services for JAX-RPC Extension uses regular non-distributed destinations to ensure that a locally processed request on a service gets enqueued only to a local member. Note: This directory must exist before the managed server is started or the start operation fails. Configuring High Availability for Oracle Fusion Middleware SOA Suite 5-197 JMS Modules page appears. Click WseeJmsModule represented as a hyperlink in the Names column of the table. The Settings page for WseeJmsModule appears. Follow steps d through v to complete this step.

d. In the Change Center, click Lock and Edit. Click New.

e. Select Queue.

f. Click Next.

g. Enter DefaultCallbackQueue-WseeJmsServer_auto_n as name for the queue. h. Enter weblogic.wsee.DefaultCallbackQueue-WseeJmsServer_ auto_n as the JNDI name.

i. Click Next.

j. Click Create a New Subdeployment.