IBM BJ0NJML Integration Guide - Page 53

User Exit Object Processing, Object Processing, Enterprise Service Response Processing

Page 53 highlights

Synchronous Inbound Integration Processing Condition The object structure class stops the record. The object structure processing completes successfully. Output None; processing ends and an error is sent to the caller. The predefined enterprise services do not implement the stop action; object structure processing exceptions stop processing. The updated object. User Exit Object Processing Summary The integration framework applies any final custom logic to the object. TIP To see if object processing customization exists, go to the Enterprise Service tab in the Enterprise Services application. If the Enterprise Service Configuration table window shows a user exit class, check that class file for an object processing method. The same processing class contains the enterprise service user exit preprocessing, enterprise service user exit postprocessing, and user exit object processing methods. Output The following table shows the possible user exit object processing outcomes. Condition No user exit processing. The user exit class skips the record. Output The object, unchanged. None; processing ends. The user exit class stops the record. The user exit class completes successfully. If there are multiple records in one XML file, the class skips the current record and processes the next record. None; processing ends and an error is sent to the caller. The object, possibly updated. Object Processing Summary The objects are passed to the system and standard system processing is applied. The integration framework treats a single message from the inbound queue as a single system transaction. All objects that a message creates must be successfully processed before the database commit transaction can occur. An error in any one of the multiple object structures causes the entire transaction to fail. Enterprise Service Response Processing A synchronous enterprise service provides a response to the invoking application. The service indicates whether the message was processed successfully. For the query and create operations, XML content is returned to the invoking application. Inbound Integration Processing 39

  • 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

Synchronous Inbound Integration Processing
Inbound Integration Processing
39
User Exit Object Processing
Summary
The integration framework applies any final custom logic to the object.
T
IP
To see if object processing customization exists, go to the Enterprise Service tab in
the Enterprise Services application. If the Enterprise Service Configuration table
window shows a user exit class, check that class file for an object processing
method.
The same processing class contains the enterprise service user exit preprocessing,
enterprise service user exit postprocessing, and user exit object processing
methods.
Output
The following table shows the possible user exit object processing outcomes.
Object Processing
Summary
The objects are passed to the system and standard system processing is applied.
The integration framework treats a single message from the inbound queue as a
single system transaction. All objects that a message creates must be successfully
processed before the database commit transaction can occur. An error in any one
of the multiple object structures causes the entire transaction to fail.
Enterprise Service Response Processing
A synchronous enterprise service provides a response to the invoking application.
The service indicates whether the message was processed successfully. For the
query and create operations, XML content is returned to the invoking application.
The object structure class stops the
record.
None; processing ends and an error is
sent to the caller.
The predefined enterprise services do
not implement the stop action; object
structure processing exceptions stop
processing.
The object structure processing
completes successfully.
The updated object.
Condition
Output
Condition
Output
No user exit processing.
The object, unchanged.
The user exit class skips the record.
None; processing ends.
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 an error is
sent to the caller.
The user exit class completes
successfully.
The object, possibly updated.