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

Limited supportBMC 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.

Configuring WebSphere MQ agentless services

Agents and their extensions are typically installed on the hosts that run the monitored applications. However, in most cases, you can choose whether to install the agent and the extensions on the host that runs the applications, or on a host that is separate from the application. 

  • Local agent-based monitoring and configuration: An agent and extensions are installed on each monitored WebSphere MQ server.
  • Remote (agentless) monitoring and configuration: The agent and the extensions are installed on a computer that is separate from the monitored application.

In both deployment scenarios, the agent and the extensions are installed on the same host computer and the agent communicates with the Topic Service. 

The following topics describe how to configure agentless services to monitor WebSphere MQ (alternatively, jump to this example of how to set up a queue manager for agentless monitoring):

Related topics

Determining-whether-to-use-agent-based-or-agentless-monitoring

Agent-architecture

 

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