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 | |
How does MainView Middleware Monitor work?
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 analyse 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 will depend on your product role, as shown in the following table.
Role | How do I use MVMM? |
|---|---|
| System Administrator: Installs the product, sets up security See: Planning, Installing, Upgrading, Integrating, Defining security settings |
| Middleware Administrator: Makes middleware changes via MVMA |
| Product Administrator (typically Middleware Administrator, Application Support or Middleware Developer): Sets up events/history/monitoring/etc See: Administering, Using |
| Product User (typically Middleware Administrator, Application Support or Middleware Developer): Monitors the middleware environment 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.
How MVMM uses agents and extensions: a brief overview
MVMM enables you to monitor WebSphere MQ, largely through the monitoring and discovery of WebSphere MQ objects and by registering the objects of interest for monitoring.
MVMM uses local or remote agents and WebSphere MQ extensions to monitor WebSphere queue managers. When remote, monitoring is also performed via a WebSphere 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 WebSphere MQ extensions have been deployed they can be used to create the WebSphere 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.
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.