Applications Systems
Configure and integrate JMX monitoring in SAM
This article provides steps for configuring and troubleshooting JMX monitoring in SAM. The JConsole can be used to test if SAM can load MBeans from the perspective of the Orion server.
First published date
Last published date
Overview
Before proceeding, please note that SAM 2020.2 includes the following JMX monitoring updates:
- The Orion Platform now includes OpenJDK 14.0.
- The JMX probe for Linux now supports OpenJDK 14.0.
- The Oracle WebLogic (JMX) template was updated to support WebLogic 12.2.1.3.0.
For details, see Configure Java application servers and JVMs for SAM monitoring .
Product section
Resolution
- Configure the SAM Java application server for JMX.
- Add the JMX component monitor.
- Launch the JConsole and test the connection C:\ Program Files\ Java\ jdk1.8.0\ bin\ jconsole.exe
- Select Remote Process and enter the <IP:Port address>.
- Click Connect.
- If you receive the following message continue by clicking "Insecure connection"
Secure connection failed. Retry insecurely?
The connection to <IP:PORT address> could not be made using SSL.
Would you like to try without SSL? (Username and password will be sent in plain text.)7. Once JMX is configured correctly, the Java Monitoring & Management Console will be displayed.
For more information about the initial setup and configuration of JMX, view the Understanding Java Remote JMX article in the THWACK community.
Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.