Announcement: You can find the guides for Commerce 7.5 and later on the new Elastic Path Documentation site. This Developer Center contains the guides for Commerce 6.13.0 through 7.4.1.Visit new site

This version of Elastic Path Commerce is no longer supported or maintained. To upgrade to the latest version, contact your Elastic Path representative.

JMX Monitoring

JMX Monitoring

Elastic Path is leveraging the power of JMX technologies that are embedded into your Java platform. JMX provides an enhanced set of monitoring tools for your Elastic Path web applications. This section provides a general overview of JMX and its capabilities.

Overview:

JMX stands for Java Management Extensions.

JMX allows you to monitor and control your Java application processes. Using JMX, you can:

  • Obtain values and statistics from Java objects
  • Set values in Java objects
  • Perform operations remotely
  • Monitor your applications externally
  • Use a simple active notification system

Click here for further information.

What can I do with JMX?

For Elastic Path 6.13.0, JMX support is embedded in the following:

JConsole

The JMX client JConsole is built into your Java platform. JConsole is a JMX-compliant monitoring tool built into J2SE5.0. JMX enables it to compile performance and resource reports of applications running on the Java platform.

It is also possible to set up your own JMX client, click here for more detailed information.

Enabling JMX Remote Connections

To enable JMX remote connections to your production server:

  1. Open your server's startup script with a text editor.
  2. Modify JAVA_OPTS to include the following: 
    -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=6969 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false
    This will allow a JMX client to connect to port 6969.
  3. Restart your server.