IBM E02HMLL-I Implementation Guide - Page 16

InterChange, Server, Express, implementation

Page 16 highlights

performs its processes on the business object and responds, and that response is transformed back into the specific data format that was used at the beginning of the process. To accept calls from external processes and send the calls as business objects to a collaboration, the Server Access Interface requires the following: v A web server that uses a servlet or other process to send data to the Server Access Interface. The data must be in a MIME type for which data handlers have been configured in the InterChange Server Express. The servlet uses the Server Access Interface to call a data handler that converts the data into a business object format, and then uses the Server Access Interface to send the business object as a call into a collaboration. v A collaboration that has been configured to handle requests that are received as calls through the Server Access Interface. In the example shown in Figure 2,, at a site that has not implemented either the IBM WebSphere Business Integration Server Express system or a connector, a customer representative uses a web browser to obtain the status of a purchase order over the Internet from an ERP application (SAP in the example) that resides at a site that has implemented the IBM WebSphere Business Integration Server Express system. To enable this, the IBM WebSphere Business Integration Server Express uses the Server Access Interface, together with a collaboration (hypothetical in this example) for purchase-order business logic, an SAP connector, and definitions of business objects that represent purchase-order status information. Collaboration Server Access Interface SAP Connector START Servlet Web Server Browser SAP Application POstatus data POstatus Business Object Figure 2. Execution of a call through the Server Access Interface Data flow in an InterChange Server Express implementation A data flow is initiated by either of two types of interactions: publish-andsubscribe interactions or service call interactions. Both types of interaction supply triggers that start the execution of a collaboration's business processes. The collaboration then uses a third type of interaction-request/response -to complete the exchange of data with the intended destination. 4 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

performs
its
processes
on
the
business
object
and
responds,
and
that
response
is
transformed
back
into
the
specific
data
format
that
was
used
at
the
beginning
of
the
process.
To
accept
calls
from
external
processes
and
send
the
calls
as
business
objects
to
a
collaboration,
the
Server
Access
Interface
requires
the
following:
v
A
web
server
that
uses
a
servlet
or
other
process
to
send
data
to
the
Server
Access
Interface.
The
data
must
be
in
a
MIME
type
for
which
data
handlers
have
been
configured
in
the
InterChange
Server
Express.
The
servlet
uses
the
Server
Access
Interface
to
call
a
data
handler
that
converts
the
data
into
a
business
object
format,
and
then
uses
the
Server
Access
Interface
to
send
the
business
object
as
a
call
into
a
collaboration.
v
A
collaboration
that
has
been
configured
to
handle
requests
that
are
received
as
calls
through
the
Server
Access
Interface.
In
the
example
shown
in
Figure
2,,
at
a
site
that
has
not
implemented
either
the
IBM
WebSphere
Business
Integration
Server
Express
system
or
a
connector,
a
customer
representative
uses
a
web
browser
to
obtain
the
status
of
a
purchase
order
over
the
Internet
from
an
ERP
application
(SAP
in
the
example)
that
resides
at
a
site
that
has
implemented
the
IBM
WebSphere
Business
Integration
Server
Express
system.
To
enable
this,
the
IBM
WebSphere
Business
Integration
Server
Express
uses
the
Server
Access
Interface,
together
with
a
collaboration
(hypothetical
in
this
example)
for
purchase-order
business
logic,
an
SAP
connector,
and
definitions
of
business
objects
that
represent
purchase-order
status
information.
Data
flow
in
an
InterChange
Server
Express
implementation
A
data
flow
is
initiated
by
either
of
two
types
of
interactions:
publish-and-
subscribe
interactions
or
service
call
interactions.
Both
types
of
interaction
supply
triggers
that
start
the
execution
of
a
collaboration’s
business
processes.
The
collaboration
then
uses
a
third
type
of
interaction—request/response
—to
complete
the
exchange
of
data
with
the
intended
destination.
Browser
Servlet
Web
Server
Server Access
Interface
Collaboration
SAP
Application
SAP
Connector
POstatus data
POstatus Business Object
START
Figure
2.
Execution
of
a
call
through
the
Server
Access
Interface
4
IBM
WebSphere
Business
Integration
Server
Express
and
Express
Plus:
System
Implementation
Guide