IBM BJ0NJML Integration Guide - Page 284
A simple integration can be implemented using system configuration
![]() |
View all IBM BJ0NJML manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 284 highlights
Integration Module Implementation Properties T Can be used by different applications while using different business objects. T Can be designed to make multiple external invocations. T Can use different communication protocols for different logical management operations and operational management products. T Supports the use of another thread to accommodate a long-running service. T Can implement multiple logical management operations, even when the input configuration and the output configuration is different. T Is less likely to require the use of an external integration module. Implementing an integration module by using an invocation channel has the following advantages: T An invocation channel is useful when you pass complex data to the endpoint. It is also useful when you can define a clear mapping between the fields in the source object and the input the endpoint requires. T Can support hierarchical object structures on input and output transactions. T The integration framework handles the conversion of objects to XML, and XML to objects. T Can be configured to use processing classes, user exits, and XSL mapping for inbound and outbound transactions. T The integration framework performs endpoint invocation. T Can be invoked directly without an association to an integration module or a logical management operation. T A simple integration can be implemented using system configuration that does not require you to restart the application server. Implementing an integration module by using a Java class has the following disadvantages: T Requires you to perform more Java coding. T Does not support an object structure with a parent and child relationship as input or output. Only the parent object can be used as input, and the Java code must find the child relationship. T Conversions of objects to XML and XML to objects must be coded when you use an endpoint handler. T Customization must be built into the design of the integration module. Customization cannot be added later without redeploying the code. T Use of any integration framework components, such as an endpoint handler, must be coded in the Java class. 270 Integration Guide
![](/manual_guide/products/ibm-bj0njml-integration-guide-77e799f/284.png)