Glossary
action
An action is used to alert the user that a condition has become true. For example, some of the actions the MVMM Event Service can take include sending a Monitor Console alert, executing an external program, and sending an e-mail message.
agent policy
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.
collection
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.
Configuration Manager
A web-based administration interface that was integrated with MVMM 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 MainView Middleware Administrator (Monitor Edition), which is also embedded in the MVMM product. For more information, see the MainView Middleware Administrator (Monitor Edition) glossary item.
dashboard
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.
event
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
- Triggers
- Actions
- Contacts (used with action types that require contacts)
event journal
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 MVMM 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 template
Event templates provide a way to automatically generate rules based on similar triggers and actions, instead of having to produce rules one by one.
Monitor Console
A Java-based interface to the MVMM , via which the main functionality is performed.
monitoring extension
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.
object repository
The object repository, which is graphically represented in the Object Repository tab in the Monitor Console, stores objects; MVMM proactively discovers all objects for IBM_MQ and stores them in the Repository Manager.
policy
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.
Report Designer
The MVMM Eclipse IDE for Java and Report Developers enables you to import, design and preview MVMM History Reports before publishing them to MVMM . Once published, the report designs can be incorporated into views and dashboards in the Monitor Console. For brevity, MVMM Eclipse IDE for Java and Report Developers is referred to as the "MVMM Report Designer".
services
The services that run MVMM are:
- MVMM Topic Service
- MVMM History Service
- MVMM Event Service
- MVMM Application Service
- MVMM Client Gateway Service
- (Optional) MVMM ProactiveNet Service
services.cfg
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.
trigger
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).
MainView Middleware Administrator (Monitor Edition)
The "lite" version of MainView Middleware Administrator, customized for integration with MVMM . This web-based interface enables you to manage queue managers, queues, channels, and other objects and replaces the Configuration Manager (see above), which was available in earlier versions of the product.