Business Process Troubleshooting

Sometimes you may need to troubleshoot your IBM® Sterling B2B Integrator business processes to determine why something is not working as you intended.

Restarting and Resuming Business Process Instances
When your monitoring activities with IBM Sterling B2B Integrator uncover a process instance with a state of waiting, interrupted, or halted, or you have stopped a process for some reason, such as to correct a problem before the process continues, you may want to resume or restart the process.
Taking Actions with a Single Business Process Instance
You can restart, resume, stop, expedite, or terminate a single business process instance.
Taking Actions with One or More Business Process Instances Simultaneously
You can resume, restart, stop, expedite, or terminate multiple process instances at once.
Terminating and Restarting a Business Process
If a business process stops running, you can use the System Troubleshooter page to review the business process and to terminate and restart the business process when you see a state of Halted, Waiting, Waiting_On_IO, Interrupted_Man, or Interrupted_Auto.
Tips for Troubleshooting Your Processes
You can troubleshoot your business processes using various techniques.
Responding to Different Status and State Indicators
While monitoring and troubleshooting processing, you will find that processes pass through a variety of states.
Resolving Business Subprocess Errors
When a business process remains in a waiting state for the subprocess to return for further processing, you can reset the business process.
Resolving Lock Errors
If Sterling B2B Integrator is shut down in the middle of indexing business processes, the lock that it holds is not released, causing subsequent indexing business processes to fail.
Resolving Persistence Errors
You can resolve persistence errors by meeting a series of conditions.
Resolving Database Errors
If the business process failed because the database could not receive it, you can resolve the error two ways.