Copying the migration utilities to the source computer
If you installed IBM® Business
Process Manager V8.6.0 on a
different computer from your source environment, package the remote
migration utilities into an image and copy the image back to the source
computer. You will use the migration utilities to take a snapshot
of the previous version.
About this task
Important: To migrate to a computer with a different operating system (for example, from
Linux to Windows), or to migrate from a 32-bit to 64-bit computer, see Considerations for migrating to a different operating system or from 32-bit to 64-bit. V8.6.0 supports
64-bit platforms only.
Procedure
- On a system that has the new version installed and the same operating system as
the source environment, create a remote migration image by using the
BPMCreateRemoteMigrationUtilities command from the
target_install_root/bin directory. This image must be copied to the migration source computer and is used to
create the snapshot. Use the following syntax:
BPMCreateRemoteMigrationUtilities.sh remoteMigrationUtilities.zip
If you are migrating from a 32-bit operating system to a 64-bit operating system, see Considerations for migrating to a different operating system or from 32-bit to 64-bit. Use the following syntax:BPMCreateRemoteMigrationUtilities.sh remoteMigrationUtilities.zip 32bit
The location of the remoteMigrationUtilities.zip file is displayed when you run the BPMCreateRemoteMigrationUtilities command. If you specify only the file name and not the full path name, the remoteMigrationUtilities.zip file is created in the install_root/util/migration/scripts directory.
The BPMCreateRemoteMigrationUtilities command does not write to a log file, but displays the results in a window. For example:/opt/IBM/BPM/bin>BPMCreateRemoteMigrationUtilities.sh /opt/MigrationUtility.zip Buildfile: /opt/BPM/util/migration/scripts/createMigrationUtilDisk.ant create_zip_image: [zip] Building zip: /opt/MigrationUtility.zip BUILD SUCCESSFUL Total time: 41 seconds
After you have run the BPMCreateRemoteMigrationUtilities command, check the generated remoteMigrationUtilities.zip file and verify that it contains the following folders:- bin
- BPM
- configuration
- etc
- java
- jdbcdrivers
- lib
- plugins
- properties
- util
For more information, see the BPMCreateRemoteMigrationUtilities command-line utility command.
- Use FTP, RCP, or some other mechanism
to copy the remote migration utility image from the target system
to the source system. Then, extract the remote migration utilities
into their own unique directory on the source system. Use the unzip remoteMigrationUtilities.zip command to extract the contents of the compressed file. If there is no unzip tool on the UNIX system, either install the unzip tool manually or use the install_root/java/bin/jar xf remoteMigrationUtilities.zip command to extract the contents.Important: Ensure that all extracted files have execute permission for the logged-in user. If they do not, use the chmod command to grant execute permission for all extracted files.
- Optional: The following steps are required if
a custom resource that relies on third-party libraries, such as a
third-party JMS provider, is configured in the source environment.
The dependent third-party libraries are not migrated, so you must
copy them to the target environment manually to make the custom resource
work correctly in the target environment. For a migration
on the same computer:
- If the dependent third-party libraries are in a folder under install_root in the source environment, copy them to the same folder under install_root in the target environment.
- If the dependent third-party libraries are in a folder outside install_root in the source environment, make sure that they are in the same location in the target environment after migration.
For a migration to a different computer:
No matter where the dependent third-party libraries are placed in the source environment, copy them to the same folder in the target environment.Important: If you are migrating from a Windows system to a Linux or UNIX system, or from a Linux or UNIX system to a Windows system, besides copying the third-party libraries to the target environment, you must also modify the configuration of the custom resource so that it refers to the correct location of the libraries because of the different file path formats of the operating systems.
- Considerations for migrating to a different operating system or from 32-bit to 64-bit
To migrate to a computer with a different operating system, or to migrate from a 32-bit computer to a 64-bit computer, you must perform more migration steps.
Previous topic: Installing IBM BPM Express V8.6.0
Next topic: Checking for migration readiness
Related information: