Thesecurity-enabled ag for the JMX Connector is false. If you are running the cluster or
enterpriseprole, or if you have turned on security for the JMX Connector in the developer
prole,this ag is set to true.
<!- – The JSR 160 "system-jmx-connector"––>
<jmx-connector accept-all="false"address="0.0.0.0"
auth-realm-name="admin-realm"enabled="true"name="system"port="8686"
protocol="rmi_jrmp"security-enabled="true"/>
...
</jmx-connector>
<!- – The JSR 160 "system-jmx-connector"––>
Prerequisitesfor Connecting JConsole to ApplicationServer
TheJConsole setup has two parts: a server end and a client end. For this example, the Enterprise
Serverdomain is installed on a machine called appserver.sun.com, which is a powerful Solaris
server.This is the server end.
Theclient end also has an installation of Enterprise Server. Let us assume that the client end is a
Windowsmachine with Java SE 6.0 and Enterprise Server installed.
Note– The Enterprise Server installation is needed on the client end only when your Enterprise
Serverdomain has security enabled on the remote machine (the default for cluster and
enterpriseproles). If you just want to administer an Enterprise Server developer prole
domainon the Solaris machine above, you do not need the Enterprise Server installation on this
clientmachine.
Ifthe server and client ends are on the same machine, you can use localhost to specify the host
name.

Connecting JConsoleto Application Ser ver

Thisprocedure describes connecting JConsole to Enterprise Server without security enabled on
theJMX Connector. By default, security is not enabled on Enterprise Server for the developer
prole.
Startthe domain on appserver.sun.com.
StartJConsole by running JDK_HOME/bin/jconsole.
1
2
UsingJConsole
Chapter18 • Monitoring Components and Ser vices 211