IBM BJ0NJML Integration Guide - Page 283

Java Class and Invocation Channel Usage, Java Integration Modules, Endpoint Handlers

Page 283 highlights

Java Integration Modules Endpoint Handlers Integration Module Implementation Properties and PASSWORD properties that are returned from the credential mapper can also override the endpoint properties. Integration module endpoint properties are overwritten by the endpoint properties that are passed by the process management product. For example, the USERNAME and PASSWORD properties. Java integration modules can communicate directly with an operational management product or external integration module, without the use of an endpoint. Excluding endpoint use eliminates the need for the Java integration module to convert the source objects into the required XML format. When you exclude endpoint use, you can use any communication protocol that is supported by the operational management product. Integration modules are not required to use endpoints. You can configure the integration module to communicate with an operational management product by using integration module properties. The integration framework provides some handlers to support different communication protocols, such as HTTP and Web services. If one of the predefined handlers does not support the operational management product service protocol, implement an external integration module. The external integration module acts as an interface to the operational management product service that can use one of the available handler protocols. An alternative solution is to write a custom handler that supports the operational management product service protocol. Configure a different endpoint for each operational management product to establish individual protocols for each product. The handler that you define for the endpoint must match the handler that you configure for the integration module. Configure an endpoint on invocation channel-based integration modules. The endpoint determines how the integration module communicates with the operational management product. The endpoint name is one of the parameters the integration framework passes as input to the invocation channel. The caller of the integration module can override the endpoint name. Regardless of whether you use an endpoint handler to communicate with the operational management product, the integration module must handle scenarios that require multiple invocations of the operational management product for a single logical management operation execution. Java Class and Invocation Channel Usage You can implement an integration module either as a Java class or as an invocation channel. When you use either approach, your integration module can communicate with an external product, such as an operational management product. Before you start your integration module development, review the advantages and disadvantages to Java class and invocation channel usage. Implementing an integration module by using a Java class has the following advantages: T Requires less registration and configuration of system artifacts. Integration Modules 269

  • 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
Integration Modules
269
and PASSWORD properties that are returned from the credential mapper can also
override the endpoint properties. Integration module endpoint properties are
overwritten by the endpoint properties that are passed by the process
management product. For example, the USERNAME and PASSWORD
properties.
Java Integration Modules
Java integration modules can communicate directly with an operational
management product or external integration module, without the use of an
endpoint. Excluding endpoint use eliminates the need for the Java integration
module to convert the source objects into the required XML format. When you
exclude endpoint use, you can use any communication protocol that is supported
by the operational management product.
Integration modules are not required to use endpoints. You can configure the
integration module to communicate with an operational management product by
using integration module properties.
Endpoint Handlers
The integration framework provides some handlers to support different
communication protocols, such as HTTP and Web services. If one of the
predefined handlers does not support the operational management product
service protocol, implement an external integration module.
The external integration module acts as an interface to the operational
management product service that can use one of the available handler protocols.
An alternative solution is to write a custom handler that supports the operational
management product service protocol.
Configure a different endpoint for each operational management product to
establish individual protocols for each product. The handler that you define for
the endpoint must match the handler that you configure for the integration
module.
Configure an endpoint on invocation channel-based integration modules. The
endpoint determines how the integration module communicates with the
operational management product. The endpoint name is one of the parameters
the integration framework passes as input to the invocation channel.
The caller of the integration module can override the endpoint name.
Regardless of whether you use an endpoint handler to communicate with the
operational management product, the integration module must handle scenarios
that require multiple invocations of the operational management product for a
single logical management operation execution.
Java Class and Invocation Channel Usage
You can implement an integration module either as a Java class or as an
invocation channel. When you use either approach, your integration module can
communicate with an external product, such as an operational management
product. Before you start your integration module development, review the
advantages and disadvantages to Java class and invocation channel usage.
Implementing an integration module by using a Java class has the following
advantages:
Requires less registration and configuration of system artifacts.