For Tomcat Server, Traverse-JMX uses a connector based on RMI which supports the standard RMI transports - Java Remote Method Protocol (JRMP) and the Internet Inter-Object Request Broker (ORB) Protocol (IIOP).
Common Configurations on Tomcat Server
The configuration settings common for both IIOP and JRMP transports are as follows:
com.sun.management.jmxremote
Com.sun.management.jmxremote. port = portvalue
Com.sun.management.jmxremote. ssl = false
Com.sun.management.jmxremote. authenticate = false [Default: true]
com.sun.management.jmxremote. password.file = path of password file
com.sun.management.jmxremote. access.file = path of the access file
If authentication is not set, the value defaults to true. If access.file is set, the path defaults to $CATALINA_BASE/conf/
.
After you specify a password (password.file), you must secure the password. For more information, go to http://java.sun.com/j2se/1.5.0/docs/guide/management/security-windows.html
.
JMX Remote Settings in the Apache Tomcat Properties
You can set the following Tomcat Server in catalina.bat
and catalina.sh
, or from within the Tomcat server properties windows.
You can enter the values shown in the image above in the webapp.lax
file.
The above configurations to enable JMX monitoring on Traverse itself running on tomcat server can be set as follows:
Add the following lines under LAX.NL.JAVA.LAUNCHER.MAIN.METHOD
. Do not remove any existing parameters.
Dcom.sun.management.jmxremote
Dcom.sun.management.jmxremote.port = 9004
Dcom.sun.management.jmxremote.ssl = false
Dcom.sun.management.jmxremote.authenticate = true
Dcom.sun.management.jmxremote.password.file= ../apps/tomcat/conf/jmxremote.password
Dcom.sun.management.jmxremote.access.file= ../apps/tomcat/conf/jmxremote.access
Copy the jmxremote.password and jmxremote.access files to the specified directory.
Initial Configuration for connecting through RMI-JRMP
Start an RMI registry on the port of the localhost:
Start rmiregistry portvalue
where portvalue in the port to use for Traverse monitoring.
Initial Configuration for connecting via RMI-IIOP
Start the Object Request Broker Daemon (ORBD):
Start orbd -ORBInitialPort portvalue
where portvalue in the port to use for Traverse monitoring.
Client-side Connection
Monitor monitor configuration parameters: