BPM Logging Issues

Logging involves the recording of all events generated by TIBCO ActiveMatrix BPM to local log files. Logging data can be used for numerous purposes, ranging from debugging within a system, through to storage for non-repudiation logs, and all messaging in between.

Logging administration tasks are performed using TIBCO Administrator. Refer to the TIBCO Administrator documentation and to TIBCO ActiveMatrix BPM - BPM Administration for additional information on logging.

  1. BPM Log Files Location
    Logging involves the recording of all events generated by TIBCO ActiveMatrix BPM to local BPM log files.
  2. BPM Logging Levels
    Every logged event is categorized with a severity level. The severity levels are DEBUG, TRACE, INFO, WARN, ERROR or FATAL.
  3. Turning Debug On and Changing the BPM Logging Level
    Logging data can be used for debugging within a system. You can turn debug on and off and specify the logging level you require.
  4. Using the BPM Logs for Troubleshooting
  5. Log Viewer
    TIBCO ActiveMatrix runtime objects-hosts, nodes, and applications-use log4j technology to output log statements. The Log Viewer allows you to view log files generated by TIBCO ActiveMatrix BPM. You can view the log files directly but the Log Viewer enables you to view the log files more easily. For example, messages display in configurable columns, you can open multiple log files at the same time and filter or highlight entries using EventCollectorQueryLanguage (ECQL).
  6. Workspace Application Log
    The Application Log is available to assist with troubleshooting the application. This log provides detailed debug information generated by the application, as well as information about communications between the application and the Action Processor.
  7. Workspace Application Monitor
    The Application Monitor is available to assist with troubleshooting the application. This monitor provides debug information on error conditions and exceptions encountered. You can configure the Workspace Application Monitor, depending on your requirements.
  8. Unique Constraint Errors in the Log Pertaining to RQL Due to Long Running Queries
    Long running queries can fail to be recorded in a timely manner in the database.