IBM Tivoli Composite Application Manager for Transactions, Version 7.4.0.0

Extended filtering for the Transaction Collector

The Transaction Collector in ITCAM for Transactions uses Application Management Configuration Editor configurations to filter transactions using transaction definition filter sets and maintenance schedules.

The Transaction Collector filters out all instances except those that match an active and running Application Management Configuration Editor transaction definition. If at least one Application Management Configuration Editor transaction definition matches an instance, the corresponding aggregate is active. Otherwise the corresponding aggregate is inactive.

The definition of include and exclude filters determines if an Application Management Configuration Editor transaction definition matches an aggregate.

Note: Filtering does not influence instance traces. After filtering, aggregates are not shown in the aggregate topology. However, instance traces can still find nodes that are not shown in the aggregate topology.

The Transaction Collector does not require a matching client definition. For an individual Application Management Configuration Editor transaction definition to match an instance in the Transaction Collector, ensure that the following conditions are met:

The Transaction Collector considers all configured aggregates active through a default Application Management Configuration Editor profile with an active and running transaction definition for all transaction categories.

Note: To filter out aggregates on a specific component, for example, WebSphere MQ, modify the default filter as required. When adding transaction definitions, be aware that the Application Management Configuration Editor assigns a higher priority to transaction definitions with more filters, or longer filters.


Last updated: September 2014