This portal is to open public enhancement requests for IBM Sterling products and services. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
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