Table 14 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, at least one of which is 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} {[-xCompileAll]|[-xCompileAllCollabs]|[-xCompileAllMaps]| [-xCompileCollab:collabTemplateName[+collabTemplateName][+...]]| [-xCompileMap:nativeMapName[+nativeMapName][+...]]}
Table 14. Repos_copy command options
Option | Description |
---|---|
-ai |
Ignore and do not load duplicate objects (business objects, maps,
relationships, collaboration templates and objects, and connectors) that are
found when deploying a package.
|
-ar |
Replace duplicate objects (business objects, maps, relationships,
collaboration templates and objects, and connectors) that are found when
deploying a package.
|
-arp |
Replace duplicate components. This is an interactive version of the
-ar option. If the components in the package being deployed
already exist in the repository, you are prompted to ignore or replace the
component.
|
-d |
Delete the components in the repository, except the state data. Use
this option to delete all of the components from the repository.
|
-deep |
Use with the -e option to include all the dependent
components. If you omit the -deep option, only the component
that is specified with the -e option is included.
|
-dfoEntityType:Entity[+EntityType:Entity2] |
Forcefully deletes 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. See also
the -do option.
|
-doEntityType:Entity[+EntityType:Entity2] |
Specify the entities to be deleted from the repository. See Table 15 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.
|
-eEntityType:Entity1[+EntityType:Entity2...] |
Export one or more referenced first-class entities. A first-class entity is a business object, collaboration object, collaboration template, connector, database connection pool, map, or relationship. You identify the entity to load or unload by specifying one of the keywords in Table 15. Follow the EntityType keyword with a colon (:)
and the name of the entity. Use the "+" to specify more than
one entity. When combined with the -o option, the
-e option unloads the data to an output file.
|
-fentityFile |
Similar to the -e option, but take the names of the entities from the file EntityFile. The file should contain references to the entities, with the following conditions:
When combined with the
|
-ifilename |
Deploy the specified package file to the repository. If you omit the input file name value, the command interactively prompts you to enter the name of the input file. The file can be either a .jar file containing objects in XML format or an .in file containing objects in a text format. The .jar files created by repos_copy or System Manager
have a particular structure which must be maintained for any subsequent
imports of such a file to be successful. You should not, therefore,
ever modify an input file manually.
|
-k |
Override the default behavior of repos_copy when it finds a Mercator map in
the package file it is loading. By default, repos_copy exits if it
encounters a Mercator map. If you use the -k option,
repos_copy skips over any Mercator maps in the package file and proceeds with
the deployment process.
|
-mode |
Return the mode of the server. For more information about
InterChange Server Express modes, see the Implementation Guide for WebSphere InterChange Server.
|
-ncencoding |
See the Java documentation about the String class for a list of valid character encodings. When deploying a repository created with WICS version 4.1.1,
specify the character encoding used in the 4.1.1
environment.
|
-ooutfilename |
Export 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, and .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
format as it did in previous releases. Repos_copy does not append the
.jar extension, so you must specify it when specifying the
name of the output file.
|
-ppassword |
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* |
Import relationship definitions and not create the run-time schemas for any
of them. See also the -r option.
|
-rrelationshipName1[:relationshipName2] |
Load the named relationship definition(s) into the repository without
creating its run-time schema.
|
-sserverName |
Specify 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 |
List 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.
|
-uusername |
Specify the user name to log on to InterChange Server Express. If no
user name is specified, repos_copy prompts for a user name.
|
-v |
Print the version number of the program that the repos_copy utility
executes.
|
-vp |
Validate 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 |
Validate 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.
|
-wi |
Do not display warning messages that occur during the compilation of
collaboration templates or maps. Only errors that occur during
compilation are displayed. This allows the user to ignore warnings
about deprecated methods, for example.
|
-xCompileAll |
Compile all collaboration templates and maps in the repository.
|
-xCompileAllCollabs |
Compile all collaboration templates in the repository.
|
-xCompileAllMaps |
Compile all maps in the repository.
|
-xCompileCollab:collabTemplateName[+collabTemplateName] |
Compile the specified collaboration templates in the repository.
|
-xCompileMap:nativeMapName[+nativeMapName] |
Compile the specified maps in the repository.
|
-xCompilePackage |
Automatically compile the package deployed to the server. Because
the production-mode server automatically compiles all packages, this option
applies only to design-mode servers. For a full description of
InterChange Server Express modes, see the System Implementation Guide.
|
Table 15. Keywords for different entity types
Entity type | Keyword |
---|---|
Business object | BusObj |
Collaboration object | Collaboration |
Collaboration template | CollabTemplate |
Database connection pool | ConnectionPool |
Connector | Connector |
Map | Map |
Relationship | Relationship |