In certain circumstances, you must specify the WebSphere® MQ installation
path by using two parameters in the kmcenv file
before the agent can work properly.
About this task
If any of the following cases applies to your Windows environment, complete the steps to
specify the installation path of WebSphere MQ:
- Only one copy of WebSphere MQ 7.1
or later is installed and it is installed to a single directory.
- Different copies of WebSphere MQ are
installed to different directories.
Procedure
- If you have installed different versions of WebSphere MQ on
the same system (including WebSphere MQ 7.1
or later), specify the library path of the latest WebSphere MQ version.
To specify the library path, add the library path of the
latest WebSphere MQ version
to the beginning of the PATH system environment
variable and restart the system.
For example, if
both WebSphere MQ 7.1
and 7.5 are installed, and the installation path of WebSphere MQ 7.5
is C:\IBM\WMQ75, add C:\IBM\WMQ75\bin to
the beginning of the PATH variable.Remember: If
the agent that you installed is 64-bit, specify the bin64 library
path of the WebSphere MQ,
for example, C:\IBM\WMQ71\bin64.
WebSphere Message Broker considerations: If WebSphere Message
Broker is
also installed on the same system, check whether the latest version
of WebSphere MQ is
supported by WebSphere Message
Broker before
you make the change. If the specified WebSphere MQ version
is not supported, the broker might not be able to find the appropriate
queue manager after the PATH value change.
- Specify different installation directories of WebSphere MQ with
the following two parameters in the kmcenv file:
- KMC_CURRENT_WMQ_INSTALLPATH:
Specify the
installation path of WebSphere MQ that
is to be managed by the current agent instance.
- KMC_LATEST_WMQ_INSTALLPATH:
Specify the
installation path of the latest version of WebSphere MQ that
is installed on the same system. If you have more than one copy of
the latest version installed on the same system, specify any of their
directories in this parameter.
Tip: You can do this step from the Manage
Tivoli Enterprise Monitoring Services window. In this window,
right-click the instance of ITCAM configuration agent for WebSphere MQ and
click . The kmcenv file
is open for you to edit.
Remember: - When
you edit the kmcenv file, make the changes before
the asterisk lines. Changes after the asterisk lines will be lost
after the agent is reconfigured from the Manage Tivoli Enterprise
Monitoring Services window.
- Both the two parameters are required in an agent configuration
file, no matter which WebSphere MQ is
managed by the current agent instance. For example, if the agent instance
is to manage WebSphere MQ 7.0.1,
you are also required to specify the KMC_LATEST_WMQ_INSTALLPATH parameter
in the agent configuration file. If the agent instance is to manage WebSphere MQ 7.5,
which is the latest version on the system, you must specify the installation
paths of WebSphere MQ 7.5
twice in the agent configuration file (one for KMC_CURRENT_WMQ_INSTALLPATH and
the other for KMC_LATEST_WMQ_INSTALLPATH).
- If only WebSphere MQ 7.1
or later is installed and it is installed to a single directory, specify
the same installation path for the two parameters.
- On Windows systems, those
parameter values must be embraced by double quotation marks, for example, KMC_CURRENT_WMQ_INSTALLPATH="C:\IBM\WMQ71", KMC_LATEST_WMQ_INSTALLPATH="C:\IBM\WMQ75".
Results
Important: If and only if you
have different versions of WebSphere MQ installed
on the same system, use different agent instances for different versions
of WebSphere MQ separately.
One agent instance discovers and configures only one single version
of WebSphere MQ. If
you use multiple agent instances for only one version of WebSphere MQ,
multiple records of the same queue manager in the configuration database
might cause configuration conflict.
Tip: To distinguish
multiple agent instances, set KMC_CLUSTERNAME parameter
in the configuration file.