Process Webservice Call Does Not Render Endpoints Properly When Load Balancer is Configured as Front End (Doc ID 1058452.1)

Last updated on OCTOBER 24, 2016

Applies to:

Oracle Business Process Management Suite - Version 10.3.1 to 10.3.1 [Release AS10gR3]
Information in this document applies to any platform.
***Checked for relevance on 12-Jan-2012***
***Checked for relevance on 17-July-2013***

Symptoms

When calling a process exposed as webservice, the WSDL endpoint URL location does not reflect the Load Balancer host/port URL.

Environment description:

- WLS 10g - Cluster - 2 Nodes
- Load Balancer acting as Front End host
- BPM Engine deployed and targeted to the Cluster
- BPM process exposed as webservice in both nodes

BPM Process is exposed as webservice and the WSDL definition has been obtained directly from the WLS instance node that exposes the webservice.
WLS configuration defines the host name and port of a Load Balancer Front End.

However, the obtained WSDL location URL refers to the node host name, as follows:

- <wsdl:service name="TestExposedProcessService">
- <wsdl:port name="TestExposedProcess" binding="tns:TestExposedProcessSoapBinding">
<wsdlsoap:address location="http://<node_host_name>:<load_balancer_port>/albpmServices/bpmengine/ws/TestExposedProcessServiceListener" />
</wsdl:port>
</wsdl:service>



Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms