Try OpenEdge Now
skip to main content
Administration Guide
Administrative tools : JConsole and JMX : Running JConsole remotely

Running JConsole remotely

One of the reasons for running JConsole remotely is to minimize the effect of JConsole on server performance, since JConsole does consume a lot of system resources. However, you should be aware of the security impact of running JConsole remotely and take appropriate measures to guard against unauthorized access.
This procedure tells you how to enable JMX remote access to a PAS for OpenEdge instance, which is a prerequisite for running the JConsole administrative tool remotely.
1. Turn on the JMXLifecycle feature in a PAS for OpenEdge instance's /conf/server.xml file.
The best way to turn on the feature is to use the instance's TCMAN utility. For example:
$CATALINA_BASE/bin/tcman feature JMXLifecycle=on
TCMAN enables the JMX remote process and also opens ports for remote connection (JNDI 10001 and RMI 10002). You can change these ports by manually editing the JMXLifecycle section in server.xml
2. Add the name of the instance's host to its /conf/ file.
Add and set the following property in
Note: If you do not set java.rmi.server.hostname, the default localhost will be used.
3. Restrict read/write access to the instance's /conf/jmxremote.password file to the user with owner privileges.
Important: jmxremote.password is a plain-text file that contains the username/password combination that you need in order to log in to the instance from a remote JConsole. The default username and password (jmxadmin, jmxadmin) should be changed for security reasons.
On Windows, you can change permissions on the Security tab of the file's Properties dialog. On a UNIX system, you would run the following command:
chmod 600 jmxremote.password
4. On a remote machine, browse to $JAVA_HOME/bin and run jconsole.exe.
The JConsole New Connection dialog appears.
a. Click the Remote Process button.
b. Specify hostname and port of the instance that you want to manage.
c. Enter the credentials that are specified in the instance's jmxremote.password file.
Upon successful login, the Java Monitoring & Management Console appears.