In a browser, go to http:vip0:7001console. Log in as the administrator. Verify that the WLS_SOA1 and WLS_SOA2 managed servers are listed. Also Verify that the SOA_Cluster cluster is listed. Also verify that the OSB_Cluster Verify that you can access Enter

5-166 Oracle Fusion Middleware High Availability Guide password=password

5.14.6 Starting and Validating the Administration Server in SOAHOST1

This section describes procedures for starting and validating the Administrator Server in SOAHOST1

5.14.6.1 Starting the Administration Server on SOAHOST1

To start the Administration Server on SOAHOST1, run the following commands: SOAHOST1 cd MW_HOMEuser_projectsdomainssoadomainbin SOAHOST1 .startWebLogic.sh

5.14.6.2 Validating the Administration Server

To verify that the Administration Server is properly configured:

1. In a browser, go to http:vip0:7001console.

2. Log in as the administrator.

3. Verify that the WLS_SOA1 and WLS_SOA2 managed servers are listed. Also

verify that the WLS_OSB1 and WLS_OSB2 managed servers are listed.

4. Verify that the SOA_Cluster cluster is listed. Also verify that the OSB_Cluster

cluster is listed.

5. Verify that you can access Enterprise Manager at http:vip0:7001em.

6. Verify that you can access the Oracle Service Bus Console at

http:vip0:7001sbconsole. 5.14.7 Disabling Host Name Verification for the Administration Server and the WLS_ SOAnWLS_OSBn Managed Servers This step is required if you have not set up the appropriate certificates for hostname verification between the Administration Server and 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. Set Hostname Verification to None.

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. Configuring High Availability for Oracle Fusion Middleware SOA Suite 5-167 5. Save and activate the changes. 6. Repeat these steps for the WLS_SOA1, WLS_SOA2, WLS_OSB1, and WLS_OSB2 servers. 7. Restart the Administration Server.

5.14.8 Configuring Oracle Coherence for Deploying Composites