My Oracle Support Banner

Applications like Oracle IPM fail to retrieve WSDL's to SOA composites via URL's that use different protocol/hostname/port than they are configured to (Doc ID 1290812.1)

Last updated on JANUARY 30, 2022

Applies to:

Oracle WebCenter Content: Imaging - Version and later
Oracle SOA Suite - Version and later
Information in this document applies to any platform.


You have an installation of Oracle Imaging and Process Management J2EE (Oracle IPM) running as part of a clustered deployment where a load balancer is being used to distribute HTTP requests across the WebLogic Servers (WLS) that are managed within the cluster. Consequently, the WLS managed servers do not receive HTTP requests that reference the specific hostname and port where the servers are running but using a common hostname and portthat is further re-distributes the load across the available servers to provide improved throughput and fault tolerance.

In response to the upload a document, the Oracle IPM implementation intends to invoke a DocumentRouting business process, which is implemented as a SOA composite application and runs within the SOA managed servers in the environment (typically named soa_server1).

Within Oracle IPM a configuration screen "Workflow Settings" is used to provide Oracle IPM with the location where the SOA managed server is running. The "Workflow Settings" screen is used to provide configuration details such as the hostname, port and whether or not the port is SSL enabled.

However, when a document is uploaded and the Oracle IPM agent attempts to invoke a Document Routing composite running in the SOA server, the composite invocation fails with errors similar to the following in the WebLogic Server log file that is running Oracle IPM:



  1. The protocol, hostname and port in the WSDL location do not match the location where the SOA server is running nor do they match the information provided to the Oracle IPM configuration.
  2. A variety of different underlying java exceptions other than NoRouteToHostException mat be cited as the underlying cause.


You may have recently made changes to the HTTP protocol section of the soa_server1 configuration but not yet restarted that WebLogic managed server.


To view full details, sign in with your My Oracle Support account.

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

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.