In the Oracle Enterprise Manager Console, select Oracle WebLogic Server Expand the Environment node in the Domain Structure window. Click Servers. The Summary of Servers page appears. Select WLS_OSBn in the Names column of the table. Click the SSL tab. Cl

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

Administration Console .

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

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

Note: The preceding configuration assumes that servers WLS_OSB1 and WLS_OSB2 are running when WLS_OSBn starts. 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-206 Oracle Fusion Middleware High Availability Guide

d. Select WLS_OSBn in the Names column of the table.

The Settings page for server appears.

e. Click the SSL tab.

f. Click Advanced.

g. Set Hostname Verification to None.

h. Click Save.

18. Start the Node Manager on the new node. To start the Node Manager, use the installation in shared storage from the existing nodes, and start Node Manager by passing the host name of the new node as a parameter as follows: OSBHOSTN WL_HOMEserverbinstartNodeManager new_node_ip 19. Start and test the new managed server from the Oracle WebLogic Server Administration Console: a. Shut down all the existing managed servers in the cluster. b. Ensure that the newly created managed server, WLS_OSBn, is running. c. Access the application on the newly created managed server http:vip:portsbinspection.wsil. The application should be functional. 20. Configure server migration for the new managed server. Configure server migration following these steps: a. Log into the Administration Console.

b. In the left pane, expand Environment and select Servers.