Applying the Java Required Files JRF Template to the WSM-PM_ Cluster

4-12 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter 2. Log in as the administrator. 3. Verify that the WLS_WSM1 and WLS_WSM2 managed servers are listed. 4. Verify that the WSM-PM_Cluster cluster is listed. 5. Check that you can access Oracle Enterprise Manager at http:ADMINVHN:7001em. 6. Log in to EM Console with the username and password you specified in Section 4.5, Creating boot.properties for the Administration Server on SOAHOST1. 4.9 Creating a Separate Domain Directory for Managed Servers in the Same Node as the Administration Server Use the pack and unpack commands to separate the domain directory used by the Administration Server from the domain directory used by the managed server in SOAHOST1as recommended in Chapter 2, Database and Environment Preconfiguration. 1. Run the pack command on SOAHOST1 to create a template pack as follows: SOAHOST1 cd ORACLE_COMMON_HOMEcommonbin SOAHOST1 .pack.sh -managed=true -domain=ORACLE_BASEadmindomain_ name aserverdomain_name -template=soadomaintemplate.jar -template_name=soa_ domain_template 2. Run the unpack command on SOAHOST1 to unpack the template in the managed server domain directory as follows: SOAHOST1 cd ORACLE_COMMON_HOMEcommonbin SOAHOST1 .unpack.sh -domain=ORACLE_BASEadmindomain_namemserverdomain_name -template=soadomaintemplate.jar -app_dir=ORACLE_BASEadmindomain_ name mserverapplications

4.10 Applying the Java Required Files JRF Template to the WSM-PM_ Cluster

After the domain is created with the Configuration Wizard, you must target a number of resources not included in the WebLogic server installation to the WSM-PM Cluster. To target these resources: 1. Log in to Oracle Enterprise Manager Fusion Middleware Control with the username and password you specified in Section 4.5, Creating boot.properties for the Administration Server on SOAHOST1.

2. On the navigation tree on the left, expand Farm_domain_name, WebLogic

Domain , and then domain_name, and select WSM_PM_Cluster. 3. Click Apply JRF Template on the right. 4. Wait for the confirmation message to appear on the screen. This message should confirm that the JRF Template has been successfully applied to the WSM-PM_Cluster cluster. Creating a Domain 4-13 4.11 Disabling Host Name Verification for the Oracle WebLogic Administration Server and the WLS_WSM1 Managed Server This step is required if you have not set up the appropriate certificates to authenticate the different nodes with the Administration Server see Chapter 7, Setting Up Node Manager . If you have not configured the server certificates, you will receive errors when managing the different WebLogic Servers. To avoid these errors, disable host name verification while setting up and validating the topology, and enable it again once the Enterprise Deployment topology configuration is complete as described in Chapter 7, Setting Up Node Manager. Perform these steps to disable host name verification: 1. Log in to Oracle WebLogic Server Administration Console.

2. Click Lock and Edit.

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

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

5. Select AdminServeradmin in the Names column of the table. The Settings page

for AdminServeradmin appear.

6. Click the SSL tab.

7. Click Advanced.

8. Set Hostname Verification to None.

9. Click Save.

10. Repeat steps 4 to 8 for the WLS_WSM1 server. 11. Save and activate the changes. 12. The change requires restart of the Administration Server to be effective. To do this, complete these steps:

a. In the Summary of Servers screen, select the Control tab.