Exit Print View

Sun GlassFish Enterprise Server v3 Administration Guide

  This Document Entire Library
Print View

Document Information

Preface

1.  Overview of Enterprise Server Administration

Default Settings and Locations

Configuration Tasks

Administration Tools

Instructions for Administering Enterprise Server

Part I Runtime Administration

2.  General Administration

3.  Administering Domains

4.  Administering the Virtual Machine for the Java Platform

5.  Administering Thread Pools

6.  Administering Web Applications

7.  Administering the Logging Service

8.  Administering the Monitoring Service

About Monitoring

How the Monitoring Tree Structure Works

Tree Structure of Monitorable Objects

About Monitoring for Add-on Components

Tools for Monitoring Enterprise Server

Configuring Monitoring

To Enable Monitoring

To Disable Monitoring

Viewing Common Monitoring Data

To View Common Monitoring Data

Common Monitoring Statistics

HTTP Listener Common Statistics

JVM Common Statistics

Web Module Common Statistics

Viewing Comprehensive Monitoring Data

Guidelines for Using the list and get Subcommands for Monitoring

To View Comprehensive Monitoring Data

Comprehensive Monitoring Statistics

EJB Statistics

HTTP Service Statistics

Jersey Statistics

JMS/Connector Service Statistics

JRuby Statistics

JVM Statistics

Network Statistics

ORB Statistics (Connection Manager)

Resource Statistics (Connection Pool)

Security Statistics

Thread Pool Statistics

Transaction Service Statistics

Web Statistics

Configuring JConsole to View Enterprise Server Monitoring Data

To Connect JConsole to Enterprise Server

9.  Administering Life Cycle Modules

10.  Extending Enterprise Server

Part II Security Administration

11.  Administering System Security

12.  Administering User Security

13.  Administering Message Security

Part III Resources and Services Administration

14.  Administering Database Connectivity

15.  Administering EIS Connectivity

16.  Administering Internet Connectivity

17.  Administering the Object Request Broker (ORB)

18.  Administering the JavaMail Service

19.  Administering the Java Message Service (JMS)

20.  Administering the Java Naming and Directory Interface (JNDI) Service

21.  Administering Transactions

Part IV Appendixes

A.  Subcommands for the asadmin Utility

Index

Configuring JConsole to View Enterprise Server Monitoring Data

Java SE provides tools to connect to an MBean Server and view the MBeans registered with the server. JConsole is one such popular JMX Connector Client and is available as part of the standard Java SE distribution. When you configure JConsole for use with Enterprise Server, Enterprise Server becomes the JMX Connector's server end and JConsole becomes the JMX connector's client end.

To Connect JConsole to Enterprise Server

Java SE 6 enhances management and monitoring of the virtual machine by including a Platform MBean Server and by including managed beans (MBeans) to configure the virtual machine.

To view all MBeans, Enterprise Server provides a configuration of the standard JMX connector server called System JMX Connector Server. As part of Enterprise Server startup, an instance of this JMX Connector Server is started. Any compliant JMX connector client can connect to the server using the JMX Connector Server.

By default, Enterprise Server is configured with a non-secure System JMX Connector Server. If this is an issue, the JMX connector can be removed. However, access can be restricted to a specific IP address (for example, the loopback address) by setting address to locahost.

  1. Start the domain.

    For instructions, see To Start a Domain.

  2. Start JConsole using this format: JDK_HOME/bin/jconsole

    For example:

    /usr/java/bin/jconsole

    The JConsole Connect to Agent window is displayed.

  3. Click the Remote tab and type the host name and port.

    Always connect remotely with JConsole, otherwise MBeans will not load automatically.

  4. Click Connect.

  5. In the Remote Process text box, specify the JMX Service URL.

    For example:

    service:jmx:rmi:///jndi/rmi://localhost:8686/jmxrmi 

    The JMX Service URL is emitted by the server at startup, looking something like this:

    [#|2009-12-03T10:25:17.737-0800|INFO|glassfishv3.0|
    javax.enterprise.system.tools.admin.org.glassfish.server|_ThreadID=20;
    _ThreadName=Thread-26;|JMXStartupService: Started JMXConnector, JMXService 
    URL = service:jmx:rmi://localhost:8686/jndi/rmi://localhost:8686/jmxrmi|#]

    However, in most cases, simply entering host:port is fine, such as, 192.168.1.150:8686. The long Service URL is not needed.


    Note - Another host name can be substituted for localhost. The default port number (8686) could change if the jmx-connector configuration has been modified.


  6. Click Connect.

    In the JConsole window you will see all your MBeans, JVM information, and so on, in various tabs. Most of the useful MBeans are to be found in the amx and java.lang domains.

See Also

For more information about JConsole, see http://java.sun.com/javase/6/docs/technotes/guides/management/jconsole.html.