IBM BPM, V8.0.1, All platforms > Migrating and upgrading your IBM BPM environment > Migrating from previous versions > Migrating from IBM BPM Standard V7.5.x, Teamworks 7, or WebSphere Lombardi Edition > Migrating to IBM BPM V8.0.1

Install IBM BPM V8.0.1 for migration

Install the Process Center and then install a Process Server for each runtime environment that you require (for example, staging, test, and production environments).

For installation instructions, refer to the appropriate topics for your IBM BPM configuration, as described in the following table:

Installation Installation instructions in IBM BPM Information Center
Process Center

Roadmap for install IBM BPM Advanced

Roadmap for install IBM BPM Standard

Profile creation for IBM BPM Standard enables you to configure for either Process Center or Process Server.

Process Server (runtime environment)

Roadmap for installing and configuring IBM BPM Advanced: Process Server

Roadmap for installing and configuring IBM BPM Standard

Profile creation for IBM BPM Standard enables you to configure for either Process Center or Process Server.

The steps required to install IBM BPM V8.0.1 differ depending on whether you want a stand-alone or a ND configuration. The following sections provide instructions for each type of configuration.


Installing and migrating to IBM BPM V8.0.1 stand-alone environment

Follow these steps to install IBM BPM V8.0.1 in a stand-alone configuration and then upgrade your existing databases:

  1. When installing IBM BPM V8.0.1 for a migration, use the Custom installation option.

    You must perform a custom installation when migrating. The default profile that is created using the Typical installation option does not have the option to delay the database table creation. Using a previous version of an existing database during a typical installation will corrupt the database and make your environment unusable.

    Install the latest fix pack level of the target environment and any migration or upgrade-related interim fixes before you create the profiles for migration.

  2. Create a stand-alone profile for your server. When creating this profile, be sure that you:

    • Specify the parameters for the existing databases (Process Server and Performance Data Warehouse) that you will be upgrading and using with IBM BPM V8.0.1.

    • Specify the parameters for the common database when installing IBM BPM Advanced Process Center or Process Server.
    • Do not enable the option to run database scripts to initialize the databases. The upgrade utility described in Upgrading existing databases performs all the necessary database and system data initialization for IBM BPM V8.0.1.

  3. Configure the Business Space database after profile creation as described in Configure the Business Space database. If the target is an IBM BPM Advanced Process Center or IBM BPM Advanced Process Server installation, configure the common database as described in Upgrading existing databases and the Business Process Choreographer database as described in Use a generated SQL script to create the database schema for Business Process Choreographer.

  4. Run the upgrade utility as described in Upgrading existing databases.

  5. If you used the internal Lombardi security provider in conjunction with an external LDAP security provider (such as Active Directory) in your previous Lombardi installation, configure LDAP as described in Applying customizations as soon as you have completed upgrading your existing databases.

  6. Start and verify your migrated environment.


Installing and migrating to IBM BPM V8.0.1 ND environment

Follow these steps to install IBM BPM V8.0.1 in an ND configuration and then upgrade your existing databases:

  1. When installing IBM BPM V8.0.1 for a migration, it is recommended that you use the Custom installation option, which provides more control over the setting of properties during the installation.

    Install any migration or upgrade-related interim fixes and the latest level fix pack level of the target environment before you create the profiles for migration.

  2. Create the profiles required for your ND environment.

    If you are using the file user registry, use the same profile administrator user name and password on the new system that you used on the legacy system. Otherwise, after the migration, you will not be able to log on to the new system, because your newly created profile administrator will not be in the migrated file user registry.

    • If you are migrating to BPM Advanced: When creating the profiles, be sure that you specify the parameters for the common database when installing IBM BPM V8.0.1. If the target platform is IBM BPM Advanced Process Center or IBM BPM Advanced Process Server, either enable the option to initialize the database for the dmgr profile or configure the common database as described in Upgrading existing databases after the dmgr profile creation.

    • If you are migrating to BPM Standard, the parameters for the common database are specified when creating the deployment environment.

  3. Create a new deployment environment. When creating the deployment environment, be sure that you do not enable the option to create tables for each Process Server and Performance Data Warehouse database. The upgrade utility described in Upgrading existing databases performs all the necessary database creation and system data initialization for IBM BPM V8.0.1.

  4. Run the wsadmin command to switch to a custom user registry as described in Applying customizations.

  5. Run the upgrade utility as described in Upgrading existing databases.

  6. If you used the internal Lombardi security provider in conjunction with an external LDAP security provider (such as Active Directory) in your previous Lombardi installation, configure LDAP as described in Applying customizations as soon as you have completed upgrading your existing databases and have switched to a custom user registry.

  7. Start and verify your migrated environment.

: Migrating to IBM BPM V8.0.1


Related concepts:
Upgrading existing databases


Related information:
upgradeProcessData command-line utility