IBM E02HMLL-I Implementation Guide - Page 105

Showing, dependencies, references

Page 105 highlights

resolved. If it detects any unresolved dependencies or references then InterChange Server Express fails to start in production mode. The terms dependencies and references are used to describe the relationship between components, depending on the context. For example, a connector definition requires the business object definitions it supports and the maps associated with those business object definitions to exist so that it can exchange data with InterChange Server Express. In this context, the business object definitions and maps are dependencies of the connector definition. If you view the same relationship between the business object definition and the connector definition, but in the context of the business object, the connector is one of the references of the business object definition-along with any other business objects that contain it as a child, any maps that transform it, any collaboration templates that support it for their port definitions, and so forth. Table 8 specifies the components that can be dependencies and references for each component type. Table 8. Integration component dependencies and references Component Dependencies References Business objects v Business objects v Business objects v Maps v Connectors v Collaboration templates v Collaboration objects Relationships v Business objects None Connectors v Business objects v Maps v Collaboration objects Maps v Business objects v Maps v Connectors v Collaboration objects Collaboration templates Collaboration objects v Business objects v Business objects v Maps v Connectors v Collaboration templates v Collaboration objects None v Collaboration objects Showing dependencies and references You can use System Manager to show the dependencies and references for an integration component. To show the dependencies for a component, right-click it in System Manager and select Show Dependencies from the context menu. The "Dependency Tree" wizard appears. For more information, see "Using the Dependency Tree" on page 52. To show the references for a component, right-click it in System Manager and select Show References from the context menu. The "Object References" window appears. Chapter 4. Using System Manager 93

  • 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

resolved.
If
it
detects
any
unresolved
dependencies
or
references
then
InterChange
Server
Express
fails
to
start
in
production
mode.
The
terms
dependencies
and
references
are
used
to
describe
the
relationship
between
components,
depending
on
the
context.
For
example,
a
connector
definition
requires
the
business
object
definitions
it
supports
and
the
maps
associated
with
those
business
object
definitions
to
exist
so
that
it
can
exchange
data
with
InterChange
Server
Express.
In
this
context,
the
business
object
definitions
and
maps
are
dependencies
of
the
connector
definition.
If
you
view
the
same
relationship
between
the
business
object
definition
and
the
connector
definition,
but
in
the
context
of
the
business
object,
the
connector
is
one
of
the
references
of
the
business
object
definition—along
with
any
other
business
objects
that
contain
it
as
a
child,
any
maps
that
transform
it,
any
collaboration
templates
that
support
it
for
their
port
definitions,
and
so
forth.
Table
8
specifies
the
components
that
can
be
dependencies
and
references
for
each
component
type.
Table
8.
Integration
component
dependencies
and
references
Component
Dependencies
References
Business
objects
v
Business
objects
v
Business
objects
v
Maps
v
Connectors
v
Collaboration
templates
v
Collaboration
objects
Relationships
v
Business
objects
None
Connectors
v
Business
objects
v
Maps
v
Collaboration
objects
Maps
v
Business
objects
v
Maps
v
Connectors
v
Collaboration
objects
Collaboration
templates
v
Business
objects
None
Collaboration
objects
v
Business
objects
v
Maps
v
Connectors
v
Collaboration
templates
v
Collaboration
objects
v
Collaboration
objects
Showing
dependencies
and
references
You
can
use
System
Manager
to
show
the
dependencies
and
references
for
an
integration
component.
To
show
the
dependencies
for
a
component,
right-click
it
in
System
Manager
and
select
Show
Dependencies
from
the
context
menu.
The
“Dependency
Tree”
wizard
appears.
For
more
information,
see
“Using
the
Dependency
Tree”
on
page
52.
To
show
the
references
for
a
component,
right-click
it
in
System
Manager
and
select
Show
References
from
the
context
menu.
The
“Object
References”
window
appears.
Chapter
4.
Using
System
Manager
93