1. Developing SOA Applications with Oracle SOA Suite
  2. Completing Your Application
  3. Deploying SOA Composite Applications
  4. Anatomy of a Composite

Anatomy of a Composite

When you deploy a SOA composite application in Oracle JDeveloper, the composite is packaged in a JAR file (for a single composite application) or a ZIP file (for multiple SOA composite applications). These files can include the following artifacts:

  • Binding components and service components.

  • References to Oracle B2B agreements, Oracle Web Service Manager (OWSM) policies, and human workflow task flows.

  • Shared data such as WSDL and XSD files. All shared data is deployed to an existing SOA Infrastructure partition on the server. This data is deployed under the /apps namespace. When you refer to this artifact in Oracle JDeveloper using a SOA-MDS connection, the URL is prefixed with oramds.