TABLE18–32 ORBLevel (Continued)
Command DottedName Output
get -m server.orb.connection-managers.* No output except message saying there are no
attributesat this node.
list -m server.orb.connection-managers.
orb\.Connections\.Inbound\
.AcceptedConnections
Noattributes, but a message saying “Use get
commandwith the --monitor option to view
thisnode’sattributes and values.”
get -m server.orb.connection-managers.
orb\.Connections\.Inbound\
.AcceptedConnections.*
Listof attributes and values corresponding to
ORBConnection Manager attributes as
describedin Table 18–13.
Thefollowing table shows the command, dotted name, and corresponding output for the JVM
level.
TABLE18–33 JVMLevel
Command Dotted Name Output
list -m server.jvm Noattributes, but a message
saying“Use get command with
the--monitor option to view this
node’sattributesand values.”
get -m server.jvm.* Listofattributes and values
correspondingto JVM attributes
asdescribed in Table 18–16.
UsingJConsole
Thissection contains the following topics:
■“SecuringJConsole to Application Server Connection” on page 210
■“Prerequisitesfor Connecting JConsole to Application Server” on page 211
■“ConnectingJConsole to Application Server” on page 211
���“ConnectingJConsole 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
MBeanServerrunning in the Enterprise Server's JVM.
JavaSE 5 enhances management and monitoring of the JVM by including a Platform MBean
Serverand by including MBeans to congure the JVM. Enterprise Server leverages these
enhancementsand registers its MBeans with the Platform MBean Server. Thus a JMX
ConnectorClient gets a unied view of JVM MBeans as well as Enterprise Server MBeans.
UsingJConsole
Chapter18 • Monitoring Components and Ser vices 209