Submit a ticketCall us
Home > Success Center > Server & Application Monitor (SAM) > Monitor JMX over SSL

Monitor JMX over SSL

Table of contents

Updated April 14th, 2016

Overview

This article provides steps to configure SAM to use secure JMX connections.

Environment

  • All SAM versions 
  • All Windows versions
  • JMX

Steps

Note: Establish what parameters you need to use with JConsole in order to connect to your JMX server over SSL.  Information on how to do this is found in the following Oracle documentation: 

Enabling Client SSL Authentication

 

1. Add the established parameters as parameters to the following file:

\program files (x86\SolarWinds\Orion\APM\jmxbridge\jsl\jsl.ini

 

For example, if you use the following command to connect:

 

jconsole -J-Djavax.net.ssl.trustStore=truststore -J-Djavax.net.ssl.trustStorePassword=trustword

 

You need to edit the jsl.ini file and replace:

 

[java]

jrepath=%APM_HOME%\jre6

jvmtype=client

params = 4

param00 = -cp

param01 = %APM_HOME%\jmxbridge\SolarWinds.JMX.Bridge.jar;%APM_HOME%\jmxbridge\lib\log4j-1.2.16.jar;%APM_HOME%\jmxbridge\lib\wlclient.jar;%APM_HOME%\jmxbridge\lib\wljmxclient.jar

param02 = -Denv.allusersprofile=%ALLUSERSPROFILE%

param03 = com.solarwinds.jmxbridge.Service

 

with

 

[java]

jrepath=%APM_HOME%\jre6

jvmtype=client

params = 6

param00 = -cp

param01 = %APM_HOME%\jmxbridge\SolarWinds.JMX.Bridge.jar;%APM_HOME%\jmxbridge\lib\log4j-1.2.16.jar;%APM_HOME%\jmxbridge\lib\wlclient.jar;%APM_HOME%\jmxbridge\lib\wljmxclient.jar

param02 = -Denv.allusersprofile=%ALLUSERSPROFILE%

param03 = -Djavax.net.ssl.trustStore=truststore

param04 = -Djavax.net.ssl.trustStorePassword=trustword

param05 = com.solarwinds.jmxbridge.Service

 

All JMX Monitors configured within SAM should be able to use a secure connections.

 

 

 

Last modified

Tags

Classifications

Public