During the profile creation or augmentation process, you can choose to configure the Process Server database, Performance Data Warehouse database, and Common database. Alternatively, you can configure the databases using a design file that was generated by the database design tool.
Before you begin
Before creating a profile, you must install Microsoft SQL Server on the server that hosts the database.
Restriction: The Process Server database (BPMDB) and the Performance
Data Warehouse database (PDWDB) must NOT be case-sensitive. Other
databases can be case-sensitive.
When you create your database schemas, you must have a user ID with enough authority to create your tables. After the tables are created, the applications must have enough authority to select, insert, update, and delete information in the tables.
The following table shows the database privileges
that are required to access the data store.
Isolation level specifies the transaction
locking behavior. You should set the isolation level to READ_COMMITTED.
You can check the isolation level of the Process Server database,
the Performance Data Warehouse and the Common database with the following
SQL command: SELECT name, is_read_committed_on FROM sys.database.
You can set the isolation level with the following SQL command: ALTER
DATABASE <database> SET READ_COMMITTED ON.
| Database management system | Minimum privilege required to use the data store tables | Additional privilege required to create the data store tables |
|---|---|---|
| Microsoft SQL Server | Configure the SQL Server for SQL Server so that authentication can be based on an SQL server login ID and password. The user ID can own the tables or be a member of a group that has sufficient authority to issue TRUNCATE TABLE statements. | The user ID requires the CREATE TABLE statement privilege. |
If you plan to use Microsoft SQL
Server 2005 or Microsoft SQL
Server 2008 with a stand-alone profile, and put the messaging engine
tables into the Common database, you must create the following schemas
in the CMNDB database as owner dbo using
the SQL Server Studio. These schemas are required for the SIBus messaging
engines.
Important: You must configure these schemas either
before you start the server and messaging engine (recommended) or
while the messaging engine is starting. Note that these are the default
values if Windows Authentication is selected. You can specify different
values. For SQL Authentication, the values are the same as the specified
user IDs.
- MEDPS00 (Process Server messaging engine)
- MEDPE00 (Performance Data Warehouse messaging engine)
IBM® Business Process Manager packages
JDBC drivers for SQL Server. For information about the JDBC drivers
(including version and level information), see the 
Detailed hardware and software requirements
for IBM Business Process Manager page.
Detailed hardware and software requirements
for IBM Business Process Manager page. Note: You are responsible
for providing JDBC driver levels outside of what is packaged with IBM Business Process Manager.
You must configure XA transactions after the database is installed and before you start the server.