I can't seem to find any instructions on SolarWinds site. Everything references linux. Any help out there? Using JMX monitoring.
Okay, this is what i had to do for it to work.
From solarwinds: Must have agentless monitor for jmx. Also, know a dedicated port to use in the jmx monitor.
On the windows server/websphere server, went into java virtual machine, process definition and added these parameters below what was already there. 8686 is solarwinds default port. You can change it.
-Dcom.ibm.xml.xlxp.jaxb.opti.level=3 -Dlogica.arm.logfilepath=D:/logs
-Djavax.management.builder.initial= -Dcom.sun.management.jmxremote
-Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.port=8686
Click OK, save (at the top).
RESTART WEBSPHERE APPLICATION SERVER.
Run a netstat -an and you'll see your 8686 port is up and listening on local host. Then viola! Working.
matt.adams Have you reviewed Configuring Java Application Servers for JMX? It describes how to configure JVM servers for JMX monitoring on JBoss, Glassfish, IBM WebSphere, and Oracle Weblogic servers in both Linux and Windows.
Additional links that may help include:
Also, are you using SNMP for monitoring? I found a topic that was removed from the SAM documentation but can be restored, if necessary. Here is that content, in case it's helpful. Excuse the formatting -- it's coming straight out of our authoring tool.
Configuring a Standalone Java Virtual Machine for SNMP (Windows)
1. Download the JDK from the Oracle website: http://www.oracle.
com/technetwork/java/javase/downloads/index.html (tested on JDK SE 6, update version 24).
2. Install the JDK.
3. On the license agreement page, read and accept the license and the click Next.
4. Click Change to change the installation directory to C:\Program Files\Java\jdk1.6.0_24, and
then click OK.
5. Click Next.
6. Click Finish to exit from the installer.
7. Add a variable to the system with its path pointing to the JDK installation folder. For example:
Variable name: JAVA_HOME
Variable value: C:\Program Files\Java\jdk1.6.0_24
Note: If you want to run Java commands from the command line, you should add the JDK installation path to
the PATH variable.
8. Navigate to the %JAVA_HOME%\jre\lib\management folder.
9. Rename the snmp.acl.template file to snmp.acl. Edit snmp.acl by replacing its content with the following:
acl = {
{
communities = public, private
access = read-only
managers = localhost, sam-server
}
Where sam-server is the hostname of your SAM server.
10. Grant access to the snmp.acl file only for the Administrator. To grant access only for the Administrator, refer
to this topic at the following location: http://-
download.oracle.com/javase/6/docs/technotes/guides/management/security-windows.html
Configuring IBM WebSphere (tested on version 7.0):
IBM WebSphere uses its own JDK, installed at %WEBSHERE_HOME%\java (where %WEBSHERE_HOME% is
the path to your WebSphere installation).Configure the IBM JDK in the following manner:
1. Go to the $JAVA_HOME/jre/lib/management folder.
2. Rename the snmp.acl.template file to snmp.acl.
3. Edit snmp.acl by replacing its content with the following:
acl = { { communities = public, private access = read-only managers = localhost, SAM-server
}}Where SAM-server is the hostname of your SAM server.
4. Grant access to the snmp.acl file only for the root user. Run the following commands as the root user in your
shell:
# chown root.root $JAVA_HOME/jre/lib/management/snmp.acl
# chmod 600 $JAVA_HOME/jre/lib/management/snmp.acl
5. Run the IBM WebSphere Application Server.
6. Open a web browser and then navigate to: https://hostname:9043 where hostname is the name of the IBM
WebSphere server.
7. In the left panel, click Expand Servers and Server types.
8. Click WebSphere Application Servers.
9. In the main window, click your server.
In the Server Infrastructure section, expand Java and Process Management.
11. Click Process Definition.
12. In the Additional Properties section, click Java Virtual Machine.
13. In Generic JVM Arguments, add the following:
-Dcom.sun.management.snmp.port=1161 -Dcom.sun-
.management.snmp.interface=0.0.0.0
14. Click OK.
15. Click, Save and then click OK.
16. Click Save.
17. Go to the Windows Services console.
18. Right -click the IBM Websphere service.
19. Click Properties.
20. Click the Log On tab and then select Log on as this account.
21. Click Browse, find the user “Administrator," and then type the Administrator password twice.
22. Click OK.
23. Restart the IBM WebSphere Application Server.
Thanks for this info. I had found this. I just performed the following and now getting the error of "Network connection failed. Cannot connect to JMX server" when I apply the Websphere (JMX) monitor to it and attempted to test it. While the node shows up and green, the error in red above persists. These changes I've added within the JVM on the websphere server. Any ideas?
To enabe remote JMX monitoring, use the following Java arguments:
-Djava.rmi.server.hostname=192.168.0.236
This line indicates the IP address the RMI server will use. Type your server IP address here.
-Dcom.sun.management.jmxremote
This line enables remote JMX monitoring.
This line indicates which port the JMX module will use to accept JMX connections.
-Dcom.sun.management.jmxremote.ssl=false
This line indicates if SSL is used.
-Dcom.sun.management.jmxremote.authenticate=true
This line indicates if authentication is used. Use of authentication is recommended. If you do not want to use authentication, you should change the value to false.
-Dcom.sun.management.jmxremote.password.file=c:\jmxremote.password
This line indicates where the passwords file is stored. Do not add this line if you are not using authentication.
-Dcom.sun.management.jmxremote.access.file=c:\jmxremote.access
This line indicates where the access file is stored. Do not add this line if you are not using authentication.
matta785,
I found the following links that may be helpful:
You may also want to check logs at \ProgramData\Solarwinds\Logs\APM\jmxbridge.log.
If that info is not helpful, I recommend enabling SAM debug logging and contacting SolarWinds Support so one of your reps can assist you further.
I'm trying to use jmx. I'll look more at these links and see what I can figure out.
cmazko wrote:matta785 , I found the following links that may be helpful:Re: JMX Monitoring https://support.solarwinds.com/SuccessCenter/s/article/Update-the-Java-Runtime-Environment-JRE-SAM-uses-for-JMXHow do I monitor for Tomcat being down with JMX? You may also want to check logs at \ProgramData\Solarwinds\Logs\APM\jmxbridge.log.If that info is not helpful, I recommend enabling SAM debug logging and contacting SolarWinds Support so one of your reps can assist you further.
cmazko wrote:
matta785 ,
If that info is not helpful, I recommend enabling SAM debug logging and contacting SolarWinds Support so one of your reps can assist you further.
matta785 I recommend opening a support ticket so we can access your diagnostics. If there is a bug, that will enable us to address any identified underlying issues.
