The reposMigrate utility is invoked from a command line or via
the Migration wizard launched from the First Steps console. Details of the
syntax and usage of the reposMigrate utility are provided.
Note: If you enable security for a WebSphere Process Server cell,
setup the
soap.client.props file to supply authentication
information to communicate with servers when using the SOAP related parameters
of the reposMigrate command. For detailed information refer to the
Configuring
security with scripting topic in the
WebSphere Application Server Information Center.
Purpose
Use the reposMigrate utility to migrate WebSphere
InterChange Server artifacts to WebSphere Process Server deployable artifacts.
Location
The command file is located in the install_root/bin directory.
The command file is a script named reposMigrate.sh for
Linux and UNIX-based operating systems and reposMigrate.bat for
Windows operating systems.
Syntax
reposMigrate -iSourceArtifactJAR -oOutputArtifactDirectory [-scell=CellName,node=NodeName,server=ServerName] [-fh] [-lfLogFileName]
[-lv] [-sh] [-sp]
[-sf] [-ai] [-r]
[-ao] [-wi]The first
two arguments are required.
Parameters
- -iSourceArtifactJAR
- Required parameter. Specifies the source artifact JAR file containing
one or more WebSphere InterChange Server artifacts in XML format.
- -oOutputArtifactDirectory
- Required parameter. Specifies the output directory where the results of
the conversion will be placed.
- [-scell=CellName,node=NodeName,server=ServerName]
- Optional parameter. Specifies that the output artifacts should be deployed
to the specified target cell, node or server as part of the reposMigrate processing.
If this option is not specified, one or more EAR files is created for later
deployment.
- [-fh]
- Optional parameter. By default reposMigrate will continue processing the
remaining artifacts in the JAR file, if an error occurs during the processing
of a certain artifact. If this option is set, the processing will stop as
soon as an error is detected. The artifact with the error and all subsequent
artifacts are not processed and no deployment is performed.
- [-lfLogFileName]
- Optional parameter. Redirects migration messages to LogFileName.
By default, error message are sent to standard out.
- [-lv]
- Optional parameter. Sets the log level to verbose.
- [-sh]
- Optional parameter. SOAP is used to communicate with the server to deploy
artifacts. Use this parameter to override the default host name for SOAP access.
The default is localhost.
- [-sp]
- Optional parameter. SOAP is used to communicate with the server to deploy
artifacts. Use this parameter to override the default port number for SOAP
access. The default is 8880.
- [-sf]
- Optional parameter. SOAP is used to communicate with the server to deploy
artifacts. Use this parameter to specify the properties file to use for SOAP
access.
- [-ai]
- Optional parameter. Warn on duplicate data-sources.
- [-r]
- Optional parameter. By default data sources are reused when possible.
If this flag is specified, a unique authentication alias and data source will
be created for each relationship that is converted.
- [-ao]
- Optional parameter. Create artifact jar files only. This option cannot
be used with the [-s] option.
- [-wi]
- Optional parameter. If this option is set, all Java conversion warning
messages are ignored.
Sample
This sample migrates existing WebSphere InterChange
Server artifacts directly to a running WebSphere Process Server:
%WAS_HOME%\bin\reposMigrate.bat -iC:\ICSRepos.jar
-oC:\IBM\WebSphere\MigratedArtifacts -scell=CellA1,node=Node4,server=Server1