Viewing Monitoring Data in the Admin Console

To view monitoring data for a component or service deployed in a server instance using the Application Server Admin Console, follow these steps. For more description on the attributes for each component or service, refer to the Monitoring chapter of the Administration Guide.

  1. Access the Monitoring page. To do this:
    1. In the tree component, select the Application Server node.
    2. Select the Monitor page.
    3. Select the Monitor Values tab.
  2. From the View list, select a component or service that has been deployed onto the server instance and for which monitoring is enabled.
  3. Monitoring data for the selected component or service displays below the View field. For a description of the monitorable properties, refer to the Monitoring chapter of the Administration Guide.

    On this page, it is possible to view monitoring data for JVM, Server, Thread Pools, HTTP Service, and Transaction Service if monitoring is enabled for these components and services.

  4. If you do not see the component or service you wish to monitor in this list, the Setup tab to enable and disable monitoring for selected components and services. Select OFF to disable monitoring for a component or service. Select LOW or HIGH to enable monitoring for a component or service.
  5. Select the Applications page to view monitoring data for application components that are deployed onto the server instance and for which monitoring is enabled. Select the application from the Application list. Select the specific component from the Component list.
  6. If you do see the application or component for which you wish to view monitoring, select the Setup tab to enable or disable monitoring for a component or service. To monitor applications, turn on the container in which they execute: for example, turn on the Web Container for Web applications and the EJB Container for EJB applications.

    If monitoring data is not displayed for applications, it is most likely that the application does not exist or is not exercised. Applications monitoring data will be available only when the application exists, monitoring is enabled for the application, and the application is being exercised. Once the application is executed, it is registered in the monitoring registry and the monitoring data displays.

    Monitoring data for the selected component will display below the selected component. For a description of the monitorable properties, refer to the Monitoring chapter of the Administration Guide.

  7. Select the Resources page to view monitoring data for resources that are deployed onto the server instance and for which monitoring has been enabled. Select the resource from the View list. If you do see the resource for which you wish to view monitoring data, select the Setup tab to enable or disable monitoring for a resource.
  8. If monitoring data is not displayed for resources, it is most likely that the resource does not exist or is not exercised. Resources monitoring data is available only when the resources exist, monitoring is enabled for the resource at a level of HIGH, and the resource is being exercised. For example, if you have created a JDBC connector service, but applications that use that connector service have not yet requested a connector from the service, that service has not yet been created, therefore, no service exists and no monitoring data is available. Once the JDBC application is executed and requests a connector from a service, the service is registered in the monitoring registry and monitoring data appears.

    Monitoring data for the selected component or service displays below the View field. For a description of the monitorable properties, refer to the Monitoring chapter of the Administration Guide.

  9. Select the Transactions page to freeze the transaction subsystem in order to roll back transactions and determine the transactions that are in process at the time of the freeze. To enable monitoring for the Transaction Service, select the Setup tab and make sure that Transaction Service is set to LOW. To freeze the Transaction Service in order to roll back transactions, select Freeze. To rollback a transaction, select the checkbox beside the transaction and click Rollback.

Equivalent asadmin command: get --monitor, for example, to view monitoring data for the JVM, use the following asadmin command:

asadmin> get --monitor server.jvm.*

See Also:


Legal Notices