WebSphere Lombardi Edition 7.2 > Administer the Lombardi environments > Manage Lombardi Process Servers


Maintain Lombardi Event Manager

The Event Manager monitor, included in the Process Admin console, is useful for troubleshooting processes that are supposed to run automatically (through an Undercover Agent, for example), but fail to start. Using the Event Manager monitor, you should be able to identify any underlying problems, as well as control various aspects of Event Manager processing.

Before performing any of the tasks in the following sections, go to the Process Admin console and log in


About the Event Manager

The Event Manager is the part of the Process Server that handles event scheduling and queuing. For example, when an event is received by Process Server, that event becomes a job in the Event Manager. Each job in the Event Manager is routed through a Scheduler, which schedules and tracks the execution of its assigned jobs.

For inbound integrations, where an external system or application calls into Lombardi to kick off a service, developers in Lombardi Authoring Environment can create an Undercover Agent and a Web Service to start the necessary Lombardi service.

See Create inbound integrations in Lombardi Authoring Environment User Guide or online help.) The Event Manager processes all incoming requests

For... Event Manager...
Incoming message events from external applications Queues incoming messages and then kicks off the appropriate UCA
Schedules set in UCAs Looks to find the next UCA to run, calculates the time until the next UCA is due to run, and is dormant for the time between

The following diagram shows how the Event Manager receives and processes incoming requests:


Monitoring the Event Manager

The Event Manager monitor in the Process Admin console displays information about the Scheduler for the Event Manager on your Process Center Server or Process Server, and the various jobs being tracked by that Scheduler. 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:

  1. In the Server Admin area of the Process Admin console, click the indicator next to Event Manager to list the available management options.

  2. Click the Monitor option.

  3. The monitor displays the ID and status for each Scheduler and also displays all currently scheduled jobs :

  4. You can pause a selected or all Schedulers by using the Pause or Pause All buttons. If you pause a Scheduler, any executing jobs are completed before processing is halted. (Use the Resume or Resume All buttons to resume processing.)

  5. Examine the list of jobs to determine which events are scheduled and when they should execute.

    This list can help you troubleshoot issues with your processes. For example, if an undercover agent (UCA) is supposed to start a process automatically at a certain time and you notice that the process is not running, you can examine the list of jobs to determine if the UCA was scheduled. If not, you know there could be an issue with the Process Server receiving the event. If the UCA is scheduled, but never runs, you can check the implementation of the UCA in the Designer to understand why it fails to run.

  6. Click the Refresh button to ensure you are viewing the most recent data available.

The Event Manager monitor does not show historical information about Undercover Agents (UCAs) that were successfully run, but you can capture this type of information to the [Lombardi_home]/process-server/logs/tw-ucaexecution.log file. To do so, you need to configure the TWUcaAppender property in the [Lombardi_home]/process-server/config/log4j.xml file so that the value element for the Threshold parameter is set to Info as shown in the following example:

<param name="Threshold" value="INFO"/>

After changing the value for the Threshold parameter, restart the Process Server to begin capturing information to the tw-ucaexecution.log file.


Maintain blackout periods

Administrators should establish blackout periods to specify times when events cannot be scheduled, for example, due to a holiday or when regular system maintenance is scheduled. The Event Manager takes blackout periods into account when scheduling and queuing events and undercover agents (UCAs).

To create a blackout period:

  1. In the Server Admin area of the Process Admin console, click the indicator next to Event Manager to list the available management options.

  2. Click the Blackout Periods option.

  3. Set a Date/Time Range or a Weekday/Time Range.

    For example, for a holiday, you'd set a Date/Time Range for a specific date in the future. For weekly system maintenance, you'd set a Weekday/Time Range.

  4. Click the Add button.

    The new blackout period is added to the Blackout Periods list.

To update a blackout period:

  1. In the Server Admin area of the Process Admin console, click the indicator next to Event Manager to list the available management options.

  2. Click the Blackout Periods option.

  3. Select the blackout period that you want to update from the list.

  4. Change the details of the period as required.

  5. Click the Update button.

To delete a blackout period:

  1. In the Server Admin area of the Process Admin console, click the indicator next to Event Manager to list the available management options.

  2. Click the Blackout Periods option.

  3. Select the blackout period that you want to delete from the list.

  4. Click the Delete button.


Maintain execution queues

Event Manager jobs are scheduled to be processed by an execution queue. (If you look at the job listing in the Event Manager monitor, you can see that each job is assigned to a job queue.) The Event Manager includes two types of execution queues:

Asynchronous queue Allows jobs to run at the same time.
Synchronous queue Forces one job to finish before the next job can start.

Administrators can create multiple synchronous execution queues to handle Event Manager jobs. When multiple queues are available, developers who create events and corresponding undercover agents (UCAs) can specify the queue in which they want their event to run. You may want to create separate synchronous queues so that certain types of events can all be routed to a separate queue and processed sequentially.

You can override the default values set in the [Lombardi_home]/process-server/config/system/80EventManager.xml file to control the number of events that are loaded at one time on your synchronous queues and to control the number of simultaneous events that can execute on your asynchronous queues. To override the default values, copy the <sync-queue-capacity> and <async-queue-capacity> elements to the [Lombardi_home]/process-server/config/100Custom.xml file and change the default values to the new values that you want.

To create a synchronous queue:

  1. In the Server Admin area of the Process Admin console, click the indicator next to Event Manager to list the available management options.

  2. Click the Synchronous Queues option.

  3. Enter a name for the new queue in the Description text box.

  4. Click the Add button.

    The new queue is now included in the Synchronous Queues list.

To change the name of a synchronous queue:

  1. In the Server Admin area of the Process Admin console, click the indicator next to Event Manager to list the available management options.

  2. Click the Synchronous Queues option.

  3. Select the queue that you want to change from the Synchronous Queues list.

  4. Change the name in the Description text box.

  5. Click the Update button.

    The queue is included with the new name in the Synchronous Queues list.

When you change the name of a synchronous queue, be sure to inform developers and other members of your team who may be specifying that queue to process their events.

To delete a synchronous queue:

  1. In the Server Admin area of the Process Admin console, click the indicator next to Event Manager to list the available management options.

  2. Click the Synchronous Queues option.

  3. Select the queue that you want to delete from the Synchronous Queues list.

  4. Click the Delete button.

    The queue is no longer included in the Synchronous Queues list.

When you delete a synchronous queue, be sure to inform developers and other members of your team who may be specifying that queue to process their events.


View the JMS Error Queue

The Event Manager JMS Error Queue shows records that have not been processed by the Event Manager because of errors that have occurred or due to the Event Manager being in a blackout state.

To access the JMS Error Queue:

  1. In the Server Admin area of the Process Admin console, click the indicator next to Event Manager to list the available management options.

  2. Click the EM JMS Error Queue option.

Parent topic: Manage Lombardi Process Servers

+

Search Tips   |   Advanced Search