Table 11 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} {[-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.
|
-dfoEntityType: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.
|
-doEntityType:Entity[+EntityType:Entity2] |
Specifies the entities to be deleted from the repository. See Table 12 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...] |
Exports 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 12. 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 |
This option is similar to the -e option except that the names of the entities to be imported are stored in a file. The file should contain references to the entities, with the following conditions:
When combined with the
|
-ifilename |
Deploys 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 a .jar file containing objects in XML 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 |
Overrides 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 |
Returns the mode of the server. For more information about
InterChange Server Express modes, see the Implementation Guide for WebSphere InterChange Server.
|
-ncencoding |
For a list of valid character encodings, see the Java documentation about
the String class.
|
-ooutfilename |
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.
|
-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* |
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.
|
-rrelationshipName1[:relationshipName2] |
Loads the named relationship definition(s) into the repository without
creating its runtime schema.
|
-sserverName |
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.
|
-uusername |
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.
|
-wi |
When this option is specified, repos_copy does not display any warnings
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 instance.
|
-xCompileAll |
Compiles all collaboration templates and maps in the repository.
|
-xCompileAllCollabs |
Compiles all collaboration templates in the repository.
|
-xCompileAllMaps |
Compiles all maps in the repository.
|
-xCompileCollab:collabTemplateName[+collabTemplateName] |
Compiles the specified collaboration templates in the repository.
|
-xCompileMap:nativeMapName[+nativeMapName] |
Compiles the specified maps in the repository.
|
-xCompilePackage |
This option automatically compiles the package being deployed to the
server. Since the production-mode server automatically compiles all
packages, this option applies only to design-mode servers.
|
Table 12. 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 |