Sun Microsystems GLASSFISH ENTERPRISE 820433510 - Manual (Page 209)

TABLE 18–32 ORB Level (Continued)
Command Dotted Name Output
get -m server.orb.connection-managers.* No output except message saying there are no
attributes at this node.
list -m server.orb.connection-managers.
orb\.Connections\.Inbound\
.AcceptedConnections
No attributes, but a message saying “Use get
command with the --monitor option to view
this node’s attributes and values.”
get -m server.orb.connection-managers.
orb\.Connections\.Inbound\
.AcceptedConnections.*
List of attributes and values corresponding to
ORB Connection Manager attributes as
described in
Table 18–13 .
The following table shows the command, dotted name, and corresponding output for the JVM
level.
TABLE 18–33 JVM Level
Command Dotted Name Output
list -m server.jvm No attributes, but a message
saying “Use get command with
the --monitor option to view this
node’s attributes and values.”
get -m server.jvm.* List of attributes and values
corresponding to JVM attributes
as described in
Table 18–16 .
Using JConsole
This section contains the following topics:
■ “Securing JConsole to Application Server Connection” on page 210
■ “Prerequisites for Connecting JConsole to Application Server” on page 211
■ “Connecting JConsole to Application Server” on page 211
■ “Connecting JConsole Securely to Application Server” on page 212
Administration (management and monitoring) of the Enterprise Server is based on JMX
Technology. This means that the managed components are represented as MBeans in the
MBeanServer running in the Enterprise Server's JVM.
Java SE 5 enhances management and monitoring of the JVM by including a Platform MBean
Server and by including MBeans to configure the JVM. Enterprise Server leverages these
enhancements and registers its MBeans with the Platform MBean Server. Thus a JMX
Connector Client gets a unified view of JVM MBeans as well as Enterprise Server MBeans.
Using JConsole
Chapter 18 • Monitoring Components and Services 209