You do not need to provide the JDBC database drivers for the databases above. All Oracle BPM Enterprise editions include certified JDBC drivers in the installation. You do not need to install them manually.
Note that Oracle WebLogic also includes the required JDBC drivers.
IBM WebSphere does not include the required JDBC drivers. The drivers in the Oracle BPM installation can be manually installed in WebSphere. See the BPM Configuration Guide for further information.
Support for distributed transactions, also referred to as XA, is not enabled by default with Microsoft SQL Server. In order to enable JDBC distributed transactions, 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 Oracle WebLogic Server Documentation.
Oracle BPM 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 character encoding.
No special configuration is needed for Oracle and Microsoft SQL Server databases. In these cases, Oracle BPM explicitly defines its table column types to use Unicode.
If using Sybase, you must define a page size of at least 4K to support Oracle BPM. The default page size on Sybase is 2K. If your database instance uses pages smaller that 4K, create a new Sybase instance with a page size of 4K (or bigger). Sybase provides utilities to migrate data between servers of different page sizes.
If you try to create the Oracle BPM schema database with a page size smaller than required, you may get the error messages like the following when creating Oracle BPM databases:
fuego.directory.exception.CouldNotCreateSchemaException:
Could not create schema at [jdbc:sybase:Tds:vmsybase.fuegolabs.com:5000].
600 is the maximum allowable size of an index.
Composite index specified is 1020 bytes.