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 Monitoring

By default, the monitoring service is enabled for Enterprise Server, but monitoring for the individual modules is not. To enable monitoring for a module, you change the monitoring level for that module to LOW or HIGH, You can choose to leave monitoring OFF for objects that do not need to be monitored.

The following tasks are addressed here:

To Enable Monitoring

Use the enable-monitoring subcommand to enable the monitoring service itself, or to enable monitoring for individual modules. Monitoring is immediately activated, without restarting Enterprise Server.

You can also use the set(1) subcommand to enable monitoring for a module. Using the set command is not a dynamic procedure, so you need to restart Enterprise Server for your changes to take effect.

  1. Determine which services and components are currently enabled for monitoring.

    asadmin> get server.monitoring-service.module-monitoring-levels.*

    This example output shows that the HTTP service is not enabled (OFF for monitoring), but other objects are enabled:

    configs.config.server-config.monitoring-service.module-monitoring-levels.web-container=HIGH
           configs.config.server-config.monitoring-service.module-monitoring-levels.http-service=OFF
               configs.config.server-config.monitoring-service.module-monitoring-levels.jvm=HIGH 
  2. Enable monitoring by using the enable-monitoring(1) subcommand.

    Server restart is not required.

Enabling the Monitoring Service Dynamically

This example enables the monitoring service without affecting monitoring for individual modules.

asadmin> enable-monitoring
Command enable-monitoring executed successfully
Enabling Monitoring for Modules Dynamically

This example enables monitoring for the ejb-container module.

asadmin> enable-monitoring --level ejb-container=HIGH
Command enable-monitoring executed successfully
Enabling Monitoring for Modules by Using the set Subcommand

This example enables monitoring for the HTTP service by setting the monitoring level to HIGH (you must restart the server for changes to take effect).

asadmin> set server.monitoring-service.module-monitoring-levels.http-service=HIGH
Command set executed successfully
See Also

You can also view the full syntax and options of the subcommand by typing asadmin help enable-monitoring at the command line.

To Disable Monitoring

Use the disable-monitoring subcommand to disable the monitoring service itself, or to disable monitoring for individual modules. Monitoring is immediately stopped, without restarting Enterprise Server.

You can also use the set(1) subcommand to disable monitoring for a module. Using the set command is not a dynamic procedure, so you need to restart Enterprise Server for your changes to take effect.

  1. Determine which services and components currently are enabled for monitoring.

    asadmin get server.monitoring-service.module-monitoring-levels.*

    This example output shows that monitoring is enabled for web-container, http-service, and jvm:

    configs.config.server-config.monitoring-service.module-monitoring-levels.web-container=HIGH
           configs.config.server-config.monitoring-service.module-monitoring-levels.http-service=HIGH
                  configs.config.server-config.monitoring-service.module-monitoring-levels.jvm=HIGH 
  2. Disable monitoring for a service or module by using the disable-monitoring(1) subcommand.

    Server restart is not required

Disabling the Monitoring Service Dynamically

This example disables the monitoring service without changing the monitoring levels for individual modules.

asadmin> disable-monitoring
Command disable-monitoring executed successfully
Disabling Monitoring for Modules Dynamically

This example disables monitoring for specific modules. Their monitoring levels are set to OFF.

asadmin> disable-monitoring --modules web-container,ejb-container
Command disable-monitoring executed successfully
Disabling Monitoring by Using the set Subcommand

This example disables monitoring for the HTTP service (you must restart the server for changes to take affect).

asadmin> set server.monitoring-service.module-monitoring-levels.http-service=OFF
Command set executed successfully
See Also

You can also view the full syntax and options of the subcommand by typing asadmin help disable-monitoring at the command line.