IBM BJ0NJML Integration Guide - Page 284

A simple integration can be implemented using system configuration

Page 284 highlights

Integration Module Implementation Properties T Can be used by different applications while using different business objects. T Can be designed to make multiple external invocations. T Can use different communication protocols for different logical management operations and operational management products. T Supports the use of another thread to accommodate a long-running service. T Can implement multiple logical management operations, even when the input configuration and the output configuration is different. T Is less likely to require the use of an external integration module. Implementing an integration module by using an invocation channel has the following advantages: T An invocation channel is useful when you pass complex data to the endpoint. It is also useful when you can define a clear mapping between the fields in the source object and the input the endpoint requires. T Can support hierarchical object structures on input and output transactions. T The integration framework handles the conversion of objects to XML, and XML to objects. T Can be configured to use processing classes, user exits, and XSL mapping for inbound and outbound transactions. T The integration framework performs endpoint invocation. T Can be invoked directly without an association to an integration module or a logical management operation. T A simple integration can be implemented using system configuration that does not require you to restart the application server. Implementing an integration module by using a Java class has the following disadvantages: T Requires you to perform more Java coding. T Does not support an object structure with a parent and child relationship as input or output. Only the parent object can be used as input, and the Java code must find the child relationship. T Conversions of objects to XML and XML to objects must be coded when you use an endpoint handler. T Customization must be built into the design of the integration module. Customization cannot be added later without redeploying the code. T Use of any integration framework components, such as an endpoint handler, must be coded in the Java class. 270 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

Integration Module Implementation Properties
270
Integration Guide
Can be used by different applications while using different business
objects.
Can be designed to make multiple external invocations.
Can use different communication protocols for different logical
management operations and operational management products.
Supports the use of another thread to accommodate a long-running
service.
Can implement multiple logical management operations, even when the
input configuration and the output configuration is different.
Is less likely to require the use of an external integration module.
Implementing an integration module by using an invocation channel has the
following advantages:
An invocation channel is useful when you pass complex data to the
endpoint. It is also useful when you can define a clear mapping between
the fields in the source object and the input the endpoint requires.
Can support hierarchical object structures on input and output
transactions.
The integration framework handles the conversion of objects to XML, and
XML to objects.
Can be configured to use processing classes, user exits, and XSL mapping
for inbound and outbound transactions.
The integration framework performs endpoint invocation.
Can be invoked directly without an association to an integration module
or a logical management operation.
A simple integration can be implemented using system configuration that
does not require you to restart the application server.
Implementing an integration module by using a Java class has the following
disadvantages:
Requires you to perform more Java coding.
Does not support an object structure with a parent and child relationship
as input or output. Only the parent object can be used as input, and the
Java code must find the child relationship.
Conversions of objects to XML and XML to objects must be coded when
you use an endpoint handler.
Customization must be built into the design of the integration module.
Customization cannot be added later without redeploying the code.
Use of any integration framework components, such as an endpoint
handler, must be coded in the Java class.