This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.
BMC Middleware Management - Performance and Availability
BMC Middleware and Transaction Management
BMC Application Transaction Tracing BMC Middleware Management - Performance and Availability BMC Middleware Monitoring BMC TrueSight Middleware Monitor BMC TrueSight Middleware Transaction Monitor
Is there any place where all the steps to install the agent and WMQ extensions is concentrated?
Installing BMM 8.0.01 Agents and WMQ Extensions on UNIX
The New Default Layout for Agents and Extensions
The directory layout for agent and extensions is new and different in BMM 8, and is now called the "default layout". BMC recommends that you maintain this layout to ensure compatibility with future releases and features.
The default distribution assumes this layout, and has a default configuration based on this layout (specifically, the location of the Java Runtime Environment).
The default layout is shown below. This layout is created when unzipping the bootstrap package:
The root of this directory (
<AGENTS> in the example above), is referred to as the directory where the BMTM agents and extensions are installed, and installations typically occur relative to this location.
Configuring the MQS_HOME system environment variable for the Default layout
The BMTM Extensible Agent, BMTM Configuration Agent and most performance and availability monitoring extensions have all the required files located in the directory where they are executed. However, if you wish to consolidate where logging is controlled and where log files reside you may place
QPLog.ini in a directory specified by the
MQS_HOME system environment variable. This is recommended for supportability.
BTM: The directory specified by the
MQS_HOME system environment variable is also used as a well-known location for packages and BTM deployments which are distributed.
BTM: Some TrueSight Middleware and Transaction Monitor extensions and applications which are monitored by a BTM Extension need the
MQS_HOME environment variable pointing to a directory with the
QPLog.ini file. If not set up properly, monitoring of that application can fail due to translation issues and the btm log files may be written to the
To configure the MQS_HOME system environment variable on UNIX
The following approaches can be used for defining the
/home/$username/.profileor shell equivalent in the users home directory, but this works only for this user when they have a login shell
/etc/profileworks globally for all users who have a shell logon
/etc/environmentworks for all users without a shell login. If you do an
su - usernamethe variable is gone, then
- define it for a service in, for example,
env = MQS_HOME=/directory_path
- Control the agent and extensions through shell scripts which have defined
- Set and export the system environment variable to a directory of your choice where all logs and other BTM files are to be saved. This should be done from a logon script such as .profile or whatever is applicable for your default shell. This should be the same directory and set for all users which run an extension.
- Reinitiate your profile to ensure the system environment variable is set. Under Linux it may help to identify if a running process has an environment variable by looking in
Additional DirectoriesThe following additional subdirectories may also be used.
- mqs_home is the directory defined in the MQS_HOME system environment variable.
- ExtensionConfig is the default directory that contains the extension configuration files. This directory is automatically created and managed by the BMTM Configuration Agent when the system environment variable MQS_HOME is defined (when the BMTM Configuration Agent is started).
- AgentDistribution is the default directory that contains the agent distribution files. This directory is automatically created and managed by the BMTM Configuration Agent when the system environment variable
MQS_HOMEis defined (when the BMTM Configuration Agent is started).
- ManualDeployments is a directory for manual deployments of BTM models.
Distributing the BMTM Extensible Agent and extensions via the launch page
This section describes how to obtain the bootstrap package for your system that contains the BMTM Extensible agent package and other common packages.
To obtain the relevant bootstrap package for your system:
- Open Internet Explorer.
http://hostname:15007in the URL field, where:
hostnameis the hostname or IP address of the computer running the BMC MTM Application Service
15007is the default port used by the BMC MTM Application Service
- From the displayed page, click
Download Agents. A list of all the supported agent platforms is displayed, with links to download the package in zip, tar, and tgz formats.
- Choose the Agent Configuration. Default is "Agent does not use a Secure Tunnel Connection". For more information about the other options, see the Installation Guide page 55.
- Optional: enter a description for the agent. This description can be used with Policies to have certain actions performed when this agent first connects to the services.
- Download the bootstrap package by clicking the appropriate link to download the package in zip, tar, or tgz format.
- Transfer the bootstrap package to the target system.
Installing the Bootstrap Package
If you have not made a backup of the agent directory, do so now. The
tar utility is recommended over zip.
- In the command prompt, set your working directory to the directory where the agent installation will reside (
- Verify that the
MQS_HOMEsystem environment variable has been configured. Enter
- Expand the bootstrap package in the
- Change to the
QPTTAB.DATto the directory you defined for the
MQS_HOMEsystem environment variable. This file is needed if any of your transactions must have their message format CCSID converted. If you are unsure if any of the message formats must be converted, you should still add this file to the
- Make qpea executable, for example:
chmod +x qpea
- Start the BMTM Extensible Agent:
- Change to the
- Start the Configuration Agent, enter:
The service connection information was pre-configured in the bootstrap and the Extensible Agent should connect to the BMM server without further configuration.
Secure Tunnel: Note that the secure tunnel information was also pre-configured in the bootstrap and the Extensible Agent should connect unless additional Secure Tunnel certificate configuration is required.
- (Optional) Using cron or the
/etc/rc.d/init.ddirectory, configure the BMTM ExtensibleAgent and BMTM Configuration Agent to start automatically when the computer is restarted.
Note: Although most shells can be used with TrueSight Middleware and Transaction Monitor, many of the script files are written for the Korn shell.
Installing the WebSphere MQ Configuration and Monitoring Extensions on UNIX platforms
Before you begin
libstdc++.so.6 is installed on Linux. This is required for SSL/TLS because the IBM WebSphere MQ GSKit SSL/TLS libraries supplied with MQ depend on
Ensure that the BMTM Extensible Agent is installed on the agent machine.NOTE: The WebSphere MQ Monitoring and Configuration extensions must be able to find the local MQ installation (either the server for Agent based configurations or the MQ Client for agentless configurations) on the installed host. The extensions look in the default installation location automatically, but may fail to locate the installation when multiple WebSphere MQ versions are installed (in MQ 7.1 and above), when WebSphere MQ is not installed in the default location, or when no WebSphere MQ 7.x is designated as the primary installation. In these situations you must configure the WebSphere MQ Monitor preference DefaultMQInstallationPath to point to the path to any valid WebSphere MQ installation. This can be configured via the Configuration Manager Agent Preferences dialog or via
IBM WebSphere MQ 7.0.1 single version installation
- On AIX with 32/64-bit Queue Managers and IBM WebSphere MQ symbolic links are pointing from
/usr/mqm/lib, you need to set the
LIBPATHenvironment variable to contain the 64 IBM WebSphere MQ library directories. They should precede other directories, as in the examples below.
- On AIX with 64-bit Queue Managers without IBM WebSphere MQ symbolic links pointing from
/usr/mqm/lib, set the
- On all other UNIX/Linux IBM WebSphere MQ 7.0.1 installations, set the
IBM WebSphere MQ 7.1, MQ 7.5 and 8.x single installation with default installation path
No specific action is required.
IBM WebSphere MQ 7.x and 8.x single installation with non-default installation path
Set DefaultMQInstallationPath with agentpref.
IBM WebSphere multi-version installations
Set DefaultMQInstallationPath with agentpref to the most recent IBM WebSphere MQ version.
agentprefutility is installed in the
AIX: agentpref.sh --set "WebSphere MQ Monitor" DefaultMQInstallationPath /usr/mqm
Linux: agentpref.sh --set "WebSphere MQ Monitor" DefaultMQInstallationPath /opt/mqm
You may encounter a port conflict for port 6001 betwen the WebSphere MQ Monitoring Extension (and qpmon) and The X WIndow System on UNIX. The qpmon port is changeable and can be redefined as necessary. The port is changed by setting the
ServicePort extension preference:
agentpref.sh --set "WebSphere MQ Monitor" ServicePort 6001
Restart the agent and extensions after making this change.
To install the WebSphere MQ Configuration and Monitoring Extensions on a UNIX platform
- Open a command prompt and change to the
- Make the following files executable; for example:
chmod +x qpmon
chmod +x qpcfg
- At a command prompt change to
- If you are reinstalling or upgrading the BMTM Extensible Agent:
This is to check that the BMTM Extensible Agent is running. If it is running, stop it with:
- Restore your backup copy of the
eaa.xmlfile to the
- Install and start the extensions:
This is to check that the BMTM Extensible Agent is running. If it is not running, start it with:
- Start the configuration extension. Enter:
- Starr the monitoring extension. Enter:
- (Optional) Using cron or the
/etc/rc.d/init.ddirectory, configure the BMTM Extensible Agent and WebSphere MQ extensions to start automatically when the computer is restarted.
WARNING regarding 32-bit extensions and WebSphere MQ 64-bit commands: When running some BMTM Extensible Agent extensions (qpmon, qpcfg) you may run into a problem where the extensions attempt to load the wrong WebSphere MQ libraries. Whether this occurs depends on the version of the executables (32-bit or 64-bit), the version (and location) of the WebSphere MQ installation, and the entries in the library path.
This is an example of the error:
exec(): 0509-036 Cannot load program qpcfg because of the following errors: 0509-150 Dependent module /usr/mqm/lib64/libmqm.a(libmqm.o) could not be loaded.
0509-103 The module has an invalid magic number.
Beginning with WebSphere MQ 6, WebSphere MQ uses 64-bit commands and supplies
lib64 directories containing shared libraries that the extensions use (e.g.
Most of TrueSight Middleware and Transaction Monitor’s extensions are 32-bit and require the 32-bit versions of the WebSphere MQ libraries. These extensions could fail to start if the library path (
LIBPATH / LD_LIBRARY_PATH) includes WebSphere MQ’s lib64 directory before its lib directory. (The inverse could also occur for the 64-bit extensions if the lib directory is specified before the lib64 directory.) To prevent the error, ensure that the library path is set correctly (the
lib directory appear before the
You must keep both directories on the path because WebSphere MQ programs still require a reference to the lib64 directories to run.
Additionally, IBM hard-coded a path into their commands using
RUNPATH can help ensure that the correct libraries are loaded, but only if WebSphere MQ is installed in the default location. If the default location is not used, then setting the proper library path may be required.