IBM BJ0NJML Integration Guide - Page 47

Object Structure Identification

Page 47 highlights

Synchronous Inbound Integration Processing 2 You can use the following code to invoke the Enterprise JavaBean to process the enterprise service message synchronously: public byte{} processExternalDataSync(byte[] extData, String serviceName, String sender) A client can use the Java Naming and Directory Interface name of the Enterprise JavaBean (ejb/maximo/remote/enterpriseservice) to look up the Enterprise JavaBean reference and to invoke the method. The client also needs the following settings: „ Access to the Home and Remote class files „ Access to the J2EE jar files for the server „ The URL of the server that hosts the Enterprise JavaBean „ The context factory class name The client code must instantiate the default IntialContext object. The context derives the provider URL and the context factory from the environment. 3 The integration framework checks that the external system and enterprise service are valid an enabled. If the verification fails, the integration framework notifies the sender of the error and does not process the message. TIP To see if an external system is enabled, go to the System tab in the External Systems application. To see if an enterprise service is valid and enabled, go to the Enterprise Services tab in the External Systems application. Object Structure Identification Summary The integration framework identifies the object structures that are associated with the enterprise service and creates a copy of the message for each object structure. The following activities identify the object structures that are associated with the message: 1 The integration framework retrieves the record from the inbound queue. 2 The integration framework identifies the enterprise service from the retrieved record. 3 The enterprise service definition lists the object structures used by the processing service. 4 The integration framework creates one copy of the enterprise service for every object structure that is associated with the enterprise service. The processing sequence that is associated with the object structure specifies the sequence in which the subsequent object structure processing is to be performed on the enterprise service. Inbound Integration Processing 33

  • 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
33
2
You can use the following code to invoke the Enterprise JavaBean to process
the enterprise service message synchronously:
public byte{} processExternalDataSync(byte[] extData, String
serviceName, String sender)
A client can use the Java Naming and Directory Interface name of the
Enterprise JavaBean (ejb/maximo/remote/enterpriseservice) to look up the
Enterprise JavaBean reference and to invoke the method. The client also needs
the following settings:
Access to the Home and Remote class files
Access to the J2EE jar files for the server
The URL of the server that hosts the Enterprise JavaBean
The context factory class name
The client code must instantiate the default IntialContext object. The context
derives the provider URL and the context factory from the environment.
3
The integration framework checks that the external system and enterprise
service are valid an enabled.
If the verification fails, the integration framework notifies the sender of the
error and does not process the message.
T
IP
To see if an external system is enabled, go to the System tab in the
External Systems application.
To see if an enterprise service is valid and enabled, go to the Enterprise
Services tab in the External Systems application.
Object Structure Identification
Summary
The integration framework identifies the object structures that are associated with
the enterprise service and creates a copy of the message for each object structure.
The following activities identify the object structures that are associated with the
message:
1
The integration framework retrieves the record from the inbound queue.
2
The integration framework identifies the enterprise service from the retrieved
record.
3
The enterprise service definition lists the object structures used by the
processing service.
4
The integration framework creates one copy of the enterprise service for every
object structure that is associated with the enterprise service.
The processing sequence that is associated with the object structure specifies
the sequence in which the subsequent object structure processing is to be
performed on the enterprise service.