Configuring Oracle RAC Failover for the WLS_BAM Servers Configuring the BAM Web Applications to Use the BAM Server in BAMHOST1

5-226 Oracle Fusion Middleware High Availability Guide 2. Access http:bamhost1vhn1:9001OracleBAM to verify status of WLS_ BAM1. 3. Start the WLS_BAM2 managed servers: a. Log into the Oracle WebLogic Server Administration Console at http:bamhost1vhn0:7001console.

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

select Servers. The Summary of Servers page appears.

c. Click the Control tab.

d. Select WLS_BAM2 from the Servers column of the table.

e. Click Start.

4. Access HTTP:BAMHOST2:9001OracleBAM to verify status of WLS_BAM2. If the managed servers fails to start with the following message: Listener refused the connection with the following error: ORA-12519, TNS:no appropriate service handler found The Connection descriptor used by the client was db_connect_string Verify that the PROCESSES initialization parameter for the database is set to a high enough value.

5.15.15 Configuring Oracle RAC Failover for the WLS_BAM Servers

Oracle BAM allows customizing the behavior of a BAM server when Oracle RAC is used as the repository for the BAM schemas and a failure occurs in the database. The properties that allow this customization can be adjusted depending on the application and based on the desired expected behavior for each BAM system. The properties are configured in the Fusion Middleware Control Console System MBean Browser, or in the corresponding Oracle BAM-specific XML configuration file. If you want to completely disable Oracle BAMs failover to the database in an Oracle RAC configuration set UseDBFailover to false in the Fusion Middleware Control Console System MBean Browser for your BAM server. The default value of this property is true, therefore, failover is provided. You can also increase or decrease the number of retries in the access to the database when there is a database instance failure for BAM to retry the in flight transactions. To adjust the number of retries change the MaxDBNodeFailoverRetries in the Fusion Middleware Control Console System MBean Browser. The default value for MaxDBNodeFailoverRetries is 5 times. See the Oracle Fusion Middleware Administrator’s Guide for Oracle SOA Suite for more details on the properties that can be configured for Oracle BAM.

5.15.16 Configuring the BAM Web Applications to Use the BAM Server in BAMHOST1

To configure the OracleBamWeb WLS_BAM1 and OracleBamWeb WLS_BAM2 applications to use the BAM server in BAMHOST1: 1. Access Oracle Enterprise Manager Fusion Middleware Control at the following URL http:bamhost1vhn0:7001em

2. Expand BAM in the navigation tree.

3. Right-click OracleBamWebWLS_BAM1.

Configuring High Availability for Oracle Fusion Middleware SOA Suite 5-227 ■ Select BAM Web Properties from the context menu. The BAM Web Properties page appears. ■ Define the following properties: – Enter WEBHOST:7777 for the application URL. – Enter BAMHOST1VHN1 for the server name. ■ Modify the listening port for the BAM server using the Mbean browser. To do this, follow these steps in the order shown: – Log onto the Oracle Enterprise Manager Fusion Middleware Control. – Expand the domain name in the left navigation tree. – Expand the BAM item in the left navigation tree. – On the BAM drop down menu at the top right, select Mbean Browser. – Navigate to the oracle.bam.web - Server - Application - Config - BAMWebConfig on the right. – In the ServerPort field, replace the DEFAULT value with 9001.

4. Select OracleBamWebWLS_BAM2 from the navigation tree and repeat these

steps. 5.15.17 Configuring Oracle HTTP Servers for the Administration Server and the WLS_ BAMn Managed Servers To enable Oracle HTTP Server to route to the BAM_Cluster, which contains the WLS_ BAMn managed servers, you must set the WebLogicCluster parameter to the list of nodes in the cluster: 1. On WEBHOST1 and WEBHOST2, add the following lines to the ORACLE_ BASEadmininstance_nameconfigOHScomponent_namemod_wl_ ohs.conf file: WSM-PM Location wsm-pm SetHandler weblogic-handler WebLogicCluster bamhost1vhn1:9001,bamhost2:9001 Location UMS Location sdpmessaging SetHandler weblogic-handler WebLogicCluster SOAHOST1VHN1:8001,SOAHOST2VHN1:8001 Location UMS WS Location ucsmessagingwebservice SetHandler weblogic-handler WebLogicCluster SOAHOST1VHN1:8001,SOAHOST2VHN1:8001 Location BAM Web app Location OracleBAM SetHandler weblogic-handler WebLogicCluster bamhost1vhn1:9001,bamhost2:9001 Location 5-228 Oracle Fusion Middleware High Availability Guide BAM Web Services Location OracleBAMWS SetHandler weblogic-handler WebLogicCluster bamhost1vhn1:9001,bamhost2:9001 Location Make sure the httpd.conf file located in the same directory as the mod_wl_ ohs.conf file contains the following lines pointing to your load balancing router addresses: NameVirtualHost :7777 VirtualHost :7777 ServerName https:bam.mycompany.com:443 ServerAdmin youyour.address RewriteEngine On RewriteOptions inherit VirtualHost NameVirtualHost :7777 VirtualHost :7777 ServerName admin.mycompany.com:80 ServerAdmin youyour.address RewriteEngine On RewriteOptions inherit VirtualHost 2. Restart Oracle HTTP Server on WEBHOST1 and WEBHOST2. WEBHOST1 ORACLE_BASEadmininstance_namebinopmnctl restartproc ias-component=ohs1 WEBHOST2 ORACLE_BASEadmininstance_namebinopmnctl restartproc ias-component=ohs2

5.15.18 Validating Access through Oracle HTTP Server