Administration Console > Monitor > Server Monitoring
  

Server Monitoring

After pressing the Server Monitoring command, Process Server displays the following page:
Server Monitoring Page
Server Monitoring
Process Server monitoring includes:

Server Statistics

Note: You only see this command if you have selected an agent.
Use the Server Statistics page to view the monitoring properties you configured or which are the default. Process Server collects engine statistics and then aggregates them by intervals. If desired, you can configure a threshold interval and an error/warning level for each of these properties. If you configure these settings, you will see additional signals displayed on this page, such as an eyeglass icon indicating a property is being watched.
Server Statistics
During a collection interval, Process Server maintains statistics for each configured property value, including the maximum, average, and total count values. In addition, historical statistics are collected. Historical statistics include minimum and maximum values for the intervals being recorded. Statistics are collected in-memory.
In a clustered environment, the monitoring report’s top level is an aggregate of values from all engines in the cluster. Below the aggregate information is a report for each individual engine in the cluster. In a clustered environment, statistical information is relayed from one node to the next to allow for aggregation.
Select Reset to clear statistics. For example, if you correct an error condition, you can reset the statistics collection starting with zero values to see if performance improves. Once all errors and warnings are cleared, the engine monitoring level is reset to Normal.
Monitoring indicators include the following:
Monitoring Report
During each threshold interval, if an error or warning occurs, it is reported at the end of an evaluation period. For example, if your threshold interval is set to five minutes, and the evaluation frequency is set to five times per interval, the first trouble item may appear after one minute has elapsed, but will not be reported more than once per threshold interval. If competing threshold levels occur during same evaluation cycle, the highest severity is reported.
Each time you refresh your browser or open the Monitoring page, monitoring statistics are updated. The report, however, is updated only at the end of an evaluation period.
The list of trouble items shows the error/warning level, time, property name, and configuration details for each item reported. The following is an example of a report.
Monitored engine properties
For details on setting up monitored engine properties, see Monitoring Thresholds, Properties, and Monitor Alert Service

Deployment Logs

The Deployment Logs page shows a list of logs generated when new and modified business process archive (.bpr) files are deployed.
Deployment Logs
The number of errors and warnings generated, if any, are shown.
On this page you can:
After you click on a .bpr file, Process Developer displays its Deployment Log page. This page has the name, date, and log for the selected .bpr file.
Deployment Log Detail
During deployment, the engine validates the deployment descriptor of the BPEL process, ensuring that the its WSDL file and other resources are available and valid for the current version of the process. If validation errors or warnings occur, make corrections and redeploy the .bpr file or create a new .bpr file for invalid processes.
Note: When you delete a contribution, its deployment log is also deleted. For details, see Contributions.
Selection Filter
  1. 1. Select the Log Contents type, if desired.
  2. 2. Select Deployed between dates, if desired.
  3. 3. Type in the Name of a .bpr file, if desired. You can use a wildcard (*) in the name.
  4. 4. Select Submit. The Deployment Logs list redisplays based on your selection filters.

Server Log

The Server Log captures events occurring on the server so that you can view and troubleshoot problems. For each event, the log includes the time, problem level, source (initiator), service (event type), engine, and message describing the event. For example, a BPR deployment causes a log event with info level, system source, engine service.
Note: The server log may not updated immediately after an event occurs. It is typically updated between 30 and 60 seconds after an event. If you are not seeing what you think should be there, you may just need to update your browser.
The interface for the Server Log is available in Process Developer as a system service. This feature allows BPEL designers to create and deploy a process that inserts custom messages into the Server Log.
Server Log page
This topic discusses:

Server Log Information

One of the following filters was used when generating logging information:
The console records the User/IP address when a purge or scheduling request occurs. An application server may have its own method. Here, for example, is what might be shown for Tomcat: https://tomcat.apache.org/tomcat-7.0-doc/api/org/apache/catalina/valves/RemoteIpValve.html.

Deleting the Process Server Log

On the Storage page, you can delete the Process Server log. See Admin > Maintenance > Storage.
In addition, the interface for clearing the server log is available in Process Developer as a system service so that a developer can create and deploy a process to delete the log programmatically.

System Logging for WebLogic Users

If you are using WebLogic, you must enable system logging from the WebLogic Process Console to have the Process Server stdout write to the WebLogic server log.
  1. 1. In the WebLogic Process Console, select the Logging top-level tab.
  2. 2. In the General sub-tab, enable Advanced options'
  3. 3. Select the Lock & Edit button so you can make changes.
  4. 4. Enable the Redirect stdout logging enabled checkbox.
  5. 5. Choose Activate Changes to apply your changes

System Performance

Note: You see this option only if you have selected an agent.
The System Performance page provides details to show:
For example:
Monitoring does not effect process execution. The statistics show a snapshot of what was in memory when you first open the page. Refresh the page to get updates.
These statistics let you ask questions such as:
After you run a load test, you can watch the metrics and set or reset configuration properties.
Platform Support
As you analyze performance in relation to your application server, keep the following in mind: