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

Monitoring Lombardi servers

The Process Admin console enables you to monitor the performance of the Process Servers in your environment. And, when necessary, you can view Lombardi logs from the Process Admin console to help resolve issues. Read the following sections to learn more:

• Monitoring Process Server performance
• Monitoring processes and services
• View Process Server logs

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

Monitoring Process Server performance

The Process Admin console includes an Instrumentation monitor to help identify performance bottlenecks in Process Server and to capture instrumentation data that you can use to further analyze any performance issues.

To access the Instrumentation monitor and display the most recent data:

1. In the Server Admin area of the Process Admin console, click the indicator next to Monitoring to list the available monitoring options.
2. Click the Instrumentation option.

3. Click the Refresh button.

   To automatically refresh the displayed data, select the time interval that you want from the drop-down menu.

   To reset all values to 0, click the Reset button. This enables you to monitor performance as data is collected.

To log instrumentation data to an external .dat file:

1. In the Server Admin area of the Process Admin console, click the indicator next to Monitoring to list the available monitoring options.
2. Click the Instrumentation option.

3. Click the Start Logging button.

   The Instrumentation monitor displays the path and file to which the data is saved. The file is created and stored on the host of the Lombardi server that you are currently monitoring.

4. Click the Stop Logging button to end data capture to the log file.

Monitoring processes and services

The Process Admin console includes a Process Monitor that enables administrators to view the processes and services that are running on Process Server, and also to stop any problematic processes or services. For example, you may need to stop a service that causes an exception or a service that is stuck in a repeating loop.

The Process Monitor includes the following tabs:

• Summary

  Shows you how many active services and processes are currently consuming CPU resources. Also shows which services and processes are most expensive in terms of the total time, total number of instances, and the total number of steps needed to execute them.

  Data displayed	Description
  Active Processes Currently Executing	Total number of process instances currently executing on this server that are potentially problematic.
  Active Services Currently Executing	Total number of services currently executing on this server that are potentially problematic.
  Most Expensive Services	Name, total running time, and the number of steps required for each executed service deemed most costly on this server.
  Most Expensive Processes	Name, total running time, and the number of steps required for each executed process deemed most costly on this server.
  Most Expensive Service Steps	Service name, step name, total running time, and total number of instances required to run each executed step 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 required to run each executed step deemed most costly on this server. (If any sub-processes are associated with the step, the Process Monitor displays those sub-process names as well.)

• Processes

  Shows the following data for all processes on this server:

  Data displayed	Description
  Active Processes Currently Executing	Name, enter time (start time), duration (running time), and total number of steps for each process instance currently running on this server that is potentially problematic. 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 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 executed successfully on this server.

• Services

  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 that is potentially problematic. 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 previously started, but not currently active, on this server and for services that executed successfully on this server. This category includes two types of services: (1) services that completed successfully and (2) services that were previously started but are not currently executing. For example, if a service is waiting for an event, it is included in this category.

To access the Process Monitor:

1. In the Server Admin area of the Process Admin console, click the indicator next to Monitoring to list the available monitoring options.
2. Click the Process Monitor option.
3. Click the option that you want: Summary, Processes, or Services.

To stop an active process:

1. Access the Process Monitor

2. Click the Processes option.

3. Under Active Processes Currently Executing, click the name of the process that you want to stop.

4. Click the Halt Process button.

   

   The halted process now appears in the Active Processes Not Currently Executing list.

To stop an active service:

1. Access the Process Monitor

2. Click the Services option.

3. Under Active Services Currently Executing, click the name of the service that you want to stop.

4. Click the Halt Service button.

   

   The halted service now appears in the Active Services Not Currently Executing/Completed Services list.

View Process Server logs

Lombardi logs data about its performance and actions in several different types of log files. The physical log files are stored on Process Server, but you can view these logs from the Process Admin console. The following table describes the logs available with Lombardi and the data that each provides. By default, you can access all of the following logs from the Process Admin Console.

See Configure available log files to learn how to customize the list of log files that is available from the Process Admin Console.

Log file	Description
TW BPD Engine	Records errors generated as a result of process instance execution on the current server.
TW Console	Records actions that have occurred in the Process Admin console.
TW Debug	Records warnings from the Process Server.
TW Error	Records Lombardi Javaâ„¢ exceptions.
TW EventManager	Records historical information about Event Manager processing.
TW Exp/Imp	Records the process export and import transactions in Lombardi Authoring Environment.
TW Limit	Records Process Server limit overruns. You can configure Process Server limits in the 99Local.xml file in [Lombardi_home]/process-server/config/system.
TW JavaScript	Records any logging associated with JavaScript log functions like log.info() or log.debug(). Basically, this log records anything you write out to the log in a Server Script component.
WS UCA Execution	Records errors generated as a result of Undercover Agent (UCA) execution.
WS Inbound	Records calls to published Lombardi Web services.
WS Outbound	Records data about Web services that a Lombardi process consumes.

To view Lombardi logs:

1. In the Server Admin area of the Process Admin console, click the indicator next to Monitoring to list the available monitoring options.

2. Click the View Logs option.

3. From the Log Name drop-down list, select the log that you want to view. (The preceding table describes each available log.)

4. From the # of Lines drop-down list, select the number of lines that you'd like to view.
5. To view oldest log entries first, click the Ascending check box. (By default, the check box is disabled and the newest log entries are shown first.)
6. To find a particular word or phrase in the log file, enter the string to search for in the Filter text box.

7. Click the Refresh button to ensure you are viewing the most recent data available from Process Server.

   See to learn how to configure the list of log files that is available

Configure available log files

By editing the 50AppServer.xml file, which you can find in [Lombardi_home]/process-server/config/system, you can establish:

• Which log files can be viewed from the Process Admin Console
• The default location for log files generated by Lombardi components

1. Open the 50AppServer.xml file in a text editor (for example, Notepad).
2. Find the <log-watcher> section.
3. Make the appropriate edits to the path for each log file whose default location you want to change.
4. If you want a particular log file to be inaccessible from the View Logs page, comment out or remove the log name element for that log.

Parent topic: Manage Lombardi Process Servers

+

Search Tips   |   Advanced Search