IBM E02HMLL-I Implementation Guide - Page 95

Working, components, InterChange, Server, Express, repository, Validating

Page 95 highlights

Use the InterChange Server Express Component Management view or System Monitor to stop the duplicate components in the server before deploying a package. For more information, see "Managing component states in the repository" on page 84. 2. Do the following in the WebSphere Business Integration System Manager view to select the components you want to deploy: v Select user projects or integration component libraries to choose all of the components in them. v Choose all components of one type by selecting its folder in a user project or integration component library. v Expand the component folders and select individual components to choose them. You can use standard Windows selection techniques to select multiple user projects for deployment at the same time, such as the following: - Hold down Shift to select contiguous items. - Hold down Ctrl to select non-contiguous items. 3. Drag-and-drop the selected resources onto the InterChange Server Express instance to which you want to deploy the components in the InterChange Server Express Component Management view. System Manager attempts to deploy the components to the specified InterChange Server Express instance. Messages and errors are displayed in the Console view. Note: If you selected duplicate components in the WebSphere Business Integration System Manager view then System Manager generates an error when you try to deploy the components. Refine your selection to include only unique components and then attempt the deployment again. Working with components in an InterChange Server Express repository The InterChange Server Express Component Management view allows you to manage the repositories of the InterChange Server Expresss you have registered, and to manage the components in those repositories. Validating the components in the repository As described in "InterChange Server modes" on page 45, InterChange Server Express has different restrictions regarding the integrity of the repository depending on the mode you start it in. Although a server running in design mode allows the repository to be inconsistent so that you can add components as they become available, a server running in production mode requires that all references and dependencies among the components be resolved. When you migrate from a design-mode server to a production-mode server, then, you should validate the repository beforehand to make sure that the repository will be in a consistent state. Do the following to validate the repository using System Manager: 1. In the InterChange Server Express Component Management view, right-click the server instance whose repository you want to validate and choose Validate Repository from the context menu. 2. If the repository is in a consistent state, an informational prompt is displayed. Click OK to close the "Validate Repository" prompt. Chapter 4. Using System Manager 83

  • 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

Use
the
InterChange
Server
Express
Component
Management
view
or
System
Monitor
to
stop
the
duplicate
components
in
the
server
before
deploying
a
package.
For
more
information,
see
“Managing
component
states
in
the
repository”
on
page
84.
2.
Do
the
following
in
the
WebSphere
Business
Integration
System
Manager
view
to
select
the
components
you
want
to
deploy:
v
Select
user
projects
or
integration
component
libraries
to
choose
all
of
the
components
in
them.
v
Choose
all
components
of
one
type
by
selecting
its
folder
in
a
user
project
or
integration
component
library.
v
Expand
the
component
folders
and
select
individual
components
to
choose
them.
You
can
use
standard
Windows
selection
techniques
to
select
multiple
user
projects
for
deployment
at
the
same
time,
such
as
the
following:
Hold
down
Shift
to
select
contiguous
items.
Hold
down
Ctrl
to
select
non-contiguous
items.
3.
Drag-and-drop
the
selected
resources
onto
the
InterChange
Server
Express
instance
to
which
you
want
to
deploy
the
components
in
the
InterChange
Server
Express
Component
Management
view.
System
Manager
attempts
to
deploy
the
components
to
the
specified
InterChange
Server
Express
instance.
Messages
and
errors
are
displayed
in
the
Console
view.
Note:
If
you
selected
duplicate
components
in
the
WebSphere
Business
Integration
System
Manager
view
then
System
Manager
generates
an
error
when
you
try
to
deploy
the
components.
Refine
your
selection
to
include
only
unique
components
and
then
attempt
the
deployment
again.
Working
with
components
in
an
InterChange
Server
Express
repository
The
InterChange
Server
Express
Component
Management
view
allows
you
to
manage
the
repositories
of
the
InterChange
Server
Expresss
you
have
registered,
and
to
manage
the
components
in
those
repositories.
Validating
the
components
in
the
repository
As
described
in
“InterChange
Server
modes”
on
page
45,
InterChange
Server
Express
has
different
restrictions
regarding
the
integrity
of
the
repository
depending
on
the
mode
you
start
it
in.
Although
a
server
running
in
design
mode
allows
the
repository
to
be
inconsistent
so
that
you
can
add
components
as
they
become
available,
a
server
running
in
production
mode
requires
that
all
references
and
dependencies
among
the
components
be
resolved.
When
you
migrate
from
a
design-mode
server
to
a
production-mode
server,
then,
you
should
validate
the
repository
beforehand
to
make
sure
that
the
repository
will
be
in
a
consistent
state.
Do
the
following
to
validate
the
repository
using
System
Manager:
1.
In
the
InterChange
Server
Express
Component
Management
view,
right-click
the
server
instance
whose
repository
you
want
to
validate
and
choose
Validate
Repository
from
the
context
menu.
2.
If
the
repository
is
in
a
consistent
state,
an
informational
prompt
is
displayed.
Click
OK
to
close
the
“Validate
Repository”
prompt.
Chapter
4.
Using
System
Manager
83