IBM BJ0NJML Integration Guide - Page 286
Invocation Channel Implementation, Java Methods for Inbound and Outbound Processing, primary object - jobs
![]() |
View all IBM BJ0NJML manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 286 highlights
Integration Module Implementation Properties management operation is being called. At run time, the integration module retrieves the LMONAME and LMONAMESPACE properties from the metaData input map: import psdi.iface.omp.IMConstants; . . . String lmoName = metaData.get(IMConstants.LMONAME); String lmoNamespace = metaData.get(IMConstants.LMONAMESPACE); The integration module can retrieve logical management operation data from the source object. The following example code retrieves logical management operation values from the source object: String guid = sourceMbo.getString("GUID"); int packID = sourceMbo.getInt("PACKID"); boolean hasSubs = sourceMbo.getBoolean("HASSUBS"); In the example, the logical management operation has an alphanumeric input attribute called globally unique identifier, an Integer attribute called PACKID, and a Boolean attribute called HASSUBS. Service invoker methods can take a MboSetRemote set of values as a source input, instead of a single MboRemote value. In some cases, the integration module passes all of the objects in the object set to the operational management product. In other cases, the integration module passes only the first object in the set. There are no set rules that apply to the integration module behavior, but you must clearly define the expected behavior in the logical management operation description. Invocation Channel Implementation Invocation channels use object structures in its implementations to expand the message data content. The object structure uses the object that the process management product passes as the source object to build an entire record that can consist of multiple related objects. For example, if the process management product passes a work order as the primary object, the integration framework can build a transaction that consists of the work order and its related objects, such as planned material or job plans. The objects that are identified in the object structures are used in the XML message creation. Java Methods for Inbound and Outbound Processing Invocation channels support optional inbound and outbound processing exits. Processing exits provide the opportunity for integration modules to implement additional logic, such as retrieving the configuration item source token. The inbound and outbound processing classes must be instances of the Java class psdi.iface.migexits.ExternalExit. In the outbound direction, the integration framework calls the following method: public StructureData setDataOut(StructureData irData) In the inbound direction, the integration framework calls the following method: public StructureData setDataIn(StructureData erData) 272 Integration Guide
![](/manual_guide/products/ibm-bj0njml-integration-guide-77e799f/286.png)