Configuring a JMS Persistence Store for BAM UMS Configuring a Default Persistence Store for Transaction Recovery

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

Configure the location for all of the persistence stores as a directory that is visible from both BAMHOST1 and BAMHOST2. This is required in order to enable the resume of transactions when a server is migrated to a different node. By using a shared location for the persistent stores from both nodes, it is guaranteed that no messages are lost should a failover take place. 1. Log into the Oracle WebLogic Server Administration Console.

2. In the Domain Structure window, expand the Services node and then click the

Persistence Stores node. The Summary of Persistence Stores page appears. Configuring High Availability for Oracle Fusion Middleware SOA Suite 5-223 3. Select the a persistent store represented as a hyperlink from the Name column of the table. The Settings page for the persistence store appears. 4. In the Configuration tab, enter the location on a persistent storage solution such as NAS or SAN that is available to other servers in the cluster in the Directory field. Specifying this location enables pending JMS messages to be sent.

5. Click Save.

6. Repeat these steps for all persistent stores. 7. Save and Activate the changes.

5.15.10 Configuring a Default Persistence Store for Transaction Recovery

Each server has a transaction log that stores information about committed transactions that are coordinated by the server that may not have been completed. The WebLogic Server uses this transaction log for recovery from system crashes or network failures. To leverage the migration capability of the Transaction Recovery Service for the servers within a cluster, store the transaction log in a location accessible to a server and its backup servers. To set the location for the default persistence store:

1. Log into the Oracle WebLogic Server Administration Console.

2. In the Domain Structure window, expand the Environment node and then click

the Servers node. The Summary of Servers page appears.

3. Click the name of the server represented as a hyperlink in Name column of the

table. The settings page for the selected server appears and defaults to the Configuration tab.

4. Click the Services tab.

5. In the Default Store section of the page, enter the path to the folder where the

default persistent stores will store its data files.

6. Save and Activate the changes.

5.15.11 Untargeting the BAM Server System from BAMHOST2