IBM BJ0NJML Integration Guide - Page 22

Integration Framework for Data Exchange, Object Structures

Page 22 highlights

Integration Framework for Data Exchange Integration Framework for UI Integration Component Actions Description You use actions to implement an automated or semi-automated invocation of integration modules and operational management products by a process management product. You can initiate actions from user interface applications, escalations, and workflows. The integration framework provides a mechanism for you to navigate from a system application user interface to an external application user interface. You can define the context to facilitate the navigation into the external application interface. The integration framework supports URL substitutions of any values of any system business object. For example, you can configure the system to display a specific part number in an external application. You can use operational management product-specific features when you launch to an operational management product application user interface. Features include retrieving the registered host name of the operational management product and a configured item source token for the operational management product. Through the Launch in Context application, you can navigate to any external application other than the operational management product. You also can navigate to a system user interface from an external application (Land in Context). Integration Framework for Data Exchange The integration framework consists of individual data exchange components and features. Object Structures An object structure is the common data layer that the integration framework uses for all outbound and inbound application data processing. An object structure consists of one or more business objects that make up the content of an XML message. You can use the message content of a single object structure to support inbound and outbound messages. When you define multiple objects in the object structure, the objects must have a reference to a valid parent-child relationship within the system. The object structure has a Java definition class that you can code to perform logic such as filtering for outbound messages. For inbound messages, you can use an object structure Java processing class to invoke specific business object logic that is beyond the normal integration framework insert, update, and delete processing. 8 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 Framework for Data Exchange
8
Integration Guide
Integration Framework
for UI Integration
The integration framework provides a mechanism for you to navigate from a
system application user interface to an external application user interface. You can
define the context to facilitate the navigation into the external application
interface. The integration framework supports URL substitutions of any values of
any system business object. For example, you can configure the system to display
a specific part number in an external application.
You can use operational management product-specific features when you launch
to an operational management product application user interface. Features
include retrieving the registered host name of the operational management
product and a configured item source token for the operational management
product.
Through the Launch in Context application, you can navigate to any external
application other than the operational management product. You also can
navigate to a system user interface from an external application (Land in
Context).
Integration Framework for Data Exchange
The integration framework consists of individual data exchange components and
features.
Object Structures
An object structure is the common data layer that the integration framework uses
for all outbound and inbound application data processing. An object structure
consists of one or more business objects that make up the content of an XML
message. You can use the message content of a single object structure to support
inbound and outbound messages.
When you define multiple objects in the object structure, the objects must have a
reference to a valid parent-child relationship within the system.
The object structure has a Java definition class that you can code to perform logic
such as filtering for outbound messages. For inbound messages, you can use an
object structure Java processing class to invoke specific business object logic that
is beyond the normal integration framework insert, update, and delete
processing.
Actions
You use actions to implement an
automated or semi-automated
invocation of integration modules
and operational management
products by a process management
product. You can initiate actions from
user interface applications,
escalations, and workflows.
Component
Description