IBM E02HMLL-I Implementation Guide - Page 26

Binding, destinations, mapping

Page 26 highlights

Collaboration Subscribe Connector Controller Publish Client Connector Framework Figure 8. A connector providing a triggering event Multiple collaborations can subscribe to the same event. When the connector controller publishes the event, it can publish simultaneously to all subscribers. Binding to receive access requests Instead of binding the collaboration to a connector for triggering, you can specify that the collaboration will receive access requests from external processes as triggers. Binding destinations In addition to binding collaborations to triggering elements, you also bind collaborations to the destination elements with which the collaborations will engage in request/response interactions. Destination elements can be either connectors or other collaborations. A single collaboration can be bound to multiple destination elements. Data mapping Figure 7 shows different types of business objects at each application and at the collaborations. The IBM WebSphere Business Integration Server Express system, therefore, must convert business objects into like forms so that it can send events and data across applications and collaborations. Data mapping is the process of converting business objects from one type to another. Data mapping is required whenever the IBM WebSphere Business Integration Server Express system sends data between a source and a destination that does not share exactly the source's data model. Unlike custom application integration solutions that map data directly from one application to another, InterChange Server Express collaborations generally use the generic business object between the application-specific data models. The generic business object serves as a common, cross-application data set. If you change applications in the future, you need only get a new connector and map the new application-specific business object to the generic business object. Collaborations then continue to work as they did previously. Whenever a collaboration transfers a business object across dissimilar applications, mapping transforms the business object to and from the common data set. Business object transformation takes place: 14 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

Multiple
collaborations
can
subscribe
to
the
same
event.
When
the
connector
controller
publishes
the
event,
it
can
publish
simultaneously
to
all
subscribers.
Binding
to
receive
access
requests
Instead
of
binding
the
collaboration
to
a
connector
for
triggering,
you
can
specify
that
the
collaboration
will
receive
access
requests
from
external
processes
as
triggers.
Binding
destinations
In
addition
to
binding
collaborations
to
triggering
elements,
you
also
bind
collaborations
to
the
destination
elements
with
which
the
collaborations
will
engage
in
request/response
interactions.
Destination
elements
can
be
either
connectors
or
other
collaborations.
A
single
collaboration
can
be
bound
to
multiple
destination
elements.
Data
mapping
Figure
7
shows
different
types
of
business
objects
at
each
application
and
at
the
collaborations.
The
IBM
WebSphere
Business
Integration
Server
Express
system,
therefore,
must
convert
business
objects
into
like
forms
so
that
it
can
send
events
and
data
across
applications
and
collaborations.
Data
mapping
is
the
process
of
converting
business
objects
from
one
type
to
another.
Data
mapping
is
required
whenever
the
IBM
WebSphere
Business
Integration
Server
Express
system
sends
data
between
a
source
and
a
destination
that
does
not
share
exactly
the
source’s
data
model.
Unlike
custom
application
integration
solutions
that
map
data
directly
from
one
application
to
another,
InterChange
Server
Express
collaborations
generally
use
the
generic
business
object
between
the
application-specific
data
models.
The
generic
business
object
serves
as
a
common,
cross-application
data
set.
If
you
change
applications
in
the
future,
you
need
only
get
a
new
connector
and
map
the
new
application-specific
business
object
to
the
generic
business
object.
Collaborations
then
continue
to
work
as
they
did
previously.
Whenever
a
collaboration
transfers
a
business
object
across
dissimilar
applications,
mapping
transforms
the
business
object
to
and
from
the
common
data
set.
Business
object
transformation
takes
place:
Client Connector
Framework
Connector
Controller
Collaboration
Subscribe
Publish
Figure
8.
A
connector
providing
a
triggering
event
14
IBM
WebSphere
Business
Integration
Server
Express
and
Express
Plus:
System
Implementation
Guide