Admin Console Tasks for Enabling and Disabling Monitoring

• To configure monitoring levels using the Admin Console

• To configure monitoring using the asadmin tool

To configure monitoring levels using the Admin Console

1. Access the Monitoring Service page. To do this,

   1. In the tree component, select the Application Server node.

   2. Select the Monitor page.

   3. Select the Setup tab.

2. On the Monitoring Service page, choose the appropriate value from the combo box opposite the component(s) or service(s) whose monitoring level is changing.

   By default, monitoring is turned off for all components and services. To turn monitoring on, select LOW or HIGH from the combo box. To turn monitoring off, select OFF from the combo box. It is possible to turn monitoring on or off for the following components and services:

   • JVM - Set the monitoring level to LOW for this option to monitor the Java Virtual Machine.

   • HTTP Service - Set the monitoring level to LOW for this option to monitor all HTTP listeners and virtual servers.

   • Transaction Service - Set the monitoring level to LOW for this option to monitor any transaction subsystem.

   • JMS/Connector Service - Set the monitoring level to LOW for this option to monitor any Java Message Service (JMS).

   • ORB - Set the monitoring level to LOW for this option to monitor the system ORB used by the Application Server core and its connection managers.

   • Web Container - Set the monitoring level to LOW for this option to monitor all deployed servlets.

   • EJB Container - Set the monitoring level to LOW for this option to monitor all deployed EJB components, EJB pools, and EJB caches. Set this method to HIGH to also monitor EJB business methods.

   • JDBC Connection Pool - Set the monitoring level to LOW for this option to monitor all JDBC connection pools.

   • Thread Pool - Set the monitoring level to LOW for this option to monitor all thread pools.

3. Click Save.

   There are no Additional Monitoring Service Properties in this release, therefore ignore the Additional Properties table.

Equivalent asadmin command

set

For example, to turn on monitoring for the HTTP Service, use the following asadmin command:

asadmin> set --user admin-user server.monitoring-service.module-monitoring-levels.http-service=LOW

See Also

• To view monitoring data in the Admin Console

• Viewing Monitoring Data With the asadmin Tool

To configure monitoring using the asadmin tool

To turn monitoring off, or to set a level for monitoring a component or service, you can use the Admin Console as described in To configure monitoring levels using the Admin Console.

1. Use the get command to find out what services and components currently have monitoring enabled.

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

   Returns:

   server.monitoring-service.module-monitoring-levels. connector-connection-pool = OFF server.monitoring-service.module-monitoring-levels. connector-service = OFF server.monitoring-service.module-monitoring-levels.ejb-container = OFF server.monitoring-service.module-monitoring-levels.http-service = OFF server.monitoring-service.module-monitoring-levels.jdbc-connection-pool = OFF server.monitoring-service.module-monitoring-levels.jms-service = OFF server.monitoring-service.module-monitoring-levels.jvm = OFF server.monitoring-service.module-monitoring-levels.orb = OFF server.monitoring-service.module-monitoring-levels.thread-pool = OFF server.monitoring-service.module-monitoring-levels.transaction-service = OFF server.monitoring-service.module-monitoring-levels.web-container = OFF

2. Use the set command to enable monitoring.

   For example, to enable monitoring for the HTTP service:

   asadmin> set --user admin-user server.monitoring-service.module-monitoring-levels.http-service=LOW

   To disable monitoring, use the set command and specify OFF for the monitoring level.