IBM E02HMLL-I Implementation Guide - Page 124

outfilename, password, serverName, username

Page 124 highlights

Table 11. Repos_copy command options (continued) Option -ooutfilename -ppassword -r* -rrelationshipName1[:relationshipName2] -sserverName -summary -uusername -v -vp -vr Description Exports the components in the repository to the specified package file. You must specify the name of the package file. If the file already exists then repos_copy prompts you to overwrite it or not. The output file is in .jar format, and contains the component definitions in XML format, as well as .java source files for components that have them. This option cannot be combined with the -i or -d options, nor can it export components in text formats. Repos_copy does not append the .jar extension, so you must specify it when specifying the name of the output file. Specifies the password for the user name supplied with the -u option. The password case-sensitive. If you do not specify this option then repos_copy prompts you for the password. This option is similar to the -r option; it allows you to import relationship definitions and not create the runtime schemas for any of them. Loads the named relationship definition(s) into the repository without creating its runtime schema. Specifies the name of the InterChange Server Express instance with which repos_copy should interface. The name is case-sensitive. If the server name is not specified, the tool prompts for a server name. This option prints a list of components in the server repository (they are identified as "artifacts" rather than as components in the output). The output is in XML format. You can combine this option with the -o option to print the output to a file rather than the console. Specifies the user name to log in to InterChange Server Express. If no user name is specified, repos_copy prompts for a user name. Prints the version number of the program that the repos_copy utility executes. This option validates a package file. The server validates packages against the repository and makes sure that the dependencies among the components in the package are resolved. If the validation is not successful, repos_copy prints a list of the missing dependencies. This option does not make any changes to the repository; it just validates the package file. When using the -vp option you must also use the -i option to specify the package file to be validated. This option validates the repository. The output message indicates whether the validation is successful or not. If the validation is not successful, repos_copy prints a list of the missing dependencies. 112 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

Table
11.
Repos_copy
command
options
(continued)
Option
Description
-o
outfilename
Exports
the
components
in
the
repository
to
the
specified
package
file.
You
must
specify
the
name
of
the
package
file.
If
the
file
already
exists
then
repos_copy
prompts
you
to
overwrite
it
or
not.
The
output
file
is
in
.jar
format,
and
contains
the
component
definitions
in
XML
format,
as
well
as
.java
source
files
for
components
that
have
them.
This
option
cannot
be
combined
with
the
-i
or
-d
options,
nor
can
it
export
components
in
text
formats.
Repos_copy
does
not
append
the
.jar
extension,
so
you
must
specify
it
when
specifying
the
name
of
the
output
file.
-p
password
Specifies
the
password
for
the
user
name
supplied
with
the
-u
option.
The
password
case-sensitive.
If
you
do
not
specify
this
option
then
repos_copy
prompts
you
for
the
password.
-r*
This
option
is
similar
to
the
-r
option;
it
allows
you
to
import
relationship
definitions
and
not
create
the
runtime
schemas
for
any
of
them.
-r
relationshipName1[:relationshipName2]
Loads
the
named
relationship
definition(s)
into
the
repository
without
creating
its
runtime
schema.
-s
serverName
Specifies
the
name
of
the
InterChange
Server
Express
instance
with
which
repos_copy
should
interface.
The
name
is
case-sensitive.
If
the
server
name
is
not
specified,
the
tool
prompts
for
a
server
name.
-summary
This
option
prints
a
list
of
components
in
the
server
repository
(they
are
identified
as
“artifacts”
rather
than
as
components
in
the
output).
The
output
is
in
XML
format.
You
can
combine
this
option
with
the
-o
option
to
print
the
output
to
a
file
rather
than
the
console.
-u
username
Specifies
the
user
name
to
log
in
to
InterChange
Server
Express.
If
no
user
name
is
specified,
repos_copy
prompts
for
a
user
name.
-v
Prints
the
version
number
of
the
program
that
the
repos_copy
utility
executes.
-vp
This
option
validates
a
package
file.
The
server
validates
packages
against
the
repository
and
makes
sure
that
the
dependencies
among
the
components
in
the
package
are
resolved.
If
the
validation
is
not
successful,
repos_copy
prints
a
list
of
the
missing
dependencies.
This
option
does
not
make
any
changes
to
the
repository;
it
just
validates
the
package
file.
When
using
the
-vp
option
you
must
also
use
the
-i
option
to
specify
the
package
file
to
be
validated.
-vr
This
option
validates
the
repository.
The
output
message
indicates
whether
the
validation
is
successful
or
not.
If
the
validation
is
not
successful,
repos_copy
prints
a
list
of
the
missing
dependencies.
112
IBM
WebSphere
Business
Integration
Server
Express
and
Express
Plus:
System
Implementation
Guide