IBM BJ0NJML Integration Guide - Page 287

Integration Module Invocation

Page 287 highlights

Integration Module Invocation 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 Integration Modules 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. 273

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330

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.