Validating Access Through Setting the Frontend HTTP Host and Port

Extending the Domain for SOA Components 5-17

5.16 Validating Access Through

Oracle HTTP Server Verify that the server status is reported as Running in the Admin Console. If the server is shown as Starting or Resuming, wait for the server status to change to Started. If another status is reported such as Admin or Failed, check the server output log files for errors. See Section 11.6, Troubleshooting for possible causes. Verify that you can access these URLs, where ’webhostN’ specifies the name of each Oracle HTTP Server host for example, WEBHOST1, WEBHOST2: ■ http:webhostN:7777soa-infra ■ http:webhostN:7777integrationworklistapp ■ http:webhostN:7777b2bconsole ■ http:webhostN:7777sdpmessaginguserprefs-ui ■ http:webhostN:7777soacomposer Validate SOA_Cluster through both Oracle HTTP Server instances. Refer to load balancer configuration to access the system through the load balancer.

5.17 Setting the Frontend HTTP Host and Port

You must set the frontend HTTP host and port for the Oracle WebLogic Server cluster: 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. Select HTTP. 5. Set the values for the following: ■ Frontend Host : wc.mycompany.com ■ Frontend HTTPS Port : 443 ■ Frontend HTTP Port : 80

6. Click Save.

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

the Administration Console. 8. Restart the servers to make the Frontend Host directive in the cluster effective. 5-18 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter Callback URL The SOA system calculates the callback URL as follows: ■ If a request to SOA originates from an external or internal service, then SOA uses the callback URL specified by the client. ■ If a request to an external or internal asynchronous service originates from SOA, the callback URL is determined using the following method, in decreasing order of preference: 1. Use callbackServerURL specified as a binding property for the specific reference. You can set this when modeling the composite or at runtime using the MBeans. This allows different service calls to have different callback URLs. That is, a callback URL from an external service can be set to be different than one to an internal service In the context of the Enterprise Deployment architecture, typically this will be wc.mycompany.com 443https for external services and wcinternal.mycompany.com 7777http for internal services. At runtime, this property is set using the System MBean Browser, through the corresponding binding mbean. To add a specific URL, add a callbackServerURL property to its Properties attribute, then invoke the save operation. 2. Use the callback URL as specified in soa-infra-config.xml. In this case, only one address can be specified. When a mix of both external and internal services can be invoked, this should be set to wc.mycompany.com 443https in the Enterprise Deployment architecture. When only internal services are to be invoked, this can be set to wcinternal.mycompany.com 7777http. Note: When HTTPS is enabled in the load balancer and the load balancer terminates SSL the SOA servers receive only HTTP requests, not HTTPS, as suggested in this guide, the endpoint protocol for webservices is set to http. Since the load balancer redirects HTTP to HTTPS this causes the following exception when testing webservices fucntionality in Oracle Enterprise Manger Fusion Middleware Control: javax.xml.soap.SOAPException: oracle.j2ee.ws.saaj.ContentTypeException To resolve this exception, update the URL endpoint: In the Enterprise Manager Test Page, check Edit Endpoint URL. Within the endpoint URL page: ■ Change http to https. ■ Change the default port number say 80 to SSL port say 443. Note: If you do not set the frontend 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. Extending the Domain for SOA Components 5-19 3. Use the callback URL as the frontend host specified in WLS for the SOA_ Cluster. In this case, too, only one address can be specified and the recommendation is same as the one for soa-infra-config.xml. 4. Use the local host name as provided by WLS MBean APIs. This is not recommended in HA environments such as Enterprise Deployment.

5.18 Setting the WLS Cluster address for Direct BindingRMI invocations to composites