Restarting the Administration Server Disabling Host Name Verification for the WebCenter Managed Servers Starting Node Manager on SOAHOST1 Propagating the Domain Changes to the Managed Server Domain Directory

6-6 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter – AdminServer – WLS_WSM1 ■ SOAHOST2: – WLS_WSM2 ■ WCHOST1: – WC_Spaces1 – WC_Portlet1 – WC_Collaboration1 – WC_Utilities1 ■ WCHOST2: – WC_Spaces2 – WC_Portlet2 – WC_Collaboration2 – WC_Utilities2 Click Next. 16. In the Target Deployment to Clusters or Servers screen, click Next. 17. In the Target Services to Clusters or Servers screen, click Next. 18. In the Configuration Summary screen, do not change the values that appear on the screen since you are extending a domain. Click Extend.

19. In the Extending Domain screen, click Done.

6.3 Restarting the Administration Server

Restart the Administration Server so that the changes to the domain are picked up. 1. Stop the Administration Server. SOAHOST1 .stopWebLogic.sh 2. Start the Administration Server: SOAHOST1 .startWebLogic.sh

6.4 Disabling Host Name Verification for the WebCenter Managed Servers

Before you can start and verify the managed servers, you must disable host name verification. You can re-enable it after you set up SSL communication between the Administration Server and the Node Manager. To disable host name verification, complete these steps:

1. Expand the Environment node in the Oracle WebLogic Server Administration

Console. Note: You can rename the originals servers, which appear by default in the Configuration Wizard, but never delete them. Extending the Domain for WebCenter Components 6-7

2. Select Servers. The Summary of Servers page appears.

3. Select WC_Spaces1 represented as a hyperlink from the Names column of the

table. The Settings page appears.

4. Select the SSL tab.

5. Expand the Advanced section of the page.

6. Set Hostname Verification to None.

7. Repeat these steps for the WC_Spaces2, WC_Portlet1, WC_Portlet2, WC_ Collaboration1, WC_Collaboration2, WC_Utilities1, and WC_Utilities2 managed servers.

6.5 Starting Node Manager on SOAHOST1

Make sure that Node Manager was started on SOAHOST1. If this is not the case, start Node Manager: SOAHOST1 cd WL_HOMEserverbin SOAHOST1 .startNodeManager.sh

6.6 Propagating the Domain Changes to the Managed Server Domain Directory

As described in Section 2–2, Directory Structure, we need to separate the Administration Server domain directory from the managed server directories. In this step, we propagate the changes from one to the other. To propagate the start scripts and classpath configuration from the Administration Server’s domain directory to the managed server domain directory, complete these steps: 1. Create a copy of the managed server domain directory and the managed server applications directory. 2. Move these directories using the following command both commands : mv ORACLE_BASEadmindomain_namemserverapps ORACLE_BASEadmindomain_ namemserverappsbackup mv ORACLE_BASEadmindomain_namemserverdomain_name ORACLE_ BASEadmindomain_namemserverdomain_namebackup 3. Run the pack command on SOAHOST1 to create a template pack using the following commands: SOAHOST1 cd MW_HOMEwccommonbin SOAHOST1 .pack.sh -managed=true -domain=ORACLE_BASEadmindomain_ nameaserverdomain_name -template=wcdomaintemplateExtWC.jar -template_ name=wc_domain_templateExtWC 4. Run the unpack command on SOAHOST1 to unpack the propagated template to the domain directory of the managed server using the following command: SOAHOST1 .unpack.sh -domain=ORACLE_BASEadmindomain_namemserverdomain_ name -template=wcdomaintemplateExtWC.jar -overwrite_domain=true -app_ dir=ORACLE_BASEadmindomain_namemserverapps 6-8 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter

6.7 Propagating the Domain Configuration to SOAHOST2, WCHOST1, and WCHOST2 Using the unpack Utility