Setting the WLS Cluster Address for Direct BindingRMI Invocations to Composites

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

You must set the WLS Cluster address for the SOA_Cluster if you are going to use direct binding to composites. To do this follow these steps: 1. In the WebLogic Server Administration Console, in the Change Center section, click Lock Edit.

2. In the left pane, choose Environment in the Domain Structure window and then

choose Clusters. The Summary of Clusters page appears. 3. Select the SOA_Cluster cluster. 4. In the Configuration General tab, enter the following in the Cluster Address field: SOAHOST1VHN1:8001,SOAHOST2VHN1:8001 Note: The SOA system calculates the callback URL as follows: ■ If a request to SOA originates from an external or internal service is originating a request to SOA, then SOA uses the callback URL specified by the client. ■ If a request to an external or internal service originates from SOA, the callbackURL cannot be populated in the SOA request dynamically because SOA is the originator. Instead, callbackServerURL is used if it is specified as a binding property for the specific reference. You can set this when modeling the composite or at runtime using the MBeans accessed through Oracle Enterprise Manager console. This allows different service calls to have different callback URLs. That is, a callback URL from an external service is different than one to an internal service. However, if the callbackServer URL is not specified as a binding property for that reference, then the system uses the callback URL as specified in soa-infra-config. If the callback URL is not specified in soa-infra-config, then the system uses the callback URL as the front end host specified in WLS. If the front end host is not specified in WLS, the system uses the callback URL as the local host name as provided by WLS MBean APIs. 5-124 Oracle Fusion Middleware High Availability Guide

5. Click Save.

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

the Administration Console. 7. Restart the servers to make the Frontend Host directive in the cluster effective.

5.13.20 Deploying Applications