IBM BPM, V8.0.1, All platforms >
Migrating and upgrading your IBM BPM environment
Migrating refers to the process of moving applications and configuration information from an earlier version of a product to a later version of the product, or from one product to a different product. Upgrading refers to the process of installing a new release of the product on top of the previous release and updating the existing installation, configuration, and database in place.
Migrating
Migration is the movement of profiles, applications, and data associated with an earlier version of WebSphere Process Server or IBM BPM to a newly installed version of IBM BPM. With version-to-version migration (also referred to as side-by-side migration), you create a new (target) installation parallel to an existing (source) installation. You use an existing database configured in the source version, or a new database instance configured in the target version. The database type (Oracle, Microsoft SQL, DB2, DB2 for z/OS ) of the new database instance must be the same as that of the source.
Depending on the migration pattern, existing applications:
- Are migrated to the new version, where they can exploit new capabilities.
- Have binary compatibility, in which they run in the new environment but do not use any of its new features.
- Have version compatibility, in which the old binary files or artifacts are updated to the new version, but their behavior is the same as in the source environment and they do not use any new features.
Upgrading
Upgrading refers to either:
- Upgrading from one release of IBM BPM to a refresh pack or fix pack.
For example, you might upgrade from IBM BPM V8.0 to IBM BPM V8.0.1.
- Upgrading a configuration of IBM BPM by using IBM Installation Manager to install a new configuration over
a previously installed configuration in the same package group. You can upgrade from:
- IBM BPM Express to IBM BPM Standard
- IBM BPM Express to IBM BPM Advanced
- IBM BPM Standard to IBM BPM Advanced
When you upgrade, you update the existing installation, configuration, and database in the source environment.
- Upgrading from IBM BPM V8.0 to IBM BPM V8.0.1
The topics in this section describe the steps to follow when completing the upgrade from IBM BPM V8.0 to IBM BPM V8.0.1. - Upgrading configurations
Upgrade a configuration of IBM BPM by using IBM Installation Manager to install the new configuration over a previously installed configuration in the same package group. - Migrating from previous versions
You can migrate from a previous version of IBM BPM or WebSphere Process Server, or use the migration facilities provided by WebSphere Lombardi Edition.
-
Migrating from other products
You can migrate applications and configuration data from certain IBM products that existed before IBM BPM or IBM Integration Designer. - Migrating to the same version on new hardware
Use these migration procedures to migrate your existing environment, including applications and running instances, to the same version running on new hardware. - Deprecated and removed features of IBM BPM
IBM BPM extends capabilities found in previous versions of IBM Integration Developer, WebSphere Lombardi Edition, IBM BPM, WebSphere Process Server, WebSphere Enterprise Service Bus, and other business process management products. Some features of those products are deprecated and removed in IBM BPM V8.0.1.
Related tasks:
Installing fix packs and interim fixes interactively
Related reference:
Related information: