Transaction Reporter agent configuration parameters
You can tune the default Transaction Reporter data collection settings to suit your system.
Table 1 describes the collection and display parameters that you can customize for the Transaction Reporter using the Manage Tivoli Monitoring Services user interface. These parameters are also configurable in the ktoenv file.
| Tab | Field | Description |
|---|---|---|
| General | Stitching Filenames | List of the XML files that define the configuration for stitching. Separate multiple file names with a space. Default: kto_stitching.xml |
| Workspace Linking and Launch-In_Context Filenames | List of the XML files that define the configuration for workspace linking and launch-in-context. Separate multiple file names with a space. Default: kto_dwl.xml |
|
| Resource Filenames | List of the XML files that define the GUI items used in the workspaces. Separate multiple file names with a space. Default: kto_resources.xml |
|
| TEP Server Host | Host name of the computer on which Tivoli Enterprise Portal Server is installed. The Transaction Reporter provides this setting to Tivoli Business Service Manager. Tivoli Business Service Manager then uses the setting to launch workspaces in Transaction Tracking. Default: localhost |
|
| TEP Server Port | Port number on which Transaction Tracking communicates with the Tivoli Enterprise Portal Server. The Transaction Reporter provides this setting to Tivoli Business Service Manager. Tivoli Business Service Manager then uses the setting to launch workspaces in Transaction Tracking. Default: 1920 |
|
| Aggregation agent | Aggregation agent List | Specifies the Aggregation agents from which the Transaction Reporter collects aggregate data. If this field is blank, the reporter collects data from all available Aggregation agents. To
specify Aggregation agents,
enter the name of the agent, followed by :TU or :T5.
Separate agent names with a space. For example:
Note: Do
not specify the same Aggregation agent for
more than one Transaction Reporter.
Multiple Transaction Reporters
should not collect data from the same Aggregation agent.
Default: blank |
| Update Interval (seconds) | The interval at which the list of available Transaction Collectors is updated, in seconds. Default: 15 seconds |
|
| Contact Interval | The interval at which the Transaction Reporter polls the Aggregation agents for data, in seconds. Default: 120 seconds |
|
| Contact Delay (seconds) | Initial delay measured in seconds after which the Transaction Reporter contacts the Aggregation agents for new data. Default: 30 seconds |
|
| Aggregation Period (minutes) | The interval at which the Aggregation agent produces an aggregate of the data, in minutes. Note: The Aggregation Period
set for the Transaction Reporter and
each Aggregation agent must
be the same. If the periods are different, the Transaction Reporter cannot
accept aggregates from the Aggregation agent.
Default: 5 minutes |
|
| Aggregation Period Count | The number of Aggregation Periods of data kept by the Aggregation agent in its cache. This setting is not currently used by the Transaction Reporter, however its value must be one less than the Cache Period and must match the Maximum Retained Aggregation Periods specified for the Aggregation agent. Default: 3 |
|
| Query Timeout (seconds) | Timeout, in seconds, that is specified by the Transaction Reporter when making a query to a Aggregation agent. Default: 0 (disabled, the default Tivoli Enterprise Monitoring Server timeout value is used instead) |
|
| Reporter Agent List | Specifies the Transaction Reporters from which aggregate data is collected. To specify Transaction Reporters,
enter the name of the agent, followed by :TO.
Separate agent names with a space. For example:
Default: blank |
|
| Cache | Cache Period Count | The number of Aggregation Periods of data kept in the cache. If the Aggregation Period is 5 minutes, and the Cache Period is 4, at least 20 minutes of data will be kept in the Cache before it is moved to History. Information in the Cache is updated until it is moved to History. Default: 4 |
| Cache Remove Count | The number of Aggregation Periods of data that are moved to History when the cache period is exceeded. This value must be less than or equal to the Cache Period minus the Period Count. Default: 1 |
|
| History | Baseline Style | The type of baseline calculation
used to report time and rate deviation metrics. Select from:
Default: ALL_HOURS |
| History Duration (hours, days, or weeks) | Configures the number of hours, days, or weeks used in the baseline calculation. The duration is in hours, days, or weeks depending on the Baseline Style selected. Default: 24 hours |
|
| History Period (minutes) | Configures the period used in the
baseline calculation.
Note: Do not alter this value except under advice
from IBM.
Default: 60 minutes |
|
| History Remove Count | The number of History Periods of data that are deleted when the Duration is exceeded. Default: 1 |
|
| History Warehouse Supply Count | Limits the amount of data transferred to the warehouse at any one request. This limits the CPU resources required and the time spent responding to that request enabling the Transaction Reporter to continue with other tasks. Default: 2 |
|
| Aggregation Algorithm | Recalculate Interactions | Determines whether subsequent topology changes are applied to previous aggregates in the cache. Note: Ensure
that this parameter is enabled if Calculate Remote Interactions is
enabled.
Default: Y (Yes) |
| Calculate Implied Interactions | Specifies whether or not to calculate implied interactions from historical topology data. Implied interactions are those interactions for aggregates that have been collected in the past but are not present in the current time period. Default: Y (Yes) |
|
| Calculate Pseudo Interactions | Specifies whether or not to calculate pseudo interactions from horizontal context data. Default: Y (Yes) |
|
| Calculate Remote Interactions | Specifies whether or not to calculate remote interactions from multiple Transaction Reporters and display those nodes in the topology. Note: Set
to Y to enable the use of multiple Transaction Reporters.
Ensure that Recalculate Interactions is enabled
if this parameter is enabled.
Default: N (No) |
|
| Maximum Process Aggregates (minutes) | A limit on the time spent calculating interactions between aggregates for any single aggregation time period. This limits the topology determination in the current time period and enables the Transaction Reporter to progress to the next time period. If this is disabled, data may be lost as the Aggregation agent progresses to the next aggregation period. Set to 0 to disable this setting. Default: 4 minutes |
|
| Maximum Topology Trace Backoff (minutes) | Maximum period used in the exponential backoff for determining the topology of unknown interactions in an aggregation period, measured in minutes. Set to avoid repeatedly attempting to determine the topology for the same aggregate to the exclusion of other aggregates. Set to 0 to disable this setting. Default: 120 minutes |
|
| Initial Topology Trace Event Count | Initial number of events used to determine a topology from aggregate records for unknown interactions. The number of events used increases by one from this count until the Maximum Topology Trace Event Count is reached. Default: 2 |
|
| Maximum Topology Trace Event Count | Maximum number of events used to determine a topology from aggregate records for unknown interactions. Default: 15 |
|
| Determine Topology Trace Hop Count | When determining a topology by using instance tracing, the maximum number of hops taken from each initial topology trace event. Set to the minimum value of 1 to emulate the behavior of V7.2 and earlier releases. The default value produces a more accurate topology sooner. Default: 3 |
|
| Topology Forget Interval (minutes) | Time limit to remove the topology for an aggregate record, measured in minutes. After the topology is forgotten, it is determined again. Set to 0 to disable. Default: 0 minutes |
|
| Advanced | Thread Pool Size | Number of threads used to contact Transaction Collectors simultaneously. Default: 3 |
| Show Latest Data | Determines whether data from the current Aggregation Period or from the most recent complete Aggregation Period is displayed. If set to display the latest data (Y), the topology information and rates in the workspaces will be incomplete until the first Aggregation Period is complete. If set to no (N), information from the most recent complete Aggregation Period is displayed and the topology and rates information in the workspaces is complete. Default: N |
|
| Show Latest Instances | If enabled (Y), shows the latest instance data in the workspaces. Default: N |
|
| Data File Write XML Frequency | If enabled (value > 0), the Transaction Reporter writes cache and history data to disk after collecting it from the data collectors. Default: 1 |
|
| Data File Read XML At Start | If enabled (Y), the Transaction Reporter reads cache and history data from disk at startup. Default: Y |
|
| Data File Write Topology XML | If enabled (Y), the Transaction Reporter stores topology information. Note: This
setting must be enabled for Transaction Tracking to integrate
with Tivoli Business Service Manager.
Default: Y |
|
| Data File Read Topology XML At Start | If enabled (Y), the Transaction Reporter reads the topology information written by Data File Write Topology XML at startup, allowing faster processing of aggregates. Default: Y |
|
| Instance Cache Period Count | Maximum number of periods of instance traces that are stored for presentation in the Transaction Instances workspace. Default: 4 |
|
| Workspace Trace Time Limit (seconds) | Maximum duration measured in seconds to perform an instance trace initiated from a workspace. If the instance trace is incomplete after the set time limit, a partial topology is displayed with a clock symbol. Refresh the topology to continue the instance trace. A value of zero (0) disables the time limit and a full topology is displayed only when the instance trace is complete. However, if the trace takes longer than 50 seconds the Tivoli Enterprise Portal can time out, resulting in a blank topology. Default: 20 seconds |
|
| Workspace Trace Depth Limit | Performs an instance trace initiated from a workspace for a set number of nodes. When the set number of nodes is reached, the instance trace stops. If the instance trace is incomplete, a partial topology is displayed with a clock symbol. Refresh the topology to continue the instance trace from where it finished, effectively doubling the number of nodes traced. Default: 0 (Disabled) |
|
| Instance Warehouse Period Count | Maximum number of periods of instance traces for the Tivoli Data Warehouse. Default: 4 |
|
| Situation Trace Time Limit (seconds) | Maximum duration, measured in seconds, to perform an instance trace initiated from a situation. The instance trace is then sent to the Tivoli Data Warehouse. A value of zero (0) disables the time limit and the instance trace is completed before being sent to the Tivoli Data Warehouse. Default: 40 seconds |
|
| Situation Trace Depth Limit | Performs an instance trace initiated from a situation of a set number of nodes. Default: 0 (Disabled) |
|
| Instance Warehouse Supply Count | Maximum number of periods of instance traces that are supplied to the Tivoli Data Warehouse for a single query. Default: 4 |
Other Transaction Reporter parameters
There are additional Transaction Reporter parameters that you do not need to configure but which are however configurable. These parameters are not displayed in the Transaction Reporter Agent Configuration window but can be customized directly in CANDLE_HOME/config/to.ini on Linux and UNIX systems,
- EXECUTE_INTERACTION_ALGORITHM is enabled by default to perform instance traces to determine topologies for up to 1000 nodes. Set EXECUTE_INTERACTION_ALGORITHM=N to disable instance traces so that no topologies are displayed and the Transaction Reporter can aggregate data for greater numbers of nodes.