IBM BJ0NJML Integration Guide - Page 41

User Exit Postprocessing, XSL Map

Page 41 highlights

Asynchronous Inbound Integration Processing Condition The processing class completes successfully, with mapping. Output The object structure. User Exit Postprocessing Summary The integration framework applies predefined processing logic in the user exit class to the output from the preceding activity. A user exit processing class typically customizes the object structure after the execution of any predefined enterprise service processing logic. Both the object structure and the enterprise service are available for use. The MAXIMO adapter does not provide predefined user exit classes. TIP To see if any postprocessing customization exists, go to the Enterprise Service tab in the Enterprise Services application. If the Enterprise Service Configuration and Enterprise Service Response Configuration table windows show user exit classes, check these class files for a postprocessing method values. The same processing class contains the user exit preprocessing, user exit postprocessing, and user exit object processing methods. Output The following table shows the possible user exit postprocessing outcomes. XSL Map Summary Condition No user exit class exists. The user exit class skips the record. The user exit class stops the record. The user exit class completes successfully. Output is The unchanged enterprise service object. None; processing ends and the message is deleted from the queue. If there are multiple records in one XML file, the class skips the current record and processes the next record. None; processing ends and the message in error remains in the queue The updated object structure. The integration framework applies any mapping to the enterprise service to convert it to an object structure format. The MAXIMO adapter does not provide predefined XSL maps. TIP To see if an XSL map exists for an enterprise service, go to the Enterprise Service tab in the Enterprise Services application. Look on the Enterprise Service Configuration and Enterprise Service Response Configuration table windows for XSL map values. Inbound Integration Processing 27

  • 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

Asynchronous Inbound Integration Processing
Inbound Integration Processing
27
User Exit Postprocessing
Summary
The integration framework applies predefined processing logic in the user exit
class to the output from the preceding activity.
A user exit processing class typically customizes the object structure after the
execution of any predefined enterprise service processing logic. Both the object
structure and the enterprise service are available for use.
The MAXIMO adapter does not provide predefined user exit classes.
T
IP
To see if any postprocessing customization exists, go to the Enterprise Service tab
in the Enterprise Services application. If the Enterprise Service Configuration and
Enterprise Service Response Configuration table windows show user exit classes,
check these class files for a postprocessing method values.
The same processing class contains the user exit preprocessing, user exit
postprocessing, and user exit object processing methods.
Output
The following table shows the possible user exit postprocessing outcomes.
XSL Map
Summary
The integration framework applies any mapping to the enterprise service to
convert it to an object structure format.
The MAXIMO adapter does not provide predefined XSL maps.
T
IP
To see if an XSL map exists for an enterprise service, go to the Enterprise Service
tab in the Enterprise Services application. Look on the Enterprise Service
Configuration and Enterprise Service Response Configuration table windows for
XSL map values.
The processing class completes
successfully, with mapping.
The object structure.
Condition
Output
Condition
Output is
No user exit class exists.
The unchanged enterprise service
object.
The user exit class skips the record.
None; processing ends and the
message is deleted from the queue.
If there are multiple records in one
XML file, the class skips the current
record and processes the next record.
The user exit class stops the record.
None; processing ends and the
message in error remains in the queue
The user exit class completes
successfully.
The updated object structure.