IBM BJ0NJML Integration Guide - Page 26

Web Services, External applications, Enterprise Service Bus, and Business Process Execution

Page 26 highlights

Integration Framework for Data Exchange To create an external system, you specify an endpoint, the queues, and the integration control values in the External System application. You can also define the following properties on the external system: T The endpoint that identifies how and where the integration framework exchanges data with the system T The Java Message Service (JMS) queues that the system uses T Whether the external system is ready to begin integration processing Web Services External applications, Enterprise Service Bus, and Business Process Execution Language processes can use Web services to query or send transactions to the integration framework. The integration framework provides three types of services that you can deploy as a Web service: T Object structure service T Enterprise service T Standard service When you deploy Web services, the system generates a schema and Web Services Description Language (WSDL) file that you can access with a URL. Optionally, a Universal Description Discovery and Integration (UDDI) registry can be updated for each deployed service. The integration framework supports the following Web services: T Object structure Web service - Object structure Web services are created from an object structure and do not provide a processing layer which is available to enterprise services. An object structure Web service supports five operations: create, delete, query, sync, and update. T Enterprise Web service - Enterprise Web services are created from an enterprise service and provide exit processing and optional JMS support. The integration framework creates individual enterprise Web services for the operation that is defined in an enterprise service (one operation per service). The operations that are supported in an object structure service are also supported in an enterprise Web service. You can deploy an enterprise Web service to use a JMS queue (asynchronous process) or to bypass the JMS queue (synchronous process). T Standard Web service - Standard Web services are created from methods that are defined in application services. The methods must be annotated in the application service to be available for Web service implementation. The integration framework links input and output parameters of the methods to the Web Services Description Language operation parameters. 12 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
12
Integration Guide
To create an external system, you specify an endpoint, the queues, and the
integration control values in the External System application.
You can also define the following properties on the external system:
The endpoint that identifies how and where the integration framework
exchanges data with the system
The Java Message Service (JMS) queues that the system uses
Whether the external system is ready to begin integration processing
Web Services
External applications, Enterprise Service Bus, and Business Process Execution
Language processes can use Web services to query or send transactions to the
integration framework.
The integration framework provides three types of services that you can deploy
as a Web service:
Object structure service
Enterprise service
Standard service
When you deploy Web services, the system generates a schema and Web Services
Description Language (WSDL) file that you can access with a URL. Optionally, a
Universal Description Discovery and Integration (UDDI) registry can be updated
for each deployed service.
The integration framework supports the following Web services:
Object structure Web service - Object structure Web services are created
from an object structure and do not provide a processing layer which is
available to enterprise services. An object structure Web service supports
five operations: create, delete, query, sync, and update.
Enterprise Web service - Enterprise Web services are created from an
enterprise service and provide exit processing and optional JMS support.
The integration framework creates individual enterprise Web services for
the operation that is defined in an enterprise service (one operation per
service).
The operations that are supported in an object structure service are also
supported in an enterprise Web service. You can deploy an enterprise Web
service to use a JMS queue (asynchronous process) or to bypass the JMS
queue (synchronous process).
Standard Web service - Standard Web services are created from methods
that are defined in application services. The methods must be annotated in
the application service to be available for Web service implementation.
The integration framework links input and output parameters of the
methods to the Web Services Description Language operation parameters.