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 scope is invoked before the main transformation is executed. This transformation aids in converting the source XML that comes in 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 scope is invoked after the main transformation is executed. This transformation aids in converting the target XML that comes in as an input to the target queue 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
The custom transformations are used to map data to custom elements in the incoming and outgoing messages. If the incoming and outgoing messages have custom elements defined in the message; these custom elements would refer to a custom XML schema. The main transformation would invoke the custom transformation to map the fields.
Empty custom transformation and custom schemas are delivered with the product. The implementation team can add additional fields in the custom schema and map them using the custom transformations.
Using custom transformations allows the implementation to define and pass additional data from the source system to the target system.
Refer to
Implementing Custom Transformations section for more instructions and examples.
Customizable Scopes
Along with the pre, post extension points this integration provides an option to customize the composite at specific scopes.
To customize a composite, you have to login into JDeveloper in the Customization Developer role.
You can only customize the composite.xml file, .bpel file (for Oracle BPEL Process Manager), .xsl map file, and .mplan file (for Oracle Mediator) when logged into Oracle JDeveloper with the Customization Developer role.
Example: BPEL can be customized at scopes which has “customizable=’true’”.
Refer to
Customizing SOA Composite Applications for instructions on how to customize a composite.