IBM E02HMLL-I Implementation Guide - Page 122

Option, Description

Page 122 highlights

{[-xCompileAll]|[-xCompileAllCollabs]|[-xCompileAllMaps]| [-xCompileCollab:collabTemplateName[+collabTemplateName][+...]]| [-xCompileMap:nativeMapName[+nativeMapName][+...]]} Table 11. Repos_copy command options Option -ai -ar -arp -d -deep -dfoEntityType:Entity[+EntityType:Entity2] -doEntityType:Entity[+EntityType:Entity2] Description Ignore and do not load any duplicate objects (business objects, maps, relationships, collaboration templates and objects, and connectors) that are found when deploying a package. Replace any duplicate objects (business objects, maps, relationships, collaboration templates and objects, and connectors) that are found when deploying a package. This is an interactive version of the -ar option. If the components in the package being deployed already exist in the repository then repos_copy displays a prompt asking if you want to ignore or replace the component. Deletes the components in the repository, except the state data. Use this option to delete all of the components from the repository. Used with the -e option when you want to include all the dependent components. If you omit the -deep option, only the component that is specified with the -e option will be included. This option is the same as the -do option except that it will forcefully delete the component even if the component has referents that depend on it. This option only works with the repository of a server that is running in design mode. A server that is running in production mode does not permit unresolved dependencies and references. Specifies the entities to be deleted from the repository. See Table 12 on page 113 for the list of entity types and keywords. If the object has no referents-other components that depend on it-then the deletion takes place. If the object has referents, then the deletion fails and a message is displayed. The behavior is the same in both design mode and production mode. For more information about starting the server in design mode or production mode, see the System Implementation Guide. 110 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

{[-xCompileAll]|[-xCompileAllCollabs]|[-xCompileAllMaps]|
[-xCompileCollab:collabTemplateName[+collabTemplateName][+...]]|
[-xCompileMap:nativeMapName[+nativeMapName][+...]]}
Table
11.
Repos_copy
command
options
Option
Description
-ai
Ignore
and
do
not
load
any
duplicate
objects
(business
objects,
maps,
relationships,
collaboration
templates
and
objects,
and
connectors)
that
are
found
when
deploying
a
package.
-ar
Replace
any
duplicate
objects
(business
objects,
maps,
relationships,
collaboration
templates
and
objects,
and
connectors)
that
are
found
when
deploying
a
package.
-arp
This
is
an
interactive
version
of
the
-ar
option.
If
the
components
in
the
package
being
deployed
already
exist
in
the
repository
then
repos_copy
displays
a
prompt
asking
if
you
want
to
ignore
or
replace
the
component.
-d
Deletes
the
components
in
the
repository,
except
the
state
data.
Use
this
option
to
delete
all
of
the
components
from
the
repository.
-deep
Used
with
the
-e
option
when
you
want
to
include
all
the
dependent
components.
If
you
omit
the
-deep
option,
only
the
component
that
is
specified
with
the
-e
option
will
be
included.
-dfo
EntityType:Entity[+EntityType:Entity2]
This
option
is
the
same
as
the
-do
option
except
that
it
will
forcefully
delete
the
component
even
if
the
component
has
referents
that
depend
on
it.
This
option
only
works
with
the
repository
of
a
server
that
is
running
in
design
mode.
A
server
that
is
running
in
production
mode
does
not
permit
unresolved
dependencies
and
references.
-do
EntityType:Entity[+EntityType:Entity2]
Specifies
the
entities
to
be
deleted
from
the
repository.
See
Table
12
on
page
113
for
the
list
of
entity
types
and
keywords.
If
the
object
has
no
referents—other
components
that
depend
on
it—then
the
deletion
takes
place.
If
the
object
has
referents,
then
the
deletion
fails
and
a
message
is
displayed.
The
behavior
is
the
same
in
both
design
mode
and
production
mode.
For
more
information
about
starting
the
server
in
design
mode
or
production
mode,
see
the
System
Implementation
Guide
.
110
IBM
WebSphere
Business
Integration
Server
Express
and
Express
Plus:
System
Implementation
Guide