Agent installation overview

Before installing the MainView Middleware Monitor (MVMM ) agent and monitoring extensions in a traditional agent-based configuration, BMC recommends you review this section to confirm the requirements and to gain an overview of the typical installation process.

Note

For information about configuring "agentless" IBM MQ Monitoring, see Configuring IBM MQ agentless services.

Related topics

Installing-the-Agent-and-monitoring-extensions

Installing

System-requirements-and-product-compatibility 

The general installation process involves the following steps:

  1. Identify the platforms and technologies (machines) to be monitored. Supported middleware monitoring technologies (Performance and Availability) lists the available platform/technology pairs supported for performance and availability monitoring and transaction tracing by MVMM .
  2. Identify the extensions required by each machine.
  3. Plan your agent and extensions layout (see Defining your Agent installation layout).
  4. Plan how you want the agent to connect to the service set (see Choosing how the Agent installation and services communicate).
  5. Distribute the bootstrap package or manually distribute the files.
  6. Install the bootstrap package or files and packages manually distributed.
  7. Configure the MVMM  Extensible Agent environment (MQS_HOME environment variable).
  8. Start the MVMM  Extensible Agent.
  9. Configure the MVMM  Extensible Agent.
  10. Start the MVMM  Configuration Agent.
  11. Distribute extensions packages.
  12. Install and configure the extensions. See the relevant sections in the Administering section for more information about the supported platform.
  13. Enable monitoring for each extension.
  14. Start the required extensions (typically by entering a simple command in a command prompt). Instructions are provided in the corresponding sections in the Administering section.

Note

Password preferences are stored in the eaa.xml file in the agent directory. The passwords are encoded using obfuscation. Note that this obfuscation is not cryptographic encryption. Care must be taken to ensure that the agent and extension files and directories have sufficient protection to prevent unauthorized individuals from accessing these parameters.

 

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