WebSphere Adapter Runtime Migration
abhishekrohira 270002KM77 Visits (1651)
This blog post deals with the procedure to perform the migration of the applications to work with the higher version of the runtime. The Adapter RAR used by the applications can also be migrated to the higher version during the migration.
Runtime Migration is basically migrating the applications and artifacts of older version of runtime( i.e. profiles, workspaces etc) to the newer version using some commands and migration tool provided by the Business Process Manager(BPM). It also provides an option to migrate the WebSphere Adapter RAR deployed in the BPM Runtime.
Note: This procedure is application for migrating to BPM v7.5 version onwards which means that user can migrate application from any older version of WPS to the BPM version 7.5 or later.
a) One should have the v7.5 or later version of BPM installed in the environment (target runtime).
b) The source runtime (older version) may be present at any location (remote or local).
c) User should create an empty sample directory named Snapshot_folder at any location.
The step by step instructions are listed below:
1. Run the command from New BPM location (Parent directory where BPM has installed)
For eg: “C:\Program Files
i. <source install root> = the Old WPS location
ii. <source profile name> = The old WPS profile where application deployed
iii. <snapshot directory> = Any directory where output is getting created.
For eg: >>BP
This command will generate an
2. If you want to migrate the
adapter RAR as well, then
→ Put the new version Adapter RAR in BPM installablesApp folder
3. Run BPMmigrate.bat from BPM installation location, specify the path of Appl
How MigrationContext handles the migration process
-Collects the connection migration tasks from old versions to new version
-Collects the module migration tasks from old versions to new version
-From each migration task, identifies the change required for each migration participant file object
-Creates the backup of current migration participant projects
-Executes the perform method, where in each change file will be executed and serialized to file system
-Incase of failure restores the backup workspace projects, and maintains consistency
The application of the older version of the runtime will be migrated to the latest version using the above steps.