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 update 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 following image shows a sample Server Log:
This topic discusses:
•Server Log Information
•Deleting the Process Server Log
Server Log Information
One of the following filters was used when generating logging information:
•Log Time (Logged after and Logged before). By default, the log displays the most recent six hours of events. Refresh the page to view the most recent date and time. You can change the log period by setting the date and time. As a time shortcut, you can select the Now icon at the end of the time text box.
• Level. One of the following was selected:
- Verbose—All levels
- Info
- Warning
- Error
- Critical
•Source. The initiator of the event or select All. Sources are:
- System—Process Server events such as deployments
- Maintenance—Storage and deployment log deletions
- User—User-initiated
• Service. The services are:
- Alert—Alert service configuration events
- Email—Email service configuration events
- Engine—Engine events, including deployments, Process Server start/stop, storage events, monitoring alerts
- Identity—Identity service (file, LDAP, JDBC) configuration events
- Messaging—Messaging service (JMS or other) configuration events
- Task.—Client URI update events
- Process—Messages added to Process Server Log from a process using the Process Server Log Comment system service
- All—All services are shown
• Engine Name. The engine upon which execution occurred.
•Message . Text describing the event.
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 Server Log
Use the Clean Up Storage on the Storage tab of the Server Configuration page.
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.
Setting the Process Server Logging Level
Use the following filters to display the Process Server log.
•Minimum Level. Select one of the following information levels:
- Verbose. All levels
- Info
- Warning
- Error
- Critical
•Logging Source. Select the initiator of the event or select All. Sources are:
- System. Process Server events, such as deployments
- Maintenance. Storage and deployment log deletions
- User. User-initiated
•Logging Service. Select one service or select All. The services are:
- Alert. Alert service configuration events.
- Email. Email service configuration events.
- Engine. Engine events, including deployments, Process Server start/stop, storage events, monitoring alerts
- Identity. Identity service (file, LDAP, JDBC) configuration events.
- Messaging. Messaging service (JMS or other) configuration events.
- Task. client URI update event.
- Process. Messages added to Process Server Log from a process using the Process Server Log Comment system service.
•Logging Engine Name. Select one engine in a cluster or select All.
•Logged after and Logged before. By default, the log displays the most recent six hours of events. Refresh the page to view the most recent date and time. You can change the log period by setting the date and time. As a time shortcut, you can select the Now icon at the end of the time text box.
•Message String. Type in a text string to search for within the Message column of the log. Use wild cards to locate the message. For example, type in Error* to find all messages beginning with the word "Error". Type in *-StorageException* to find all messages containing the string "StorageException".
Deleting the Process Server Log
You can delete the Process Server log from the Server Configuration > Storage after you select a Secure Agent.
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.
