Plan the component-specific database configurations

IBM BPM, V8.0.1, All platforms > Install IBM BPM > Plan for IBM BPM > Plan the database configuration
Plan the component-specific database configurations

IBM BPM includes components that require database tables and specific names of the databases where the tables are stored.
Use the information in this section to familiarize yourself with IBM BPM components that your database administrator must manage, configure, and administer.
To plan your database configuration, you must know the components that you will use. Table 1 lists the IBM BPM components that require a database table, and the default names of the databases where the tables associated with these components are stored.
You can change these names if you choose, but you must remember to use the names consistently in later configuration steps.

Databases that are required by individual components
Server component Database (default name) If s

Process Server

BPMDB

The Process Server tables are used to hold, store, and track the data for the process application repository.

Performance Data Warehouse

PDWDB

Application scheduler

CMNDB (the common database)

You must create the common database before you start IBM BPM.
You must configure the CMNDB tables either during the startup of the dmgr or stand-alone server or before you start the dmgr or stand-alone server.

Business Process Choreographer

BPEDB

You must create the BPEDB before you start a server or cluster with Business Process Choreographer configured.

Business Process Choreographer Explorer reporting function

OBSRVDB

The Business Process Choreographer Explorer reporting functionality is deprecated. To monitor and report on BPEL processes, use IBM Business Monitor .

Business Space

CMNDB (the common database)

For stand-alone profiles, create the common database before you start IBM BPM. For other profiles, use the administrative console to configure Business Space. Configure a Business Space database is mandatory for using Business Space powered by WebSphere and Process Portal.Business Space powered by WebSphere provides a common interface for application users to create, manage, and integrate web interfaces across a range of IBM products.

Common Event Infrastructure (CEI)

EVENT (stores events)

CEI database configuration is not supported by pmt.sh or manageprofiles.sh.
Do not create this database for production environments because the performance of persisting events may be impacted.
The Common Base Event browser relies on the CEI database.
If you want to use the Common Base Event browser to retrieve and view logging, tracing, management, and business events in your business enterprise applications, create the CEI database manually.

Enterprise service bus
CMNDB (the common database)ESBDB
You must configure these tables either during startup of the dmgr or stand-alone server or before you start the dmgr or stand-alone server

Mediation

CMNDB (the common database)

You must create the common database before you start IBM BPM.
You must configure the CMNDB tables either during the startup of the dmgr or stand-alone server or before you start the dmgr or stand-alone server.

Recovery

CMNDB (the common database)

You must create the common database before you start IBM BPM.
You must configure the CMNDB tables either during the startup of the dmgr or stand-alone server or before you start the dmgr or stand-alone server.

Relationships

CMNDB (the common database)

You must create the common database before you start IBM BPM.
You must configure the CMNDB tables before or during the startup of the dmgr or stand-alone server.

Selectors and business rules

CMNDB (the common database)/Repository DB

You must create the common database before you start IBM BPM.
You must configure the CMNDB tables before or during the startup of the dmgr or stand-alone server.

SIBus

User created

You must configure these tables during the startup of the messaging engine or before you start the messaging engine. You can use a file store with SIBus in a stand-alone environment during profile creation. However, you cannot use a file store with SIBus in a ND environment.

Table and schema creation
Depending on your database provider, you need different database tables and schemas for your database in IBM BPM.
Plan to configure the common database
The common database configurations contain information about supported database types, script names and their locations, profile creation configuration actions, installation parameters, types of created tables, and user ID privileges.
Plan to configure the Common Event Infrastructure database
The Common Event Infrastructure (CEI) database specifications list the types of supported databases, script locations, profile configuration types, and necessary user ID privileges. You can optionally use the CEI database to store events that are captured when it is monitoring IBM BPM.
Plan to configure the Business Process Choreographer database
Business Process Choreographer requires a database. For a non-production configuration, the Business Process Choreographer database can reside in the common database. For a production configuration, the Business Process Choreographer database should be a separate, high-performance database system.
Plan to configure the messaging engine database
The messaging engine database specifications list supported database type, scripts and their locations, profile creation types, and necessary user ID privileges.
Plan to configure the selector and business rules group database
Use the selector and business rules group database specifications to find information about supported database types, scripts and their locations, profile creation configuration actions, restrictions, table names, and user ID privileges.

Plan the database configuration

Server component	Database (default name)	If s
Process Server	BPMDB	The Process Server tables are used to hold, store, and track the data for the process application repository.
Performance Data Warehouse	PDWDB
Application scheduler	CMNDB (the common database)	You must create the common database before you start IBM BPM. You must configure the CMNDB tables either during the startup of the dmgr or stand-alone server or before you start the dmgr or stand-alone server.
Business Process Choreographer	BPEDB	You must create the BPEDB before you start a server or cluster with Business Process Choreographer configured.
Business Process Choreographer Explorer reporting function	OBSRVDB	The Business Process Choreographer Explorer reporting functionality is deprecated. To monitor and report on BPEL processes, use IBM Business Monitor .
Business Space	CMNDB (the common database)	For stand-alone profiles, create the common database before you start IBM BPM. For other profiles, use the administrative console to configure Business Space. Configure a Business Space database is mandatory for using Business Space powered by WebSphere and Process Portal.Business Space powered by WebSphere provides a common interface for application users to create, manage, and integrate web interfaces across a range of IBM products.
Common Event Infrastructure (CEI)	EVENT (stores events)	CEI database configuration is not supported by pmt.sh or manageprofiles.sh. Do not create this database for production environments because the performance of persisting events may be impacted. The Common Base Event browser relies on the CEI database. If you want to use the Common Base Event browser to retrieve and view logging, tracing, management, and business events in your business enterprise applications, create the CEI database manually.
Enterprise service bus	CMNDB (the common database)ESBDB	You must configure these tables either during startup of the dmgr or stand-alone server or before you start the dmgr or stand-alone server
Mediation	CMNDB (the common database)	You must create the common database before you start IBM BPM. You must configure the CMNDB tables either during the startup of the dmgr or stand-alone server or before you start the dmgr or stand-alone server.
Recovery	CMNDB (the common database)	You must create the common database before you start IBM BPM. You must configure the CMNDB tables either during the startup of the dmgr or stand-alone server or before you start the dmgr or stand-alone server.
Relationships	CMNDB (the common database)	You must create the common database before you start IBM BPM. You must configure the CMNDB tables before or during the startup of the dmgr or stand-alone server.
Selectors and business rules	CMNDB (the common database)/Repository DB	You must create the common database before you start IBM BPM. You must configure the CMNDB tables before or during the startup of the dmgr or stand-alone server.
SIBus	User created	You must configure these tables during the startup of the messaging engine or before you start the messaging engine. You can use a file store with SIBus in a stand-alone environment during profile creation. However, you cannot use a file store with SIBus in a ND environment.