Publishing Audit Data to a Java Message Service (JMS) Topic

TIBCO ActiveMatrix BPM can publish audit data to a JMS topic hosted by a TIBCO Enterprise Message Service (EMS) server.

Messages are published using the TIBCO ActiveMatrix BPM Event format. These conform to the definition of the Event element in the ec-basetypes schema.

The rules file ec-event-rules.xml is used to control whether messages and their attributes are written to the database and/or published to a JMS topic. It provides the same level of control as the ec-probe-rules.xml file which governs the level of auditing, and defines the connection details for the EMS server that hosts the topic, and the name and output format of the JMS topic to which audit data messages will be published. You can only publish events and attributes that have been centrally audited, so the list of events and attributes in ec-event-rules.xml must be a subset of (or the same as) that in the ec-probe-rules.xml file.

Note: This file replaces the rules that were in the ECPublicationJMS.properties in previous versions of BPM.

A business activity monitoring (BAM) or other JMS reporting application can subscribe to the JMS topic to retrieve all TIBCO ActiveMatrix BPM audit messages.

The rules file allows you to enable and disable JMS publication, and also to configure what audited messages are to be published. TIBCO ActiveMatrix BPM is delivered with the file set up to publish a defined subset of messages, and a defined subset of attributes. You can change the rules file so that all audited messages are published, or you can change the specifications of exactly which messages are published. You can make similar changes to the level of attribute publishing within published events.

See TIBCO ActiveMatrix BPM Administration for more information.