Click Create a New Subdeployment. Click OK. Click Finish. In the Change Center, click Lock Edit. In the general Configuration tab, click on Advanced.

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.

k. Accept the default name.

l. Click OK.

m. Select OSB_rpc_JMSServer_n as the target.

n. Click Finish.

o. Activate the changes. p. Update the local JNDI name for the destination by following steps q though u.

q. In the Change Center, click Lock Edit.

r. In the Settings for the WseeJmsModule page, click on the DefaultCallbackQueue-WseeJmsServer_auto_n destination.

s. In the general Configuration tab, click on Advanced.

t. Update the local JNDI name to weblogic.wsee.DefaultCallbackQueue. u. Activate the changes. v. Repeat steps d through n for the DefaultQueue-WseeJmsServer_auto_n queue, using weblogic.wsee.DefaultQueue-WseeJmsServer_auto_n as the JNDi name and weblogic.wsee.DefaultQueue as the local JNDI name. 9. Create a new SAF agent and target it to the newly added managed server, as follows: In the Oracle WebLogic Server Administration Console, expand Services Messaging Store-and-Forward Agents , and add a new SAF agent ReliableWseeSAFAgent_auto_N. Select persistent store Wsee_rpc_JMSFileStore_N persistent store created for OSB JAX-RPC. Target the SAF Agent to the new managed server and activate changes. 10. Configure TX persistent store for the new server. This should be a location visible from other nodes as indicated in the recommendations about shared storage. From the Administration Console, select Server_name Services tab. Under Default Store , in Directory, enter the path to the folder where you want the default persistent store to store its data files. 11. Disable host name verification for the new managed server. Before starting and verifying the WLS_OSBn managed server, you must disable host name verification. You can re-enable it after you have configured server certificates for 5-198 Oracle Fusion Middleware High Availability Guide the communication between the Oracle WebLogic Administration Server and the Node Manager in OSBHOSTn. If the source server from which the new one has been cloned had already disabled hostname verification, these steps are not required the hostname verification settings is propagated to the cloned server. To disable host name verification: a. In the Oracle Enterprise Manager Console, select Oracle WebLogic Server Administration Console.

b. Expand the Environment node in the Domain Structure window.