IBM E02HMLL-I Implementation Guide - Page 128

Validating, repository, Compiling, components

Page 128 highlights

-rCustomer:Order would not create schemas for the Customer and Order relationships, but would still create schemas for any other relationships in the package being deployed. Important: Although there are options to compile maps and collaboration templates after deployment, there is no way to either through repos_copy or System Manager to create the schema for a relationship other than during deployment. So, if you chose not to create the schema for a relationship during deployment because you needed to change the database settings, then you need to re-deploy the relationship afterwards and allow repos_copy to create the schema for the relationship. Validating the repository The repository must be in a valid state for a server instance to start in production mode. The reason for this is that ultimately the repository must be valid for the server to process flows successfully. Use the -vr option to validate a server repository, as in the example below: C:\WebSphereICS>repos_copy -sWebSphereICSServer -uadmin -pnull -vr If the server is valid then repos_copy writes the following output to the console: Validation Succeeded.All Dependencies Resolved. If the repository is not valid then repos_copy prints a list of the dependencies that must be resolved. Compiling components in the repository If you deployed maps or collaboration templates to the repository and did not compile them during deployment, you can use repos_copy to compile them afterwards. This can be useful in situations where there are many components to deploy because deployment can take a long time and compiling can make the operation take even longer. Waiting until after the deployment has succeeded to do the compilation task can reduce the risk of spending an even greater amount of time migrating the environment if an error occurs. The following example shows the use of the -xCompileAll option to compile all maps and collaboration templates in the the repository: C:\WebSphereICS>repos_copy -sWebSphereICSServer -uadmin -pnull -xCompileAll There are options to compile all of either type of component as well. Use -xCompileAllCollabs to compile all the collaboration templates, and -xCompileAllMaps to compile all the maps. The example below shows the use of -xCompileAllMaps: C:\WebSphereICS>repos_copy -sWebSphereICSServer -uadmin -pnull -xCompileAllMaps Just as you can compile all of one type of component, you can also compile an individual component. Use the -xCompileCollab or -xCompileMap option followed by a colon and the name of the collaboration template or map to compile a single component. The example below would compile a collaboration template named CustomerSync: C:\WebSphereICS>repos_copy -sWebSphereICSServer -uadmin -pnull -xCompileCollab:CustomerSync 116 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

-rCustomer:Order
would
not
create
schemas
for
the
Customer
and
Order
relationships,
but
would
still
create
schemas
for
any
other
relationships
in
the
package
being
deployed.
Important:
Although
there
are
options
to
compile
maps
and
collaboration
templates
after
deployment,
there
is
no
way
to
either
through
repos_copy
or
System
Manager
to
create
the
schema
for
a
relationship
other
than
during
deployment.
So,
if
you
chose
not
to
create
the
schema
for
a
relationship
during
deployment
because
you
needed
to
change
the
database
settings,
then
you
need
to
re-deploy
the
relationship
afterwards
and
allow
repos_copy
to
create
the
schema
for
the
relationship.
Validating
the
repository
The
repository
must
be
in
a
valid
state
for
a
server
instance
to
start
in
production
mode.
The
reason
for
this
is
that
ultimately
the
repository
must
be
valid
for
the
server
to
process
flows
successfully.
Use
the
-vr
option
to
validate
a
server
repository,
as
in
the
example
below:
C:\WebSphereICS>repos_copy
-sWebSphereICSServer
-uadmin
-pnull
-vr
If
the
server
is
valid
then
repos_copy
writes
the
following
output
to
the
console:
Validation
Succeeded.All
Dependencies
Resolved.
If
the
repository
is
not
valid
then
repos_copy
prints
a
list
of
the
dependencies
that
must
be
resolved.
Compiling
components
in
the
repository
If
you
deployed
maps
or
collaboration
templates
to
the
repository
and
did
not
compile
them
during
deployment,
you
can
use
repos_copy
to
compile
them
afterwards.
This
can
be
useful
in
situations
where
there
are
many
components
to
deploy
because
deployment
can
take
a
long
time
and
compiling
can
make
the
operation
take
even
longer.
Waiting
until
after
the
deployment
has
succeeded
to
do
the
compilation
task
can
reduce
the
risk
of
spending
an
even
greater
amount
of
time
migrating
the
environment
if
an
error
occurs.
The
following
example
shows
the
use
of
the
-xCompileAll
option
to
compile
all
maps
and
collaboration
templates
in
the
the
repository:
C:\WebSphereICS>repos_copy
-sWebSphereICSServer
-uadmin
-pnull
-xCompileAll
There
are
options
to
compile
all
of
either
type
of
component
as
well.
Use
-xCompileAllCollabs
to
compile
all
the
collaboration
templates,
and
-xCompileAllMaps
to
compile
all
the
maps.
The
example
below
shows
the
use
of
-xCompileAllMaps
:
C:\WebSphereICS>repos_copy
-sWebSphereICSServer
-uadmin
-pnull
-xCompileAllMaps
Just
as
you
can
compile
all
of
one
type
of
component,
you
can
also
compile
an
individual
component.
Use
the
-xCompileCollab
or
-xCompileMap
option
followed
by
a
colon
and
the
name
of
the
collaboration
template
or
map
to
compile
a
single
component.
The
example
below
would
compile
a
collaboration
template
named
CustomerSync
:
C:\WebSphereICS>repos_copy
-sWebSphereICSServer
-uadmin
-pnull
-xCompileCollab:CustomerSync
116
IBM
WebSphere
Business
Integration
Server
Express
and
Express
Plus:
System
Implementation
Guide