Tracking Process Status
The status of a process can be changed programmatically (for example, when a step fails) or manually (for example, when a webMethods Monitor user suspends a process). Before running a step, each Process Engine checks the process status to determine if its server should run the step.
When a webMethods Monitor user has suspended the process, the Process Engine will not run subsequent steps until the process has been resumed. When a step fails, the Process Engine will not run subsequent steps until the process has been recovered or resubmitted.
Notification of the change is process status is carried out as follows:
When a step changes the process status, the
Process Engine for the server that ran the step publishes a status control document.
When a
webMethods Monitor user changes the process status,
webMethods Monitor publishes a status control document.
The method used by the Process Engine to track process status depends on your configuration and tuning settings.
When volatile tracking is enabled (the document is stored in memory), the control triggers on all servers that run process steps retrieve the document and pass it to their
Process Engines. Each
Process Engine updates the process status in its server memory.
When volatile tracking is disabled (the document is stored in the
Process Engine Database Component), the control triggers on all servers that run process steps retrieve the document and pass it to their
Process Engines. Each
Process Engine updates the process status in the PRTPROCESS table in the
Process Engine database component.
In both of the above cases, the Process Engines also publish a document to the Integration Server audit subsystems indicating the new process status. The audit subsystems update the PRA_PROCESS table in the Process Audit Log database component with the new status.