Hi, I'm Ask INFA!
What would you like to know?
ASK INFAPreview
Please to access Ask INFA.

Table of Contents

Search

  1. Preface
  2. The Application Integration Console
  3. Process Server Configuration
  4. Deployed Assets
  5. Process Schedules
  6. Processes
  7. Process Server Health
  8. Process Metrics
  9. APIs
  10. Connections
  11. Guides
  12. Logs

Monitor

Monitor

Server Log

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), and message describing the event. For example, a BPR deployment causes a log event with info level and system source.
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 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:
  • Minimum Level
    . Select one of the following options:
    • Verbose—All levels
    • Info
    • Warning
    • Error
    • Critical
  • Source
    . The initiator of the event or select All. Sources are:
    • All—All the services
    • 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
    • Eventing—Detectable occurrences or changes in the system's state, to trigger actions or responses within workflows and applications.
    • 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 the services
  • Add Filter
    . Select one of the following options from the
    Add Filter
    list:
    • Logged Between
      . Specify the time duration for which the log contents need to be displayed. Select one of the following options:
      • Any Time—Displays all the log contents that were generated in the runtime environment.
      • Today—Displays log contents that were generated today.
      • Last Hour—Displays log contents that were generated in the last one hour.
      • Last Week—Displays log contents that were generated today over the last week.
      • Last Month—Displays log contents that were generated over the last month.
      • Last Year—Displays log contents that were generated over the last year.
      • Custom—Displays log contents that were generated in the date range that you select after you click the
        Custom
        option.
    • Message
      . Text describing the event. You must enter the complete message string that is provided in the specific Secure Agent log file.
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.

0 COMMENTS

We’d like to hear from you!