System Logging

The TIBCO ActiveMatrix platform supports a flexible logging architecture that enables runtime objects to log events to various types of destinations.

The TIBCO ActiveMatrix logging environment is depicted in TIBCO ActiveMatrix Logging Architecture.

TIBCO ActiveMatrix Logging Architecture


TIBCO ActiveMatrix runtime objects—hosts, nodes, and applications—use log4j technology to output log statements to a variety of output targets. In log4j, a target is called an appender. TIBCO ActiveMatrix supports the following logging appender types: Events logged to a JMS appender are stored in a database.

In log4j, a logger associates a runtime object with an appender, specifies the types of events to be logged, and whether to pass messages to a parent logger. In the Administrator web interface, a logger is referred to as a logging configuration.

A TIBCO ActiveMatrix logging environment involves the following participants:

  • Log event generator A TIBCO ActiveMatrix runtime object that generates log events. You specify the appender to which runtime objects send log events in a logging configuration. In TIBCO ActiveMatrix Logging Architecture, Node 1 sends message to a JMS appender. Node 2 sends messages to a file and JMS appenders.
  • Log event queue A JMS queue to which log event generators can send events.
  • Log service An application that monitors a log event queue and stores log events to a database.
  • Payload service An application that manages large payloads associated with log events.
  • Log viewer A browser-based server and client UI for viewing log events stored to a database.