Defining Logging Information
TIBCO ActiveMatrix BPM uses the logging facilities provided by TIBCO ActiveMatrix Administrator. This provides you with different types, levels, and formats of logging information depending on your requirements.
Loggers
Loggers define which component(s) of BPM are being logged and at which level.
By default you are provided with the following loggers:
| com.tibco.bx | Logging of BPM Applications |
| com.tibco.pvm | Logging of Process Engine components |
| com.tibco.n2 | Logging of BPM Work Manager components |
| com.tibco.bds | Logging of Business Data Services components |
If you want to get information about document-related activities and CDS (local data), add the following loggers:
| com.tibco.bpm | Logging of document-related activities |
| com.tibco.amxbpm | Logging of document-related activities |
| com.tibco.cds | Logging of CDS (local data) |
The Logger Name you choose restricts the logs you receive to cover particular components.
You can edit the level of logging information you require in TIBCO ActiveMatrix Administrator.
You can also add new Logger Names. See the Administrator interface documentation for your BPM runtime environment for more information.
Logging Appenders
Appenders define where the logging you generate goes.
By default in TIBCO ActiveMatrix BPM, the BPM components (com.tibco.bx, com.tibco.pvm, com.tibco.n2, and com.tibco.bds) all use a single BPM_ROOT appender that writes to a file called BPM.log. This file is found in:
CONFIG_HOME\tibcohost\HostInstance\\data_3.2.x\nodes\.BPMNode\logs\BPM.
Logging Formats
Log messages are produced in the BPM internal logging format (called the TIBCO ActiveMatrix BPM Event format -- see Supported JMS Message Format).