Minimum System Requirements

Minimum System Requirements
Java Virtual Machine	Oracle JDK or JRE at version 1.8.0 or above
Operating Systems	Anything that supports Java 8
Memory	1GB RAM to support up to 4 queue managers with approximately 200 objects (queues, channels, etc) and 5000 event or accounting / statistics messages.
Disk Space	100MB
WebSphere MQ	WebSphere MQ v6 or above. NOTE: PUBSUB functionality does not work monitoring MQ6 queue managers.

Table 4: Datatype to Category mapping

Preparing for installation

Before installing, ensure all the prerequisite requirements have been met by completing this checklist.

Prerequisite Installation Requirements

File system

A file system with 250mb of space is required for the installation and the ongoing logging which will be done by the Lamaxu. This requirement may increase if you choose to maintain logs for a longer period.

Ensure the file system is owned by the user you plan to run the Lamaxu as and has been granted read, write and execute rights for the owner.

User account

A user which owns the file system created earlier and has read, write and execute rights on it.

Installation archive

Download the installation archive from the customer portal of the QueueMetrix website.

The available artefacts are:

LAMAXU-N.N.N-[NNNN]-bundle.tar.gz (Unix variants)
LAMAXU-N.N.N-[NNNN]-bundle.zip (windows or other)

Where N.N.N = to the appropriate version (for example 1.6.5) and [NNNN] is a qualifier which may be the mode (e.g. BETA) or another build instance number.

Table 5: Prerequisite Installation Requirements

Installing on Linux

Installation Steps
Install Command Reference
Starting and Stopping
- On Centos 7 and RedHat 7
- On Centos 6, RedHat 6 and Amazon Linux

Download the Linux RPM package from https://www.queuemetrix.com/download

Installation Steps

Login to the target server.
Copy the downloaded RPM package to the /tmp directory
Install the RPM package as the root user using the command below where {version} is the version of Lamaxu being installed.The root user is required for the installation as it is required to create the Lamaxu service.
1. rpm -iv /tmp/lamaxu-{version}.x86_64.rpm

NOTE: The RPM package installation will create a user and group named 'lamaxu' if it does not already exist. This is required in order to set non-root permissions on the installed files.It's suggested that you have this user created prior to the installation where identity management processes are required.

Install Command Reference

Installing on Linux (UNIX)
Installation directory	/opt/queuemetrix/lamaxu-{version}
User	lamaxu
Group	lamaxu
Install Command	rpm -iv /tmp/lamaxu-{version}.x86_64.rpm
Uninstall Command	rpm -e lamaxu

Starting and Stopping

On Centos 7 and RedHat 7

systemctl start lamaxu
systemctl stop lamaxu
systemctl check lamaxu
systemctl restart lamaxu

On Centos 6, RedHat 6 and Amazon Linux

service lamaxu start
service lamaxu stop
service lamaxu check
service lamaxu restart

Installing on Windows

Download the Windows Install package from https://www.queuemetrix.com/download

Enter the Lamaxu Installation location

License Agreement

Enter the Lamaxu Shortcut name

Completing Setup

Confirm the post install options. It's recommended you leave the options set as shown below.

Start Menu Options

Once Lamaxu has been installed there will be a new application in the Start menu

Configuration GUI

Click on 'Configure', the default username and password is admin/password.

In some cases it may be necessary to manually install Lamaxu as a Windows Service as described below.

Manually Installing Lamaxu as a Windows Service

The Open Source project ‘Yet Another Java Service Wrapper’, https://sourceforge.net/projects/yajsw/ can be used to install the Lamaxu agent as a Windows service.

Download and extract the YAJSW bundle then edit the YAJSW project’s configuration file named, conf/wrapper.conf. Locate and edit the properties below to match your installation of Lamaxu.

Example YAJSW wrapper.conf File

#********************************************************************
# working directory
#********************************************************************
wrapper.working.dir=C:\\Program Files (x86)\\QueueMetrix\\LAMAXU\\bin\\# Java Application main class
wrapper.java.app.mainclass=com.qm.lamaxu.Main# Title to use when running as a console
wrapper.console.title=Queuemetrix LAMAXU IBM MQ Monitoring Agent#********************************************************************
# Application Console Properties
#********************************************************************
# Title to use when running as a console
wrapper.console.title=Queuemetrix LAMAXU IBM MQ Monitoring Agent#********************************************************************
# Wrapper Windows Service and Posix Daemon Properties
#********************************************************************
# Name of the service
wrapper.ntservice.name=LAMAXU# Display name of the service
wrapper.ntservice.displayname=LAMAXU# Description of the service
wrapper.ntservice.description=Queuemetrix LAMAXU IBM MQ Monitoring Agent

Add the following lines to the end of the file. Make sure the full path to the java.exe command is set, as well as the path to the location LAMAXU is installed.

wrapper.java.command = C:\\Program Files (x86)\QueueMetrix\\LAMAXU\\jre\\bin\\java.exe
wrapper.java.classpath.1 = C:\\Program Files (x86)\QueueMetrix\\LAMAXU\\config
wrapper.java.classpath.2 = C:\\Program Files (x86)\QueueMetrix\\LAMAXU\\lib\\*.jar
wrapper.app.parameter.1 = -config
wrapper.app.parameter.2 = C:\\Program Files (x86)\QueueMetrix\\LAMAXU\\config\\config.xml
wrapper.java.additional.1 = -d64
wrapper.java.additional.2 = -DLOG_PATH=C:\\Program Files (x86)\\QueueMetrix\\LAMAXU\\logs\\
wrapper.java.additional.3 = -Djavax.net.ssl.trustStore=C:\\Program Files (x86)\\QueueMetrix\\LAMAXU\\config\\truststore.jks
wrapper.java.additional.4 = -Dcom.ibm.mq.cfg.useIBMCipherMappings=false
wrapper.java.additional.5 = -Djava.rmi.server.hostname = 0.0.0.0
#Adjust the values below to set the max amount memory Lamaxu can use.
wrapper.java.additional.6 = -XX:+UseParallelGC
wrapper.java.additional.7 = -Xms4G
wrapper.java.additional.8 = -Xmx14G
wrapper.java.additional.9 = -XX:-UseGCOverheadLimit

Once the wrapper.conf file has been updated, install the windows service using the command below.

C:\Program Files (x86)\QueueMetrix\LAMAXU\bin\yajsw\bat>installService.bat
C:\Program Files (x86)\QueueMetrix\LAMAXU\bin\yajsw\bat>cd C:\Program Files (x86)\QueueMetrix\LAMAXU\bin\yajsw\bat\
C:\Program Files (x86)\QueueMetrix\LAMAXU\bin\yajsw\bat>call setenv.bat
"java" -Xmx30m -Djna_tmpdir="C:\Program Files (x86)\QueueMetrix\LAMAXU\bin\yajsw\bat\/../tmp" -Djava.net
.preferIPv4Stack=true -jar "C:\Program Files (x86)\QueueMetrix\LAMAXU\bin\yajsw\bat\/../wrapper.jar" -i
"C:\Program Files (x86)\QueueMetrix\LAMAXU\bin\yajsw\bat\/../conf/wrapper.conf"
YAJSW: yajsw-beta-12.04
OS : Windows 8.1/6.3/amd64
JVM : Oracle Corporation/1.8.0_66/C:\Program Files (x86)\QueueMetrix\LAMAXU\jre/64
Apr 16, 2016 10:16:32 PM org.apache.commons.vfs2.VfsLog info
INFO: Using "C:\Users\Matt\AppData\Local\Temp\vfs_cache" as temporary files store.
************* INSTALLING LAMAXU ***********************service cmd: "C:\Program Files (x86)\QueueMetrix\LAMAXU\jre\bin\java.exe" -classpath C:\Program Files (x86)\QueueMetrix\LAMAXU\bin\yajsw\wrapper.jar -Xrs -Dwrapper.service=true -Dwrapper.working.d
ir=C:\Program Files (x86)\QueueMetrix\LAMAXU\bin -Djna_tmpdir=C:\Program Files (x86)\QueueMetrix\LAMAXU\bin\yajsw\bat\/../tmp -D
wrapper_home=C:\Program Files (x86)\QueueMetrix\LAMAXU\bin\yajsw\bat\/.. -Dwrapper.config=C:\Program Files (x86)\QueueMetrix\LAMAXU\bin\yajsw\conf\wrapper.conf -Dwrapper.additional.1x=-Xrs -Djna_tmpdir=C:\lam
axu-1.0.5.6\bin\yajsw\bat\..\tmp org.rzo.yajsw.boot.WrapperServiceBooter
Service LAMAXU installed

Now check that the LAMAXU service has been installed by opening the ‘Windows Services’ administration tool.

Manually Uninstalling Lamaxu as a Windows Service

C:\Program Files (x86)\QueueMetrix\LAMAXU\bin\yajsw\bat>uninstallService.bat
C:\Program Files (x86)\QueueMetrix\LAMAXU\bin\yajsw\bat>cd C:\lamaxu-1.0.5.6\bin\yajsw\bat\
C:\Program Files (x86)\QueueMetrix\LAMAXU\bin\yajsw\bat>call setenv.bat
"java" -Xmx30m -Djna_tmpdir="C:\Program Files (x86)\QueueMetrix\LAMAXU\bin\yajsw\bat\/../tmp" -Djava.net.preferIPv4Stack=true -jar "C:\lamaxu-1.0.5.6\bin\yajsw\bat\/../wrapper.jar" -r"C:\Program Files (x86)\QueueMetrix\LAMAXU\bin\yajsw\bat\/../conf/wrapper.conf"
YAJSW: yajsw-beta-12.04
OS : Windows 8.1/6.3/amd64
JVM : Oracle Corporation/1.8.0_66C:\Program Files (x86)\QueueMetrix\LAMAXU\jre/64
Apr 16, 2016 8:28:15 AM org.apache.commons.vfs2.VfsLog info
INFO: Using "C:\Users\Matt\AppData\Local\Temp\vfs_cache" as temporary files store.
************* REMOVING LAMAXU ***********************
Service LAMAXU removed

Configuring a Queue Manager

As of version 7.1 of MQ, the default security configuration is more restrictive and as such will probably need to be modified further before you can get a successful connection via a channel that has mcauser('mqm').

Refer to the WebSphere MQ documentation for further information if you still want to use the ‘mqm’ user. It is recommended that you create a new user for LAMAXU to user and apply the OAM authorities as described below.

Please replace the values below with the correct ones for your installation.

{qmgr} Queue Manager Name
{User} The MQ user being used by Lamaxu

Enable Queue Manager Monitoring and Statistics

For LAMAXU to work, the MONQ and MONCHL properties on the queue manager MUST be set to MEDIUM or higher to enable MQ to publish the Status and event information.

Use the MQSC commands below to modify the queue manager configuration and restart the LAMAXU agent.

ALTER QMGR CHLEV(ENABLED) +
MONCHL(MEDIUM) +
MONQ(MEDIUM) +
PERFMEV(ENABLED) +
STATCHL(MEDIUM) +
STATQ(ON) +
STATINT(60) +
FORCE

Define the Lamaxu Channel

For the purposes of this example the username 'lamaxu' has been used.

DEFINE CHANNEL('LAMAXU.CHANNEL') CHLTYPE(SVRCONN) MCAUSER('lamaxu')

MQ8/9 Unauthenticated Setup

To disable the security on the SVRCONN channels execute the following runmqsc commands below.

Note: This should only be performed in DEV for testing purposes.

ALTER AUTHINFO('SYSTEM.DEFAULT.AUTHINFO.IDPWOS') AUTHTYPE(IDPWOS) CHCKCLNT(OPTIONAL)
REFRESH SECURITY TYPE(CONNAUTH)
ALTER QMGR CHLAUTH(DISABLED)

MQ8/9 Authenticated Setup

To enable username/password authentication on the queue manager, the changes below need to be made to the queue manager configuration.

Note: The CHLAUTH(DISABLED) command below is required to disable the IP address filtering on CLIENT channels that MQ has enabled by default. Disabling CHLAUTH does not disable username/password checks.

The commands below are MQ 'runmqsc' commands that need to be executed by an MQ privileged user, like the 'mqm' user.

ALTER QMGR CONNAUTH(USE.PW) CHLAUTH(DISABLED)
ALTER AUTHINFO(USE.PW) +
AUTHTYPE(IDPWOS) +
FAILDLAY(10) +
CHCKLOCL(OPTIONAL) +
CHCKCLNT(REQUIRED)
REFRESH SECURITY TYPE(CONNAUTH)

Setmqaut OAM Commands

OAM Configuration for Objects

The Lamaxu agent needs to be granted access to the following queue manager objects to enable it work.

setmqaut -m {qmgr} -t qmgr -p {User} +connect +dsp +inq
setmqaut -m {qmgr} -n SYSTEM.ADMIN.COMMAND.QUEUE -t queue -p {User} +put +dsp +inq
setmqaut -m {qmgr} -n SYSTEM.DEFAULT.MODEL.QUEUE -t queue -p {User} +get +dsp
setmqaut -m {qmgr} -n SYSTEM.MQEXPLORER.REPLY.MODEL -t queue –p {User} +get +dsp +inq
setmqaut -m {qmgr} -n "**" -t queue -p {User} +inq +dsp
setmqaut -m {qmgr} -n "**" -t topic -p {User} +dsp
setmqaut -m {qmgr} -n "**" -t channel -p {User} +dsp
setmqaut -m {qmgr} -n "**" -t authinfo -p {User} +dsp
setmqaut -m {qmgr} -n "**" -t clntconn -p {User} +dsp
setmqaut -m {qmgr} -n "**" -t comminfo -p {User} +dsp
setmqaut -m {qmgr} -n "**" -t listener -p {User} +dsp
setmqaut -m {qmgr} -n "**" -t namelist -p {User} +dsp
setmqaut -m {qmgr} -n "**" -t process -p {User} +dsp
setmqaut -m {qmgr} -n "**" -t service -p {User} +dsp

OAM Configuration for Events, Accounting and Statistics

The Lamaxu agent needs to be granted access to the following queue manager event queues to enable it work.

setmqaut -m {qmgr} -n SYSTEM.ADMIN.CHANNEL.EVENT -t queue -p {User} +get +dsp +inq +browse
setmqaut -m {qmgr} -n SYSTEM.ADMIN.COMMAND.EVENT -t queue -p {User} +get +dsp +inq +browse
setmqaut -m {qmgr} -n SYSTEM.ADMIN.CONFIG.EVENT -t queue -p {User} +get +dsp +inq +browse
setmqaut -m {qmgr} -n SYSTEM.ADMIN.LOGGER.EVENT -t queue -p {User} +get +dsp +inq +browse
setmqaut -m {qmgr} -n SYSTEM.ADMIN.PERFM.EVENT -t queue -p {User} +get +dsp +inq +browse
setmqaut -m {qmgr} -n SYSTEM.ADMIN.PUBSUB.EVENT -t queue -p {User} +get +dsp +inq +browse
setmqaut -m {qmgr} -n SYSTEM.ADMIN.QMGR.EVENT -t queue -p {User} +get +dsp +inq +browse
setmqaut -m {qmgr} -n SYSTEM.ADMIN.STATISTICS.QUEUE -t queue -p {User} +get +dsp +inq +browse
setmqaut -m {qmgr} -n SYSTEM.ADMIN.ACCOUNTING.QUEUE -t queue -p {User} +get +dsp +inq +browse
setmqaut -m {qmgr} -n SYSTEM.ADMIN.TRACE.ACTIVITY.QUEUE -t queue -p {User} +get +dsp +inq +browse
setmqaut -m {qmgr} -n SYSTEM.ADMIN.TRACE.ROUTE.QUEUE -t queue -p {User} +get +dsp +inq +browse

AUTHREC OAM Authorities

The following OAM authorities can be used in situations where it's not possible to execute the usual 'setmqaut' command, such as the MQ appliance.

You must perform a search and replace of {userName} with your MQ Service user name.

Download script

** OAM Configuration for EVENTS and Activity Trace
SET AUTHREC +
 PROFILE('SYSTEM.ADMIN.CHANNEL.EVENT') +
 GROUP('{userName}') +
 OBJTYPE(QUEUE) +
 AUTHADD(BROWSE,DSP,GET,INQ)
*
SET AUTHREC +
 PROFILE('SYSTEM.ADMIN.COMMAND.EVENT') +
 GROUP('{userName}') +
 OBJTYPE(QUEUE) +
 AUTHADD(BROWSE,DSP,GET,INQ)
*
SET AUTHREC +
 PROFILE('SYSTEM.ADMIN.CONFIG.EVENT') +
 GROUP('{userName}') +
 OBJTYPE(QUEUE) +
 AUTHADD(BROWSE,DSP,GET,INQ)
*
SET AUTHREC +
 PROFILE('SYSTEM.ADMIN.LOGGER.EVENT') +
 GROUP('{userName}') +
 OBJTYPE(QUEUE) +
 AUTHADD(BROWSE,DSP,GET,INQ)
*
SET AUTHREC +
 PROFILE('SYSTEM.ADMIN.PERFM.EVENT') +
 GROUP('{userName}') +
 OBJTYPE(QUEUE) +
 AUTHADD(BROWSE,DSP,GET,INQ)
*
SET AUTHREC +
 PROFILE('SYSTEM.ADMIN.PUBSUB.EVENT') +
 GROUP('{userName}') +
 OBJTYPE(QUEUE) +
 AUTHADD(BROWSE,DSP,GET,INQ)
*
SET AUTHREC +
 PROFILE('SYSTEM.ADMIN.QMGR.EVENT') +
 GROUP('{userName}') +
 OBJTYPE(QUEUE) +
 AUTHADD(BROWSE,DSP,GET,INQ)
*
SET AUTHREC +
 PROFILE('SYSTEM.ADMIN.STATISTICS.QUEUE') +
 GROUP('{userName}') +
 OBJTYPE(QUEUE) +
 AUTHADD(BROWSE,DSP,GET,INQ)
*
SET AUTHREC +
 PROFILE('SYSTEM.ADMIN.ACCOUNTING.QUEUE') +
 GROUP('{userName}') +
 OBJTYPE(QUEUE) +
 AUTHADD(BROWSE,DSP,GET,INQ)
*
SET AUTHREC +
 PROFILE('SYSTEM.ADMIN.TRACE.ACTIVITY.QUEUE') +
 GROUP('{userName}') +
 OBJTYPE(QUEUE) +
 AUTHADD(BROWSE,DSP,GET,INQ)
*
SET AUTHREC +
 PROFILE('SYSTEM.ADMIN.TRACE.ROUTE.QUEUE') +
 GROUP('{userName}') +
 OBJTYPE(QUEUE) +
 AUTHADD(BROWSE,DSP,GET,INQ)
*
** OAM Configuration for Objects
SET AUTHREC +
 PROFILE('SYSTEM.ADMIN.COMMAND.QUEUE') +
 GROUP('{userName}') +
 OBJTYPE(QUEUE) +
 AUTHADD(DSP,PUT,INQ)
*
SET AUTHREC +
 PROFILE('SYSTEM.DEFAULT.MODEL.QUEUE') +
 GROUP('{userName}') +
 OBJTYPE(QUEUE) +
 AUTHADD(DSP,GET,INQ)
*
SET AUTHREC +
 PROFILE('SYSTEM.MQEXPLORER.REPLY.MODEL') +
 GROUP('{userName}') +
 OBJTYPE(QUEUE) +
 AUTHADD(DSP,GET,INQ)
*
SET AUTHREC +
 GROUP('{userName}') +
 OBJTYPE(QMGR) +
 AUTHADD(CONNECT,INQ)
*
SET AUTHREC +
 PROFILE(**) +
 GROUP('{userName}') +
 OBJTYPE(QUEUE) +
 AUTHADD(DSP,INQ)
*
SET AUTHREC +
 PROFILE(**) +
 GROUP('{userName}') +
 OBJTYPE(TOPIC) +
 AUTHADD(DSP)
*
SET AUTHREC +
 PROFILE(**) +
 GROUP('{userName}') +
 OBJTYPE(CHANNEL) +
 AUTHADD(DSP)
*
SET AUTHREC +
 PROFILE(**) +
 GROUP('{userName}') +
 OBJTYPE(AUTHINFO) +
 AUTHADD(DSP)
*
SET AUTHREC +
 PROFILE(**) +
 GROUP('{userName}') +
 OBJTYPE(CLNTCONN) +
 AUTHADD(DSP)
*
SET AUTHREC +
 PROFILE(**) +
 GROUP('{userName}') +
 OBJTYPE(COMMINFO) +
 AUTHADD(DSP)
*
SET AUTHREC +
 PROFILE(**) +
 GROUP('{userName}') +
 OBJTYPE(LISTENER) +
 AUTHADD(DSP)
*
SET AUTHREC +
 PROFILE(**) +
 GROUP('{userName}') +
 OBJTYPE(NAMELIST) +
 AUTHADD(DSP)
*
SET AUTHREC +
 PROFILE(**) +
 GROUP('{userName}') +
 OBJTYPE(PROCESS) +
 AUTHADD(DSP)
*
SET AUTHREC +
 PROFILE(**) +
 GROUP('{userName}') +
 OBJTYPE(SERVICE) +
 AUTHADD(DSP)

ZOS RACF Commands for Events, Accounting and Statistics

You must perform a search and replace of {USER} with your MQ Service user name and {QMGR} with the name of the MQ queue manager.

Generic Display

PE {QMGR}.DISPLAY.* CLASS(MQCMDS) ID({USER}) ACCESS(READ)

Event Queues

PE {QMGR}.SYSTEM.ADMIN.CHANNEL.EVENT CLASS(MQQUEUE) ID({USER}) ACCESS(UPDATE)
PE {QMGR}.SYSTEM.ADMIN.COMMAND.EVENT CLASS(MQQUEUE) ID({USER}) ACCESS(UPDATE)
PE {QMGR}.SYSTEM.ADMIN.CONFIG.EVENT CLASS(MQQUEUE) ID({USER}) ACCESS(UPDATE)
PE {QMGR}.SYSTEM.ADMIN.PERFM.EVENT CLASS(MQQUEUE) ID({USER}) ACCESS(UPDATE)
PE {QMGR}.SYSTEM.ADMIN.QMGR.EVENT CLASS(MQQUEUE) ID({USER}) ACCESS(UPDATE)
PE {QMGR}.SYSTEM.ADMIN.ACTIVITY.QUEUE CLASS(MQQUEUE) ID({USER}) ACCESS(UPDATE)
PE {QMGR}.SYSTEM.ADMIN.TRACE.ROUTE.QUEUE CLASS(MQQUEUE) ID({USER}) ACCESS(UPDATE)

Model and Command Queues

PE {QMGR}.SYSTEM.COMMAND.REPLY.MODEL CLASS(MQQUEUE) ID({USER}) ACCESS(UPDATE)
PE {QMGR}.SYSTEM.DEFAULT.MODEL.QUEUE CLASS(MQQUEUE) ID({USER}) ACCESS(UPDATE)
PE {QMGR}.SYSTEM.ADMIN.CHANNEL.EVENT CLASS(MQQUEUE) ID({USER}) ACCESS(UPDATE)
PE {QMGR}.AMQ.MQEXPLORER.* CLASS(MQQUEUE) ID({USER}) ACCESS(UPDATE)
PE {QMGR}.SYSTEM.MQEXPLORER.REPLY.MODEL CLASS(MQQUEUE) ID({USER}) ACCESS(UPDATE)

Statistics

PE {QMGR}.RESET.* CLASS(MQCMDS) ID({USER}) ACCESS(CONTROL) 
PE {QMGR}.QUEUE.* CLASS(MQADMIN) ID({USER}) ACCESS(CONTROL)

SETR GENERIC(MQCMDS) REFRESH 
SETR GENERIC(MQADMIN) REF
SETR RACLIST(MQADMIN) REF

MQ command

REFRESH SECURITY

Multi-Instance Queue Managers

To monitor a multi-instance queue manager, enter a comma separated list of hosts into the 'Host Name' field as shown below. The list can consist of an IP address or DNS host name.

Port number must remain the same for all hosts.

Queue Manager SSL Configuration

To Import a Trust Certificate
Recommended CipherSpecs and Equivalent CipherSuites
Defining a Private Keystore for Mutual SSL

Lamaxu versions greater than 1.0.5.9 are required in order to use SSL Connections to the MQ queue manager.

Open a web browser and navigate to the Lamaxu Admin page.

Example, http://localhost:8085/admin/dashboard/#/mq/admin (the default username and password is admin/password)

Navigate to the 'Queue Managers' tab and enter the required Cipher Suite into the Cipher input box. Note the Cipher Suite used needs to match the Cipher Spec on the MQ channel.

To Import a Trust Certificate

keytool -importcert -file mycert.txt -keystore truststore.jks -alias mycert

Where mycert.txt is is your trust certificate.

The default password for the truststore.jks file is 'changeit'

Recommended CipherSpecs and Equivalent CipherSuites

https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_8.0.0/com.ibm.mq.dev.doc/q113210_.htm

MQ CipherSpec	Equivalent CipherSuite (Oracle JRE)	Protocol
TLS_RSA_WITH_AES_128_CBC_SHA	TLS_RSA_WITH_AES_128_CBC_SHA	TLS v1
TLS_RSA_WITH_AES_128_CBC_SHA256	TLS_RSA_WITH_AES_128_CBC_SHA256	TLS v1.2
TLS_RSA_WITH_AES_256_CBC_SHA	TLS_RSA_WITH_AES_256_CBC_SHA	TLS v1
TLS_RSA_WITH_AES_256_CBC_SHA256	TLS_RSA_WITH_AES_256_CBC_SHA256	TLS v1.2

Defining a Private Keystore for Mutual SSL

To use Mutual certificate authentication, enter the keystore Filename and Keystore Password, of the keystore with the private key, in the in the Agent Config. The password can be obfuscated here as well.

Password Obfuscation

On Linux

/opt/queuemetrix/lamaxu.{version}/bin/obfuscate.sh password
Obfuscated password is: {obf}hZSGhoKah5E=

On Windows

The command below will obfuscate the password 'password'.

C:\Program Files (x86)\QueueMetrix\LAMAXU\bin>obfuscate.bat password
Obfuscated password is: {obf}hZSGhoKah5E=

Post Install Verification

After installation is complete, and the Lamaxu agent has been started, navigate to the logs directory and check the contents of the agent.log file. You should see activity indicating that data is being collected from each of the queue managers that you configured at step 6.

Data collection for a queue manager has started when the following lines can be found in the agent.log file. The example log entries below would normally be preceded by addition information such as date/time and the queue manager the log entries are for.

Example agent.log output

Objects and Status Collection

2016-10-17 16:04:51 INFO Sweeper:158 - [MQ9TST data collector] - Collecting data from message broker name: MQ9TST
2016-10-17 16:04:51 INFO WebSphereMQQueueManager:1149 - [MQ9TST data collector] - getObjectsViaPcfRequest Collecting QUEUE data
2016-10-17 16:04:52 INFO WebSphereMQQueueManager:1524 - [MQ9TST data collector] - Collected QUEUE data
2016-10-17 16:04:52 INFO WebSphereMQQueueManager:1149 - [MQ9TST data collector] - getObjectsViaPcfRequest Collecting PROCESS data
2016-10-17 16:04:52 INFO WebSphereMQQueueManager:1524 - [MQ9TST data collector] - Collected PROCESS data
2016-10-17 16:04:52 INFO WebSphereMQQueueManager:1149 - [MQ9TST data collector] - getObjectsViaPcfRequest Collecting QMGR data
2016-10-17 16:04:52 INFO WebSphereMQQueueManager:1524 - [MQ9TST data collector] - Collected QMGR data
2016-10-17 16:04:52 INFO WebSphereMQQueueManager:1149 - [MQ9TST data collector] - getObjectsViaPcfRequest Collecting QUEUE_STATUS data
2016-10-17 16:04:52 INFO WebSphereMQQueueManager:1524 - [MQ9TST data collector] - Collected QUEUE_STATUS data
2016-10-17 16:04:52 INFO WebSphereMQQueueManager:1149 - [MQ9TST data collector] - getObjectsViaPcfRequest Collecting SUBSCRIPTION data
2016-10-17 16:04:52 INFO WebSphereMQQueueManager:1524 - [MQ9TST data collector] - Collected SUBSCRIPTION data
2016-10-17 16:04:52 INFO WebSphereMQQueueManager:1149 - [MQ9TST data collector] - getObjectsViaPcfRequest Collecting TOPIC data
2016-10-17 16:04:52 INFO WebSphereMQQueueManager:1524 - [MQ9TST data collector] - Collected TOPIC data
2016-10-17 16:04:52 INFO WebSphereMQQueueManager:1149 - [MQ9TST data collector] - getObjectsViaPcfRequest Collecting PUBSUB_STATUS data
2016-10-17 16:04:52 INFO WebSphereMQQueueManager:1524 - [MQ9TST data collector] - Collected PUBSUB_STATUS data
2016-10-17 16:04:52 INFO WebSphereMQQueueManager:1149 - [MQ9TST data collector] - getObjectsViaPcfRequest Collecting SUBSCRIPTION_STATUS data
2016-10-17 16:04:52 INFO WebSphereMQQueueManager:1524 - [MQ9TST data collector] - Collected SUBSCRIPTION_STATUS data
2016-10-17 16:04:52 INFO WebSphereMQQueueManager:1149 - [MQ9TST data collector] - getObjectsViaPcfRequest Collecting CHANNEL data
2016-10-17 16:04:52 INFO WebSphereMQQueueManager:1524 - [MQ9TST data collector] - Collected CHANNEL data
2016-10-17 16:04:52 INFO WebSphereMQQueueManager:1149 - [MQ9TST data collector] - getObjectsViaPcfRequest Collecting CHANNEL_STATUS data
2016-10-17 16:04:52 INFO WebSphereMQQueueManager:1524 - [MQ9TST data collector] - Collected CHANNEL_STATUS data
2016-10-17 16:04:52 INFO WebSphereMQQueueManager:357 - [MQ9TST data collector] - LISTENER_STATUS - Platform number = 3
2016-10-17 16:04:52 INFO WebSphereMQQueueManager:1149 - [MQ9TST data collector] - getObjectsViaPcfRequest Collecting LISTENER data
2016-10-17 16:04:52 INFO WebSphereMQQueueManager:1524 - [MQ9TST data collector] - Collected LISTENER data
2016-10-17 16:04:52 INFO WebSphereMQQueueManager:1149 - [MQ9TST data collector] - getObjectsViaPcfRequest Collecting LISTENER_STATUS data
2016-10-17 16:04:52 INFO WebSphereMQQueueManager:1524 - [MQ9TST data collector] - Collected LISTENER_STATUS data
2016-10-17 16:04:52 INFO WebSphereMQQueueManager:1149 - [MQ9TST data collector] - getObjectsViaPcfRequest Collecting QMGR_STATUS data
2016-10-17 16:04:52 INFO WebSphereMQQueueManager:1524 - [MQ9TST data collector] - Collected QMGR_STATUS data
2016-10-17 16:04:52 INFO WebSphereMQQueueManager:1149 - [MQ9TST data collector] - getObjectsViaPcfRequest Collecting SERVICE data
2016-10-17 16:04:52 INFO WebSphereMQQueueManager:1524 - [MQ9TST data collector] - Collected SERVICE data

Events and Statistics Collection

2016-10-12 14:04:39 INFO WebSphereMQQueueManager:728 - [MQ9TST data collector] - Collecting CHANNEL_EVENT data
2016-10-12 14:04:39 INFO WebSphereMQQueueManager:1019 - [MQ9TST data collector] - Collected CHANNEL_EVENT data
2016-10-12 14:04:39 INFO WebSphereMQQueueManager:728 - [MQ9TST data collector] - Collecting COMMAND_EVENT data
2016-10-12 14:04:39 INFO WebSphereMQQueueManager:1019 - [MQ9TST data collector] - Collected COMMAND_EVENT data
2016-10-12 14:04:39 INFO WebSphereMQQueueManager:728 - [MQ9TST data collector] - Collecting PERFM_EVENT data
2016-10-12 14:04:39 INFO WebSphereMQQueueManager:1019 - [MQ9TST data collector] - Collected PERFM_EVENT data
2016-10-12 14:04:39 INFO WebSphereMQQueueManager:728 - [MQ9TST data collector] - Collecting QMGR_EVENT data
2016-10-12 14:04:39 INFO WebSphereMQQueueManager:1019 - [MQ9TST data collector] - Collected QMGR_EVENT data
2016-10-12 14:04:39 INFO WebSphereMQQueueManager:728 - [MQ9TST data collector] - Collecting LOGGER_EVENT data
2016-10-12 14:04:39 INFO WebSphereMQQueueManager:1019 - [MQ9TST data collector] - Collected LOGGER_EVENT data
2016-10-12 14:04:39 INFO WebSphereMQQueueManager:728 - [MQ9TST data collector] - Collecting TRACE_ACTIVITY data
2016-10-12 14:04:39 INFO WebSphereMQQueueManager:1019 - [MQ9TST data collector] - Collected TRACE_ACTIVITY data
2016-10-12 14:04:39 INFO WebSphereMQQueueManager:728 - [MQ9TST data collector] - Collecting PUBSUB_EVENT data
2016-10-12 14:04:39 INFO WebSphereMQQueueManager:1019 - [MQ9TST data collector] - Collected PUBSUB_EVENT data
2016-10-12 14:04:39 INFO WebSphereMQQueueManager:728 - [MQ9TST data collector] - Collecting CONFIG_EVENT data
2016-10-12 14:04:39 INFO WebSphereMQQueueManager:1019 - [MQ9TST data collector] - Collected CONFIG_EVENT data
2016-10-12 14:04:39 INFO WebSphereMQQueueManager:728 - [MQ9TST data collector] - Collecting STATISTICS data
2016-10-12 14:04:39 INFO WebSphereMQQueueManager:1019 - [MQ9TST data collector] - Collected STATISTICS data
2016-10-12 14:04:39 INFO WebSphereMQQueueManager:728 - [MQ9TST data collector] - Collecting ACCOUNTING data
2016-10-12 14:04:39 INFO WebSphereMQQueueManager:1019 - [MQ9TST data collector] - Collected ACCOUNTING data
2016-10-12 14:04:39 INFO Sweeper:179 - [MQ9TST data collector] - Finished collecting data from message broker: MQ9TST

If there are multiple queue managers defined then you will see additional repeated messages for each of them.

As the Lamaxu collects data from each configured queue manager in parallel, you may begin querying data as soon as collection is complete for at least one.

Page tree

INSTALLATION