Monitoring the Application Server with the SAP Management Console Perspective 
With the monitoring options provided by the SAP Management Console perspective, several main monitoring scenarios are available.
Prerequisites
The SAP Management Console (SAP MC) is started and the systems to be monitored are registered.
Activities
Request or Response Monitoring
You can use this scenario to monitor the requests executed by the applications deployed on the application server, and to check the status of the application threads that are processing these particular requests.
In the navigation view, choose the
AS Java 
Aliases 
instance node to locate your application. The result view displays the started web applications, their aliases, and other details. You can open an application in a browser directly from this table simply by double-clicking the corresponding entry line. However, to be able to launch the application successfully, it has to provide an index page – otherwise you will end up with an 403 Forbidden error page.The deployment perspective provided the following features:
It supports deployment to several systems based on SAP NetWeaver 7.0 and not only to the default system.
It explores the repository of Software Deployment Manager (SDM).
It undeploys from SAP NetWeaver 7.0 –based systems.
In the navigation view, choose the Sessions, EJB Sessions, or Remote Object nodes from the AS Java tree structure to monitor the Web, EJB, and remote object requests of your application using HTTP and RMI. The respective Content View displays details about the incoming requests.
In the navigation view, select the Threads node from the AS Java tree structure to monitor the threads that process the requests. Locate the threads that serve the incoming requests (if necessary, use the column filter options). Details about the threads, such as the task executed by the thread, start time, user triggering the request, status, and so on, are displayed in the Content View.
System Monitoring
You can use this scenario to monitor the system performance and operations.
To monitor the status of the Java processes, choose the Process Table node from the AS Java tree structure.
To view the overall cache and thread system information, choose the Caches or Threads node from the AS Java tree structure.
To view the overall VM performance, choose the GC History or Heap Memory node from the AS Java tree structure.
System State Monitoring
The SAP MC provides alert monitoring information based on predefined thresholds. With the SAP MC you can view the current state of the system as well as the most severe alerts that exist in the system.
To monitor the current data reported for every monitoring tree element, expand the Current Status tree structure and choose the relevant tree element. In the result view, the SAP MC displays the current state of the system and the most severe current alerts. The table in the result view displays the relevant monitors, their value, and the time the value was last measured.
To monitor the most severe alerts in the system, expand the Open Alerts tree structure and choose the relevant monitor. In the result view, the SAP MC displays the most severe alerts that have occurred in the system. The table in the result view displays the relevant monitors, their values, and the time the alert last occurred. This view does not necessarily reflect the current state of the system.
If the system has generated no alerts, the table in the result view only displays the name of the relevant monitor.
If the predefined levels are not suitable for your needs, you can configure the threshold values. You can also activate or deactivate monitors that are important for your scenario from the Java System Reports.
Database Monitoring
The SAP Systems tree structure in the SAP MC includes a node in a special blue color for the database server. To view detailed information, select the Database node. The result view displays the server type, the database instance host, the database vendor, and the SAP system ID (SAPSID).
Note
Database monitoring is only available if SAP Host Agent is installed and running on the DB server host.
SAP AS Java Health Check
The SAP MC summarizes some of the crucial JVM parameters beneath the Monitors node of the AS Java server node.
These include:
The memory throughput in MB/minute (1 GB/minute)
The ratio between garbage collection time and working time (1%)
The ratio of used and available heap memory (98%)
The ratio of used and available class memory (90%)
The number of long-running busy threads (3 threads running longer than 30 seconds)
The number of log records written per second (100)
If one of these values exceeds its limit, the instance will be highlighted with an error marker. You can change the limits for all systems or for a specific system using the Configure context menu of the monitor entry.
ICM Monitoring
In the SAP MC you can view basic monitoring information about Internet Communication Manager (ICM) operation under the ICM mode.
To display information about the created worker threads, choose the Thread List sub-node.
To display information about the existing connections, choose the Connection List sub-node.
To display information about all objects currently in the ICM server cache, choose the Cache List sub-node.
To display information about the proxy server list, choose the Proxy List sub-node.