JDBC Resources

There are two types of JDBC resource template, DataSource and DataSourceDirect. The only difference is that the DataSource templates use XA transaction co-ordination for the transactions performed with the database, while the DataSourceDirect templates do not.

Note: When you reconfigure the JDBC resource templates you must restart the BPM node.

There are three resource templates (and by default one resource instance for each template):

  • DataSourceBDS  Used by Business Data Services (BDS) to persist case data to the case data store via an XA-based transaction.
  • DataSource  Used by all other BPM components for database operations required when processing work items or organizational information within an XA transaction.
  • DataSourceDirect  Used by all other components for database operations required when processing work items or organizational information within a non-XA transaction.
Note: Use of XA transactions in TIBCO ActiveMatrix BPM 4.0 has been significantly reduced (providing improved system performance). As part of this change, the following JDBC resource templates are deleted as part of an upgrade from a pre-4.0 BPM system:
  • DataSourcePE  Used by Process Engine (PE) for database operations required when starting and processing process instances within an XA transaction.
  • DataSourceEC  Used by Event Collector (EC) to persist audit events to the database via an XA-based transaction.
  • DataSourceDirectPE  Used by Process Engine for database operations required when starting and processing process instances within a non-XA transaction.
  • DataSourceDirectEC  Used by Event Collector (EC) to persist audit events to the database via a non-XA based transaction.

Process Engine and Event Collector components now share the use of the common DataSource and DataSourceDirect database connection pools with other BPM components, instead of having their own pools. An end-to-end item of work is now processed as a single transaction, no matter what components are involved.

If you have upgraded from a pre-4.0 BPM system, you should review and possibly increase the Maximum Connections or Prepared Statement Cache Size values for the DataSource and DataSourceDirect resource templates to take account of this, in line with the performance of your upgraded system. As there are now less connection pools you may need to increase the number of connections per pool. See TIBCO ActiveMatrix BPM Installation and Configuration for more information about how to do this.