Configuring TIBCO ActiveMatrix BPM Auditing

TIBCO ActiveMatrix BPM generates events, which are messages that record its activity, and logs these messages locally. A selection of these events can be audited - that is, collected and stored centrally by ActiveMatrix BPM. The details of auditing are defined by the ec-probe-rules.xml and ec-event-rules.xml files.

The ec-probe-rules.xml file controls what messages are passed to BPM’s central Event Collector auditing. This audit information can then be used by different reporting and monitoring applications. Among other things, it can be published to a JMS topic hosted by a TIBCO Enterprise Message Service™ (EMS) server. The rules in the ec-event-rules.xml file control whether messages are written to the database and are published. Settings in the ec-event-rules.xml file control which messages are published and how, while property values set in the ECPublicationJMS.properties file control connection details and other settings for publication.

Note: JMS publication of an event is not transactional. Event Collector publishes an event to a JMS topic as soon as it receives that event, independent of any transaction involved in the ActiveMatrix BPM activity that generated that event. Consequently, event messages and the ActiveMatrix BPM transactions that generated them may be out of synchronization with each other. For example, when a case is updated, notification of the update could, if the system was very heavily loaded, be received before that update has been committed to the ActiveMatrix BPM database. If the update transaction was rolled back, the event would still be published.

Information collected in the central event database tables is also used by the auditing and graphical auditing tools in Workspace and Openspace.

See: