Archiving Messages

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. ActiveMatrix BPM enables you to archive these messages so that they are no longer visible in the ec_event view. This can improve the responsiveness of the ec_event view when performing queries against it.

Restriction: If you have upgraded your ActiveMatrix BPM system and migrated your audit data, these events cannot be archived. See "Migrating Data Stored in Event Collector" in TIBCO ActiveMatrix BPM Installation and Configuration for more information.

The ActiveMatrix BPM messages are always available in the ec_event_int table, unless they have been purged. See "Purging Audit Data" in the TIBCO ActiveMatrix BPM Developer's Guide.

Archived data consists of:

  • Process instances: events that are attached to process instances or case data.
  • System events: events that are not attached to process instances or case data.

By default, ActiveMatrix BPM automatically archives all these messages. The properties that determine how the messages are archived are configured in the ec.properties file. For example, you can specify when messages are archived, how old messages should be before archiving, or disable archiving completely, depending on your requirements. See Configuring How BPM Audit Messages Are Auto-archived.

Archiving in ActiveMatrix BPM is given a certain length of time to complete. If archiving fails to complete in that time, it is cancelled. However, ActiveMatrix BPM warns you if the archive needs intervention. For example, ActiveMatrix BPM warns when archiving has taken up half of the time it is allowed to run for.

All process instance events are archived. You cannot specify a list of individual message IDs for process instance events. However, you can configure which system event messages are archived. See Configuring Which System Event Messages are Archived.

Archived messages are stored in the BPM tablespace, by default. You can specify that archived messages are stored in Apache Cassandra. See Configuring Archived Messages to be Stored in Apache Cassandra.