IBM BJ0NJML Integration Guide - Page 72

Request XSL Map, Send the Invocation Channel Data to the Endpoint, No preprocessing method exists.

Page 72 highlights

Synchronous Outbound Integration Processing Output The following table shows the possible request user exit preprocessing outcomes. Condition No preprocessing method exists. The preprocessing method skips the record. The preprocessing method stops the record. The preprocessing method completes successfully. Output The existing object structure or invocation channel, unchanged. None; processing ends. None; processing ends, and an exception is returned to the caller of the invocation channel. The existing invocation channel, possibly updated. Request XSL Map Summary The integration framework applies any custom request mapping to the invocation channel. You can use XSL mapping to map user-defined invocation channels or customize the mapping done by predefined invocation channel processing classes. Both the object structure and invocation channel are available. TIP To see if request XSL mapping exists for an invocation channel, go to the Invocation Channel tab in the Invocation Channel application. Look on the Service Request Configuration table window for a request XSL map. Output The output of this activity must be an XML message in invocation channel format. The notation used by the integration framework to represent numbers greater than seven digits is controlled by the mxe.int.usesscientific variable. By default, numbers greater than seven digits use a scientific notation. Send the Invocation Channel Data to the Endpoint Summary The integration framework writes the invocation channel data to the location that you specify on the endpoint. The endpoint determines the data transport mechanism of an invocation channel. 1 The integration framework writes the XML message to the endpoint location. TIP To see what location, and the transport mechanism the endpoint uses, go to the End Point tab in the End Points application. To see which handler an endpoint uses, select Add/Modify End Points from the Select Action menu in the End Points application. 2 The handler processing class invokes an external application or system. 58 Integration Guide

  • 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 Outbound Integration Processing
58
Integration Guide
Output
The following table shows the possible request user exit preprocessing outcomes.
Request XSL Map
Summary
The integration framework applies any custom request mapping to the invocation
channel.
You can use XSL mapping to map user-defined invocation channels or customize
the mapping done by predefined invocation channel processing classes. Both the
object structure and invocation channel are available.
T
IP
To see if request XSL mapping exists for an invocation channel, go to the
Invocation Channel tab in the Invocation Channel application. Look on the
Service Request Configuration table window for a request XSL map.
Output
The output of this activity must be an XML message in invocation channel format.
The notation used by the integration framework to represent numbers greater
than seven digits is controlled by the
mxe.int.usesscientific
variable. By
default, numbers greater than seven digits use a scientific notation.
Send the Invocation Channel Data to the Endpoint
Summary
The integration framework writes the invocation channel data to the location that
you specify on the endpoint. The endpoint determines the data transport
mechanism of an invocation channel.
1
The integration framework writes the XML message to the endpoint location.
T
IP
To see what location, and the transport mechanism the endpoint uses,
go to the End Point tab in the End Points application.
To see which handler an endpoint uses, select Add/Modify End Points
from the Select Action menu in the End Points application.
2
The handler processing class invokes an external application or system.
Condition
Output
No preprocessing method exists.
The existing object structure or
invocation channel, unchanged.
The preprocessing method skips the
record.
None; processing ends.
The preprocessing method stops the
record.
None; processing ends, and an
exception is returned to the caller of
the invocation channel.
The preprocessing method completes
successfully.
The existing invocation channel,
possibly updated.