|
Measures reported by SapWasProcessTest
A Java instance is a unit in the AS Java cluster which is identified by its instance number.
A Java Instance consists of:
The ICM is an element of the Java instance which handles requests coming from clients and dispatches them to the available server processes. The server processes of AS Java actually execute the Java application. They are responsible for processing incoming requests which are assigned to them by the ICM. Each server process is multi-threaded, and can therefore process a large number of requests simultaneously.
The proper functioning of a Java instance therefore depends upon the availability and error-free functioning of the ICM and server processes. If the ICM or any of the server processes experience errors or reboot often, then the Java instance may not be able to process requests from clients. To ensure the smooth transaction of business, administrators should periodically run the SapWasProcessTest on the target Java instance, check on the health state (whether Critical, Normal, Offline, or Online) and operational state (whether running or not running) of the ICM and each of the server processes in that instance, and capture process failures before they impact the critical business operations.
Outputs of the test : One set of results for the ICM and each of the server processes in a target Java instance.
The measures made by this test are as follows:
| Measurement |
Description |
Measurement Unit |
Interpretation |
| Status |
Indicates the current health state of this process. |
|
The values that this measure can report and their corresponding numeric values are discussed in the table below:
| Measure Value |
Numeric Value |
| Normal |
1 |
| Critical |
2 |
| Error |
3 |
| Offline |
4 |
Note:
By default, this measure reports the Measure Values in the table above to indicate process state. In the graph of this measure however, the same is represented using the numeric equivalents only.
If the value of this measure is Critical, Error, or Offline, you can use the detailed diagnosis of the measure to determine the probable cause of the abnormal process status. The detailed diagnosis will also reveal when the process was started and the elapsed time of the process. From this information, you can figure out when the problem could have occurred and how long the problem may have persisted. |
| Has_restarted |
Indicates whether/not the process was restarted in the last measurement period. |
|
The values that this measure can report and their corresponding numeric values are discussed in the table below:
| Measure Value |
Numeric Value |
| No |
1 |
| Yes |
2 |
Note:
By default, this measure reports the Measure Values in the table above to indicate whether a process was restarted or not. In the graph of this measure however, the same is represented using the numeric equivalents only. |
| CPU_utilization |
Indicates the percentage of CPU that is currently utilized by this process. |
Percent |
A value close to 100% is a cause of concern which requires further investigation. |
| Errors |
Indicates the number errors encountered by this process. |
Number |
The value of this measure should be zero. A non-zero value for this measure is a cause of concern. |
|