Setting the Front End HTTP Host and Port

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

You must set the front end HTTP host and port for Oracle WebLogic Server cluster: 1. In the WebLogic Server Administration Console, in the Change Center section, click Lock Edit.

2. In the left pane, select Environment Clusters.

3. Select the SOA_Cluster.

4. Select HTTP.

5. Set the values for the following: ■ Frontend Host : soa.mycompany.com Frontend HTTP Port : 80 ■ Frontend HTTPS Port : leave it blank

6. Click Save.

7. To activate the changes, click Activate Changes in the Change Center section of

the Administration Console. 8. If you have started the server before, notice this change requires a restart of the managed servers in the cluster. Note: Make sure this address is correct and available the load balancing router is up. An incorrect value, for example, http: in the address, or trailing in the hostname, may prevent the SOA system from being accessible even when using the virtual IPs to access it. Configuring High Availability for Oracle Fusion Middleware SOA Suite 5-123 For SOA high availability installations frontended by Oracle HTTP Server, monitoring should be done on the Oracle HTTP Server ports of the real backend servers. This is the case when a deployment is using all the components deployed to the SOA Managed Server. A simple HTTP monitor that pings the HTTPHTTPS port and expects a pre-determined response in turn should suffice. If only a specific SOA component is being used such as B2B, then a monitor that does a deeper level check all the way to the managed server can be considered to validate the health of the component in use. Please check with your load balancer vendor on setting up the HTTP monitors with your load balancer. If you do not set the front end HTTP host and port, you get the following message when trying to retrieve a document definition XSD from Oracle B2B: An error occured while loading the document definitions. java.lang.IllegalArgumentException: Cluster address must be set when clustering is enabled.

5.13.19 Setting the WLS Cluster Address for Direct BindingRMI Invocations to Composites