You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

Lamaxu intergates with Solarwinds SAM using Java Management Extensions (JMX), https://en.wikipedia.org/wiki/Java_Management_Extensions.

Lamaxu connects to the MQ queue manager and exposes MQ metrics as JMX MBeans. 

Before attemting to integrate Lamaxu with Solarwinds, it's important to confirm that Lamaxu is operating correctly and is able to both access the MQ manager and expose metrics via JMX. The easiest way to do this is to obtain a copy of the Java 8 JDX and use the buddled utility called 'jconsole'. 

Please follow the instructions below.

Setting up the Lamaxu JMX Gateway

The JMX Gateway can be accessed using an RFC2609 compliant service URL:

service:jmx:rmi://<TARGET_MACHINE>:<JMX_RMI_SERVER_PORT>/jndi/rmi://<TARGET_MACHINE>:<RMI_REGISTRY_PORT>/jmxrmi

Given the above and the following parameters:

TARGET_MACHINE = localhost
JMX_RMI_SERVER_PORT = 3098
RMI_REGISTRY_PORT = 3099

We can derive the following functional URL:

service:jmx:rmi://localhost:3098/jndi/rmi://localhost:3099/jmxrmi

For your convenience, this URL is also generated by the LAMAXU process and written to the log file at start-up: Please substitute someHostName for the correct IP or DNS address for the Lamaxu agent.

2018-06-23 18:07:37,039 [main] JmxGateway remote URL is: service:jmx:rmi://localhost:3098/jndi/rmi://localhost:3099/jmxrmi

 

 

IMPORTANT: While it is possible to define a (:) colon character as part of an MQ object name, the JMX standard prohibits its use. Please be aware that any (:) colon characters in names will be stripped out when generating the MBean tree.

 

Testing JMX Connectivity with JConsole

JConsole is a JMX utility that is bundled with the Java JDK edition.

Locate and run jconsole from you JDK bin directory. You should be prompted for a URL, username and password. Assuming you have a local user called “admin” with password “password” and role of “admin”, you should be able to connect to the Lamaxu successfully.

As shown in the screenshot on the left, the information is displayed under the MBeans tab.

A successful connection via jconsole means you can now proceed to connecting your enterprise monitoring solution using the same parameters.

SSL Secured Communications

A Lamaxu process secured by SSL can be accessed by specifying an appropriately configured JKS trust store.

The command below can be specified on the jconsole command line:

jconsole –J -Djavax.net.ssl.trustStore=/app/LAMAXU/keystore.jks -J-Djavax.net.ssl.trustStorePassword=password


 

Once JConsole is able to connect to the Lamaxu agent, the defined queue managers will appear as MBeans as shown in the tree list example shown below.

 

IMPORTANT : Set the agent config.xml property <valueFormat>solarwinds</valueFormat> for Lamaxu to expose numeric metrics rather than mapping to string values.

Note : Only values that return numerical data can be monitored. String data is not supported by SolarWinds at this time. Non-numerical data will be shown without a check box when selecting MBeans to poll from within SAM, as illustrated above

 

Adding a JMX Componenet Monitor to SAM

To add a JMX Monitor to a node using the wizard, perform the following steps from the SAM web console.

1. Click SAM Settings.

2. Click Component Monitor Wizard

3. Select JMX Monitor from the dropdown list.

4. Click Browse to find the node you want to monitor.
5. Choose a credential from the Credential Library or create a new one using the Username and Password fields.

Note: For the next step, the defaults are sufficient for most environments. If they are not, you can change them to suit your environment.

6. Add the Port number, Protocol type, URL path, and Credentials for the remaining fields. Use the customized URL below:

It's important to use the structure shown below as Solarwinds has a string limit to the size of the custom URL provided.

service:jmx:rmi://${IP}:${PORT}/jndi/${PROTOCOL}://${IP}:3099${PATH}

7. Click Next. The following MBean selection screen appears

 

 


 

  • No labels