Writer instructions
Page title	For most spaces, this page must be titled Space announcements. For spaces with localized content, this page must be titled Space announcements l10n.
Purpose	Provide an announcement banner on every page of your space.
Location	Move this page outside of your home branch.
Guidelines	Adding-a-banner-announcement-to-a-space

Navigating the Monitor Console

The Monitor Console acts as the main interface for MainView Middleware Monitor (MVMM). IT Operations and other specialists use the Monitor Console to monitor applications, events, and devices, define users and security settings, or to diagnose problems.

This section includes:

	Console feature	Use
	Toolbar	The tool bar contains icon buttons that allow access to key operations. See Toolbar.
	Tabs	The Monitor Console tabs arrange the product's functionality as described under Tabs.
	Explorer pane	The explorer allows you to navigate to monitored objects in both their physical and logical trees. Expand the physical tree to select the objects whose attributes you want to see or modify. Expand the logical tree to select the logical types whose attributes you want to see or modify. Hide or show the explorer by clicking the globe icon in the tool bar.
	View pane	The view pane displays views and dashboards. See Working with views and dashboards.
	Alerts pane	Alerts can be warnings about your monitored objects or notifications that some condition has or has not been met. To configure alerts, see What-are-actions-and-how-to-define-them.
	Status bar	Status of the TMTM services. See Working-with-the-subscriber-services.

Toolbar

The Monitor Console toolbar, illustrated in the following image, duplicates some of the options available in the Monitor Console menu options.

Operations tab

The Operations tab contains two trees in the explorer.

The physical tree shows the networks, nodes/hosts, extensions, queue managers, and queue manager objects (queues, channels, processes, topics, subscriptions, authentication objects, namelists, listener objects, and service objects) configured for TMTM.
The logical tree shows the logical types and logical instances configured for TMTM. The objects at each level in both trees can contain attributes that can be monitored. The monitored information is presented in views (supplied or user-designed) and dashboards (user-designed) which open in the view pane.

The objects listed in the physical tree can be represented by their own views in the view pane. The logical tree contains logical types that are displayed in dashboards in the view pane. A logical type (and a related dashboard) might contain queues from different queue managers or queues from different monitored technologies.

In normal operation, the Operations tab operates in non-edit mode. In this mode it displays data as configured on the view pane.

Configuration and layout of the view pane is accomplished in edit mode. In this mode, the View pane toolbar appears and allows you to place display items on the view pane and configure them to display data. How this is done is described in detail in Working with views and dashboards.

Policies tab

The Policies tab allows the dynamic configuration of objects based on sets of expressions and actions that are configured in policies. 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.

There are options to Test Policies, Apply Policies, and Disable Policies (the Test and Apply options are also available in the Object Repository tab).

See Policies for more details.

Object Repository tab

The Object Repository tab stores objects; TMTM proactively discover all objects for WMQ and stores them in the Repository Manager.

When you connect an agent to the Topic Service, the information about that agent's WMQ and other monitored objects is stored in the repository.

The tree displays all the objects the repository knows about. Unlike the tree in the Operations tab, the Object Repository tab includes both monitored and unmonitored objects.

See Object Repository for more details.

Logical Types tab

The Logical Types tab presents a Logical Hierarchy, which enables you to combine objects and attributes that are connected, or in which you are specifically interested in.

You can then create a view that combines these objects and attributes into a specific and relevant view while removing attributes that are not relevant to this view.

Available Types are displayed in the left pane.
The center pane shows the Artifacts that are included in the type. It also shows the association to a physical object when looking at an instance.
The right pane is visible when looking at or creating an instance, and allows viewing or associating physical objects with the logical artifacts. When creating an artifact this pane contains type information.
There are several default types that are included by default.

See Logical types, logical instances, and artifacts for additional information.

Collections tab

The Logical Types tab presents a Logical Hierarchy, which enables you to combine objects and attributes that are connected, or in which you are specifically interested in.

You can then create a view that combines these objects and attributes into a specific and relevant view while removing attributes that are not relevant to this view.

Available Types are displayed in the left pane.
The center pane shows the Artifacts that are included in the type. It also shows the association to a physical object when looking at an instance.
The right pane is visible when looking at or creating an instance, and allows viewing or associating physical objects with the logical artifacts. When creating an artifact this pane contains type information.
There are several default types that are included by default.

See Logical types, logical instances, and artifacts for additional information.

History tab

The History tab contains the functionality required to create and maintain history rules. History rules control how monitored data is recorded and stored in the database for future use. History rules are attached to monitored objects either as concrete rules, or are attached to more than one object as rule templates. A rule template contains one history rule but it can be attached to more than one object.

Events tab

The Events tab allows you to create event rules, triggers, actions, and contacts and associate them with objects.
Event rules designed for a particular object type can be applied to any object of that type. For example, a rule created for a dead letter queue can be applied to any or all dead letter queues. The same is true for triggers, actions, and contacts.

Typical actions are:

Send a Monitor Console alert
Execute an external program
Send an e-mail message
Log a message to a file.

See Defining events, triggers, and actions for additional information.

Security tab

The Security tab enables the following operations:

Create user and group accounts that control access to TMTM.
Configure and enforce WebSphere MQ security. This level of security enforces any WebSphere MQ object security that is configured. For example, a WebSphere MQ secured queue might only allow messages to be read from it. In this instance, TMTM enforces the security and does not allow unauthorized users to put messages to the queue.
Allow administrators to review audit logs of actions taken by users.

See Defining user access and security settings for additional information.

BTM tab

The BTM tab contains all the functionality required to create and manage transaction pathways in or across the enterprise.

A TMTM transaction pathway model consists of:

message formats
activity implementations in the transaction pathway
a transaction pathway

The TMTM transaction pathway defines where in the physical environment transaction traffic is monitored. The transaction pathway, created and configured in the BTM tab, is a set of implemented activities each of which represents a monitoring point. The transaction pathway, shown in the BTM tab, is not a graphical representation of the whole or part of a physical network. The transaction pathway model tracks transactions from one activity to the next.

Each activity has configurable properties which define how transactions are handled at that point in the pathway.

Each activity is implemented by an activity implementation which contains definitions of the host, platform, and technology extension at the monitoring point. Transaction pathways can contain activities across all supported technology/platform pairs. See Supported middleware monitoring technologies (Performance and Availability) and Supported application transaction tracing technologies (Transaction Monitoring).

Message formats define how transactions are identified in TMTM. See Defining transaction pathways to monitor your infrastructure for additional information.

Package Distribution tab

The Package Distribution tab enables you to distribute and update various packages automatically - including toolkits and extensions for a variety of platforms - at any time to a directory on your agent machine. Distribution and upgrade can also be scheduled for a specific time. Refer to the Distributing-the-Agent-and-extensions-via-the-launch-page for details. Note that the packages are only distributed; the packages are not installed automatically.

Monitor Console menus

The following table describes menu options unique to TMTM.