| IMPORTANT Please be aware that EVENT and STATISTICS dataTypes are not available via the JMX gateway at this time and will be delivered in a future release. Please use the Web REST gateway, or the eventData.log for these dataTypes. |
To integrate Lamaxu with AppDynamics, simply include the AppDynamics -javaagent option to the LAMAXU startup.sh script.
Please contact your AppDynamics administrators as they need to generate, and provide you with, a new client configuration bundle for every Lamaxu agent deployed.
The ./conf/controller-info.xml located in the AppDynamics agent’s directory contains information about the server LAMAXU will push JMX updates to.
Example;
This example uses the following values to identify the LAMAXU agent.
./conf/controller-info.xml
<application-name>LAMAXU MQ</application-name>
<tier-name>Messaging</tier-name>
<node-name>Node 8536</node-name>
Add the option in red below to the ${LAMAXU_HOME}/bin/startup.sh file.
nohup "$JAVA_HOME/bin/java" -javaagent:/app/AppServerAgent-4.0.6.0/ver4.0.6.0/javaagent.jar -DLOG_PATH=${LAMAXU_HOME}/logs -cp ${LAMAXU_CLASSPATH} com.qm.lamaxu.Main -config ${LAMAXU_HOME}/config/config.xml >nohup.out 2>&1 &
On Windows, changes are required to the services configuration file wrapper.conf, see the sample.
Edit the file; C:\Program Files (x86)\QueueMetrix\LAMAXU\bin\yajsw\conf\wrapper.conf
On the second last line of the sample conf file you see the path to the AppD java agent. Please change the path to where your AppD agent is installed.
wrapper.java.additional.1 = -javaagent:C:\\Program Files (x86)\\AppServerAgent-4.0.6.0\\ver4.0.6.0\\javaagent.jar
The easiest way is replace the file located in the C:\Program Files (x86)\QueueMetrix\LAMAXU\bin\yajsw\conf\ directory, with the sample one attached after making the required changes. You’ll need to restart the service after the file has been changed.
Once the Lamaxu agent has been started, open AppDynamics and navigate to the LAMAXU MQ Application on the menu.
Once in the Lamaxu MQ application, navigate to App Servers and select the node.
Navigate to ‘More/JMX’ and click on the ‘Refresh Domains’ button to view the monitored MQ queue manager MBeans, as show in screen shots below.
