IBM BJ0NJML Integration Guide - Page 25

Enterprise Services, External Systems

Page 25 highlights

Integration Framework for Data Exchange invocation channel can be configured to ignore the response that is returned from the external service and return no data to the caller of the channel. Enterprise Services The enterprise service is a pipeline for querying system data and importing data into the system from an external system. You can configure enterprise services to process data synchronously (without a queue) or asynchronously (with a queue). Enterprise services can use multiple protocols, such as Web services and HTTP. The enterprise service has data processing layers that transform data and apply business processing rules to data before the it reaches the system objects. When the inbound message reaches the object structure layer, the XML message must be in the format of the object structure schema. The system then can process the message successfully. The enterprise service 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. T User exit - Represents a Java class that you can use to filter, 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. External Systems Any business application that sends data to the system or receives data from the system is an external system. External systems are an integral part of enterprise service and publish channel processing. You use and configure enterprise services and publish channels to exchange data with one or more external systems. Object structure services and invocation channels do not use external systems. You can use the External Systems application to perform the following functions: T Name the external applications or systems that exchange data with the integration framework T Specify the protocol that the integration framework uses to send data to the external system T Identify the publish channels and enterprise services that each system implements T Create interface tables Integration Framework Architecture 11

  • 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
11
invocation channel can be configured to ignore the response that is returned from
the external service and return no data to the caller of the channel.
Enterprise Services
The enterprise service is a pipeline for querying system data and importing data
into the system from an external system. You can configure enterprise services to
process data synchronously (without a queue) or asynchronously (with a queue).
Enterprise services can use multiple protocols, such as Web services and HTTP.
The enterprise service has data processing layers that transform data and apply
business processing rules to data before the it reaches the system objects. When
the inbound message reaches the object structure layer, the XML message must be
in the format of the object structure schema. The system then can process the
message successfully.
The enterprise service can use the following processing layers:
Processing rules – The integration framework provides a rule engine
where you can filter and transform the XML message.
User exit – Represents a Java class that you can use to filter, 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.
External Systems
Any business application that sends data to the system or receives data from the
system is an external system. External systems are an integral part of enterprise
service and publish channel processing. You use and configure enterprise services
and publish channels to exchange data with one or more external systems.
Object structure services and invocation channels do not use external systems.
You can use the External Systems application to perform the following functions:
Name the external applications or systems that exchange data with the
integration framework
Specify the protocol that the integration framework uses to send data to
the external system
Identify the publish channels and enterprise services that each system
implements
Create interface tables