The Process Admin Console includes a Process Monitor that
enables administrators to view information about the processes and
services that are running on Workflow Server. You can
use the information to identify any problematic processes or services.
The process monitor displays information only for the current cluster member. For example:
Server: cell=nodename1Node01Cell,node=nodename1,process=server1
To see data
for all cluster members at the same time, you must use JMX.
Summary
The summary
shows you how many active services and processes are currently consuming
processor resources in the current cluster. You can view the total
time, total number of instances, and the total number of steps that
are needed to run a service or process; and identify the services
and processes that are the most expensive. For example, a service
that takes a long time to run, or a process that has a large number
of steps.
| Data displayed |
Description |
| Active Processes Currently Executing |
Total number of process instances currently
running on this server. |
| Active Services Currently Executing |
Total number of services currently running on
this server that are potentially problematic. |
| Most Expensive Services |
Name, total running time, and the number of
steps that are required for each service that is deemed most costly
on this server. |
| Most Expensive Processes |
Process name, which includes the instance ID,
total running time (which includes service execution time), and the
number of steps that are required for each process that is deemed
most costly on this server. |
| Most Expensive Service Steps |
Service name, step name, total running time,
and total number of instances that are required to run each step that
is deemed most costly on this server. (If any sub-services are associated
with the step, the Process Monitor displays those sub-service names
as well.) |
| Most Expensive Process Steps |
Process name, step name, total running time,
and total number of instances that are required to run each step that
is deemed most costly on this server. (If any subprocesses are associated
with the step, the Process Monitor displays those subprocess names
as well.) |
Processes
The Processes page
shows the following data for all processes on the server, in the current
cluster.
| Data displayed |
Description |
| Active Processes Currently Executing |
Process name, which includes the instance ID,
enter time (start time), duration (running time), and total number
of steps for each process instance currently running on this server.
In addition to processes that are running smoothly, this category
also includes currently running processes that might have problems.
For example, if a process instance is stuck in a repeating loop, it
is shown in this list. |
| Active Processes Not Currently Executing |
Name, last enter time (most recent start time),
last duration (running time from most recent execution), total duration
(cumulative running time), and total number of steps for processes
that were previously started, but not currently active, on this server.
This category includes process instances that are active but not running
at this moment. For example, if a process instance is waiting for
an event, it is included in this category. |
| Completed Processes |
Name, last enter time (most recent start time),
last duration (running time from most recent execution), total duration
(cumulative running time), and total number of steps for processes
that ran successfully on this server. |
Services
The Services page
shows the following data for all services on this server:
| Data displayed |
|
| Active Services Currently Executing |
Name, enter time (start time), duration (running
time), and total number of steps for each service currently running
on this server. In addition to services that are running smoothly,
this category also includes currently running services that might
have problems. For example, if a service is stuck in a repeating loop,
it is shown in this list. |
| Active Services Not Currently Executing/Completed
Services |
Name, last enter time (most recent start time),
last duration (running time from most recent execution), total duration
(cumulative running time), and total number of steps for services
that were previously started, but not currently active, on this server
and for services that ran successfully on this server. This category
includes two types of services:
|