IBM BPM, V8.0.1, All platforms > Install IBM BPM > Plan for IBM BPM > Plan the database configuration > Plan the component-specific database configurations
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.
When install an application containing selector or business rule artifacts, the server stores the artifacts in database tables.
You can then dynamically update them without changing the application. The selector and business rules group components use a database to hold the selector and business rule artifacts that are created in Integration Designer and installed on the server. If you change a selector through the administrative console, or a business rule through the Business Process Rules Manager, the database is updated with the latest information. The original artifacts in the enterprise archive (EAR) are not synchronized with updates that are made after the application is installed.
Supported database types
The selector and business rules group database can use the following database products:
| Database Types | Considerations |
|---|---|
 DB2 Express
| Used as the default database type for a stand-alone profile. |
| DB2 Universal
| Used as the database in ND configurations. Optionally, can be used as the database in stand-alone server configurations. |
| DB2 Data
Server
| Used as the database in ND configurations. Optionally, can be used as the database in stand-alone server configurations. |
|
DB2 for z/OS v8
DB2 for z/OS |
Important: When creating a profile for a server that uses DB2 for z/OS v9, the server must be able to connect to the DB2 database. Used as the database in ND configurations. Optionally, can be used as the database in stand-alone server configurations. |
| Microsoft SQL Server (Microsoft)
| |
| Oracle
| You need system database administrator privileges to create the database, tables, and schemas. If you do not have these privileges, you might receive errors when you create or access the tables and schemas. |
User ID privileges
The user credentials that you provide in pmt.sh must have the permissions necessary to create table
spaces, tables, schemas, indexes, and stored procedures. For the Create new database option, the user ID must have the necessary privileges to create a database. If the user who is running the script has the authority to create tables, the script does not require an authentication ID within the script. See Database
privileges and User ID or schema name privileges.
Database Management Service (DBMS) instances
Only one database instance is available in a stand-alone configuration or ND configuration (server or cluster of servers). All selectors and business rules for the server in a stand-alone configuration or in a cell use the same repository. There is no support for using separate database instances for different selectors or business rules.
Configuration actions during profile creation
- Stand-alone profile
- During profile creation, the Common database uses createTable to create selector and business rules tables. If you choose the default configuration, the default database is DB2. However, you cannot use multiple servers because DB2 allows only one Java™ virtual machine to access the database at a time.
- Deployment manager profile
- For ND configuration, the common database for the cell is set up with the appropriate tables for selector and business rule group components. All selectors and business rules for the server in a dmgr or custom profile use this database.
SQL scripts
For more information about the location of SQL scripts, refer to Plan to configure the common database.
JDBC provider
The selector and business rules group database uses the common database data source and JBDC provider:
Data source name:
- WPS DataSource
Data source JNDI name:
- jdbc/WPSDB
Restrictions
If you uninstall applications that contain selectors or business rules from the server or cell, artifacts stored in the common database or RepositoryDB databases are not removed. For information on how to manually remove the artifacts, see Remove business rule and selector data from the repository.
Tables
For selectors and business rule groups, there are three tables that you can use to hold the artifacts:
- AppTimestamp
- ByteStore
- ByteStoreOverflow
Exported scripts
The scripts are exported to the same location as the scripts for the common database. For more information about the location of exported scripts, refer to Plan to configure the common database.