IBM E02HMLL-I Implementation Guide - Page 18

service, responses

Page 18 highlights

The responses that the collaboration receives from the connectors-referred to as service call responses-can be business objects containing business data (in the case of retrieve requests) or status reports (successful or unsuccessful). Figure 3 shows a simplified view of a business process that is initiated through a publish-and-subscribe interaction and completed through request/response interactions. The example shows a distributed business process that automatically generates an invoice when a customer service representative finishes working on a case. In this example, a hypothetical service billing collaboration uses connectors to exchange business data with three different applications. Service Billing Collaboration 1 Service Case Closed 2 Retrieve Customer Contract Connector Connector 3 Generate Invoice Connector Customer Service Management Application Customer Records Application Accounting Application Figure 3. A publish-and-subscribe, request/response interaction Figure 3 illustrates the following sequence in the business process: 1. A customer service representative completes work on a case. The connector detects the case closure as an event in the customer service management application and retrieves the relevant case data. The connector then publishes the event, making it available to a collaboration that has subscribed to it. These actions comprise a publish-and-subscribe interaction. 2. In order to compute the invoice amount, the collaboration needs the terms of the customer contract. The collaboration sends a service call request to retrieve the necessary data from the connector for the customer records application. The connector responds to the request. These actions comprise a request/response interaction between the collaboration and the customer records application and connector. 3. Using both the case information and the customer contract, the collaboration produces the information needed to generate an invoice. It sends the invoice creation request to the connector for the accounting application, which forwards the request to the application itself, and responds to the collaboration with a notification of success or failure. These actions comprise a request/response interaction between the collaboration and the accounting application and connector. 6 IBM WebSphere Business Integration Server Express and Express Plus: System Implementation 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

The
responses
that
the
collaboration
receives
from
the
connectors—referred
to
as
service
call
responses
—can
be
business
objects
containing
business
data
(in
the
case
of
retrieve
requests)
or
status
reports
(successful
or
unsuccessful).
Figure
3
shows
a
simplified
view
of
a
business
process
that
is
initiated
through
a
publish-and-subscribe
interaction
and
completed
through
request/response
interactions.
The
example
shows
a
distributed
business
process
that
automatically
generates
an
invoice
when
a
customer
service
representative
finishes
working
on
a
case.
In
this
example,
a
hypothetical
service
billing
collaboration
uses
connectors
to
exchange
business
data
with
three
different
applications.
Figure
3
illustrates
the
following
sequence
in
the
business
process:
1.
A
customer
service
representative
completes
work
on
a
case.
The
connector
detects
the
case
closure
as
an
event
in
the
customer
service
management
application
and
retrieves
the
relevant
case
data.
The
connector
then
publishes
the
event,
making
it
available
to
a
collaboration
that
has
subscribed
to
it.
These
actions
comprise
a
publish-and-subscribe
interaction.
2.
In
order
to
compute
the
invoice
amount,
the
collaboration
needs
the
terms
of
the
customer
contract.
The
collaboration
sends
a
service
call
request
to
retrieve
the
necessary
data
from
the
connector
for
the
customer
records
application.
The
connector
responds
to
the
request.
These
actions
comprise
a
request/response
interaction
between
the
collaboration
and
the
customer
records
application
and
connector.
3.
Using
both
the
case
information
and
the
customer
contract,
the
collaboration
produces
the
information
needed
to
generate
an
invoice.
It
sends
the
invoice
creation
request
to
the
connector
for
the
accounting
application,
which
forwards
the
request
to
the
application
itself,
and
responds
to
the
collaboration
with
a
notification
of
success
or
failure.
These
actions
comprise
a
request/response
interaction
between
the
collaboration
and
the
accounting
application
and
connector.
Customer
Service
Management
Application
Connector
Accounting
Application
Connector
Customer
Records
Application
Connector
Service
Billing
Collaboration
Service Case
Closed
Closed
1
Retrieve
Customer Contract
2
Generate
Invoice
3
Figure
3.
A
publish-and-subscribe,
request/response
interaction
6
IBM
WebSphere
Business
Integration
Server
Express
and
Express
Plus:
System
Implementation
Guide