Integration Module Invocation
Integration Modules
273
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.
For more information and detailed instructions on adding or modifying object
structures, see the online help for the Object Structures application.
Integration Module Invocation
Process management products, such Change or Release, use a system action to
invoke an integration module. The action can be associated with an application
escalation or a workflow process, or it might be initiated from a menu item or a
button. The process management product must provide an action class that is
designed to invoke the integration module and process the response the
integration module returns.
To complete an integration module call, the custom action Java class that the
process management product provides must perform the following steps:
1
Identify the logical management operation.
Summary of Contents for BJ0NJML - Service And Asset Management
Page 12: ...xii Integration Guide ...
Page 14: ...xiv Integration Guide ...
Page 16: ......
Page 31: ...Integration Framework for User Interface Integration Integration Framework Architecture 17 ...
Page 32: ...Integration Framework for User Interface Integration 18 Integration Guide ...
Page 60: ...Synchronous Inbound Integration Processing 46 Integration Guide ...
Page 122: ...Configuring External Systems 108 Integration Guide ...
Page 142: ...Non queue Error Management 128 Integration Guide ...
Page 154: ...Integration Components 140 Integration Guide ...
Page 156: ......
Page 172: ...Writing Custom Handlers 158 Integration Guide ...
Page 176: ...Queue Tables 162 Integration Guide ...
Page 190: ...IBM WebSphere MQ 176 Integration Guide ...
Page 212: ...Inbound Message Receipt 198 Integration Guide ...
Page 226: ...Integration Controls 212 Integration Guide ...
Page 252: ...Predefined External System Modifications 238 Integration Guide ...
Page 263: ...Web Service Queries Integration Queries 249 ...
Page 264: ...Web Service Queries 250 Integration Guide ...
Page 272: ...Integration Web Service Invocations 258 Integration Guide ...
Page 276: ...Multilanguage Attributes 262 Integration Guide ...
Page 293: ...Integration Module Invocation Integration Modules 279 ...
Page 294: ...Integration Module Invocation 280 Integration Guide ...
Page 302: ...Associating a Condition with a Signature Option 288 Integration Guide ...
Page 320: ...Work Order Collaboration Switches 306 Integration Guide ...
Page 324: ...310 Integration Guide ...