Automatic recovery for critical failures such as database failures

Thank you for taking the time to provide your ideas to IBM. We truly value our relationship with you and appreciate your willingness to share details about your experience, your recommendations, and ideas.

We have reviewed this request with our technical team and have determined that we may already support the use case you have described in your request.

• The core product already supports recovery scenarios when B2Bi/SFG is configured correctly and is using a proper topology with sufficient redundancy

• 6.2.x introduced JDBC pooling for DB connections to reduce the time taken to recover from a primary DB node connection loss

• BPs need to be configured to leverage existing recovery mechanisms such as "on fault" features. This needs to be done on a case by case basis as the data BPs handle need to be considered to avoid data duplication or processing duplication

• If the DB pointers can be reused after an outage, B2Bi will pick up where it left off when the connection is dropped. If it cannot, manual intervention is needed by design as duplicate processing needs to be avoided

In summary, we would recommend to upgrade to version 6.2.x and ensure that your BP designs are using the existing fault-tolerant/error handling features. If you continue to experience problems, open a support case.

This is really important, whenever there is a failure with the database for a long period, some BPs remain false Active and the application needs to STOP/START for the Recovery process (BP Recover.bpml) to execute correctly.

I've seen this happen before.

Its a very important enhancement to allow that that tech product Platform be resilient and reliable. Autorecovry withou human action is very very important to us