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 Business Process Manager Information Center |
|---|---|
| Process Center | Roadmap for installing and configuring IBM® BPM Advanced Roadmap for installing and configuring IBM BPM Standard Note: 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 Note: Profile
creation for IBM BPM Standard
enables you to configure for either Process Center or Process Server.
|
The steps required to install IBM Business Process Manager V8.0.1 differ depending on whether you want a stand-alone or a network deployment configuration. The following sections provide instructions for each type of configuration.
Installing and migrating to IBM Business Process Manager V8.0.1 stand-alone environment
Follow these steps to install IBM Business Process Manager V8.0.1 in a stand-alone configuration and then upgrade your existing databases:
- When installing IBM Business Process Manager V8.0.1
for a migration, use the Custom installation option.Note: 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.
- 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 Business Process Manager 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.
- Configure the Business Space database after profile creation as
described in Configuring
the Business Space database.
Configure the Business Process Choreographer database as described in Using a generated SQL script to create the database schema for Business Process Choreographer.
- If the target is an IBM Business Process Manager Advanced Process
Center or IBM Business Process Manager Advanced Process Server installation,
configure the Common database by completing the following steps:
- Go to the directory containing the configCommonDB.sh or configCommonDB.bat script.
You specified its location in the Database script output
directory field on the Database Configuration panel in the Profile
Management Tool. By default, this location is:
profile_root/dbscripts/CommonDB/db_type/db_name 
profile_root\dbscripts\CommonDB\db_type\db_name
Note: For Oracle, the batch file creates tables on an existing schema, so the createDB parameter should not be specified. - Use your standard database definition tools, native commands, and procedures to create the required tables by running the configCommonDB script. The script contains only basic statements for creating databases, tables, and indexes.
- Go to the directory containing the configCommonDB.sh or configCommonDB.bat script.
You specified its location in the Database script output
directory field on the Database Configuration panel in the Profile
Management Tool. By default, this location is:
- Run the upgrade utility as described in Upgrading existing databases.
- 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.
- Start and verify your migrated environment.
Installing and migrating to IBM Business Process Manager V8.0.1 network deployment environment
Follow these steps to install IBM Business Process Manager V8.0.1 in a network deployment configuration and then upgrade your existing databases:
- When installing IBM Business Process Manager 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.Note: 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.
- Create the profiles required for your network deployment environment. Important: If you are using the file user registry, you must 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 Business Process Manager Advanced Process
Center or IBM Business Process Manager Advanced Process Server, either
enable the option to initialize the database for the deployment manager
profile or configure the Common database by completing the following
steps:
- Go to the directory containing the configCommonDB.sh or configCommonDB.bat script.
You specified its location in the Database script output
directory field on the Database Configuration panel in the Profile
Management Tool. By default, this location is:
- profile_root/dbscripts/CommonDB/db_type/db_name
- profile_root\dbscripts\CommonDB\db_type\db_name
Note: For Oracle, the batch file creates tables on an existing schema, so the createDB parameter should not be specified. - Use your standard database definition tools, native commands, and procedures to create the required tables by running the configCommonDB script. The script contains only basic statements for creating databases, tables, and indexes.
- Go to the directory containing the configCommonDB.sh or configCommonDB.bat script.
You specified its location in the Database script output
directory field on the Database Configuration panel in the Profile
Management Tool. By default, this location is:
- If you are migrating to BPM Standard, the parameters for the common database are specified when creating the deployment environment.
- 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 Business Process Manager Advanced Process
Center or IBM Business Process Manager Advanced Process Server, either
enable the option to initialize the database for the deployment manager
profile or configure the Common database by completing the following
steps:
- 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.
- If you configure Business Space, either enable the option to create the tables in the post-deployment environment, or configure the Business Space database as described in Configuring the Business Space database.
- If you are migrating to BPM Advanced, and you will configure Business Process Choreographer, either enable the option to create the tables in the post-deployment environment, or configure the Business Process Choreographer database as described in Using a generated SQL script to create the database schema for Business Process Choreographer.
- Run the wsadmin command to switch to a custom user registry as described in Applying customizations.
- Run the upgrade utility as described in Upgrading existing databases.
- 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.
- Start and verify your migrated environment.