Configuring JMS Persistence Store as Shared Across the Servers Configuring a Default Persistent Store for Transaction Recovery

Configuring High Availability for Oracle Fusion Middleware SOA Suite 5-121 ■ http:WEBHOST1:7777sdpmessaginguserprefs-ui ■ http:WEBHOST2:7777sdpmessaginguserprefs-ui ■ http:WEBHOST1:7777b2bconsole ■ http:WEBHOST2:7777b2bconsole ■ http:WEBHOST1:7777bpmcomposer ONLY FOR BPM Systems ■ http:WEBHOST2:7777bpmcomposer ONLY FOR BPM Systems ■ http:WEBHOST1:7777bpmworkspace ONLY FOR BPM Systems ■ http:WEBHOST2:7777bpmworkspace ONLY FOR BPM Systems Verify these URLs also using your load balancing router address: ■ http:soa.mycompany.com:80wsm-pm ■ http:soa.mycompany.com:80soa-infra ■ http:soa.mycompany.com:80soacomposer ■ http:soa.mycompany.com:80integrationworklistapp ■ http:soa.mycompany.com:80sdpmessaginguserprefs-ui ■ http:soa.mycompany.com:80b2bconsole ■ http:soa.mycompany.com:80bpmcomposer ONLY FOR BPM Systems ■ http:soa.mycompany.com:80bpmworkspace ONLY FOR BPM Systems Follow these instructions to ensure that routing and failover from the HTTP Server to the SOA_CLuster is working correctly: 1. While WLS_SOA2 is running, stop WLS_SOA1 from Oracle WebLogic Server Administration Console. 2. Access the following URLs and verify the appropriate functionality: ■ WEBHOST1:7777wsm-pm ■ WEBHOST1:7777soa-infra ■ WEBHOST1:7777soacomposer ■ WEBHOST1:7777integrationworklistapp ■ WEBHOST1:7777sdpmessaginguserprefs-ui ■ WEBHOST1:7777b2bconsole ■ WEBHOST1:7777bpmcomposer ONLY FOR BPM Systems ■ WEBHOST1:7777bpmworkspace ONLY FOR BPM Systems 3. Start WLS_SOA1 from Oracle WebLogic Server Administration Console. 4. Stop WLS_SOA2. 5. Access the URLs in Step 2 above again and verify the appropriate functionality:

5.13.16 Configuring JMS Persistence Store as Shared Across the Servers

Configure the location for all persistence stores to a directory visible from both nodes. Change all persistent stores to use this shared base directory. From the Fusion Middleware Administration Console, select Services, Persistence Store , Persistence_Store_Name, and then Directory. 5-122 Oracle Fusion Middleware High Availability Guide To enable resume of pending JMS messages, you must specify a location on a persistent storage solution NAS, SAN that is available to other servers in the cluster. Therefore, the directory that you enter must be accessible by both WLS_SOA1 and WLS_SOA2. This directory must exist before the server is restarted.

5.13.17 Configuring a Default Persistent Store for Transaction Recovery

Each server has a transaction log, which stores information about committed transactions coordinated by the server that may not have been completed. WebLogic Server uses the transaction log when recovering from system crashes or network failures. To take advantage of the migration capability of the Transaction Recovery Service for servers in a cluster, you must store the transaction log in a location that is available to a server and its backup servers, preferably on a dual-ported SCSI disk, or a Storage Area Network SAN. To configure the default persistent store:

1. In the Domain Structure tree, expand Environment and select Servers.

2. Select the server you want to modify.

3. Select the Configuration, Services tab.

4. Under Default Store, in the Directory field, enter the path to the folder where you

want the default persistent store to store its data files. To enable migration of the Transaction Recovery Service, you must specify a location on a persistent storage solution that is available to other servers in the cluster. Therefore, the directory that you enter must be accessible by both WLS_ SOA1 and WLS_SOA2. This directory must exist before the server is restarted.

5.13.18 Setting the Front End HTTP Host and Port