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

Compare with Current View Page History

« Previous Version 2 Next »

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

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

Given the above and the following parameters:

TARGET_MACHINE = someHostName
JMX_RMI_SERVER_PORT = 3098
RMI_REGISTRY_PORT = 3099

We can derive the following functional URL:

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

For your convenience, this URL is also generated by the LAMAXU process and written to the log file at start-up:

2016-06-23 18:07:37,039 [main] JmxGateway remote URL is: service:jmx:rmi://someHostName:3098/jndi/rmi://someHostName: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 with JConsole

Run jconsole. 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 here in the screenshot, 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

  • No labels