Installing the WebSphere MQ on TPF monitoring extension

Before you begin

  • See the Supported Technologies section to verify the intended monitored technology is supported and that all footnote prerequisites are satisfied.
  • You have administration privileges on the Windows system.
  • The following files are on the class path:
    • com.bmc.mmpa.eaapi.jar
    • com.mqs.util.jar
    • slf4j-api-1.4.2.jar
    • slf4j-log4j12-1.4.2.jar
    • qpcapi.jar
    • qptpfwmq.jar
    • log4j-1.2.14.jar
  • The TMTM Extensible Agent is installed and available
  • JAVA_HOME is set as a system variable and points to the installation directory of Java.
    If your path contains multiple versions of Java, then the supported version must appear before any older, unsupported versions. If JAVA_HOME is modified, the system might require a restart.
  • The TPF systems are configured and running. They must have:
    • TPF 4.1 PUT 16 or higher
    • IPBridge installed and configured to communicate with the Windows system on which you are installing the TPF monitoring extension.
    • TPF Operations Server is installed and available through the IPBridge to the Windows system on which you are installing the TPF monitoring extension.
  • TrueSight Middleware and Transaction Monitor supports multiple queue managers with the same name as long as these queue managers reside on different TPF hosts. For this reason, in a multi-CPU loosely coupled environment:
    • IP Bridge is set up for any CPU using a different IP address or host name (that is, any CPU is considered a separate TPF host)
    • TPF host profiles are added due to IP Bridge set up for any CPU running the qptpfwmq --addhost command.

Note

You cannot use a configuration of a loosely coupled multi-CPU TPF system assigned a common IP address but having IP Bridge setup for any CPU on a different port.

Related topics

Running-performance-and-availability-monitoring-extensions

Running-the-WebSphere-MQ-on-TPF-configuration-monitoring-extension

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

Uninstalling-TMTM-performance-and-availability-monitoring-extensions

To install the WebSphere MQ on TPF configuration monitoring extension

  1. At a command prompt, change to the directory where the TPF monitoring extension was distributed.

  2. Unzip pkg_windows_qptpfwmq.zip into the applications directory. The table below lists the extracted files.

    Binary

    ASCII

    com.bmc.mmpa.eaapi.jar

    QPCONF.DEF

    com.mqs.util.jar

    framework.props

    slf4j-api-1.4.2.jar

    qplog.props

    slf4j-log4j12-1.4.2.jar

    qptpfwmq.bat

    log4j-1.2.14.jar

    qptpfwmq.console.conf

    qpcapi.jar

    qptpfwmq.service.conf

    qptpfwmq.jar

     

    wrapper.dll

     

    wrapper.exe

     

    wrapper.jar

     

  3. Reinstalling or upgrading only:
    • To stop TPF monitoring extension, enter qptpfwmq --stop. Alternatively, use the Windows Service Manager to stop the monitoring extension.
    • To remove the TPF monitoring extension, enter qptpfwmq --remove.
  4. Enter qpea --status to ensure that the TMTM Extensible Agent is running. If it is not running, enter qpea --start.
  5. To install the TPF monitoring extension, enter qptpfwmq --install. 

Where to go from here

 

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