Configuring JMX Reporting Access

You can enable the JMX service to allow you to monitor Mashery Local using the Java Management Extension. In addition to the standard MBeans exposed by JMX, the list of TIBCO Mashery specific components and metrics that are exposed are:
  • Jetty: Metrics exposed are Connections, Open connections, Thread pool low threads, Thread pool max threads, Thread pool min threads, Thread pool spawn or shrink
  • DB Connection Pools: Metrics exposed are Active Connections, Timeout
  • Memcache Connection Pools: Metrics exposed are Active connections, Connection Timeout, Max Reconnect Delay
  • HTTP Connection Pools: Metrics exposed are Number of connections

To enable and configure the JMX Service:

Procedure

  1. Turn on the JMX service by following the instructions in the following screen shot.

    You need to enter a username and password to access the service.
  2. Download the server certificate to your local machine using the link provided on the same configuration screen:
  3. On your local computer, import the certificate to a new trust store. Use an arbitrary trust store password; for example, trustpassword. 
    keytool -import -file ~/Downloads/mashery-proxy.cer -keystore mashery-proxy-jmxremote.jks
  4. Launch JConsole with the newly-created trust store. 
    jconsole -J-Djavax.net.ssl.trustStore=mashery-proxy-jmxremote.jks -J-Djavax.net.ssl.trustStorePassword=trustpassword
  5. In JConsole, connect to the Mashery Local node to monitor by specifying its IP address (the second or private interface) and port 8084. Enter the credentials specified in the Admin console. For example: 192.168.1.110:8084 apiuser/apipassword.

    You should be successfully connected and able to monitor the node.