Creating boot.properties for the Administration Server and for WLS_BAM1 on BAMHOST1 Starting the Administration Server on BAMHOST1 Disabling Host Name Verification for the Servers

Configuring High Availability for Oracle Fusion Middleware SOA Suite 5-221 ■ The oracle.rules., oracle.sdp. and oracle.bam. deployments should be targeted only to BAM_Cluster. ■ The oracle.wsm.seedpolicies library should be targeted only to the BAM_ Cluster. 19. In the Target Services to Cluster or Servers screen, ensure the following targets: ■ WSM Startup Class should be targeted only to BAM_Cluster. ■ mds-wsm, mds-wsm-rac0, and mds-wsm-rac1 should be targeted to both BAM_Cluster and AdminServer. ■ OrasDPMDatasource, OrasDPMDatasource-rac0, and OrasDPMDatasource-rac1 should be targeted to the BAM_Cluster. ■ OWSM Startup Class is only targeted to BAM_Cluster DMS Startup is targeted both to BAM_Cluster and AdminServermds-wsm, mds-wsm-rac0, and mds-wsm-rac1 should be targeted to both BAM_Cluster and AdminServer ■ mds-soa, mds-soa-rac0, and mds-soa-rac1 should be targeted to both BAM_ Cluster and AdminServer.

20. In the Configuration Summary screen, click Create.

21. In the Creating Domain screen, click Done.

5.15.6 Creating boot.properties for the Administration Server and for WLS_BAM1 on BAMHOST1

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 on BAMHOST1. For the Administration Server: 1. Create the following directory: mkdir ORACLE_BASEproductfmwuser_ projectsdomainsbamdomainserversAdminServersecurity 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

5.15.7 Starting the Administration Server on BAMHOST1

To start the Administration Server on BAMHOST1 run the following commands: For Linux: BAMHOST1 cd MW_HOMEuser_projectsdomainsbamdomainbin 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. 5-222 Oracle Fusion Middleware High Availability Guide BAMHOST1 .startWebLogic.sh For Windows: startWebLogic.cmd 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_BAM1 and WLS_BAM2 managed servers are listed. 4. Verify that the BAM_Cluster cluster is listed. 5. Verify that you can access Enterprise Manager at http:VIP0:7001em.

5.15.8 Disabling Host Name Verification for the Servers

This step is required if you have not set up the appropriate certificates to authenticate the different nodes with the Administration Server. If you have not configured the server certificates, you 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 them again once the high availability topology configuration is complete. To disable host name verification:

1. In Oracle WebLogic Server Administration Console, select Administration Server,

SSL , and then Advanced.

2. Set Hostname Verification to None.

3. In Oracle WebLogic Server Administration Console, select WLS_BAM1, SSL, and

then Advanced. 4. Set Hostname Verification to None. 5. In Oracle WebLogic Server Administration Console, select WLS_BAM2, SSL, and then Advanced.

6. Set Hostname Verification to None.

7. Restart the Administration Server for the changes to take affect. 8. Save and activate the changes.

5.15.9 Configuring a JMS Persistence Store for BAM UMS