Transaction Tracking Take Action commands
Use Take Action commands to initiate commands for the Transaction Reporter from within the Tivoli Enterprise Portal. These commands can be used in automatic situations and isolated take action requests.
- KTO: REMEMBER AGGREGATE aggregate id stores a selection of transaction instances that are related to the specified aggregate id from the Aggregates table to the Transaction Reporter and then to the Tivoli Data Warehouse. The aggregate id is a variable which must match a row in the Aggregates table. KTO: REMEMBER AGGREGATE uses the following parameters:
- good=count where count is the number of good instances to remember
- failed=count where count is the number of failed instances to remember
- slow=count where count is the number of slow instances to remember
- depth=count where count is the number of hops for which to track the instance algorithm
- timeout=seconds where seconds is the time limit restricting the instance algorithm. This defaults to slow=1 and uses the configured depth and timeout.
- supplying failed=count where count checks for instances with Status=Failed
- supplying slow=count where count checks for instances with Status=Slow or the largest total time
- supplying good=count where count checks for instances with the smallest total time
KTO: REMEMBER AGGREGATE counts are limited by the number of instances the Transaction Collector associated with an aggregate. This is the 5 fastest, 5 average, 5 slowest, and 5 failed transactions per aggregate per period. Given that the Transaction Collector keeps three periods of data, 15 is the maximum value that you can set for available for failed, and 15 to 45 for slow and good. Setting counts higher than these values causes more resource consumption as the Instance Algorithm tracks those instances.
This command is used in the Slow_Transactions and Failed_Transactions predefined situations depending on the parameter set.
- KTO: REMEMBER INSTANCE instance id stores the transaction information for the specified instance id from the Transaction Instances table to the Transaction Reporter and then to the Tivoli Data Warehouse. The instance id is a variable which must match a row in the Transaction Instances table. The aggregate id is a variable which must match a row in the Aggregates table. KTO: REMEMBER INSTANCE uses the following parameters:
- depth=count where count is the number of hops for which to track the instance algorithm
- timeout=seconds where seconds is the time limit restricting the instance algorithm. This defaults to slow=1 and uses the configured depth and timeout.
To send a particular transaction instance to the Tivoli Data Warehouse:- In the Transaction Instances workspace, select an instance in the Transactions Instances table.
- Right-click and select .Tip: You can also right-click an instance in the Transaction Interactions table and select .
- In the Take Action dialog box, select Store Instance for Warehousing in the Name menu.
- Click OK.
- Click OK to confirm the action.
- KTO: FORGET TOPOLOGY clears the learned topology information. When data is collected from the Transaction Collector in the future, the topology is recalculated and the newly determined topology is applied to the new data. Previously collected data remains unchanged.
- KTO: EXECUTE DLA creates an iDML book describing the current Transaction Tracking topology. The iDML book is required by Tivoli Business Service Manager to provide a framework for displaying Transaction Tracking situation events in Tivoli Business Service Manager. Once the Take Action has been run and the iDML has been saved, copy the iDML book from the Transaction Reporter to Tivoli Business Service Manager. Run the Take Action and update the iDML book on Tivoli Business Service Manager as required.