Business Process Recovery in a Clustered Installation
When a cluster node fails, Sterling B2B Integrator reacts like it would when a single node environment goes down in a non-clustered implementation.
Sterling B2B Integrator tracks and persists all mid-stream activities and process states within the system, and retains the details of the business processes and services. Any active transaction on a failed node halts.
The default recovery operation marks any business processes running on the failed node as interrupted and reverts to the last edge (the state at the last completed step) of each process for recovery. You can manually resume a business process at that point on another node or restart a business process on another node. This default operation can be changed, but changing the default operation is not recommended.