IBM BJ0NJML Integration Guide - Page 23

Publish Channels, data, and implement business logic. You can use this class as part of an

Page 23 highlights

Integration Framework for Data Exchange The object structure is the building block of the integration framework that lets framework applications to perform the following functions: T Publish and query application data T Add, update, and delete application data T Import and export application data You also can use the object structure as a service to support inbound message processing. You can invoke the object structure service as a Web service, as an Enterprise JavaBean, or by using HTTP. The object structure service supports system data updates, and queries that are started outside of the system. Publish Channels A publish channel is the pipeline for sending data asynchronously from the system to an external system. Events that initiate publish channel processing are object events (insert, update, and delete), application-initiated calls, and data export. The content of a publish channel XML message is based on the associated object structure. When you trigger publish channel processing, the integration framework builds the XML message based on the object structure. The system then moves the message through multiple processing layers before placing the message into a queue and releasing the initiator of the transaction. The publish channel can use the following processing layers: T Processing rules - The integration framework provides a rule engine where you can filter and transform the XML message. You can implement rules in the Publish Channel application. T User exit - Represents a Java class that you can use to filter data, transform data, and implement business logic. You can use this class as part of an installation-customization. T Data processing class - Represents a Java class that you can use to filter, transform data, and implement business logic. Adapters for Oracle and SAP provide processing classes to support integration to these products. T XSL map - Represents an XSLT style sheet that you can use to transform data and perform mapping of the XML message to another format. After the system places the message into the queue, a polling thread (the system cron task) picks up the message and sends it to an external system through a configured endpoint. The endpoint identifies the protocol that the system uses to send data, such as HTTP or Web services. The endpoint also identifies the property values that are specific to that endpoint, such as URL, user name, and password. Integration Framework Architecture 9

  • 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
Integration Framework Architecture
9
The object structure is the building block of the integration framework that lets
framework applications to perform the following functions:
Publish and query application data
Add, update, and delete application data
Import and export application data
You also can use the object structure as a service to support inbound message
processing. You can invoke the object structure service as a Web service, as an
Enterprise JavaBean, or by using HTTP. The object structure service supports
system data updates, and queries that are started outside of the system.
Publish Channels
A publish channel is the pipeline for sending data asynchronously from the
system to an external system. Events that initiate publish channel processing are
object events (insert, update, and delete), application-initiated calls, and data
export.
The content of a publish channel XML message is based on the associated object
structure. When you trigger publish channel processing, the integration
framework builds the XML message based on the object structure. The system
then moves the message through multiple processing layers before placing the
message into a queue and releasing the initiator of the transaction.
The publish channel can use the following processing layers:
Processing rules – The integration framework provides a rule engine
where you can filter and transform the XML message. You can implement
rules in the Publish Channel application.
User exit – Represents a Java class that you can use to filter data, transform
data, and implement business logic. You can use this class as part of an
installation-customization.
Data processing class – Represents a Java class that you can use to filter,
transform data, and implement business logic. Adapters for Oracle and
SAP provide processing classes to support integration to these products.
XSL map – Represents an XSLT style sheet that you can use to transform
data and perform mapping of the XML message to another format.
After the system places the message into the queue, a polling thread (the system
cron task) picks up the message and sends it to an external system through a
configured endpoint. The endpoint identifies the protocol that the system uses to
send data, such as HTTP or Web services. The endpoint also identifies the
property values that are specific to that endpoint, such as URL, user name, and
password.