IBM BPM, V8.0.1, All platforms > Migrating and upgrading your IBM BPM environment > Migrating from previous versions > Migrating your IBM BPM Advanced V7.5.x or WebSphere Process Server V7.x or V6.2.x runtime > Plan the runtime migration
Profiles
The runtime migration tools support the migration of IBM BPM, WebSphere Process Server, WebSphere Enterprise Service Bus, and WebSphere Application Server source profiles to the corresponding profile type on the migration target.
IBM BPM profile
An IBM BPM profile is one that WebSphere Application Server created using one of the following profile templates:
| IBM BPM configuration | Profile templates |
|---|---|
| IBM BPM Process Server Standard | default.procsvr, dmgr.procsvr, managed.procsvr |
| IBM BPM Process Center Standard | default.procctr, dmgr.procctr, managed.procctr |
| IBM BPM Process Server Advanced | default.procsvr.adv, dmgr.procsvr.adv, managed.procsvr.adv |
| IBM BPM Process Center Advanced | default.procctr.adv, dmgr.procctr.adv, managed.procctr.adv |
If you were using PMT (PMT), this means that you selected IBM BPM on the Augment Selection page.
WebSphere Process Server profile
A WebSphere Process Server profile is one that WebSphere Application Server created using one of the following profile templates: “default.wbiserver,” “dmgr.wbiserver,” or “managed.wbiserver.” If you were using PMT (PMT), this means that you selected Process Server on the Augment Selection page.
WebSphere Application Server profile
A WebSphere Application Server profile is one that WebSphere Application Server created using one of the following profile templates: “default”, “dmgr”, or “managed.” If you were using PMT (PMT), this means that you selected WebSphere Application Server on the Environment selection page.
Important: Even though the definitions listed previously refer
to pmt.sh as a tool that may have been used to create the source profiles being migrated, you cannot use pmt.sh or manageprofiles.sh to create profiles that are the target of a migration.
The runtime migration procedures
require the use of the Profile Migration Wizard or the BPMCreateTargetProfile
command-line utility to create the migration target profiles.
For example, if a migration source system contains a WebSphere Enterprise Service Bus product installation that contains a WebSphere Enterprise Service Bus stand-alone profile created from the default.esbserver template, and the same system contains a WebSphere Process Server product installation that contains a WebSphere Application Server stand-alone profile created from the default template, a WebSphere Enterprise Service Bus stand-alone profile created from the default.esbserver template, and a WebSphere Process Server stand-alone profile created from the default.wbiserver template, all four stand-alone profiles are valid sources for migration to an IBM BPM installation.
Product profile augmentation
The runtime migration tools support the migration of source profiles that have been augmented by one or more of the following products:
- IBM BPM
- WebSphere Process Server
- WebSphere Enterprise Service Bus
- IBM Business Monitor
- WebSphere Business Monitor
Because augmented source profiles are migrated to a target profile that is augmented with profile templates that provide similar capabilities, the target installation must have at least the same profile capabilities as the source installation.
For example, if a source installation contains a managed profile that has been augmented by WebSphere Process Server and WebSphere Business Monitor, the target installation directory must contain both IBM BPM Advanced and IBM Business Monitor. In this scenario, the Profile Migration Wizard or the BPMCreateTargetProfile command-line utility will create a target profile that is augmented by IBM BPM and IBM Business Monitor.
In a multi-product augmentation environment, where a cell may have clusters and nodes within profiles at various augmentation levels, the dmgr profile must be augmented at the same augmentation level as the highest augmentation level of any of the profiles on the managed nodes.