IBM E02HMLL-I Implementation Guide - Page 121

Using, repos_copy

Page 121 highlights

Chapter 6. Using repos_copy Repos_copy is a command line interface for working with integration components and InterChange Server Express repositories. It allows you to deploy a package-a collection of integration components-to a server repository, or to export components from the repository to a package. To run repos_copy, enter the command in an MS-DOS command prompt window. The ProductDir/bin directory, where the utility resides, should be in your path as a result of installation. Note: The repos_copy output file contains encrypted passwords for relationships and connector applications. If you try to edit the output file and change these passwords, repos_copy will not work. Important: When repos_copy deploys components to the repository, it deploys them to the repository only. It does not deploy them to any in-memory tables of business object definitions. For instance, connectors load business object definitions from the repository into their memory space when they start. If you deploy a business object definition to the repository to update it, you must restart the connector agent so that it loads the modified business object definition into memory. You must therefore stop and restart InterChange Server Express and components that load definitions into memory for them to load recently deployed components. This chapter has the following sections: v "Repos_copy syntax" on page 109 v "Repos_copy usage scenarios" on page 113 v "Locale for repos_copy files" on page 119 For more information about backing up the system, see the System Administration Guide. Repos_copy syntax Table 11 on page 110 describes the options of repos_copy and their arguments, and shows the correct case usage for the options and the lack of spacing between the option and its argument. The syntax shows that the options between curly braces ({}) represent a set of options that are required. If you do not specify the -u, -p, -i, -o, or -s options at the command line, then repos_copy prompts you for them. If you do not specify them when prompted, repos_copy does not execute. Options enclosed in brackets ([]) are optional. repos_copy [-sserverName][-uusername][-ppassword] {-i[filename1][-rrelationshipName[relationshipName2]][[-k][-ai|-ar|-arp] [-xcompilePackage][-vp|-vr]} {-o[outfilename[[-fEntityFile][-eEntityType:Entity1[+EntityType:Entity2][+...]] [-deep][-summary]} {[-d]|[-doEntityType:Entity[+EntityType:Entity2][+...]| [-dfoEntityType:Entity[+EntityType:Entity2][+...]} {-v} {-vr} © Copyright IBM Corp. 2001, 2004 109

  • 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

Chapter
6.
Using
repos_copy
Repos_copy
is
a
command
line
interface
for
working
with
integration
components
and
InterChange
Server
Express
repositories.
It
allows
you
to
deploy
a
package—a
collection
of
integration
components—to
a
server
repository,
or
to
export
components
from
the
repository
to
a
package.
To
run
repos_copy
,
enter
the
command
in
an
MS-DOS
command
prompt
window.
The
ProductDir
/bin
directory,
where
the
utility
resides,
should
be
in
your
path
as
a
result
of
installation.
Note:
The
repos_copy
output
file
contains
encrypted
passwords
for
relationships
and
connector
applications.
If
you
try
to
edit
the
output
file
and
change
these
passwords,
repos_copy
will
not
work.
Important:
When
repos_copy
deploys
components
to
the
repository,
it
deploys
them
to
the
repository
only
.
It
does
not
deploy
them
to
any
in-memory
tables
of
business
object
definitions.
For
instance,
connectors
load
business
object
definitions
from
the
repository
into
their
memory
space
when
they
start.
If
you
deploy
a
business
object
definition
to
the
repository
to
update
it,
you
must
restart
the
connector
agent
so
that
it
loads
the
modified
business
object
definition
into
memory.
You
must
therefore
stop
and
restart
InterChange
Server
Express
and
components
that
load
definitions
into
memory
for
them
to
load
recently
deployed
components.
This
chapter
has
the
following
sections:
v
“Repos_copy
syntax”
on
page
109
v
“Repos_copy
usage
scenarios”
on
page
113
v
“Locale
for
repos_copy
files”
on
page
119
For
more
information
about
backing
up
the
system,
see
the
System
Administration
Guide
.
Repos_copy
syntax
Table
11
on
page
110
describes
the
options
of
repos_copy
and
their
arguments,
and
shows
the
correct
case
usage
for
the
options
and
the
lack
of
spacing
between
the
option
and
its
argument.
The
syntax
shows
that
the
options
between
curly
braces
({})
represent
a
set
of
options
that
are
required.
If
you
do
not
specify
the
-u
,
-p
,
-i
,
-o
,
or
-s
options
at
the
command
line,
then
repos_copy
prompts
you
for
them.
If
you
do
not
specify
them
when
prompted,
repos_copy
does
not
execute.
Options
enclosed
in
brackets
([])
are
optional.
repos_copy
[-s
serverName
][-u
username
][-p
password
]
{-i[
filename1
][-r
relationshipName
[
relationshipName2
]][[-k][-ai|-ar|-arp]
[-xcompilePackage][-vp|-vr]}
{-o[
outfilename
[[-f
EntityFile
][-e
EntityType:Entity1
[+
EntityType
:
Entity2
][+...]]
[-deep][-summary]}
{[-d]|[-doEntityType:Entity[+EntityType:Entity2][+...]|
[-dfoEntityType:Entity[+EntityType:Entity2][+...]}
{-v}
{-vr}
©
Copyright
IBM
Corp.
2001,
2004
109