Overview of MainView Middleware Monitor


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

How do I use MVMM ?

How you can use MVMM depends on your product role. 

Role

Use

System Administrator

Installs the product and 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

What are the different MVMM components?

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

Component

Description

Reference

Monitor Console

Web-based interface that enables you to view dashboards and monitored information and configure security, events, history, and policies

Database

Contains configuration information, object repository and raw and summarized history data

MVMM 

 server

Topic Service

Receives data from the Agents and functions as a broker for the subscriber services

Subscriber services

The following subscriber services can receive data from the Topic Service:

  • Application Service: makes data available to user in dashboard
  • History Service: stores data into the database for reporting and analysis
  • ProactiveNet Service: streams data to TrueSight Infrastructure Management or ProactiveNet
  • Event Service: detects and alerts on conditions

Agentless service

Provides an optional way in which you can monitor some applications through an "agentless" configuration where no 

MVMM 

 software is installed on the monitored technology host

Monitored host

Extensions

Specific to each technology, extensions capture data from each corresponding technology and then passes it to the Agent that publishes it

Agents

Installed on each system, there is one operating-specific Agent that accepts the data from all extensions and publishes it to the Topic Service

Component

Description

Reference

Monitor Console

Web-based interface that enables you to view dashboards and monitored information and configure security, events, history, and policies

Database

Contains configuration information, object repository and raw and summarized history data

MVMM 

 server

Topic Service

Receives data from the Agents and functions as a broker for the subscriber services

Subscriber services

The following subscriber services can receive data from the Topic Service:

  • Application Service: makes data available to user in dashboard
  • History Service: stores data into the database for reporting and analysis
  • ProactiveNet Service: streams data to TrueSight Infrastructure Management or ProactiveNet
  • Event Service: detects and alerts on conditions

Agentless service

Provides an optional way in which you can monitor some applications through an "agentless" configuration where no 

MVMM 

 software is installed on the monitored technology host

Monitored host

Extensions

Specific to each technology, extensions capture data from each corresponding technology and then passes it to the Agent that publishes it

Agents

Installed on each system, there is one operating-specific Agent that accepts the data from all extensions and publishes it to the Topic Service

Warning

Important

You use MVMM  to monitor IBM MQ objects, but you should use MainView Middleware Administrator to manage them, including creating and defining the IBM MQ queue manager objects, such as queues, topics, and channels. For more information, see MainView Middleware Administrator

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.

How MVMM uses agents and extensions

You use MVMM to monitor IBM MQ, largely by monitoring and discovering IBM MQ objects and by registering objects of interest for monitoring.  

MVMM uses local or remote agents and IBM MQ extensions to monitor IBM MQ queue managers. When using a remote agent, MVMM also monitors via a IBM MQ client connection. A remote configuration is also known as agentless because there is no agent physically installed on the remote system (even though an agent is still installed locally).

You can use deployed MVMM agents and IBM MQ extensions to create the IBM MQ server connection channel to support the MVMA client connections and create the MVMA WMQ connection. For more information about on the integration and connection with MVMA, see MainView-Middleware-Administrator-integration-options.


Information

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 more information about 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.

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 middleware assets.

 

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

MainView Middleware Monitor 9.2