Chat now with support
Chat with Support

Foglight for IBM WebSphere MQ 5.5.5.9 - Installation Guide

Identity properties

Use the Identity properties to assign an identity to the monitored queue manager.
To set the connection profile:
1
On the navigation panel, under Dashboards, click Administration > Agents > Agent Status.
2
On the Agent Status dashboard, select the instance of the MQ Agent whose properties you want to modify and click Edit Properties.
3
Locate the Identity properties.
4
In the Queue Manager Name box, type the name of the queue manager instance that you want to monitor.
Queue manager names can be located by doing any of the following:
•
Running the IBM WebSphere MQ dspmq program on the monitored host.
•
Using the IBM WebSphere MQ runmqsc program.
•
Using the IBM WebSphere MQ Explorer.
Contact your IBM WebSphere MQ administrator if you are unsure of the queue manager name.
 
* 
IMPORTANT: Leaving this property blank causes the MQ Agent to fail and log a warning message. Ensure that the queue manager name you enter here is valid. The name is case sensitive.
5
In the MQ Group Name box, type the name of the queue manager group that you want to monitor.
The MQ group name can be used to group related queue managers together in the dashboards. You can assign any name to the queue manager for this purpose (for example, Payroll).
6
Click Save.
7
To specify the type of connection, see Connection properties.
Otherwise, click Back to Agent Status and activate the MQ Agent, as described in Activating MQ Agent instances and starting data collection .

Connection properties

Use the Connection MQ Agent properties to specify the type of connection.
The MQ Agent can connect to a queue manager either as a remote client or in Bindings mode. It is possible to have the agent running on the same host as your MQ system, and to operate as a remote client.
To set the connection properties:
1
On the navigation panel, under Dashboards, click Administration > Agents > Agent Status.
2
On the Agent Status dashboard, select the instance of the MQ Agent whose properties you want to modify and click Edit Properties.
3
Locate the Connection properties.
4
Select the applicable Remote Connection option: True or False.
•
Select True if you want to instruct the MQ Agent to remotely monitor the queue manager client. This is the default mode.
or
•
Select False if you want to instruct the MQ Agent to locally monitor the queue manager using a bindings (local) connection.
 
* 
IMPORTANT: Support for the Bindings mode is limited. Consult the Release Notes to confirm that your platform is supported before using this feature.
If you choose the bindings mode, the path to the IBM MQ Java libraries must be defined in an environment variable before starting the Agent Manager, as specified in the following table:
Table 4. Path and environment variables
Platform
Variable
Path
AIX
LIBPATH
64-bit libraries:
/usr/mqm/java/lib64
32-bit libraries:
/usr/mqm/java/lib
HP-UX
LD_LIBRARY_PATH
64-bit libraries:
/opt/mqm/java/lib64
32-bit libraries:
/opt/mqm/java/lib
Linux (POWER, x86-64 and zSeries s390x platforms)
Solaris (x86-64 and Sparc platforms)
Linux (x86 and zSeries platforms)
LD_LIBRARY_PATH
/opt/mqm/java/lib
Windows
PATH
64-bit libraries:
install_dir\java\lib64
32-bit libraries:
install_dir\java\lib
NOTE: When using Bindings mode on a 64-bit Windows monitored system, modify the PATH system variable to first point to the 64-bit libraries (install_dir\java\lib64), and then to the 32-bit libraries (install_dir\java\lib).
For additional information about connecting the queue manager in bindings mode, see your IBM MQ documentation or visit http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/index.jsp?topic=/com.ibm.mq.csqzaw.doc/jm10340_.htm.
5
For Remote monitoring only: Configure the MQ Agent to allow the creation of remote connections.
a
In the Host Name box, type the fully qualified name or IP address of the host machine on which the remote queue manager is running.
b
In the Server Channel box, type the name of the server connection channel on the remote queue manager.
c
In the Port Number box, type the listener port number of the remote queue manager.
6
Click Save at the bottom of the window to save the entries.
7
To set the Secure Sockets Layer (SSL) agent properties, see SSL properties.
Otherwise, click Back to Agent Status and activate the MQ Agent, as described in Activating MQ Agent instances and starting data collection .

SSL properties

If you want to enable the transmission of secure data over an insecure network, use the Secure Sockets Layer (SSL) set of agent properties
The MQ Agent supports connection to an MQ Server over a server connection channel enabled with SSL. Once the appropriate keys have been created and exchanged, the MQ Agent must be configured using the agent properties.
 
* 
IMPORTANT: Prior to SSL agent property configuration, the MQ system parameter “Authentication of parties initiating connections” must be set to Optional.
To set the Secure Sockets Layer properties:
1
On the navigation panel, under Dashboards, click Administration > Agents > Agent Status.
2
On the Agent Status dashboard, select the instance of the MQ Agent whose properties you want to modify and click Edit Properties.
3
Locate the SSL properties.
4
Select a cipher suite from the Cipher Spec list.
 
* 
NOTE: After changing the cipher suite for an MQ Agent, it may be necessary to restart the Agent Manager for that MQ Agent.
 
Table 5. Cipher suites
Cipher Spec
Connection Possible if SFIPS (No)
Connection Possible if SFIPS (Yes)
DES_SHA_EXPORT
Yes
No
NONE
N/A
N/A
NULL_MD5
Yes
No
NULL_SHA
Yes
No
RC4_MD5_EXPORT
Yes
No
RC4_MD5_US
Yes
No
RC4_SHA_US
Yes
No
TLS_RSA_WITH_AES_256_CBC_SHA (MQ 7.0.1.6+)
No
Yes
TRIPLE_DES_SHA_US
Yes
No
5
In the trustStore Location box, type the path to the MQ Agent's trust store.
The path must include the name of the file itself. For example: C:\Documents and Settings\foglight\.keystore
 
* 
IMPORTANT: Only one trust store location may be used for all MQ Agent instances running under a single Agent Manager.
6
In the trustStore Password box, type the password for accessing the agent's trust store.
* 
IMPORTANT: If you select a cipher spec from the Cipher Spec list, this value is mandatory.
7
Click Save.
8
To enable or disable monitoring of auto-discovered queues and channels, see Discovery properties.
Otherwise, click Back to Agent Status and activate the MQ Agent, as described in Activating MQ Agent instances and starting data collection .

Discovery properties

Use the Discovery Settings agent properties to enable the MQ Agent to automatically discover and monitor user-defined queues and channels for a queue manager.
A useful approach during an initial configuration is to enable auto-discovery, but disable the monitoring of discovered properties for queues and channels. When the agent starts, you can then manually edit the queue and channel lists, to enable the monitoring of only those queues and channels that are of interest to you.
After the installation, consider re-enabling the monitoring of discovered properties, so that the MQ Agent starts automatically monitoring any new queues that become available.
To set the Discovery Settings properties:
1
On the navigation panel, under Dashboards, click Administration > Agents > Agent Status.
2
On the Agent Status dashboard, select the instance of the MQ Agent whose properties you want to modify and click Edit Properties.
3
Locate the Discovery Settings properties.
4
Select the applicable Auto-discovery option: True or False. Auto-discovery is a scheduled collection which occurs by default once an hour.
Select True if you want the MQ Agent to automatically populate the queue and channel lists. Otherwise, select False.
5
Select the applicable Monitor Discovered Queues option: True or False.
 
* 
NOTE: This setting can be adjusted for each queue in the queue list at a later time. Setting it to False prevents the agent from monitoring discovered queues. A discovered queue that is not being monitored can later be added to the list of monitored queues, as described in Monitor lists properties
Select True if you want the MQ Agent to immediately start monitoring all auto-discovered queues. Otherwise, select False .
6
Select the applicable Monitor Discovered Channels option: True or False.
 
* 
NOTE: This setting can be adjusted for each channel in the channel list at a later time. Setting it to False prevents the agent from monitoring discovered channels. A discovered channel that is not being monitored can later be added to the list of monitored channels, as described in Monitor lists properties .
Select True if you want the MQ Agent to immediately start monitoring all auto-discovered channels. Otherwise, select False.
7
Select the applicable Monitor MQ System Objects option: True or False.
Select True if you want the MQ dashboards to display the metrics associated with system queues and channels (that is, SYSTEM.*). Otherwise, select False .
It is possible to manually add a subset of these objects to the queue or channel lists when only specific SYSTEM objects are useful. To do that, you can add entries to the queue list, each containing a desired SYSTEM object, for example, SYSTEM.ADMIN.PERFM.EVENT. For information about editing queue lists, see Monitor lists properties .
8
Click Save.
9
To set the items in the Queue and Channel lists, see Monitor lists properties.
Otherwise, click Back to Agent Status and activate the MQ Agent, as described in Activating MQ Agent instances and starting data collection .
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating