How is Namespace Location Generated In The Concrete WSDL For An ESB Project

(Doc ID 794642.1)

Last updated on OCTOBER 31, 2010

Applies to:

Oracle ESB - Version: 10.1.3.1 to 10.1.3.4 - Release: AS10gR3 to AS10gR3
Information in this document applies to any platform.
***Checked for relevance on 31-Oct-2010***

Goal

One might encounter situations where the concrete WSDL URL or the SOAP Endpoint URI cannot be invoked externally because of imported namespace location pointing internally to the Application Server, not accessible via proxy or firewall.

For example you expose externally:

http://<virtual_host>:<external_port>/event/<prj_name>/<prj_file>?wsdl

Which points to an internally imported schema/wsdl, not accessible by external third parties:

<import namespace="_your_namespace_"
location="http://<internal_host>:<local_port>/esb/slide/ESB_Projects/<prj_name>/<prj_file>.wsdl"/>

In this case the steps provided in the solution section should do the trick in order to successfully invoke the exposed web-service.

Solution

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