Creating boot.properties for the Administration Server and for Managed Servers on APPHOST1 Install WebLogic Server and Oracle WebCenter on APPHOST2 Propagating the Domain Configuration to APPHOST2 with packunpack Utilities

6-58 Oracle Fusion Middleware High Availability Guide Figure 6–7 Assign Servers to Machines Screen ■ APPHOST1: WC_Spaces1, WC_Portlet1, WC_Collaboration1, WC_Utilities1 ■ APPHOST2: WC_Spaces2, WC_Portlet2, WC_Collaboration2, WC_Utilities2 Click Next.

18. In the Configuration Summary screen, click Create.

19. In the Creating Domain screen, click Done.

6.4.6 Creating boot.properties for the Administration Server and for Managed Servers on APPHOST1

This is an optional step for enabling the Administration Server to start without prompting you for the administrator username and password. Create a boot.properties file for the Administration Server and for the managed servers on APPHOST1. For the Administration Server: 1. Create the following directory: APPHOST1 mkdir -p MW_HOMEuser_ projectsdomainswcdomainserversAdminServersecurity 2. Use a text editor to create a file called boot.properties in the directory created in the previous step, and enter the following lines in the file: username=adminuser password=password Configuring High Availability for Oracle ADF and WebCenter Applications 6-59 For the WC_Spaces1 managed server: 1. Create the following directories: APPHOST1 mkdir ORACLE_BASEproductfmwuser_ projectsdomainswcdomainserversWC_Spaces1security 2. Use a text editor to create a file called boot.properties in the security directory created in the previous step, and enter the following lines in the file: username=adminuser password=password 3. Repeat Steps 2 and 3 for the WC_Portlet1 and WC_Collaboration1 Managed Servers on APPHOST1.

6.4.7 Starting the System in APPHOST1

This section describes procedures for starting the system in APPHOST1

6.4.7.1 Starting the Administration Server on APPHOST1

To Start the Administration Server on APPHOST1 run the following commands: APPHOST1 cd ORACLE_BASEproductfmwuser_projectsdomainswcdomainbin APPHOST1 .startWebLogic.sh

6.4.7.2 Validating the Administration Server

To verify that the Administration Server is properly configured: 1. In a browser, go to http:VIP1:7001console. 2. Log in as the administrator. 3. Verify that all the managed servers WC_Spaces1, WC_Spaces2, and so on are listed. 4. Verify that all Clusters are listed. 5. Verify that you can access Enterprise Manager at http:VIP1:7001em. Note: When you start the Administration Server, the username and password entries in the file are encrypted. For security reasons, minimize the time the entries in the file are left unencrypted. After you edit the file, start the server as soon as possible for the entries to be encrypted. Note: When you start the Administration Server, the username and password entries in the file are encrypted. For security reasons, minimize the time the entries in the file are left unencrypted. After you edit the file, start the server as soon as possible in order for the entries to be encrypted. 6-60 Oracle Fusion Middleware High Availability Guide 6.4.7.3 Disabling Host Name Verification for the Administration Server and the Managed Servers for APPHOST1 and APPHOST2 This step is required if you have not set up SSL communication between the Administration Server and the Node Manager. If SSL is not set up, you receive an error message unless you disable host name verification. You can re-enable host name verification when you have set up SSL communication between the Administration Server and the Node Manager. To disable host name verification:

1. In Oracle WebLogic Server Administration Console, select Servers, and then

AdminServer .

2. Select SSL, and then Advanced.

3. In the Change Center, click Lock Edit.

4. When prompted, save the changes and activate them.

5. Set Hostname Verification to None.

6. Select WC_Spaces1, SSL, and then Advanced.

7. Set Hostname Verification to None.

8. Repeat Steps 6 and 7 for all the Managed Servers. 9. Restart the AdminServers and all the Managed Servers.

6.4.7.4 Starting Node Manager on APPHOST1

Perform these steps to start Node Manager on APPHOST1: 1. Run the setNMProps.sh script, which is located in the ORACLE_COMMON_ HOMEcommonbin directory, to set the StartScriptEnabled property to true before starting Node Manager: APPHOST1 cd ORACLE_COMMON_HOMEcommonbin APPHOST1 .setNMProps.sh

2. Start Node Manager:

APPHOST1 cd WL_HOMEserverbin APPHOST1 .startNodeManager.sh

6.4.8 Install WebLogic Server and Oracle WebCenter on APPHOST2

Repeat the procedures for installing WebLogic Server and Oracle WebCenter for APPHOST2, start with Section 6.4.3.1, Installing Oracle WebLogic Server . The directory paths for binary files and domains used when installing new nodes must be exactly the same as those used for first node. If these paths and domains are not exactly the same as those used for the first node, failover is does not occur. Note: You must use the StartScriptEnabled property to avoid class loading failures and other problems. Configuring High Availability for Oracle ADF and WebCenter Applications 6-61

6.4.9 Propagating the Domain Configuration to APPHOST2 with packunpack Utilities

Follow these steps to propagate the domain configuration to APPHOST2 using PackUnpack utilities:

1. Run the following pack command on APPHOST1 to create a template pack:

APPHOST1 cd WL_HOMEcommonbin APPHOST1 .pack.sh -managed=true -domain=ORACLE_BASEproductfmwuser_ projectsdomainswcdomain -template=wcdomaintemplate.jar -template_name=wc_domain_template

2. Run the following command on APPHOST1 to copy the template file created in

the previous step to APPHOST2 using, in this example, scp: APPHOST1 scp wcdomaintemplate.jar APPHOST2:WL_HOMEcommonbin

3. Run the unpack command on APPHOST2 to unpack the propagated template:

APPHOST2 cd WL_HOMEcommonbin APPHOST2 .unpack.sh -domain=ORACLE_BASEproductfmwuser_projectsdomainswcdomain -template=wcdomaintemplate.jar

6.4.10 Starting Node Manager on APPHOST2