My Oracle Support Banner

SOA 11g: How to copy remote Web Service Artifacts to the Local Metadata Store / MDS to avoid loading Issues (Doc ID 1515845.1)

Last updated on JULY 26, 2018

Applies to:

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


You are having SOA composite startup issues due to remote web service artifacts, such as a wsdl is not available, causing your local SOA composite to fail to load.
Such an error may be seen in the logs as; 

oracle.fabric.common.FabricDeploymentException: Unable to find a WSDL that has a definition for service {}approvepurchasingdocument_client_ep and port ApprovePurchasingDocument_pt. Please make sure that the port attribute for the binding defined in the composite file is correct by checking the namespace, service name, and port name. In addition, check that the WSDL associated with the binding namespace is imported and currently reachable (check the import nodes at the top of the composite file). Finally, validate the HTTP proxy settings for the server. {rootCauses=[]}
at oracle.integration.platform.blocks.soap.WebServiceEntryBindingComponent.load(
at oracle.integration.platform.blocks.soap.WebServiceEntryBindingComponent.load(
at oracle.integration.platform.blocks.deploy.CompositeDeploymentConnection.deployServices(
at oracle.integration.platform.blocks.deploy.CompositeDeploymentConnection.deploy(



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.