IBM BJ0NJML - Service And Asset Management - Java Class Implementation

Integration Module Implementation Properties
Integration Modules 271
Implementing an integration module by using an invocation channel has the
following disadvantages:
T Requires more registration and configuration of system artifacts, even
when the invocation is simple.
T Multiple applications cannot use the integration module with different
business objects.
T Requires additional knowledge of the integration framework.
T Supports only a single invocation of the configured endpoint. It requires
additional coding to support multiple invocations.
T Requires additional coding to support a long-running service. By default,
the invocation channel waits for a response from the endpoint.
Java Class Implementation
Integration modules can be implemented to use Java class files. Using a Java class
file eliminates the need for integration component registration and configuration.
Additionally, all the underlying integration module implementations are
transparent to the process management product.
Java class integration modules must implement the Java interface
psdi.iface.mic.ServiceInvoker. The service invoker Java interface is included
in the businessobjects.jar file. Include the integration module Java class in the
system class path at run time.
The service invoker Java interface has variations of the following method
signature:
public byte[] invoke(Map String,Object metaData, MboRemote
sourceMbo, MboRemote targetMbo, String endPointName)
throws MXException, RemoteException;
T metaData is a map of the name and value properties that includes:
 The integration module name and version.
 The logical management operation name and name space.
 The operational management product globally unique identifier.
 The endpoint name and any endpoint properties that are being
overwritten.
T sourceMbo is the source object that you defined on the logical management
operation.
T targetMbo is the response object that you defined on the logical
management operation
T endPointName is the name of the endpoint that you use for communication
with the operational management product.
If you configured the integration module to implement multiple logical
management operations, the integration module must determine which logical