IBM BPM, V8.0.1, All platforms > Migrating and upgrading your IBM BPM environment > Migrating from other products > Migrating from WebSphere InterChange Server or WebSphere Business Integration Server Express

Migrating WebSphere InterChange Server or WebSphere Business Integration Server Express artifacts with the reposMigrate command

Migrate WebSphere InterChange Server or WebSphere Business Integration Server Express artifacts to IBM BPM artifacts with the reposMigrate command.

The functionality of the reposMigrate command is also available from with a supporting wizard (graphical user interface). See the topic "Migrating to IBM BPM from WebSphere InterChange Server."

The reposMigrate command requires as input a WebSphere InterChange Server or WebSphere Business Integration Server Express 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.

To ensure that the repository JAR file that will be generated is self-contained, run the repos_copy command with the -vr option before exporting the server repository. This validates the repository. If the repository is valid , the repos_copy command writes the following output to the console: Validation Succeeded. All Dependencies Resolved. If the repository is not valid, the repos_copy command prints a list of the dependencies that must be resolved. Resolve the dependencies before exporting the repository.

Export the repository artifacts and create the repository JAR file, using the WebSphere InterChange Server or WebSphere Business Integration Server Express repos_copy command with the -o option. See the WebSphere InterChange Server or WebSphere Business Integration Server Express v4.3 documentation for more details, including how to export individual components.

The reposMigrate command will convert the WebSphere InterChange Server or WebSphere Business Integration Server Express artifacts in a JAR file into IBM BPM 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 that contains a module of all the shared artifacts. After the new JAR files are created, you will use the serviceDeploy command to generate the EAR files that can be deployed in IBM BPM.

For WebSphere InterChange Server or WebSphere Business Integration Server Express artifacts that have no corresponding artifact in IBM BPM, a Jython script is generated during migration that can be run using the wsadmin command to create IBM BPM configuration definitions corresponding to the original WebSphere InterChange Server or WebSphere Business Integration Server Express artifacts.


Procedure

  1. Identify the JAR file containing the pre-exported WebSphere InterChange Server or WebSphere Business Integration Server Express artifacts that are to be converted to IBM BPM deployable artifacts.

  2. Invoke the reposMigrate command from a command-line prompt. Type the command at a command prompt in IBM BPM, with the required arguments and any optional arguments you require. Refer to reposMigrate command-line utility for more information.

  3. If you want, edit the resulting JAR file.

  4. Run the serviceDeploy command to create a deployable EAR file for each JAR file.

    The support in the IBM BPM runtime environment to handle migrated WebSphere InterChange Server applications relies on the default naming convention used by the serviceDeploy command. Do not specify the serviceDeploy -outputApplication parameter when building migrated projects with the serviceDeploy command, so that it will generate its default output file names.

    For more information about the serviceDeploy command, refer to serviceDeploy command-line utility.

  5. Use the wsadmin command to run the InstallAdministrativeObjects.py script. This will create resources in the IBM BPM system for all target resources, such as JDBC data sources and WBIScheduler entries.

  6. Use the administrative console or the wsadmin command to install the EAR files on IBM BPM.


Example

You can use the reposMigrate command to migrate existing WebSphere InterChange Server or WebSphere Business Integration Server Express artifacts directly to a running IBM BPM:
  1. Open a command prompt in IBM BPM.
  2. Issue the reposMigrate command with the following mandatory parameters: target_INSTALL_ROOT\bin\reposMigrate SourceArtifactJAR OutputArtifactDirectory

The reposMigrate command builds the generated artifacts as follows:


What to do next

The default behavior of the reposMigrate command is to log errors for the migration of each individual artifact and continue to migrate the remainder of the artifacts. Check output messages for errors after the execution completes. To override this default behavior and force the reposMigrate command to end processing when the first artifact that cannot be migrated is encountered, specify the -fh (halt at first failure) flag. You can run the reposMigrate command from the beginning to retry after a failed execution.

: Migrating from WebSphere InterChange Server or WebSphere Business Integration Server Express


Related reference:

Postmigration considerations
reposMigrate command-line utility


Related information:

WebSphere InterChange Server v4.3 documentation