1. Developing SOA Applications with Oracle SOA Suite
  2. Completing Your Application
  3. Deploying SOA Composite Applications
  4. Customizing Your Application for the Target Environment Before Deployment
  5. How to Use Configuration Plans to Customize SOA Composite Applications for the Target Environment
  6. Introduction to Configuration Plans

Introduction to Configuration Plans

This section provides an overview of creating and attaching a configuration plan:

  • You create and edit a configuration plan file in which you can replace the following attributes and properties:

    • Any composite, service component, reference, service, and binding properties in the SOA composite application file (composite.xml)

    • Attribute values for bindings (for example, the location for binding.ws)

    • schemaLocation attribute of an import in a WSDL file

    • location attribute of an include in a WSDL file

    • schemaLocation attribute of an include, import, and redefine in an XSD file

    • Any properties in JCA adapter files

    • Policy references for the following:

      • Service component

      • Service and reference binding components

    Note:

    The configuration plan does not alter XSLT artifacts in the SOA composite application. To modify any XSL, use the XSLT Map Editor. Using a configuration plan is not useful. For example, you cannot change references in XSL using the configuration plan file. Instead, they must be changed manually in the XSLT Map Editor in Oracle JDeveloper when moving to and from test, development, and production environments. This ensures that the XSLT Map Editor opens without any issues in design time. However, leaving the references unchanged does not impact runtime behavior. For more information about transformations and the XSLT Map Editor, see Creating Transformations with the XSLT Map Editor .

  • You attach the configuration plan file to a SOA composite application JAR file or ZIP file (if deploying a SOA bundle) during deployment with one of the following tools:

  • During deployment, the configuration plan file searches the composite.xml, WSDL, and XSD files in the SOA composite application JAR or ZIP file for values that must be replaced to adapt the project to the next target environment.