Migrate WebSphere InterChange Server artifacts to WebSphere InterChange
Server artifacts with the reposMigrate utility. You invoke
the utility from a command-line.
Before you begin
Note: The functionality of the resposMigrate utility is also available
from WebSphere Integration Developer. Refer to the
IBM WebSphere Integration Developer documentation ("Migrating applications using WebSphere Integration
Developer topic") for more information.)
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. These artifacts are modules created as one or
more JAR files. A JAR file is created for each collaboration object and for
each connector definition that has been migrated. 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 JAR file generated.
If no collaboration objects or connectors are migrated, a single JAR file
is created containing a module of all the shared artifacts. After the new
JAR files are created, you will use the serviceDeploy command
to deploy these artifacts to the intended WebSphere Process Server.
For
WebSphere InterChange Server artifacts that have no corresponding artifact
in WebSphere Process Server, a Jython® script is generated during migration
that can be run using the wsadmin command to create WebSphere
Process Server configuration definitions corresponding to the original WebSphere
InterChange Server artifacts. For further detail, see "InstallAdministrativeObjects.py
script" in More
information about migration from WebSphere Interchange Server .
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.
- 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.
- If desired, edit the resulting JAR file.
- Run serviceDeploy to create a deployable EAR file for each JAR
file.
Note: The support in the WPS Runtime to handle migrated ICS
applications relies on the default naming convention used by the serviceDeploy command.
IBM recommends that you do not specify the serviceDeploy -outputApplication parameter
when building migrated projects with the serviceDeploy command,
so that it will generate its default output filenames.
For
more information about the serviceDeploy command, refer
to the serviceDeploy command.
- Use the wsadmin command to install the EAR
files on WebSphere Process Server. Invoking wsadmin will
create resources in the WebSphere Process Server system for all target resources
such as JDBC data sources and WBIScheduler entries.
For
more information about the wsadmin command, refer to the
"Wsadmin tool" in the WebSphere Application Server Information Center.
Examples
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 ics-jar-file-name target-dir-name
The
reposMigrate utility builds the generated artifacts
as follows:
- For each WebSphere InterChange Server collaboration object and connector
definition in the input JAR file, reposMigrate will create
a JAR file from the migrated artifacts.
- 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 JAR file generated. If no collaboration objects nor connector
definitions were in the input, a single JAR file will be created with all
the shared artifacts.
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. 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.
Last updated: Thu 02 Nov 2006 03:41:28
(c) Copyright IBM Corporation 2005, 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)