Managing System Recovery
Sterling B2B Integrator is designed to automatically reset itself to a previous, stable state after a system crash. After the reset is complete, the system is up and operational.
About this task
After a system crash, restore the server on which Sterling B2B Integrator is installed to a stable state, and then restart Sterling B2B Integrator. After it is restarted, the system invokes the Recovery business process to search for and requeue any unprocessed transactions. If the database goes down, Sterling B2B Integrator stops pulling jobs from queues. The system recovers these jobs when the database becomes available.
Sterling B2B Integrator uses multithread operation to restart or resume business processes following a system crash. Unfinished business processes, up to a preconfigured number, are stored in a pool. Each of the preconfigured number of threads receive a batch of business processes to restart or resume. The size of the batch is also preconfigured. When a thread finishes restarting or resuming a batch of business processes, it requests another batch from the pool. This cycle continues until the pool is empty.
By default, the system uses 10 threads, each of which resumes or restarts 10 business processes, and then requests and processes another 10, up to a total of 1000 business processes for all threads. You can configure the system settings to adjust recovery performance according to your business requirements.
To configure the system recovery process settings, perform the following actions: