This blog is split into the following 3 parts to keep it simple and compact:
Part 1 of 3: Pre-migration considerations
This blog explains the sequential steps that are required to migrate an IBM Business Process Manager Standard Version 7.5.x to 8.0 using an existing database. As you may be aware, migration can be very complex and time consuming and it is very important to follow the steps in sequence to avoid potential issues. I hope this post helps you to avoid pitfalls and successfully migrate your IBM Business Process Manager environment. It focuses on migrating an IBM Business Process Manager Standard set up with a stand-alone Process Center, remote messaging, remote support, and web deployment pattern process server.
- IBM Business Process Manager Standard V7.5.1 on source machine
- IBM Business Process Manager Standard V8.0 is installed in the following path for this exercise: E:\IBM\bpm80
Before migrating, you need to backup the whole source environment. Follow these steps:
- Check the SystemOut.log file on the source machine (IBM Business Process
Manager V7.5.x ). If you find any unexpected errors, then resolve them
- Make a note of
the database-related information such as database, schema, user names, and
password that are used by IBM Business Process Manager V7.5.x as these details are
required to create the target environment.
- Make a note of the passwords that are used by various users such as tw_admin,
tw_user, tw_author, and tw_webservice. It would be useful to reset the
passwords in the target environment as they are changed during the
migration process to the default administrator password that was used in the profile creation process.
- Stop the AppTarget, support, web, messaging, node agents, and deployment manager in that order in the source system.
- Back up the IBM Business Process Manager V7.5.x environment.
Backup the full Business Process Manager V7.5.x installation
directory ( Process Center and each runtime environment ), depending on
your platform. On the Windows operating system, back up the directory as
a compressed (.zip) file. On Unix-based operating systems, use the “tar -cvf” command to back up the directory.
Run the backupConfig command to back up the configuration files
for the Process Center, deployment manager, and every node. For example: C:\BPM751\bin>backupConfig C:\BPM751\profileBackup\Dmgr.zip -profileName Dmgr01
It is always a good idea to back up Installation Manager as explained
in Backing up and restoring Installation Manager.
- Back up the itemized customization files.
If you have changed the configuration settings for the Process
Center using the 100Custom.xml file, you need to have a copy of that
file available. This file enables you to easily apply your customized
settings to the target system. If you have changed
the configuration settings by directly editing the configuration files, such as
99Local.xml and 00Static.xml, be sure to backup the files for each
altered file in each installation.
- Back up the databases that are used by IBM Business Process Manager V 7.5.x
and those databases that are used for the deployed applications. Backup
the following databases that are configured by any of the migration
source profiles according to the documentation for your databases:
Back up the .nifRegistry file. The .nifRegistry file identifies the
installation root for all of the installed IBM Business Process Manager V 7.5.x
products. It also identifies the installation root for all of the installed
WebSphere Application Server products. It is located at the following directories:
- Process Server database
- Performance Data Warehouse database
- Messaging engine database
Note: Back up both the Process Center database as well as the databases in each runtime environment.
Take a backup of the source tranlog and Partnerlog files. They
are located in the <Install Root>/profiles/<profile
- Linux/UNIX-based operating systems: /opt/.ibm/.nif/.nifregistry
- Windows operating systems: C:\Windows\.nifregistry
Continue to Part 2