Monitoring the Event Manager
The Event Manager monitor in the Workflow Admin displays information about the Scheduler for the Event Manager and about the various jobs that the Scheduler tracks.
When you access the Event Manager monitor, you can see the status for each scheduled job. In a clustered environment, the monitor displays all Schedulers in the cluster and the jobs for all Schedulers in the cluster.
To use the Event Manager monitor:
-
In the side menu of the Workflow Admin, click Event Manager, then Monitor to see the available management options.
-
Click the Scheduler tab.
The monitor displays the ID and status for each Scheduler and also displays all currently scheduled jobs.
-
Click Pause or Pause All to pause a selected Scheduler or all Schedulers. If you pause a Scheduler, any running jobs are completed before processing is halted.
-
Click Resume or Resume All to resume processing of the selected Scheduler or all Schedulers.
-
Examine the list of jobs to determine which events are scheduled and when they run.
This list can help you troubleshoot issues with your workflows.
For example, if an undercover agent (UCA) is supposed to start a workflow automatically at a certain time and you notice that the workflow is not running, you can examine the list of jobs to determine whether the UCA was scheduled. If not, there might be an issue with the Workflow Server receiving the event. If the UCA is scheduled but never runs, check the implementation of the UCA in the Builder to understand why it fails to run.
-
Click the Refresh button to ensure that you are viewing the most recent data available.
What to do next
The Event Manager monitor does not show historical information about UCAs that were successfully run, but you can capture this type of information in the SystemOut.log
file if the log details level for the WLE.wle_uca
exception component is set to the following default value:
*=info
If the log details level was changed, you can change it back to the default value by opening the WebSphere Application Server administrative console and selecting Troubleshooting > Logging and Tracing > server_name
> Change log detail levels > Runtime > Components.
Parent topic: