Java Application Status Test
Sometimes, Java applications running on SAP BTP Neo environment may be stopped for maintenance or for debugging activity. During such times, users will not be able to access the application. To proactively figure out the Java applications that are stopped in a target environment and ensure better user experience, administrators need to constantly keep a vigil on the status of the Java applications running on the target environment. The Java Application Status test helps administrators in this regard!
This test monitors the Java applications running on the target environment and for each Java application, this test reports the current status. Using this test, administrators can easily isolate the applications that are currently stopped and initiate remedial steps to start the applications before end users start complaining.
Target of the test : A SAP BTP Neo Environment
Agent deploying the test : An internal/remote agent
Outputs of the test : One set of results for each Java Application in the target SAP BTP Neo Environment.
Parameter | Description |
---|---|
Test Period |
How often should the test be executed |
Host |
Host name of the server for which the test is to be configured. |
PortNo |
Enter the port to which the specified host listens. By default, this is 10002. |
Subaccount |
In SAP Cloud Platform Cockpit, one user account will have multiple subaccounts. So you can mention any one of the subaccount name in the Subaccount text box. To know how to determine the Subaccount, refer to Identifying the API Endpoint URL and Subaccount topic in Pre-requisites for Monitoring SAP BTP Neo Environment. |
User |
For collecting the metrics, specify the Username in the User text box. The Username here refers to the Client ID created in SAP Cloud Platform Cockpit. To know how to create such a user (Client ID) in SAP Cloud Platform Cockpit, refer to Registering the eG Agent as an API Client topic in Pre-requisites for Monitoring SAP BTP Neo Environment. |
Password |
Specify the password in the Password text box. The Password here refers to the Client Secret created in SAP Cloud Platform Cockpit. To know how to create Password (Client Secret) in SAP Cloud Platform Cockpit, refer to refer to Registering the eG Agent as an API Client topic in Pre-requisites for Monitoring SAP BTP Neo Environment. |
Confirm Password |
Confirm the password by retyping it here in the Confirm Password text box. |
DD Frequency |
Refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD frequency. |
Detailed Diagnosis |
To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:
|
Measurement | Description | Measurement Unit | Interpretation | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Application State |
Indicates the current state of Java applications running on the target environment. |
|
The values reported by this measure and its numeric equivalents are mentioned in the table below:
Note: By default, this measure reports the Measure Values listed in the table above to indicate whether/not the status of java applications is stable. The detailed diagnosis of this measure provides the stopped java application process details like the account name, create date, updated date, application url, runtime name, argument and version. |
||||||||||||
Total processes |
Indicates the total number of Java application processes running on the target environment. |
Number |
|||||||||||||
Pending processes |
Indicates the number of Java application processes that are pending. |
Number |
A low value is typically desired for this measure. |
||||||||||||
Starting processes |
Indicates the number of Java application processes that are in starting stage. |
Number |
|
||||||||||||
Started processes |
Indicates the number of Java application processes that started. |
Number |
|
||||||||||||
Stopping processes |
Indicates the number of Java application processes that are in stopping stage. |
Number |
A low value is typically desired for this measure. |
||||||||||||
Stopped processes |
Indicates the number of Java application processes that stopped. |
Number |
A low value is typically desired for this measure. The detailed diagnosis of this measure if enabled, detailed diagnosis provides details about the stopped process like the process Id, display name, id, state, version, expiry date and availability zone. |