IBM Support

Advanced database support for IBM Business Process Manager (BPM) and IBM Business Monitor on distributed platforms

Question & Answer


Question

  1. Where can I find information about advanced database support for IBM Business Automation Workflow V18.0.0.1 and later?
  2. Which advanced configurations of IBM DB2, Oracle, and Microsoft SQL Server databases are supported for the IBM Business Process Manager and IBM Business Monitor products?

Answer

  1. See the document Advanced database support for IBM Business Automation Workflow on distributed platforms.
  2. This document outlines which configurations of IBM DB2, Oracle, and Microsoft SQL Server databases are supported for IBM Business Process Manager and IBM Business Monitor. In this document, the following information is available:

IBM has a new way for you to search, view, and collaborate with product documentation. For the most up to date product documentation about advanced database support, see the new IBM Knowledge Center .

For a complete list of hardware and software requirements, see the following websites:

Database independent limitations

  • Versions of IBM Business Process Manager earlier than Version 8.0.1.1 do not fully support all database clustering features: In case of a Database node failover these versions of the IBM Business Process Manager products react in a similar way as to a temporary database outage. When the database is not available, the IBM Business Process Manager system stops processing. It might be necessary to restart all IBM Business Process Manager nodes, depending on the database downtime.
  • Beginning with IBM Business Process Manager Version 8.0.1.1, the IBM BPM server code is aware of the SQL Exceptions passed up through the JDBC drivers and allow configurable retry count and interval.
  • IBM BPM administrators should understand the behavior of the Messaging Engine when it loses contact with its database. For example, this may occur if you are using a database clustering technique such as Oracle RAC or DB2 HADR and a database failover operation occurs. Refer to the WebSphere Application Server information for additional information:
  • During a High Availability or Disaster Recovery event that involves the unexpected failure of a IBM BPM server or database server, it is always possible that the IBM BPM system will mark a business process instance as failed. For example, in cases where it is not possible for the engine to prove the correct process instance state, the business process instance will marked as failed. A retry mechanism is in place to handle High Availability or Disaster Recovery events which typically manifest themselves in connection failures. If the retry times out before a connection to a running database node can be established, business processes can end up in that state. Therefore, after recovering from one of these events, it is important to check the system for any failed events that need to be restarted or replayed.                                        

        

Legend for database tables

  
Supported Green
Supported with Limitations Yellow
Not Supported Grey

* indicates IBM Business Process Manager Server, IBM Business Process Manager Advanced, and IBM Business Process Manager Standard only

(#) indicates which note applies in the list below the table

[#] indicates minimum database level required

Note: Required IBM BPM or IBM Business Monitor product levels are noted in the table if they are higher than the base level identified.

IBM DB2 database support for IBM Business Process Manager and IBM Business Monitor

IBM Business Process Manager* IBM Business Monitor
Versions Database software type or feature 8.6.0 CF2018.03 and later 8.6.0 CF2017.12 and earlier 8.5.7 8.5.6 8.5.5 8.5.0 8.0.1 8.0 7.5.x 8.5.7 8.5.6 8.5.5 8.0.1 8.0 7.5.x
11.1 Workgroup Server Edition IBM BPM V8.5.7.0 CF2016.09 or higher
Advanced Workgroup Server Edition IBM BPM V8.5.7.0 CF2016.09 or higher
Enterprise Server Edition IBM BPM V8.5.7.0 CF2016.09 or higher
Advanced Enterprise Server Edition IBM BPM V8.5.7.0 CF2016.09 or higher
HADR IBM BPM V8.5.7.0 CF2016.09 or higher
pureScale (1) IBM BPM V8.5.7.0 CF2016.09 or higher
10.5 Advanced Server Edition IBM BPM V8.0.1.2 or higher IBM BPM V7.5.1.2 or higher IBM Business Monitor V8.0.1.2 or higher - IBM Business Monitor V7.5.1.2 or higher

- Requires JR50127
Enterprise Server Edition IBM BPM V8.0.1.2 or higher IBM BPM V7.5.1.2 or higher IBM Business Monitor V8.0.1.2 or higher - IBM Business Monitor V7.5.1.2 or higher

- Requires JR50127
HADR IBM BPM V8.0.1.2 or higher IBM BPM V7.5.1.2 or higher IBM Business Monitor V8.0.1.2 or higher - IBM Business Monitor V7.5.1.2 or higher

- Requires JR50127
pureScale (1) IBM BPM V8.5.0.1 or higher IBM BPM V7.5.1.2 or higher - IBM Business Monitor V7.5.1.2 or higher

- Requires JR50127
10.1 Enterprise Server Edition [10.1.0.1] [10.1.0.1] [10.1.0.1] [10.1.0.1] [10.1.0.1] [10.1.0.1] [10.1.0.1] [10.1.0.1]
HADR [10.1.0.1] [10.1.0.1] [10.1.0.1] [10.1.0.1] [10.1.0.1] [10.1.0.1] [10.1.0.1] [10.1.0.1]
pureScale (1) [10.1.0.1] [10.1.0.1] [10.1.0.1] [10.1.0.1] [10.1.0.1] [10.1.0.1] [10.1.0.1] [10.1.0.1]
9.8 pureScale (1) [9.8.0.4] [9.8.0.4] [9.8.0.4] [9.8.0.4] [9.8.0.4] [9.8.0.4] [9.8.0.4] - IBM BPM V7.5.1: [9.8.0.3]

- IBM BPM V7.5: [9.8]
[9.8.0.4] [9.8.0.4] [9.8.0.4] [9.8.0.4] [9.8.0.4]
9.7 Enterprise Server Edition [9.7.0.5] [9.7.0.5] [9.7.0.5] [9.7.0.4] [9.7.0.4] [9.7.0.4] [9.7.0.4] [9.7.0.4] [9.7.0.5] [9.7.0.5] [9.7.0.4] [9.7.0.4] [9.7.0.4] [9.7.0.4]
HADR [9.7.0.5] [9.7.0.5] [9.7.0.5] [9.7.0.4] [9.7.0.4] [9.7.0.4] [9.7.0.4] [9.7.0.5] [9.7.0.5] [9.7.0.4] [9.7.0.4] [9.7.0.4]
9.5 Enterprise Server Edition [9.5.0.7] [9.5.0.7] [9.5.0.7] (2) [9.5.0.7] [9.5.0.7] [9.5.0.7]
HADR [9.5.0.7] [9.5.0.7] (2) [9.5.0.7] [9.5.0.7]

IBM DB2 limitations

  1. All IBM DB2 pureScale versions are subject to entitlement.

Oracle database support for IBM Business Process Manager and IBM Business Monitor

IBM Business Process Manager* IBM Business Monitor
Versions Database software type or feature 8.6.0 CF2018.03 and later 8.6.0 CF2017.12 and earlier 8.5.7 8.5.6 8.5.5 8.5.0 8.0.1 8.0 7.5.x 8.5.7 8.5.6 8.5.5 8.0.1 8.0 7.5.x
18C Standard Edition (7)
Enterprise Edition (7)
RAC (2,3) (7)
Data Guard (7)
Multitenant support (7)
Secure file LOBs (7)
12C R2 Standard Edition [12.2.0.1] [12.2.0.1]

IBM BPM V8.6 CF 2017.12
[12.2.0.1]
(8)
Enterprise Edition [12.2.0.1] [12.2.0.1]

IBM BPM V8.6 CF 2017.12
[12.2.0.1]
(8)
RAC (2,3) [12.2.0.1] [12.2.0.1]

IBM BPM V8.6 CF 2017.12
[12.2.0.1]
(8)
Data Guard [12.2.0.1] [12.2.0.1]

IBM BPM V8.6 CF 2017.12
[12.2.0.1]
(8)
Multitenant support [12.2.0.1] [12.2.0.1]

IBM BPM V8.6 CF 2017.12
[12.2.0.1]
(8)
Secure file LOBs [12.2.0.1] [12.2.0.1]

IBM BPM V8.6 CF 2017.12
[12.2.0.1]
(8)
12C R1 Standard Edition [12.1.0.1.0] [12.1.0.1.0] [12.1.0.1.0] [12.1.0.1.0] [12.1.0.1.0] [12.1.0.1.0]

IBM BPM V8.5.0.2
[12.1.0.1.0]

IBM BPM V8.0.1.3 or higher
[12.1.0.1.0] [12.1.0.1.0] [12.1.0.1.0]
Enterprise Edition [12.1.0.1.0] [12.1.0.1.0] [12.1.0.1.0] [12.1.0.1.0] [12.1.0.1.0] [12.1.0.1.0]

IBM BPM V8.5.0.2
[12.1.0.1.0]

IBM BPM V8.0.1.3 or higher
[12.1.0.1.0] [12.1.0.1.0] [12.1.0.1.0]
RAC (2,3) [12.1.0.1.0] [12.1.0.1.0] [12.1.0.1.0] [12.1.0.1.0] [12.1.0.1.0] [12.1.0.1.0]

IBM BPM V8.5.0.2
[12.1.0.1.0]

IBM BPM V8.0.1.3 or higher
(5)
[12.1.0.1.0]
(5)
[12.1.0.1.0]
(5)
[12.1.0.1.0]
Data Guard [12.1.0.1.0] [12.1.0.1.0] [12.1.0.1.0] [12.1.0.1.0] [12.1.0.1.0] [12.1.0.1.0]

IBM BPM V8.5.0.2
[12.1.0.1.0]

IBM BPM V8.0.1.3 or higher
[12.1.0.1.0] [12.1.0.1.0] [12.1.0.1.0]
Multitenant support [12.1.0.1.0] [12.1.0.1.0] [12.1.0.1.0]

IBM BPM V8.5.7.0 CF2016.09 or higher
Secure file LOBs [12.1.0.1.0] [12.1.0.1.0] [12.1.0.1.0] [12.1.0.1.0] [12.1.0.1.0] [12.1.0.1.0]

IBM BPM V8.5.0.2
[12.1.0.1.0] [12.1.0.1.0] [12.1.0.1.0]
11G R2 Standard Edition (4) [11.2.0.2] [11.2.0.2] [11.2.0.2] [11.2.0.2] [11.2.0.2] [11.2.0.2] [11.2.0.2] [11.2.0.2] [11.2.0.2] [11.2.0.2] [11.2.0.2] [11.2.0.2] [11.2.0.2]
Enterprise Edition [11.2.0.2] [11.2.0.2] [11.2.0.2] [11.2.0.2] [11.2.0.2] [11.2.0.2] [11.2.0.2] [11.2.0.2] [11.2.0.2] [11.2.0.2] [11.2.0.2] [11.2.0.2] [11.2.0.2]
RAC (1,2,3) [11.2.0.2] [11.2.0.2] [11.2.0.2] [11.2.0.2] [11.2.0.2] [11.2.0.2]

IBM BPM V8.0.1.1 or higher
[11.2.0.2] (5)
[11.2.0.2]
(5)
[11.2.0.2]
(5)
[11.2.0.2]
[11.2.0.2] [11.2.0.2] [11.2.0.2]
Data Guard [11.2.0.2] [11.2.0.2] [11.2.0.2] [11.2.0.2] [11.2.0.2] [11.2.0.2] [11.2.0.2] [11.2.0.2] [11.2.0.2] [11.2.0.2] [11.2.0.2] [11.2.0.2]
Secure file LOBs [11.2.0.2] [11.2.0.2] [11.2.0.2] [11.2.0.2] [11.2.0.2] [11.2.0.2] [11.2.0.2] [11.2.0.2]
11G R1 Standard Edition (4) [11.1.0.7] [11.1.0.7] [11.1.0.7] [11.1.0.7] [11.1.0.7] [11.1.0.7] [11.1.0.6] [11.1.0.7] [11.1.0.7] [11.1.0.7] [11.1.0.7] [11.1.0.7] [11.1.0.6]
Enterprise Edition [11.1.0.7] [11.1.0.7] [11.1.0.7] [11.1.0.7] [11.1.0.7] [11.1.0.7] [11.1.0.6] [11.1.0.7] [11.1.0.7] [11.1.0.7] [11.1.0.7] [11.1.0.7] [11.1.0.6]
RAC (1,2,3) [11.1.0.7] [11.1.0.7] [11.1.0.7] [11.1.0.7] [11.1.0.7]

IBM BPM V8.0.1.1 or higher
[11.1.0.7] (5)
[11.1.0.7]
(5)
[11.1.0.7]
(5)
[11.1.0.7]
[11.1.0.7] [11.1.0.7]
Data Guard [11.1.0.7] [11.1.0.7] [11.1.0.7] [11.1.0.7] [11.1.0.7] [11.1.0.7] [11.1.0.7] [11.1.0.7] [11.1.0.7] [11.1.0.7] [11.1.0.7]
Secure file LOBs [11.1.0.7] [11.1.0.7] [11.1.0.7] [11.1.0.7] [11.1.0.7] [11.1.0.7] [11.1.0.7]
10G R2 Standard Edition [10.2.0.2]
Enterprise Edition [10.2.0.2]

Oracle limitations

  1. Beginning with IBM Business Process Manager Version 8.0.1.1, Oracle RAC is supported in active/active and active/passive modes. Prior to version 8.0.1.1, Oracle RAC is only supported in active/passive mode.
  2. Manual interventions are required in the database configuration to set up the IBM Business Process Manager products with Oracle RAC. These limitations are described in the following topics:
  3. IBM Business Process Manager does not use the Oracle RAC Fast Application Notification (FAN) feature.
  4. IBM Business Monitor does not support Oracle RAC in active/active mode.
  5. Oracle Database 11G Standard Edition One R1 and Oracle Database 11G Standard Edition One R2 are not supported.
  6. Oracle Database 11G Enterprise Edition R2 and Oracle Database 11G Standard Edition R2 are deprecated in IBM BPM V8.6 CF 2017.12 and removed in IBM BPM V8.6 CF 2018.03.
  7. IBM Cognos Business Intelligence 10.2.2 does not support Oracle 18C and cannot be installed. Cognos-related functionality, including the Report Viewer and Report Designer widgets, is not supported.
  8. Oracle 12C R2 support requires IBM Cognos Business Intelligence 10.2.2 Fix Pack 8.

Note: The Oracle Exadata product can be used to provide the infrastructure for several Oracle database versions that are supported by IBM Business Process Manager (BPM). Although IBM BPM does not leverage any specific features of Oracle Exadata, you can run IBM BPM databases on Oracle Exadata if the corresponding Oracle database version is supported by IBM BPM.


Microsoft SQL Server database support for IBM Business Process Manager and IBM Business Monitor

IBM Business Process Manager* IBM Business Monitor
Versions Database software type or feature 8.6.0 8.5.7 8.5.6 8.5.5 8.5.0 8.0.1 8.0 7.5.x 8.5.7 8.5.6 8.5.5 8.0.1 8.0 7.5.x
2017 Enterprise Edition (1,2,8) IBM BPM V8.6 CF 2018.03 or higher
FCI (4)
Always on Availability (3)
2016 Enterprise Edition (1,2,8)
FCI (4)
Always on Availability (3)
2014 Enterprise Edition (1,2,8)
FCI (4)
Always on Availability (3)
2012 Enterprise Edition (1,2,8) IBM BPM V8.0.1.3 or higher IBM Business Monitor V8.0.1.3 or higher
FCI (4)
Always on Availability (3)
2008 R2 Enterprise Edition (1,2,8)
FCI (4)
2008 Enterprise Edition (1,2,8) (6) (6) (6) (6) (6) (6)
FCI (4)
2005 Enterprise Edition (1,2,8) (7)
[2005 SP3]
(7)
[2005 SP3]
[2005 SP3] (7)
[2005 SP3]
(7)
[2005 SP3]
FCI (4)


Microsoft SQL Server limitations

  1. XA transactions must be configured.
  2. High Availability events require manual intervention -- As described on the Microsoft Support website ( http://support.microsoft.com/en-us/kb/3005016 ) loss of communication between the IBM BPM server and its database (for example, caused by a software or network failure) may result in orphaned transactions that persist in the database and hold resources (such as database locks) active indefinitely. Resolving these orphaned transactions may require manual rollback or restarting the IBM BPM and Database servers. More details can be found on the IBM Support site: http://www.ibm.com/support/docview.wss?uid=swg21633692
    Important: Be aware that many customers find that this manual intervention can undermine the high availability behavior you are attempting.
  3. AlwaysOn Availability Groups: As described on the Microsoft Support site ( https://msdn.microsoft.com/en-us/library/ms366279.aspx ), AlwaysOn Availability Groups is not supported for applications that make use of distributed transactions, so this feature should not be used with IBM BPM.
  4. Failover Cluster Instances (FCI): IBM BPM has not been certified using the FCI feature with the databases housing the IBM BPM product data. Therefore, the IBM BPM support teams might require that problems under investigation be reproduced without this feature present to continue problem determination activities. The intermittent nature of the issues that might occur during a High Availability event makes this reproduction extremely challenging. Therefore, it is not recommended to use the FCI feature with IBM BPM.
  5. The WebSphere Application Server software upon which IBM BPM is built does not declare formal support for FCI. Support for this feature falls under the ‘Other Categories’ description available at the WebSphere support site: http://www.ibm.com/support/docview.wss?uid=swg27004311 . IBM BPM support takes the same position as the WebSphere base.
  6. WebSphere Application Server does not support storing transaction logs in Microsoft SQL Server. Because of this limitation, IBM BPM and IBM Business Monitor do not support database-managed replication options.
  7. Microsoft SQL Server Enterprise Edition 2005 is deprecated for IBM BPM versions 8.0.x and IBM Business Monitor versions 8.0.x.
  8. Microsoft SQL Server Enterprise Edition 2008 is deprecated for IBM BPM versions 8.5.x and IBM Business Monitor version 8.5.5. It is removed for IBM BPM V8.6 CF 2018.03.
  9. Microsoft SQL Server Enterprise Edition 2008 R2 is deprecated for IBM BPM V8.5.7 and IBM Business Monitor V8.5.7. It is removed for IBM BPM V8.6 CF 2018.03.
  10. IBM BPM V8.6.0 (2017.09) and later releases only support the sqljdbc42.jar driver. Before you can use the sqljdbc42.jar driver with IBM BPM V8.6.0 (2017.09) or IBM BPM V8.6.0 cumulative fix (CF) 2017.12, you must apply the IBM BPM interim fix JR59388.
     

Internal Use Only

Link no longer works, removed before publishing - SP


Link no longer works, removed before publishing - SP
Refer to this Request for Enhancement for additional information: https://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=66915
(Note: You must log in with your IBM ID to access this link.)


This document outlines which configurations of IBM DB2, Oracle, and Microsoft SQL Server databases are supported for IBM Business Process Manager and IBM Business Monitor. In this document, the following information is available:

IBM has a new way for you to search, view, and collaborate with product documentation. For the most up to date product documentation about advanced database support, see the new IBM Knowledge Center .


For a complete list of hardware and software requirements, see the following websites.

Oracle database support for IBM Business Process Manager and IBM Business Monitor

IBM Business Process Manager* IBM Business Monitor
Database Versions 8.5.5
8.5.6
8.5.0 8.0.1 8.0 7.5.x 8.5.5
8.5.6
8.0.1 8.0 7.5.x
Oracle 10G
11G R1
11G R2
12C R1
Oracle Data Guard 10G
11G R1
11G R2
12C R1
Oracle RAC 10G
11G R1
11G R2
12C R1

IBM DB2 database support for IBM Business Process Manager and IBM Business Monitor

IBM Business Process Manager* IBM Business Monitor
Database Versions 8.5.5
8.5.6
8.5.0 8.0.1 8.0 7.5.x 8.5.5
8.5.6
8.0.1 8.0 7.5.x
DB2 9.1
9.5
9.7
10.1
10.5
DB2 HADR 9.1
9.5
9.7
10.1
10.5
DB2 pureScale 9.8
10.1
10.5

Microsoft SQL Server database support for IBM Business Process Manager and IBM Business Monitor

IBM Business Process Manager* IBM Business Monitor
Database Versions 8.5.5
8.5.6
8.5.0 8.0.1 8.0 7.5.x 8.5.5
8.5.6
8.0.1 8.0 7.5.x
Microsoft SQL Server Enterprise Edition 2005
2008 R2
2012
2014

*IBM Business Process Manager Advanced and IBM Business Process Manager Standard only

Legend:

Supported
Supported with limitations
Not supported

IBM Business Process Manager Advanced and IBM Business Process Manager Standard database support by product version


IBM Business Monitor database support by product version

Database independent limitations

  • Stand-alone message engine issue:
  • In case of -aa database fail-over (or temporarily outage) the message engines on a stand alone server will force a Business Process Manager server shutdown. A Business Process Manager server restart using an alternate database node (the new primary DB cluster node) requires manual intervention on the Business Process Manager stand alone server.
  • Use a clustered message engine topology.
  • Versions of IBM Business Process Manager earlier than Version 8.0.1.1 do not fully support all database clustering features: In case of a Database node failover these versions of the IBM Business Process Manager products react in a similar way as to a temporary database outage. When the database is not available, the IBM Business Process Manager system stops processing. It might be necessary to restart all IBM Business Process Manager nodes, depending on the database downtime.
  • Beginning with IBM Business Process Manager Version 8.0.1.1, the IBM BPM server code is aware of the SQL Exceptions passed up through the JDBC drivers and allow configurable retry count and interval.
  • During a High Availibility event that involves the unexpected failure of a IBM BPM Server or a Database server it is always possible that the IBM BPM system will mark a business process instance as failed (for example, in cases where it is not possible for the engine to prove the correct process instance state).
  • For business process definition (BPD) processes following document describes how to use the Process Inspector to repair these instances: Process recovery issues with business process definitions (BPD) in IBM Business Process Manager Versions 7.5.x and 8.0.x.


Oracle RAC limitations


For more information about configuring the IBM Business Process Manager products with Oracle RAC, see Failover Scenarios in a Highly Available WebSphere Business Process Management V7 Production Environment . This document was written for Oracle RAC 11g with WebSphere Process Server V7.0.0 Fix Pack 2 and WebSphere Business Monitor V7.0.0 Fix Pack 2. It describes the manual configuration steps that are needed. You can apply these steps to the IBM Business Process Manager products.


Microsoft SQL Server limitations

  • High Availability Events require manual intervention:
  • As described on the Microsoft Support website ( http://support.microsoft.com/en-us/kb/3005016 ) loss of communication between the IBM BPM server and its database (for example, caused by a software or network failure) may result in orphaned transactions that persist in the database and hold resources (such as database locks) active indefinitely. Resolving these orphaned transactions may require manual rollback or restarting the IBM BPM and Database servers. More detail can be found at: http://www.ibm.com/support/docview.wss?uid=swg21633692
  • Microsoft SQL Server database clustering techniques:
  • Always On Availability Groups: As described on the Microsoft Support site, Always On Availability Groups is not supported for applications that make use of distributed transactions, so this feature should not be used with IBM BPM.
  • Failover Cluster Instances (FCI): The WebSphere Application Server software upon which IBM BPM is built does not declare formal support for FCI. Support for this feature falls under the ‘Other Categories’ description available at the WebSphere support site: http://www.ibm.com/support/docview.wss?uid=swg27004311 . IBM BPM support takes the same position as the WebSphere base.

In this document, the following information is available:

IBM has a new way for you to search, view, and collaborate with product documentation. For the most up to date product documentation about advanced database support, see the new IBM Knowledge Center .


For a complete list of hardware and software requirements, see the following websites.

Advanced database support for Business Process Manager and Business Monitor products

IBM Business Process Manager* IBM Business Monitor
Database Versions 8.5.5
8.5.6
8.5.0 8.0.1 8.0 7.5.x 8.5.5
8.5.6
8.0.1 8.0 7.5.x
Oracle 10G
11G R1
11G R2
12C R1
Oracle Data Guard 10G
11G R1
11G R2
12C R1
Oracle RAC 10G
11G R1
11G R2
12C R1
IBM Business Process Manager* IBM Business Monitor
Database Versions 8.5.5
8.5.6
8.5.0 8.0.1 8.0 7.5.x 8.5.5
8.5.6
8.0.1 8.0 7.5.x
DB2 9.1
9.5
9.7
10.1
10.5
DB2 HADR 9.1
9.5
9.7
10.1
10.5
DB2 pureScale 9.8
10.1
10.5
IBM Business Process Manager* IBM Business Monitor
Database Versions 8.5.5
8.5.6
8.5.0 8.0.1 8.0 7.5.x 8.5.5
8.5.6
8.0.1 8.0 7.5.x
Microsoft SQL Server Enterprise Edition 2005
2008 R2
2012
2014

*IBM Business Process Manager Advanced and IBM Business Process Manager Standard only

Legend:
 

Supported
Supported with limitations
Not supported


IBM Business Process Manager Advanced and IBM Business Process Manager Standard


IBM Business Monitor

Database independent limitations

  • Stand-alone message engine issue
  • In case of a database fail-over (or temporarily outage) the message engines on a stand alone server will force a Business Process Manager server shutdown. A Business Process Manager server restart using an alternate database node (the new primary DB cluster node) requires manual intervention on the Business Process Manager stand alone server.
  • Use a clustered message engine topology.
  • Versions of IBM Business Process Manager earlier than Version 8.0.1.1 do not fully support all database clustering features: In case of a Database node failover these versions of the IBM Business Process Manager products react in a similar way as to a temporary database outage. When the database is not available, the IBM Business Process Manager system stops processing. It might be necessary to restart all IBM Business Process Manager nodes, depending on the database downtime.
  • Beginning with IBM Business Process Manager Version 8.0.1.1, the IBM BPM server code is aware of the SQL Exceptions passed up through the JDBC drivers and allow configurable retry count and interval.
  • During a High Availibility event that involves the unexpected failure of a BPM Server or a Database server it is always possible that the BPM system will mark a business process instance as failed (for example, in cases where it is not possible for the engine to prove the correct process instance state).
  • For business process definition (BPD) processes following document describes how to use the Process Inspector to repair these instances: Process recovery issues with business process definitions (BPD) in IBM Business Process Manager Versions 7.5.x and 8.0.x.
     











































  •  

Oracle RAC limitations


For more information about configuring the IBM Business Process Manager products with Oracle RAC, see Failover Scenarios in a Highly Available WebSphere Business Process Management V7 Production Environment . This document was written for Oracle RAC 11g with WebSphere Process Server V7.0.0 Fix Pack 2 and WebSphere Business Monitor V7.0.0 Fix Pack 2. It describes the manual configuration steps that are needed. You can apply these steps to the IBM Business Process Manager products.


Microsoft SQL Server limitations

  • High Availability Events require manual intervention:
  • As described on the Microsoft Support website ( http://support.microsoft.com/en-us/kb/3005016 ) loss of communication between the BPM server and its database (for example, caused by a software or network failure) may result in orphaned transactions that persist in the database and hold resources (such as database locks) active indefinitely. Resolving these orphaned transactions may require manual rollback or restarting the BPM and Database servers. More detail can be found at: http://www.ibm.com/support/docview.wss?uid=swg21633692
  • Microsoft SQL Server database clustering techniques:
  • Always On Availability Groups: As described on the Microsoft Support site, Always On Availability Groups is not supported for applications that make use of distributed transactions, so this feature should not be used with IBM BPM.
  • Failover Cluster Instances (FCI): The WebSphere Application Server software upon which BPM is built does not declare formal support for FCI. Support for this feature falls under the ‘Other Categories’ description available at the WebSphere support site: http://www.ibm.com/support/docview.wss?uid=swg27004311 . BPM support takes the same position as the WebSphere base.

7.5 --> http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r5mx/index.jsp?topic=/com.ibm.wbpm.imuc.ebpm.doc/topics/tcnfg_oracle_rac.html

7.5.1 --> http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r5m1/index.jsp?topic=/com.ibm.wbpm.imuc.ebpm.doc/topics/tcnfg_oracle_rac.html

8.0 --> TBD

Original tables:

IBM Business Process Manager Advanced IBM Business Process Manager Standard IBM Business Monitor
Database Versions 8.0.0 7.5.x 8.0.0 7.5.x 8.0.0 7.5.x
Oracle 10G
11G R1
11G R2
Oracle Data Guard 10G
11G R1
11G R2
Oracle RAC 10G
11G R1
11G R2

IBM Business Process Manager Advanced IBM Business Process Manager Standard IBM Business Monitor
Database Versions 8.0.0 7.5.x 8.0.0 7.5.x 8.0.0 7.5.x
DB2 9.1
9.5
9.7
DB2 HADR 9.1
9.5
9.7
DB2 pureScale 9.8


Legend:

Supported
Supported with limitations
Not supported

Backup - 12/17/2012 - Joseph Lam

DB2 and Oracle advanced database support for Business Process Manager and Business Monitor products
In this document, the following information is available:

For a complete list of hardware and software requirements, visit the following websites.


The following tabs list the DB2 and Oracle database versions that are supported, supported with limitations, and are not supported.

IBM Business Process Manager Advanced

Tab navigation


IBM Business Process Manager Standard

Tab navigation

IBM Business Monitor

Tab navigation


Database independent limitations

  • Failed business process definition (BPD) processes

    You might experience process recovery issues in certain situations in IBM Business Process Manager V7.5 and 8.0.x. Refer to the following document: You might experience process recovery issues in certain situations in IBM Business Process Manager V7.5 .
     
  • Stand alone message engine issue
  • In case of a database fail-over (or temporarily outage) the message engines on a stand alone server will by default force a Business Process Manager server shutdown. A Business Process Manager server restart using an alternate database node (the new primary DB cluster node) requires manual intervention on the Business Process Manager stand alone server.
  • Use a clustered message engine topology to avoid the previously described behavior.

Oracle RAC limitations

  • In case of an Oracle RAC node failover, the IBM Business Process Manager products react in a similar way as it does in a temporary Oracle database outage. When the database is not available, the IBM Business Process Manager system stops processing. It might be necessary to restart all IBM Business Process Manager nodes, depending on the database downtime.
  • For business process definition (BPD) processes in the IBM Business Process Manager products, limitations apply that are described in the following document: You might experience process recovery issues in certain situations in IBM Business Process Manager V7.5 .
  • Certain scalability capabilities offered by Oracle RAC, such as multiple active database nodes concurrently active, are not supported.
  • All known Business Process Manager testing with Oracle RAC has been done in active/passive mode. Using the active/active mode now supports distributed transaction processing (DTP).


For more information about configuring the IBM Business Process Manager products with Oracle RAC, see Failover Scenarios in a Highly Available WebSphere Business Process Management V7 Production Environment . This document was written for Oracle RAC 11g with WebSphere Process Server V7.0.0 Fix Pack 2 and WebSphere Business Monitor V7.0.0 Fix Pack 2. It describes the manual configuration steps that are needed. You can apply these steps to the IBM Business Process Manager products.

[{"Product":{"code":"SS3PUM","label":"IBM Business Process Manager"},"Business Unit":{"code":"BU004","label":"Hybrid Cloud"},"Component":"Installation \/ Configuration","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"8.6.0.0","Edition":"IBM Business Process Manager Server"},{"Product":{"code":"SSFTDH","label":"IBM Business Process Manager Standard"},"Business Unit":{"code":"BU004","label":"Hybrid Cloud"},"Component":"Installation \/ Configuration","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"8.5.7;8.5.6;8.5.5;8.5;8.0.1;8.0;7.5.1;7.5","Edition":""},{"Product":{"code":"SS7NQD","label":"IBM Business Monitor"},"Business Unit":{"code":"BU004","label":"Hybrid Cloud"},"Component":"Monitor Configuration","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"8.5.7;8.5.6;8.5.5;8.0.1;8.0;7.5.1;7.5","Edition":""},{"Product":{"code":"SSFTN5","label":"IBM Business Process Manager Advanced"},"Business Unit":{"code":"BU004","label":"Hybrid Cloud"},"Component":"Installation \/ Configuration","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"8.5.7;8.5.6;8.5.5;8.5;8.0.1;8.0;7.5.1;7.5","Edition":""}]

Product Alias/Synonym

BPM;Monitor

Document Information

Modified date:
15 May 2019

UID

swg21578920