Skip to Content

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

Information
Limited support BMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see MainView Middleware Monitor 9.2.

Installing the MainView monitoring extension

This section describes how to install the MainView monitoring extension on various platforms, and includes:

Related topics

Running-performance-and-availability-monitoring-extensions

Running-the-MainView-monitoring-extension

Running-application-transaction-tracing-transaction-monitoring-extensions

Uninstalling-MVMM-performance-and-availability-monitoring-extensions

Installing the MainView monitoring extension on Windows

The supported Windows platforms are listed in Supported-middleware-monitoring-technologies-for-performance-and-availability.

In this section, Windows commands are show with a bat extension on the qpmainview command. The .bat extension is optional. For example, qpmainview.bat --help and qpmainview --help perform the same operation.

  1. At a command prompt, change to the directory where the TMTM Agents and Extensions are installed.
  2. Unzip the contents of the pkg_*_qpmainview.zip package, as appropriate for your platform, to a sub-directory of the TMTM Agents and Extensions (e.g. into a directory named qpmainview).
  3. If you are not using the provided Java Runtime Environment (JRE), verify that JAVA_HOME is set in your environment. Do not edit qpmainview.bat to achieve this, because the file might be replaced during a reinstall or upgrade.
  4. To install the MainView Monitoring Extension as a Windows service, enter:

    qpmainview.bat --install
  5. To register the type definitions for the MainView Monitoring Extension, enter:

    qpmainview.bat --registerTypes
  6. For each MainView server to be monitored, add a preference for the monitoring extension:

    qpmainview.bat --addpref -srv:servername -host:hostname -port:port -usr:TSOuserid -pwd:TSOpassword

    where:

    servername is the name of the BMC MainView server (required). The name of the MainView server must match exactly the name used for the MainView server in the qpreg input script generated by the QPREGZ/REGISTER view in MainView.
    host is the IP address or hostname of the BMC MainView server (required).
    port is the port the BMC MainView server is listening on (required).
    TSOuserid is the TSO ID required to connect to the MainView server.
    TSOpassword is the password (required) for the TSOuserid.

    For example:
    qpmainview --addpref -srv:ABCD -host:ABCD.yourcompany.com -port:1234 -usr:TSOuserid pwd:TSOpassword
  7. Start the MainView Monitoring Extension by entering: qpmainview.bat --start

Installing the MainView monitoring extension on UNIX

The supported UNIX platforms are listed in Supported-middleware-monitoring-technologies-for-performance-and-availability.

Before you begin

  • Ensure that the TMTM Extensible Agent is installed on the agent machine.

To install the MainView monitoring extension on UNIX

  1. At a command prompt, change to the directory where the TMTM Agents and Extensions are installed.
  2. Unzip the contents of the pkg_*_qpmainview.zip package, as appropriate for your platform, to a sub-directory of the TMTM Agents and Extensions (e.g. into a directory named qpmainview).
  3. If you are not using the provided Java Runtime Environment (JRE), verify that JAVA_HOME is set in your environment. Do not edit qpmainview.sh to achieve this, because the file might be replaced during a reinstall or upgrade.
  4. To make the BMM-PA for MainView Extension file executable, enter chmod +x qpmainview.sh
  5. To register the type definitions for the TrueSight Middleware and Transaction Monitor for MainView Extension, enter:

    qpmainview.sh --registerTypes
  6. For each MainView server to be monitored, add a preference for the monitoring extension:

    qpmainview.sh --addpref -srv:servername -host:hostname -port:port -usr:UserName -pwd:Password

    where:
    servername is the name of the BMC MainView server (required). The name of the MainView server must match exactly the name used for the MainView server in the qpreg input script generated by the QPREGZ/REGISTER view in MainView.
    host is the IP address or hostname of the BMC MainView server (required).
    port is the port the BMC MainView server is listening on (required)
    UserName is the user name (required).
    Password is the password (required).

    For example:
    qpmainview --addpref -srv:ESAJ -host:esaj.bmc.com -port:4347 -usr:monitor32 -pwd:s75gt8y
  7. Run qpreg: qpreg file name
  8. To start the monitoring extension, enter: qpmainview.sh --start

Where to go from here


 

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

MainView Middleware Monitor 9.0