Extension Methods
The integration process allows extensibility of transaction messages using the following methods:
Custom Extension Points
The integration layer defines an external call from each extension point which accepts the source/target XML as input and gives the source /target XML as output. The integration layer points to an abstract WSDL and can be plugged in by a concrete WSDL by the implementation team.
This helps the implementation to invoke any external web service and transform the respective XML.
Pre-transformation Extension Point
The pre-transformation extension point is invoked before the main transformation is executed. This transformation helps in transforming the source XML coming as an input to the integration process and helps the implementation to invoke external web services and/or transform the input XML.
Post-transformation Extension Point
The post transformation extension point is invoked after the main transformation is executed. It aids in the transformation of the target XML that is input into the target system and helps the implementation to invoke external web services and/or transform the output XML. Refer to
Implementing Extension Points for more instructions and examples.
Custom Transformations
This integration has placeholders for custom elements in the incoming schema and outgoing schema at record level. When querying data into incoming message, the custom elements will be empty. This can be populated through the extension points.
The custom transformations have custom templates to map custom elements and map existing fields that are still unmapped. These mappings are done in the custom transformation files which are invoked by the main transformation. Empty custom transformations are shipped with the product.
Note: If custom elements are added to an outgoing or target schema, the custom elements in the target schema are not passed to the database adapter but they are passed to post collection extension point for implementation to use.
Customizable Scopes
The integration layer provides an option to customize the composite at each extension point. These custom scopes are empty by default.
In order to customize a composite or add code in the custom scopes, login to jdeveloper using 'Customization Developer' role. Only then you can customize the composite.xml file, .bpel file (for Oracle BPEL Process Manager), .xsl map file, and .mplan file (for Oracle Mediator).
Example: BPEL can be customized at scopes which has "customizable='true'".
Refer to the
Customizing SOA Composite Applications section for instructions on how to customize a composite.