HANA XS Applications Test
SAP HANA Extended Application Services advanced model (XS advanced) adds an application platform to the SAP HANA in-memory database. An SAP-developed run-time environment is bundled with SAP HANA installed on-premises. This provides a compatible platform that enables applications to be deployed to both the Cloud and on-premises. With SAP HANA Extended Application Services you can build and deploy your application completely self-contained within SAP HANA. Generic functionality like load balancing, elastic scaling, routing, identity and access management, API management, and application life cycle management are provided by an XS run-time platform underneath the XS advanced run-time environments.
Applications in an SAP HANA XS Advanced system are deployed and isolated using the concepts of organizations and spaces with separated OS users to meet the resource requirements of applications. An organization is a development account that one or more developers (user) can own and use. All developers in an organization share a resource quota plan, applications, services availability, and custom domains. All resources, applications, spaces, and services in the organization can be managed (and suspended) at the organization level. Every application and service is scoped to a space, and each organization contains at least one space. A space provides users with access to a shared location for application development, deployment, and maintenance.
This test discovers all the applications deployed in each space on the SAP HANA XS Advanced system and reports the actual and requested state of the application thus enabling administrators to figure out whether/not the application is up and running. This test also reveals the unexpected state and resource-usage of the applications, thus pointing administrators to the probable cause of application failures and thereby helping them in avoiding service bottlenecks.
Target of the test : A SAP HANA XS advanced Application server
Agent deploying the test : A remote agent
Outputs of the test : One set of results for each space:application on the target server being monitored.
Parameter | Description |
---|---|
Test period |
How often should the test be executed |
Host |
The host for which the test is to be configured. |
Port |
The port number at which the specified Host listens to. By default, this will be 30015. |
Organization |
Specify the name of the Organization that contains the spaces in which the applications are deployed on HANA XS in this text box. Example: org |
Spaces |
Specify a comma-separated list of Spaces for the specified Organization in HANA XS in this text box. The Spaces specified in this text box need to be included for monitoring. Example: SAP,PROD |
XS Path |
Specify the full path to the location where the HANA XS is installed in this text box. Example: /HANA/shared/HDB/xs/bin/ |
CLI User |
Typically, to connect to a HANA XS and run tests, the eG agent requires the permissions of a HANA XS client user who has been assigned the role collections as XS_CONTROLLER_ADMIN_READ_ONLY, also assigned the OrgAuditor, SpaceAuditor roles for specified organization and spaces. Ideally, you will have to create a new user role on the HANA XS for this purpose, associate the above-mentioned collections with that role, and assign the new role to an existing HANA XS client user. Once the new role is assigned to a HANA XS client user, specify the name of this user against CLI User text box. Example: To create user as XSA_ADMIN2. Execute below query in SAP HANA studio. CREATE USER XSA_ADMIN2 PASSWORD “admin”; Assign roles for HANA XS CLI user using HANA XS Client commands mentioned below:
|
CLI Password |
Specify the password of the specified CLI User in this text box. |
Confirm Password |
Confirm the password by retyping it in this text box. |
CLI Location |
The XS CLI client tools are installed by default on the SAP HANA server. However, you can also download and install the client tools locally, if you want to connect to SAP HANA from your local machine. Hence, set this flag to Remote or Local based on the location of HANA XS Client. |
CLI Endpoint |
Specify the URL of the API end point to connect to the XS advanced controller on the SAP HANA server in this text box. Syntax for this CLI endpoint is : https://<Hostname>: 3<Instance Number>30. Example: https://vhcalhdbdb.dummy.nodomain:30030. |
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 | ||||||
---|---|---|---|---|---|---|---|---|---|
Actual state |
Indicates the actual state of this application. |
|
The values reported by this measure and their numeric equivalents are available in the table below:
Note: By default, this measure reports the Measure Values listed in the table above to indicate the actual state of the application. In the graph of this measure however, the same will be represented using the numeric equivalents only. |
||||||
Requested state |
Indicates the requested/targeted state of this application. |
|
The requested state does not indicate the actual state of any application instances. The values reported by this measure and their numeric equivalents are available in the table below:
Note: By default, this measure reports the Measure Values listed in the table above to indicate the targeted state of the application. In the graph of this measure however, the same will be represented using the numeric equivalents only. |
||||||
Is unexpected state? |
Indicates the whether/not this application is in an unexpected state. |
|
The values reported by this measure and their numeric equivalents are available in the table below:
Note: By default, this measure reports the Measure Values listed in the table above to indicate whether/not the application is in an unexpected state. In the graph of this measure however, the same will be represented using the numeric equivalents only. |
||||||
Number of problems in the last 5 minutes |
Indicates the number of problems caused in this application during the last 5 minutes. |
Number |
A low value is desired for this measure. A high value is an indication of processing bottlenecks. |
||||||
Active instances |
Indicates the number of instances of this application that are currently active. |
Number |
|
||||||
Running instances |
Indicates the number of instances of this application that are currently running. |
Number |
The application instance started successfully and is accessible. |
||||||
Memory used |
Indicates the amount of memory used by this application. |
MB |
|
||||||
Allocated disk |
Indicates the total amount of disk space allocated to this application. |
MB |
|