Deployment / Configuration Applied to a SOA Instance is Unexpectedly Applied to Unrelated Instances (Doc ID 1322165.1)

Last updated on MAY 02, 2016

Applies to:

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

Symptoms


You have multiple installations of Oracle Fusion Middleware 11g within a network that you intended to be fully independent of one another. You have implemented composite applications for deployment to the BPEL components within each environment but on deploying a composite to an intended FMw installation either:

  1. the same deployment automatically appears amongst the deployed composites for a SOA managed server that is part of on a different FMw installation that was intended to have been independent and unrelated to the installation where the composite was deployed

    ---OR---

  2. the deployment fails with the following error returned to the Enterprise Manager Control window in the browser or the deployment log window in JDeveloper:
    HTTP error code returned [500]
    Error message from server:
    There was an error deploying the composite on MY_SOA1:
    Operation failed - Member(Id=5, Timestamp=2012-02-03 16:34:38.103, Address=192.168.1.100:8008, MachineId=62925, Location=site:your.company.com,machine:SOA_HOST,process:1052, Role=WeblogicServer):Unable to find a WSDL that has a definition for service {http://your.company.com/my/soa/myservice/v9}SOAMyService and port SOAMyServicePortRequest. 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

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