In the Change Center, click Create to create a session. At the bottom of the View Details page, click Edit. On the Edit a Proxy Service - Summary page, click Sav In the Change Center, click Activate. In the Domain Structure window, expand the Environment

5-204 Oracle Fusion Middleware High Availability Guide h. Restart the managed server. i. Restart the Administration Server. The business services are now configured for operation in the extended domain. 13. If your Oracle Service Bus configuration includes one or more proxy services that use JMS endpoints with cluster addresses, then you must also perform the following procedure using the Oracle Service Bus Console after adding the new managed server to the cluster:

a. In the Change Center, click Create to create a session.

b. Using the Project Explorer, locate and select a proxy service that uses JMS endpoints with cluster addresses.

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. 14. 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=osbhostnvhn1 -DOSB.coherence.localport=7890 -DOSB.coherence.wka1= osbhost1vhn1 -DOSB.coherence.wka1.port=7890 -DOSB.coherence.wka2= osbhost2vhn1 -DOSB.coherence.wka1.port=7890 Note: For business services that use a JMS MesageID correlation scheme, you must edit the connection factory settings to add an entry to the table mapping managed servers to queues. For information on how to configure queues and topic destinations, see JMS Server Targeting in Oracle Fusion Middleware Configuring and Managing JMS for Oracle WebLogic Server. Configuring High Availability for Oracle Fusion Middleware SOA Suite 5-205 g. Save and activate the changes this change requires the Oracle Service Bus servers to be restarted to be effective. 15. Run the pack command on SOAHOST1 to create a template pack as follows: SOAHOST1 cd ORACLE_COMMON_HOMEcommonbin SOAHOST1 .pack.sh -managed=true -domain=MW_HOMEuser_ projectsdomainssoadomain -template=soadomaintemplateScale.jar -template_name=soa_domain_templateScale Run the following command on SOAHOST1 to copy the template file created to OSBHOSTn: SOAHOST1 scp soadomaintemplateScale.jar oracleOSBHOSTN: ORACLE_ BASEproductfmwsoacommonbin Run the unpack command on OSBHOSTN to unpack the template in the managed server domain directory as follows: OSBHOSTN cd ORACLE_BASEproductfmwsoacommonbin OSBHOSTN .unpack.sh -domain=ORACLE_BASEproductfmwuser_ projectsdomainssoadomain -template=soadomaintemplateScale.jar 16. 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. 17. 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 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 setting is propagated to the cloned server. To disable host name verification:

a. In the Oracle Enterprise Manager Console, select Oracle WebLogic Server