Deployment plan file to replace the JCA Adapters properties – Oracle SOA Suite 11g
This post will explain how to use deployment plan file to replace the JCA Adapters properties in Oracle SOA Suite 11g and Oracle SOA Suite 12c.
We can create and edit a
configuration plan file in which we 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
The configuration plan does not
alter XSLT artifacts in the SOA composite application. If you want to modify
any XSL, do so in the XSLT Mapper. 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 Mapper in Oracle
JDeveloper when moving to and from test, development, and production
environments.
The same steps will work in Oracle SOA Suite 12c but the screens will be little different.
The same steps will work in Oracle SOA Suite 12c but the screens will be little different.
Generate the Plan file:
The plan file can be generated
through JDeveloper or through ANT script.
Generating Plan file through JDeveloper:
Right Click on Composite.xml and
click on generate config Plan.