Required Database

All ALBPM Enterprise editions require a database to store directory information and process execution engine data. This database can be accessed over the network or locally installed. Studio uses a built-in database and does not have this requirement.

The following database systems are supported:
Note: You do not need to use the same database provider for directory information and process execution engine data.

Database Drivers

You do not need to provide the JDBC database drivers for the databases above. All ALBPM Enterprise editions include BEA certified JDBC drivers in the installation. You do not need to install them manually.

Users of ALBPM for WebLogic should note that BEA WebLogic server also includes the required JDBC drivers.

IBM WebSphere does not include the JDBC drivers, but the drivers in the ALBPM installation can be manually installed in WebSphere. See the Configuration Guide for further information.

Distributed Transactions with WebLogic Server and Microsoft SQL Server

Support for distributed transactions, also referred to as XA support, is not enabled by default with Microsoft SQL Server. In order to enable JDBC distributed transactions through JTA (Java Transaction API), you must install Microsoft SQL Server JDBC XA stored procedures. To do this, follow the instructions found in the Installing Stored Procedures for JTA section within the MS SQL Server Driver topic of the BEA WebLogic Server 9.2 Documentation.

Database Character Sets

ALBPM uses Unicode in order to support multiple languages.

If you are using a DB2 database, make sure it is configured for Unicode, using either the UTF-8 or UTF-16 encoding forms.

No special configuration is needed for Oracle and Microsoft SQL Server databases because, in these cases, ALBPM explicitly defines its table column types to use Unicode.