Monitor Service

Monitor Service obtains information about the current status of the SAP J2EE Engine 6.20 system. It provides general information about cluster nodes and statistics about user sessions, thread count, and memory allocation on each of them. Collected data about monitored cluster nodes can be further viewed using SAP J2EE Engine 6.20 Visual Administrator tool, SAP CCMS, or by tools that can read comma-separated files, such as Microsoft Excel.

Visual Administrator

Runtime Control

Monitor Service “Runtime” tab provides information about the status of cluster elements, their workload and response time behavior.

Server Monitor

Workload Summary

Workload Summary®Sessions

The Session monitor provides aggregated information about the user sessions. This component displays monitor data about the Login System, the HTTP Sessions, and a summary of both for the particular server node. Information about each session is provided by the Top List monitoring data.

Login System – collects data about user sessions on the particular server node. The login monitor data is:

Current number of sessions – the number of server login sessions open
Maximum sessions since startup – the maximum number of login sessions opened since startup
Average sessions since startup – the average number of open server sessions per second
Maximum sessions gross time – the maximum duration of a user session from its opening to its closure
Average sessions gross time – the average duration of a user session from its opening to its closure

Http Sessions – monitors the current number of stateful sessions (HTTP Sessions):

Current number of sessions – the number of server HTTP sessions open
Maximum sessions since startup – the maximum number of HTTP sessions opened since startup
Average sessions since startup – the average number of open server sessions per second
Maximum sessions gross time – the maximum duration of an HTTP session from its opening to its closure
Average sessions gross time – the average duration of an HTTP session from its opening to its closure

Total Sessions – displays summary information about the sessions on the particular server node.

Workload Summary®Requests

Requests (http) – displays information about the number of HTTP requests received by the corresponding server and the number of responses. The data is distributed as follows:

TotalNumberOfRequests – the total number of HTTP requests received by the corresponding server since startup
TotalNumberOfResponses – the total number of HTTP responses returned by the corresponding server since startup
AverageTimeForRequest – the average time (in milliseconds) for response to an HTTP request by the server
MaximumTimeForRequest – the maximum period (in milliseconds) for executing an HTTP request from startup to the present
WaitingRequests – the number of requests waiting to be processed. The type of this property is “int.” Its value range is a non-negative number.
MaxNumberOfWaitingRequests – the maximum number of requests waiting at the same time. This property covers a period from startup to the present. The type of the property is “int.” Its range is greater than or equal to the requests waiting.
MaxNumberOfRequestsPerSecond – the maximum number of requests per second received from startup to the present. The type of this property is “double.” Its value range is a non-negative number.
MaxNumberOfResponsesPerSecond – the maximum number of responses returned by the server per second from startup to the present. The type of this property is “long.” Its value range is a non-negative number.
AvgNumberOfRequestsPerSecond – the average number of requests per second received from startup to the present. The type of this property is “double.” Its value range is a non-negative number.

Total Requests – displays information about the number of all requests (for example, HTTP, P4, and so on) received by the corresponding server and the number of responses. The data is presented by the same properties, described above.

Workload Summary®Top List

The Top List monitor provides information about each user and HTTP session, and information about the running threads.

Login System – displays a table containing the following information about each user session:

Session-id – the identifier of the session
User-principal – the user who opened the session
Accessed – when the session was accessed
Expires – the time the session expires
Creation time – the time the session was created

SystemMonitoredThreads – displays information about threads that have higher priority than the MonitoredThreads . The information is displayed in the same way as in the information in the MonitoredThreads group:

Summary – contains the following data

Initial threads
Current threads
Peak threads
Running threads
Idle threads
Idle waiting threads
Threads blocked by synchronization
Threads waiting for resources
Queued requests for threads

Children – displays the following information about the threads

Name
ThreadID
State
Elapsed time
LastStateChange

MonitoredThreads – displays summary information about all threads on the particular server and a table containing specific information about each thread:

Summary – contains the following data

Initial threads
Current threads
Peak threads
Running threads
Idle threads
Idle waiting threads
Threads blocked by synchronization
Threads waiting for resources
Queued requests for threads

Children – displays the following information about the threads

Name
ThreadID
State
Elapsed time
LastStateChange

Http Sessions – displays a table of the HTTP sessions. The type of the information in the table is the same as the information about the user sessions in the Login System.

Workload Summary®Memory

MemoryManager – displays information about the memory used by the server node. The following information is provided:

Allocated Memory – the memory allocated to the corresponding server node. The value of this property is in bytes. Its type is “long.” The value range is less than or equal to the Memory Limit property.
Memory Limit – the maximum amount of memory that can be allocated to the particular server node
Max Memory – the maximum amount of memory used by the corresponding server node up to the present
Memory in Use – the amount of memory being used by the server node
Utilization Level – an integer corresponding to the percentage range of memory used by the particular server node at present. There are six utilization levels according to the amount of memory used

0 – the amount of memory used is from 0% to 40%
1 – the amount of memory used is from 41% to 55%
2 – the amount of memory used is from 56% to 65%
3 – the amount of memory used is from 66% to 71%
4 – the amount of memory used is from 72% to 75%
5 – the amount of memory used is from 76% to 100%

Heart Beat

This displays a table containing information about the current state of the services running on the server node and the whole server system. The table displays the state (for example, Running, Stopped, and so on) and the time of the last change of the corresponding service state.

Configuration

This displays the configuration properties and their values for all managers and services running on the particular server node. The properties and their values can be viewed only, and cannot be modified here. To modify them, use the corresponding manager or service Visual Administrator “Properties” tab or Properties file.

System Info

Provides general information about the dispatcher node and its environment:

Cluster element ID
Cluster element host/IP
Cluster element opened port
SAP J2EE Engine 6.20 system core version
Java version
Operating system (OP) name
Operating system (OP) version
Java Virtual Machine (VM) version
Java Virtual Machine (VM) vendor
Java Virtual Machine (VM) name
User directory
Startup Time

Log

Log – displays the log messages about all significant events that have occurred on the particular server node. The following information is displayed about each log message:

Severity – the severity level of the log message
Component – the component that logs the message
Message – the ID and information about the log message
Exception – the exception that is written to the log files

Dispatcher Monitor

Log

Log – displays the log messages about all significant events that have occurred on the particular dispatcher node. The following information is displayed about each log message:

Severity – the severity level of the log message
Component – the component that logs the message
Message – the ID and information about the log message
Exception – the exception that is written to the log files

Heart Beat

This displays a table containing information about the current state of the services running on the dispatcher node and the whole dispatcher system. The table displays the state (for example, Running, Stopped, and so on) and the time of the last change of the corresponding service state.

Workload Summary

Workload Summary®Top List

MonitoredThreads – displays summary information about all threads on the particular server and a table containing specific information about each thread:

Summary – contains the following data

Initial threads
Current threads
Peak threads
Running threads
Idle threads
Idle waiting threads
Threads blocked by synchronization
Threads waiting for resources
Queued requests for threads

Children – displays the following information about the threads

Name
ThreadID
State
Elapsed time
LastStateChange

Workload Summary®Memory

MemoryManager – displays information about the memory used by the dispatcher node. The following information is provided:

Allocated Memory – the memory allocated to the corresponding dispatcher node. The value of this property is in bytes. Its type is “long.” The value range is less than or equal to the Memory Limit property.
Memory Limit – the maximum amount of memory that can be allocated to the particular dispatcher node
Max Memory – the maximum amount of memory used by the corresponding dispatcher node up to the present
Memory in Use – the amount of memory being used by the dispatcher node
Utilization Level – an integer corresponding to the percentage range of memory used by the particular dispatcher node at the current moment. There are six utilization levels according to the amount of memory used

0 – the amount of memory used is from 0% to 40%
1 – the amount of memory used is from 41% to 55%
2 – the amount of memory used is from 56% to 65%
3 – the amount of memory used is from 66% to 71%
4 – the amount of memory used is from 72% to 75%
5 – the amount of memory used is from 76% to 100%

System Info

This provides general information about the dispatcher node and its environment:

Cluster element ID
Cluster element host/IP
Cluster element opened port
SAP J2EE Engine 6.20 system core version
Java version
Operating system (OP) name
Operating system (OP) version
Java Virtual Machine (VM) version
Java Virtual Machine (VM) vendor
Java Virtual Machine (VM) name
User directory
Startup Time

Configuration

This displays the configuration properties and their values for all managers and services running on the particular dispatcher node. The properties and their values can be viewed only, and cannot be modified here. To modify them, use the corresponding manager or service Visual Administrator “Properties” tab or Properties file.

Aggregated

Workload Summary

Workload Summary®Sessions

The Session monitor provides aggregated information about the user sessions. This component displays monitor data about the Login System, the HTTP Sessions, and a summary of both for the whole cluster. Information about each session is provided by the Top List monitoring data in each server node.

Login System – used for collecting data about all user sessions on the cluster. The login monitor data is:

Current number of sessions – the number of cluster login sessions open
Maximum sessions since startup – the maximum number of login sessions opened since startup
Average sessions since startup – the average number of open cluster sessions per second
Maximum sessions gross time – the maximum duration of a user session from its opening to its closure
Average sessions gross time – the average duration of a user session from its opening to its closure

Http Sessions – monitors the current number of stateful sessions (HTTP Sessions) on the cluster:

Current number of sessions – the number of cluster HTTP sessions open
Maximum sessions since startup – the maximum number of HTTP sessions opened since startup
Average sessions since startup – the average number of open cluster sessions per second
Maximum sessions gross time – the maximum duration of an HTTP session from its opening to its closure
Average sessions gross time – the average duration of an HTTP session from its opening to its closure

Total Sessions – displays summary information about the sessions on the cluster.

Workload Summary®Requests

Requests (http) – displays information about the number of HTTP requests received by all server nodes within the cluster and the number of responses. The data is distributed as follows:

TotalNumberOfRequests – the total number of HTTP requests received by the cluster since startup
TotalNumberOfResponses – the total number of HTTP responses returned by the cluster since startup
AverageTimeForRequest – the average time (in milliseconds) for response to an HTTP request by the cluster
MaximumTimeForRequest – the maximum period of time (in milliseconds) for executing an HTTP request from startup to the present
WaitingRequests – the number of requests waiting to be processed. The type of this property is “int.” Its value range is a non-negative number.
MaxNumberOfWaitingRequests – the maximum number of requests waiting at the same time. This property covers a period from startup to the present. The type of the property is “int.” Its range is greater than or equal to the requests waiting.
MaxNumberOfRequestsPerSecond – the maximum number of requests per second received from startup to the present. The type of this property is “double.” Its value range is a non-negative number.
MaxNumberOfResponsesPerSecond – the maximum number of responses returned by the server nodes per second from startup to the present. The type of this property is “long.” Its value range is a non-negative number.
AvgNumberOfRequestsPerSecond – the average number of requests per second received from startup to the present. The type of this property is “double.” Its value range is a non-negative number.

Total Requests – displays information about the number of all requests (for example, HTTP, P4, and so on) received by the cluster and the number of responses. The data is presented by the same properties as described above.

Workload Summary®Threads

SystemMonitoredThreads – displays summary information about all system threads on the cluster:

Initial threads
Current threads
Peak threads
Running threads
Idle threads
Idle waiting threads
Threads blocked by synchronization
Threads waiting for resources
Queued requests for threads

Workload Summary®Memory

MemoryManager – displays information about the memory used by the whole cluster. The following information is provided:

Allocated Memory – the memory allocated to the cluster. The value of this property is in bytes. Its type is “long.” The value range is less than or equal to the Memory Limit property.
Memory Limit – the maximum amount of memory that can be allocated to the cluster
Max Memory – the maximum amount of memory used by the cluster up to the present
Memory in Use – the amount of memory being used by the cluster
Utilization Level – an integer corresponding to the percentage range of memory used by the cluster at the current moment. There are six utilization levels according to the amount of memory used

0 – the amount of memory used is from 0% to 40%
1 – the amount of memory used is from 41% to 55%
2 – the amount of memory used is from 56% to 65%
3 – the amount of memory used is from 66% to 71%
4 – the amount of memory used is from 72% to 75%
5 – the amount of memory used is from 76% to 100%

Properties

	Dispatcher
Property	Description	Default Value

port	The port where the dispatcher listens for a running monitor server.	3906

	Server
Property	Description	Default Value

port	The port where the server listens for a running monitor server.	3907

Console Administrator

Monitor Service can be administered using the Shell commands from the MONITOR command group as well.

Note: For information on Monitor shell commands, refer to the Shell Commands Reference section.

Property Files

../cluster/dispatcher/services/monitor/properties
Monitor Service properties specified in the Visual Administrator ® Properties section can be set from this property file as well.

../cluster/server/services/monitor/properties
Monitor Service properties specified in the Visual Administrator ® Properties section can be set from this property file as well.