You can use the reposMigrate utility in migrating
WebSphere InterChange Server artifacts to WebSphere Process Server deployable
artifacts, and optionally to deploy them to WebSphere Process Server. The
utility can be invoked from a command-line or by using the migration wizard
from the WebSphere Process Server First Steps console.
Before you begin
The
reposMigrate utility requires as input a WebSphere
InterChange Server repository JAR file. This JAR file should be self-contained
with respect to the applications being migrated. That is, all artifacts referenced
by any of the artifacts in the JAR file, must also be contained in the JAR
file. Export these artifacts, and create the JAR file, using the WebSphere
InterChange Server
repos_copy command with the
-o option
(please refer to the
WebSphere InterChange Server v4.3 documentation for
more details, including how to export individual components).
Why and when to perform this task
The
reposMigrate utility will convert all of the
WebSphere InterChange Server artifacts in a JAR file into WebSphere Process
Server deployable artifacts and optionally deploy these artifacts to a server
running on a specified cell. Follow these steps to migrate the artifacts:
Steps for this task
- Identify the JAR file containing the pre-exported WebSphere InterChange
Server artifacts that are to be converted to WebSphere Process Server deployable
artifacts.
- Migrate these artifacts in one of two ways:
Option |
Description |
Invoke the reposMigrate utility from a
command-line prompt |
Type the command at a command prompt
in WebSphere Process Server, with the required arguments and any optional
arguments you require. |
Use the Migration wizard |
- Launch the WebSphere Process Server First Steps console and select the
Migration wizard.
- Select the option to migrate a WebSphere InterChange Server repository
JAR file.
- Browse to the required JAR file, or type the full path name of the JAR
file in the Source selection field.
- Specify or browse to the migration output directory where the results
of the migration should be placed.
- Enter any other necessary parameters and click Finish.
|
- Check the output messages for any errors.
- If you chose not to deploy the newly migrated artifacts, you can
install them into a WebSphere Process Server installation at this time.
Examples
You can use the
reposMigrate utility
to migrate existing WebSphere InterChange Server artifacts directly to a running
WebSphere Process Server:
- Open a command prompt in WebSphere Process Server.
- Issue the reposMigrate command with the deploy option:
%WAS_HOME%\bin\reposMigrate -iics-jar-file-name -otarget-dir-name -scell=MyCell,node=MyNode,server=Server1
With the deploy to server flag (
-s) specified,
the
reposMigrate utility builds and installs the generated
artifacts to WebSphere Process Server as follows:
- For each WebSphere InterChange Server collaboration object and connector
definition in the input JAR file reposMigrate will utilize serviceDeploy to
create a deployable EAR file from the migrated artifacts. After creating the
EAR files, reposMigrate will use wsadmin to
install them on WebSphere Process Server.
- For other artifacts such as business objects, maps and relationships,
a copy of all of these artifacts generated from the input JAR file will be
included in each EAR file generated and will be installed as part of the service
component architecture (SCA) module EAR.
- For all target resources, such as JDBC data sources and WBIScheduler entries,
the standard resource definition machinery (i.e., wsadmin)
will be invoked to create the resources in the WebSphere Process Server system.
You can also use the
reposMigrate utility to
migrate existing WebSphere InterChange Server artifacts into EAR files which
can then later be installed on a WebSphere Process Server:
- Open a command prompt in WebSphere Process Server.
- Issue the reposMigrate command without the deploy option:
%WAS_HOME%\bin\reposMigrate -iics-jar-file-name -otarget-dir-name
What to do next
The default behavior of the
reposMigrate utility
is to log errors for the migration of each individual artifact and continue
to migrate the remainder of the artifacts. Regardless of the manner in which
reposMigrate is
invoked, output messages should be checked for errors after the execution
completes. To facilitate examination of the output, use the logfile parameter
(
-lfLogFileName) to direct the output
into the specified file. To override this default behavior, and force reposMigrate
to end processing when the first artifact that cannot be migrated is encountered,
specify the
-fh (halt at first failure) flag. The
reposMigrate utility
can be rerun from the beginning to retry after a failed execution.