Database naming restrictions

Databases cannot be reused across multiple installations of IBM® Business Process Manager. Each installation of IBM Business Process Manager requires exclusive use of its associated databases. You must configure the databases so that they can be uniquely identified.

Depending on the installation path that you select, the databases associated with an installation might be configured with default names. For example, the databases associated with IBM Business Process Manager Advanced on IBM DB2® have the following defaults:

If you have two installations of IBM Business Process Manager Advanced that use DB2, you must select, for one of the installations, an installation path that lets you specify the names instead of accepting the default values.

To ensure the uniqueness of the database names, select installation paths that prompt you for the database names.

For example, you are prompted for the database names when you use the Typical installation path. Select the option to use an existing database server instead of the default DB2 Express.
Note: When you use the Profile Management Tool to create a profile after installation, you are prompted for database names, no matter which path in the Profile Management Tool (Typical or Advanced) you choose. The only exception is when you use a database design file for your database configuration. The database design file contains the database names, user name, and password information. Thus, the Profile Management Tool does not prompt you for this information.
In contrast, you are not prompted for database names in the following cases: Additional restrictions apply to database naming. These restrictions depend on the database server that you are using.

IBM Business Process Manager Advanced Advanced installation

For IBM DB2 and Microsoft SQL Server databases, the following restrictions apply:
  • The Process Server, Performance Data Warehouse, and Common database components must be in separate databases.
  • The Process Server and Performance Data Warehouse components do not support case-sensitive databases. These databases must be case-insensitive.

For Microsoft SQL Server databases, components other than Process Server or Performance Data Warehouse require that their databases be case-sensitive.

For Oracle databases, the Process Server, Performance Data Warehouse, and Common database components must use a separate schema/user. They can use the same instance.

Note: Schema/user names in Oracle database components can contain only characters from your database character set. Oracle recommends that the user name must contain at least one single-byte character regardless of whether the database character set also contains multi-byte characters. Non-quoted schema identifiers must begin with an alphabetic character from your database character set. Quoted identifiers can begin with any character.