Untargeting the BAM Server System from BAMHOST2 Propagating the Domain Configuration from BAMHOST1 with packunpack Utilities

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

Because the BAM server component in BAM is a singleton, you must untarget it from one of the WLS_BAM servers before you configure it for server migration. Otherwise the system would use two active BAM Servers which could cause different data Note: Preferably, this location should be a dual-ported SCSI disk or on a Storage Area Network SAN. Note: To enable migration of the Transaction Recovery Service, specify a location on a persistent storage solution that is available to other servers in the cluster. This directory must also exist before you restart the server. 5-224 Oracle Fusion Middleware High Availability Guide inconsistencies. This way, BAM Web applications run in both BAMHOST1 and BAMHOST2, but BAM Server is initially active only in BAMHOST1. In this step, you remove the BAM server runtime from WLS_BAM2. To untarget the BAM server artifacts from WLS_BAM2: 1. Log into the Oracle WebLogic Administration Console at http:BAMHOST1VHN0:7001console.

2. In the Domain Structure window, choose Environment and then Servers.

The Summary of Servers page appears.

3. Select WLS_BAM2 in Name column of the table.

The Settings page for WLS_BAM2 appears.

4. Click the Deployments tab.

5. Select the oracle-bam application from the Name column of the table.

The Settings page for the oracle-bam application appears.

6. Click the Targets tab.

7. In the Change Center, click Lock Edit.

8. Change the targets for the modules as described in Table 5–24 . Save and Activate the changes

5.15.12 Propagating the Domain Configuration from BAMHOST1 with packunpack Utilities

Follow these steps to propagate the domain configuration to BAMHOST1 using PackUnpack utilities: 1. Run the following pack command on BAMHOST1 to create a template pack: Note: You must target all of these components as described in Table 5–24 , as incorrect targeting can prevent the BAM system from starting. Table 5–24 oracle-bam Component Target Types Component Type Target oracle-bam11.1.1 Enterprise Application BAM_Cluster oraclebam WEBAPP WLS_BAM1 oracle-bam-adc-ejb.jar EJB WLS_BAM1 oracle-bam-ems-ejb.jar EJB WLS_BAM1 oracle-bam-eventengine-ejb.jar EJB WLS_BAM1 oracle-bam-reportcache-ejb.jar EJB WLS_BAM1 oracle-bam-statuslistener-ejb.jar EJB WLS_BAM1 OracleBAM WEBAPP BAM_Cluster OracleBAMWS WEBAPP BAM_Cluster sdpmessagingclient-ejb.jar EJB WLS_BAM1 Configuring High Availability for Oracle Fusion Middleware SOA Suite 5-225 BAMHOST1 cd ORACLE_COMMON_HOMEcommonbin BAMHOST1 .pack.sh -managed=true domain=ORACLE_BASEproductfmwuser_projectsdomainsbamdomain -template=bamdomaintemplate.jar -template_name=bam_domain_template 2. Run the unpack command on BAMHOST2 to unpack the propagated template: BAMHOST2 cd ORACLE_COMMON_HOMEcommonbin BAMHOST2 .unpack.sh -domain=MW_HOMEuser_projectsdomainsbamdomain -template=bamdomaintemplate.jar

5.15.13 Starting Node Manager on BAMHOST1 and BAMHOST2