This glossary contains terms that are relevant to the TrueSight Middleware and Transaction Monitor (TMTM) product.
An action is used to alert the user that a condition has become true. For example, some of the actions the TMTM Event Service can take include sending a Monitor Console alert, executing an external program, and sending an e-mail message.
A file that determines how associated agents collect and manage data. First, the relevant technology is selected for the policy to monitor, then the level of monitoring itself, and then the policy is enabled.
Collections, or View Collections, are the building blocks for the Dashboard Wizard and are accessed from the Collections tab in the Monitor Console. You can create a group of view controls based on an Object type; then when you use the Dashboard Wizard, you can select the collection and as a result creating the logical dashboard becomes a much more intuitive task.
A web-based administration interface that was integrated with TMTM prior to version 8.1.00. It managed queue managers, queues, channels, and objects. Beginning with version 8.1.00, these functions are available from the TrueSight Middleware Administrator (Monitor Edition), which is also embedded in the TMTM product. For more information, see TrueSight Middleware Administrator (Monitor Edition).
A dashboard is a data and graphical representation of a logical type which in turn is an abstraction of parts of the entire transaction pathway selected especially for simultaneous monitoring and display. A dashboard is different from a view, in that a view displays data in one physical object (or more than one physical object in the same queue manager) and a dashboard displays data in many physical objects simultaneously.
An event is a trigger/action pair, defined by event rules. An event rule is a combining of a trigger and an action. Specifically, an event rule contains the following components:
- The rule name
- Contacts (used with action types that require contacts)
The event journal, accessed via the Operations or Events tab in the Monitor Console, enables you to determine what events occurred and when they occurred. For example, you can query TMTM to show you events that occurred overnight for all objects (this serves as an audit log of events), or events that occurred on a particular object (or a set of objects).
Event templates provide a way to automatically generate rules based on similar triggers and actions, instead of having to produce rules one by one.
A Java-based interface to the TMTM, via which the main functionality is performed.
There are two types of monitoring extensions: performance and availability monitoring extensions, and application transaction tracing (transaction monitoring) extensions. These extensions are compatible with a variety of technologies and platforms.
The object repository, which is graphically represented in the Object Repository tab in the Monitor Console, stores objects; TMTM proactively discovers all objects for WMQ and stores them in the Repository Manager.
Policies allow the dynamic configuration of objects based on sets of expressions and actions. Policies can apply at an agent level,or an object level, and you can create groups of policies to allow easier association and application of policies.
The BMTM Eclipse IDE for Java and Report Developers enables you to import, design and preview TMTM History Reports before publishing them to TMTM. Once published, the report designs can be incorporated into views and dashboards in the Monitor Console. For brevity, BMTM Eclipse IDE for Java and Report Developers is referred to as the "TMTM Report Designer".
The services that run TMTM are:
- TMTM Topic Service
- TMTM History Service
- TMTM Event Service
- TMTM Application Service
- TMTM Client Gateway Service
- (Optional) TMTM ProactiveNet Service
This file sets configuration options for the services and for some options needed by the Monitor Console. One services.cfg file must be installed for each computer the services are installed on.
A sequence of requests and related operations, such as updating a database, that is treated as a unit to satisfy a business need. A transaction is named after the first request in an application that is received by a monitored application server.
A transaction pathway is a visual representation or model of your business process mapped to the technologies that implement it using logical representations called activities. The creation of the transaction pathway model is accomplished using the BTM tab in the Monitor Console. Once a transaction pathway model has been defined there are many tasks you can perform, including retain the details (including payload) of a transaction in history for analysis, create Service Level Agreements with thresholds, and collect Key Performance Indicators of objects monitored by the transaction pathway.
A trigger is a user-defined condition that is used in a rule or template to determine if a rules action should be performed (or fired).
TrueSight Middleware Administrator (Monitor Edition)
The "lite" version of , customized for integration with TMTM. This web-based interface enables you to manage queue managers, queues, channels, and other objects and replaces Configuration Manager, which was available in earlier versions of the product.
TrueSight Middleware Administrator (TSMA) has been rebranded to MainView Middleware Administrator (MVMA). Note that TMTM supports TSMA 8.2 and MVMA 9.0.
This wiki includes references to both TSMA and MVMA, as both are currently supported by TMTM 8.1.