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.
The objects that are identified in the object structures are used in the XML message creation. When you use an invocation channel, the data must conform to the XML schemas specified for the associated object structures, and you must define an endpoint for the invocation channel.
Invocation channels support optional inbound and outbound processing exit classes. The integration framework uses processing exit classes to implement additional logic. The inbound and outbound processing exit classes must be instances of the Java™ class psdi.iface.migexits.ExternalExit
.
For outbound transactions, the integration framework calls the following method:
public StructureData setDataOut(StructureData irData)
For inbound transactions, the integration framework calls the following method:
public StructureData setDataIn(StructureData erData)
When you override these methods, you can perform additional integration module processing. The properties that are passed to the invocation channel are available to the processing classes.
The following outbound processing class code shows you how to retrieve the operational management product globally unique identifier when you run an invocation channel:
import psdi.server.MXServer;
import psdi.iface.omp.IMConstants;
import psdi.iface.omp.OmpServiceRemote;
import psdi.iface.mic.*;
import psdi.iface.migexits.*;
.
.
.
public class OutboundCIExit extends ExternalExit implements IMConstants
{
public StructureData setDataOut(StructureData irData)
throws MXException, RemoteException
{
IntegrationContext cntx = IntegrationContext.getCurrentContext();
String ompGUID = cntx.getStringProperty(OMPGUID);
.
.
.
}
}
Additional features of the invocation channel include user exit Java classes and an XSL mapping layer. You can configure the XSL mapping layer to do XML mapping or data transformation.
If the object structure that you need for your integration module invocation does not exist, you can create an object structure in the Object Structures application. You also can use XML with the MXINTOBJECT object structure to create object structures as part of the installation process.