The rule that specifies the boundary for a transaction is at the highest level. Messages may contain a single transaction, multiple transactions, or a part of a transaction that spans messages. These are specified as follows:

• single - The transaction rule match is not defined.

• multiple - Each transaction rule match defines new transaction.

• span – No transaction rule is defined; instead a transaction indicator is specified in an operation rule.

For a transaction rule, the following properties of the rule may also be defined through XPath or other expressions:

• timestamp – The time at which the transaction occurred.

• txid – The identifier for the transaction.

Transaction rules can have multiple subrules, but each must be of type operation.

The following example specifies a transaction that is the whole message and includes a timestamp that comes from the JMS property.

singletxrule.timestamp=$JMSTimeStamp

dyntxrule.match=/Transaction
dyntxrule.timestamp=@ts