Documentation forServer & Application Monitor

JMX Monitor

You can use the predefined JMX Monitor included in SAM to poll available managed beans (MBean) on properly configured Java application servers and JVMs results. You can also create custom Java Management Extension (JMX) monitors to pull specific data from target JMX servers, which may have large amounts of variables; see Create a custom JMX Monitor in SAM.

This SAM feature does not currently support polling via Orion Remote Collectors.

For example, the following SAM templates include multiple JMX Monitors:

  • GlassFish (JMX)
  • IBM WebSphere (JMX)
  • JBoss (JMX)
  • Oracle WebLogic (JMX) 12.x and higher

Note the following details about JMX Monitors"

SolarWinds recommends testing JMX components individually. Testing large numbers of JMX component monitors can impose heavy loads on agents and return incorrect results.

Prerequisites

Target servers support JMX queries. See Configure Java Virtual Machines for JMX monitoring in SAM.

Credentials

You may need either JMX credentials or none at all, depending on the credentials required based on the configuration of your Java application server.

JMX Configurations for Orion agent for Linux/Unix

See Configure Java Application Servers for JMX​.

For JMX configurations, install and configure WebSphere per your Linux/Unix distribution. See the IBM Knowledge Center (© 2020 IBM Corp., available at https://www.ibm.com, obtained on January 10, 2020) for details.

The overall steps include:

  1. Install WebSphere and note the following details:
    • You may need to create an administrator account and a new package group.
    • During installation, turn off the secure storage option as this is not needed.
    • Make sure to select the Application Server during installation.
  2. Start and stop the WebSphere AppServer.
  3. Use a browser to access the WebSphere AppServer console at http://websphere-host:9060/ibm/console
    • You may need to open a port to 9060 on the Websphere host.
    • Use the credentials for the account created during installation.
  4. In the console, expose the JMX platform mbeans in the WebSphere AppServer by:
    1. Clicking Servers > Server Types > WebSphere application servers.
    2. Selecting the listed application server.
  5. Locate the Java and Process Management > Process definition. In the Generic JVM arguments dialog box, enter the following code:

    Djavax.management.builder.initial=

    Note: There is nothing after the = sign.

    Dcom.sun.management.jmxremote=true

    Dcom.sun.management.jmxremote.port=8686

    Dcom.sun.management.jmxremote.ssl=false

    Dcom.sun.management.jmxremote.authenticate=false

    Djava.rmi.server.hostname=localhost

  6. Restart the AppServer.

Field descriptions

Description

A default description of the monitor. You can override the default description by editing the text, which is automatically saved. The variable to access this field is ${UserDescription}.

Component Type

The type of monitor being used.

Enable Component

Determines if a component is enabled. Disabling a component leaves it in the application as deactivated and does not influence application availability or status, as displayed in the Orion Web Console.

Credential for Monitoring

Provide JMX credentials to query MBeans. Select a credential from the list provided or use the <Inherit credential from node> option. If the credential you need is not in the credentials list, add it in the Credentials Library. See Understand the Credentials Library for details.

Count statistic as difference

Select this option to change the statistic to be the difference in query values between polling cycles. This measure is the difference in polled values and trend that statistic. This is a constantly increasing value, as it tracks total collection time since the JVM started.

Port Number

Specify the port number used for JMX connections.

Protocol

Choose between using Remote Method Invocation (RMI) and Invocation over Internet Inter-Orb Protocol (IIOP). Note: RMI should be correctly referred to as RMI/JRMP and IIOP as RMI/IIOP based on JMX Specifications.

URL Path

This field is for the last part of the JMX service URL. This follows hostname:portnumber and begins with a slash. For example: service:jmx:rmi:///jndi/rmi://HostName:portnumber/jmxrmi

Custom URL Format

(Optional) Enter a custom format for the URL. You can use the following available macros: ${IP}, ${PORT}, ${PROTOCOL}, or ${PATH}. Leave the field empty to use the default format (set by default).

Object Name

The unique string identifier of an MBean in the form of <domain -name>:<key property >.

Attribute Name

The name of an MBean attribute.

Key

This can be used to monitor composite attributes, which consist of key:value pairs.

SAM only supports monitoring of numerical data type attributes.

Convert Value

Select this check box to open the Formula box where you can manipulate the returned value with a variety of mathematical possibilities. Choose common functions from drop-down lists to manipulate the returned value, or select the Custom Conversion option. See Convert values in data transformations for SAM component monitors.

Statistic Threshold

Specify a threshold that indicates a warning or critical level was breached. Logical operators are in the drop-down list, followed by a blank field where you can enter the value of this threshold. For example: Less than 15 for warning, Less than 5 for critical. See Application Monitor Thresholds.

User Notes

Add notes for easy reference, accessible by using the variable, ${UserNotes}.