IBM E02HMLL-I Implementation Guide - Page 126

Printing, repos_copy, command, Validating, package, Deploying, repository

Page 126 highlights

Printing the repos_copy command You can run repos_copy without any arguments to have the command and its arguments printed out. The example below shows repos_copy when executed without any arguments, and the resulting output: C:\>repos_copy No Command line arguments to ReposCopy were specified Usage: repos_copy {-o[outputFile] | -i[inputFile]} [-sserverName] [-uuserName] [-ppassword] [-ai] [-ar] [-arp] [-d] [-k] [-v] [-eentityType:entityName1[+entityType:entityName2] -deep] [-fentityFileName] [-rrelationshipName1[:relationshipName2] ] [-xCompileAll] [-xCompileAllCollabs] [-xCompileAllMaps] [-xCompileCollab:collabTemplateName[+collabTemplateName]] [-xCompileMap:nativeMapName[+nativeMapName]] [-xcompilepackage] [-mode] [-doentityType:entityName1[+entityType:entityName2] -deep] [-dfoentityType:entityName1[+entityType:entityName2] -deep] [-summary] [-vp] [-vr] Validating a package You can validate a package of components before deploying the package to a server. This is very useful because if you deploy a package to a production-mode server all the dependencies must be resolved or the deployment will fail. You cannot validate a user project or integration component library in System Manager to make sure that the dependencies are satisfied, so the only way to find out if a package is valid when deploying with System Manager is to attempt the deployment and use the error information when it fails to resolve the dependencies. If there are many components in the package, this can be a very time-consuming process. Although you cannot validate an integration component library, you can export it to a package file and then validate the package file using repos_copy. To validate a package file using repos_copy, use the -i option to specify the name of the package file to be validated and the -vp argument to validate it rather than deploy it. C:\WebSphereICS>repos_copy -sWebSphereICSServer -uadmin -pnull -iWebSphereICSServer.jar -vp Repos_copy validates the contents of the package and displays a message to indicate whether or not the dependencies are resolved. Deploying a package to the repository The -i option allows you to deploy a package of components to the repository. If you do not specify the name of the package file then you are prompted to enter it. The following example shows a a file named WebSphereICSServer.jar being deployed to a repository: C:\WebSphereICS>repos_copy -sWebSphereICSServer -uadmin -pnull -iWebSphereICSServer.jar 114 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

Printing
the
repos_copy
command
You
can
run
repos_copy
without
any
arguments
to
have
the
command
and
its
arguments
printed
out.
The
example
below
shows
repos_copy
when
executed
without
any
arguments,
and
the
resulting
output:
C:\>repos_copy
No
Command
line
arguments
to
ReposCopy
were
specified
Usage:
repos_copy
{-o[outputFile]
|
-i[inputFile]}
[-sserverName]
[-uuserName]
[-ppassword]
[-ai]
[-ar]
[-arp]
[-d]
[-k]
[-v]
[-eentityType:entityName1[+entityType:entityName2]
-deep]
[-fentityFileName]
[-rrelationshipName1[:relationshipName2]
]
[-xCompileAll]
[-xCompileAllCollabs]
[-xCompileAllMaps]
[-xCompileCollab:collabTemplateName[+collabTemplateName]]
[-xCompileMap:nativeMapName[+nativeMapName]]
[-xcompilepackage]
[-mode]
[-doentityType:entityName1[+entityType:entityName2]
-deep]
[-dfoentityType:entityName1[+entityType:entityName2]
-deep]
[-summary]
[-vp]
[-vr]
Validating
a
package
You
can
validate
a
package
of
components
before
deploying
the
package
to
a
server.
This
is
very
useful
because
if
you
deploy
a
package
to
a
production-mode
server
all
the
dependencies
must
be
resolved
or
the
deployment
will
fail.
You
cannot
validate
a
user
project
or
integration
component
library
in
System
Manager
to
make
sure
that
the
dependencies
are
satisfied,
so
the
only
way
to
find
out
if
a
package
is
valid
when
deploying
with
System
Manager
is
to
attempt
the
deployment
and
use
the
error
information
when
it
fails
to
resolve
the
dependencies.
If
there
are
many
components
in
the
package,
this
can
be
a
very
time-consuming
process.
Although
you
cannot
validate
an
integration
component
library,
you
can
export
it
to
a
package
file
and
then
validate
the
package
file
using
repos_copy.
To
validate
a
package
file
using
repos_copy,
use
the
-i
option
to
specify
the
name
of
the
package
file
to
be
validated
and
the
-vp
argument
to
validate
it
rather
than
deploy
it.
C:\WebSphereICS>repos_copy
-sWebSphereICSServer
-uadmin
-pnull
-iWebSphereICSServer.jar
-vp
Repos_copy
validates
the
contents
of
the
package
and
displays
a
message
to
indicate
whether
or
not
the
dependencies
are
resolved.
Deploying
a
package
to
the
repository
The
-i
option
allows
you
to
deploy
a
package
of
components
to
the
repository.
If
you
do
not
specify
the
name
of
the
package
file
then
you
are
prompted
to
enter
it.
The
following
example
shows
a
a
file
named
WebSphereICSServer.jar
being
deployed
to
a
repository:
C:\WebSphereICS>repos_copy
-sWebSphereICSServer
-uadmin
-pnull
-iWebSphereICSServer.jar
114
IBM
WebSphere
Business
Integration
Server
Express
and
Express
Plus:
System
Implementation
Guide