Overview of MainView Middleware Monitor

This topic provides an overview of MainView Middleware Monitor (MVMM ), its components, and who uses it. The topic includes the following sections:

Related topics

Architecture

Monitoring

Overview-of-policies

Overview-of-objects

What can I do with MVMM ?

MVMM  is a monitoring tool that helps you deal with the ever-growing challenge of monitoring transactions. MVMM  offers the following core capabilities:

  • Monitor all transactions passing through middleware applications across many technologies and platforms.
  • Automatically isolate infrastructure problems to specific components in an application, greatly reducing time to problem resolution. 
  • Access end-to-end middleware transaction tracing and analyze historical data to assess trends.
  • View and customize dashboards to show how captured metrics relate to the application flow.
  • View and access historical records of the past values of middleware assets.

How do I use MVMM ?

Your usage of MVMM  depends on your product role, as shown in the following table:

Role

How do I use MVMM ?

System Administrator

Installs the product, sets up security

For more information, see:

Middleware Administrator

Makes middleware changes via MVMA

For more information, see MainView Middleware Administrator

Product Administrator (typically Middleware Administrator, Application Support or Middleware Developer): 

Sets up events, history, monitoring, and so on.

For more information, see:

Product User (typically Middleware Administrator, Application Support or Middleware Developer)

 Monitors the middleware environment

For more information, see Using. MainView Middleware Administrator


What are the different components of MVMM ?

The different components that make up MVMM  are described in the following table. For further information about these components and their role in your environment, see Architecture. 

Failed to execute the [excerpt-include] macro. Cause: [Error number 2 in 0: No wiki with id [confluencePage:page] could be found]. Click on this message for details.

While the monitoring of IBM MQ objects is done using MVMM , the actual management of IBM MQ objects, including creating and defining the IBM MQ queue manager objects such as queues, topics, channels, etc, is done using MainView Middleware Administrator(MVMA).

MVMA manages each IBM MQ queue manager via a IBM MQ client connection. Within MVMA, the client connection and its properties are defined by a WMQ Connection (see below).

How MVMM  uses agents and extensions: a brief overview

MVMM  enables you to monitor IBM MQ, largely through the monitoring and discovery of IBM MQ objects and by registering the objects of interest for monitoring.  

MVMM  uses local or remote agents and IBM MQ extensions to monitor IBM MQ queue managers. When remote, monitoring is also performed via a IBM MQ client connection. A remote configuration is also known as "agentless" as there is no agent physically installed on the remote system. However, there is still an agent installed locally, which can lead to some confusion when talking about agentless configurations. 

When the MVMM agents and IBM MQ extensions have been deployed they can be used to create the IBM MQ server connection channel to support the (MVMA) client connections and create the MVMA WMQ connection. For further information on the integration and connection with MVMA, see MainView-Middleware-Administrator-integration-options.


In this documentation, the IBM MQ and MQSeries product is referred to as IBM MQ.

Also, this documentation refers to the following IBM products as IBM IIB/ACE:

  • New Era of Networks Rules and Formatter
  • MQ Series Integrator
  • WebSphere MQ Integrator
  • WebSphere Business Integration Message Broker
  • IBM Integration Bus
  • App Connect Enterprise

Where to go from here

For further information on policies and objects and how they work in MVMM , see Overview-of-policies and Overview-of-objects.

To get started with MVMM , see Getting-started-for-system-administrators and Getting-started-for-users.



 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*