Configuring a Shared JMS Persistence Store Configuring a Default Persistence Store for Transaction Recovery

Extending the Domain with SOA Components 6-19

6.15 Configuring a Shared JMS Persistence Store

Configure the location for all of the persistence stores as a directory that is visible from both nodes. See Section 2.3, Shared Storage and Recommended Directory Structure for more information. You must change all of the persistent stores to use this shared base directory as follows: 1. Log in to 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 opens. 3. Select the persistence store represented as a hyperlink from the Name column of the table. The Settings page for the persistence store opens. 4. Open the Configuration tab.

5. Click Lock Edit.

6. In the Directory field, enter the location of a persistent storage solution such as NAS or SAN that is available to other servers in the cluster. Specifying this location enables pending JMS messages to be sent. The location should follow the following directory structure: ORACLE_BASEadmindomain_namesoa_cluster_namejms

7. Click Save and Activate.

8. Restart the servers to make the change in the persistent stores take effect.

6.16 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. Perform these steps to set the location for the default persistence store: 1. Log in to 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 opens. 3. Click the name of the server represented as a hyperlink in the Name column of the table. The settings page for the selected server opens and defaults to the Configuration tab.

4. Open the Services tab within the Configuration tab not the top-level Services tab.

5. Click Lock Edit.

Note: Both WLS_SOA1 and WLS_SOA2 must be able to access this directory. This directory must also exist before you restart the server. Note: Preferably, this location should be a dual-ported SCSI disk or on a Storage Area Network SAN. 6-20 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle ECM Suite 6. In the Default Store section of the page, enter the path to the folder where the default persistent stores will store its data files. The directory structure of the path is as follows: ORACLE_BASE admindomain_namesoa_cluster_nametlogs 7. Save and activate the changes. 8. Restart the WLS_SOA1 and WLS_SOA2 managed servers.

6.17 Enabling High Availability for Oracle File and FTP Adapters