IBM E02HMLL-I Implementation Guide - Page 142

Associated

Page 142 highlights

You must restart the server for changes in transaction level to take effect. Associated maps Each connector supports a list of business object definitions and their associated maps that are currently active in InterChange Server Express. This list appears when you select the Associated Maps tab. The list of business objects contains the application-specific business object which the agent supports and the corresponding generic object that the controller sends to the subscribing collaboration. The association of a map determines which map will be used to transform the application-specific business object to the generic business object or the generic business object to the application-specific business object. If you are using maps that are uniquely defined for specific source and destination business objects, the maps will already be associated with their appropriate business objects when you open the display, and you will not need (or be able) to change them. If more than one map is available for use by a supported business object, you will need to explicitly bind the business object with the map that it should use. The Associated Maps tab displays the following fields: v Business Object Name These are the business objects supported by this connector, as designated in the Supported Business Objects tab. If you designate additional business objects under the Supported Business Objects tab, they will be reflected in this list after you save the changes by choosing Save to Project from the File menu of the Connector Configurator Express window. v Associated Maps The display shows all the maps that have been installed to the system for use with the supported business objects of the connector. The source business object for each map is shown to the left of the map name, in the Business Object Name display. v Explicit In some cases, you may need to explicitly bind an associated map. Explicit binding is required only when more than one map exists for a particular supported business object. When InterChange Server Express boots, it tries to automatically bind a map to each supported business object for each connector. If more than one map takes as its input the same business object, the server attempts to locate and bind one map that is the superset of the others. If there is no map that is the superset of the others, the server will not be able to bind the business object to a single map, and you will need to set the binding explicitly. To explicitly bind a map: 1. In the Explicit column, place a check in the check box for the map you want to bind. 2. Select the map that you intend to associate with the business object. 3. In the File menu of the Connector Configurator Express window, click Save to Project. 4. Deploy the project to InterChange Server Express. 5. Reboot the server for the changes to take effect. 130 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

You
must
restart
the
server
for
changes
in
transaction
level
to
take
effect.
Associated
maps
Each
connector
supports
a
list
of
business
object
definitions
and
their
associated
maps
that
are
currently
active
in
InterChange
Server
Express.
This
list
appears
when
you
select
the
Associated
Maps
tab.
The
list
of
business
objects
contains
the
application-specific
business
object
which
the
agent
supports
and
the
corresponding
generic
object
that
the
controller
sends
to
the
subscribing
collaboration.
The
association
of
a
map
determines
which
map
will
be
used
to
transform
the
application-specific
business
object
to
the
generic
business
object
or
the
generic
business
object
to
the
application-specific
business
object.
If
you
are
using
maps
that
are
uniquely
defined
for
specific
source
and
destination
business
objects,
the
maps
will
already
be
associated
with
their
appropriate
business
objects
when
you
open
the
display,
and
you
will
not
need
(or
be
able)
to
change
them.
If
more
than
one
map
is
available
for
use
by
a
supported
business
object,
you
will
need
to
explicitly
bind
the
business
object
with
the
map
that
it
should
use.
The
Associated
Maps
tab
displays
the
following
fields:
v
Business
Object
Name
These
are
the
business
objects
supported
by
this
connector,
as
designated
in
the
Supported
Business
Objects
tab.
If
you
designate
additional
business
objects
under
the
Supported
Business
Objects
tab,
they
will
be
reflected
in
this
list
after
you
save
the
changes
by
choosing
Save
to
Project
from
the
File
menu
of
the
Connector
Configurator
Express
window.
v
Associated
Maps
The
display
shows
all
the
maps
that
have
been
installed
to
the
system
for
use
with
the
supported
business
objects
of
the
connector.
The
source
business
object
for
each
map
is
shown
to
the
left
of
the
map
name,
in
the
Business
Object
Name
display.
v
Explicit
In
some
cases,
you
may
need
to
explicitly
bind
an
associated
map.
Explicit
binding
is
required
only
when
more
than
one
map
exists
for
a
particular
supported
business
object.
When
InterChange
Server
Express
boots,
it
tries
to
automatically
bind
a
map
to
each
supported
business
object
for
each
connector.
If
more
than
one
map
takes
as
its
input
the
same
business
object,
the
server
attempts
to
locate
and
bind
one
map
that
is
the
superset
of
the
others.
If
there
is
no
map
that
is
the
superset
of
the
others,
the
server
will
not
be
able
to
bind
the
business
object
to
a
single
map,
and
you
will
need
to
set
the
binding
explicitly.
To
explicitly
bind
a
map:
1.
In
the
Explicit
column,
place
a
check
in
the
check
box
for
the
map
you
want
to
bind.
2.
Select
the
map
that
you
intend
to
associate
with
the
business
object.
3.
In
the
File
menu
of
the
Connector
Configurator
Express
window,
click
Save
to
Project
.
4.
Deploy
the
project
to
InterChange
Server
Express.
5.
Reboot
the
server
for
the
changes
to
take
effect.
130
IBM
WebSphere
Business
Integration
Server
Express
and
Express
Plus:
System
Implementation
Guide