Configuration of HanaXsSummaryTest

This test monitors the target SAP HANA XS Advanced system and reports the status of the server and the number of used applications and instances. In addition, this test also reveals number of stopped and crashed instances, deployed,running and stopped applications, and total alerts in last 5 minutes. The detailed diagnostics provided by this test points adminitrators precisely to the XS organization, XS space, username and total applications for which alerts occured in last 5 minutes.

The default parameters associated with this test are:

• The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

• In the HOST text box, specify the HOST for which this test is to be configured.

• Specify the port at which the specified host listens to in the PORT text box.

• Specify the name of the Organization that contains the spaces in which the appplications are deployed on HANA XS in the ORGANIZATION textbox. Example: org

• Specify a comma-separated list of Spaces for the specified Organization in HANA XS in the SPACES textbox. The Spaces specified in this text box need to be included for monitoring. Example: SAP,PROD

• Specify the full path to the location where the HANA XS is installed in the XS PATH textbox. Example: /HANA/shared/HDB/xs/bin/

• 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: 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:

  • xs assign-role-collection XS_CONTROLLER_ADMIN_READ_ONLY XSA_ADMIN2;

  • xs set-org-role XSA_ADMIN2 orgname OrgAuditor;

  • xs set-space-role XSA_ADMIN2 SAP SpaceAuditor;

• Specify the password of the specified CLI User in the CLI PASSWORD text box.

• Confirm the password by retyping it in the CONFIRM PASSWORD text box.

• 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 the CLI LOCATION flag to Remote or Local based on the location of HANA XS Client.

• Specify the URL of the API end point to connect to the XS advanced controller on the SAP HANA server in the CLI ENDPOINT text box. Syntax for this CLI endpoint is : https://<Hostname>: 3<Instance Number>30. Example: https://vhcalhdbdb.dummy.nodomain:30030

• To make diagnosis more efficient and accurate, eG 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, by default, for a particular server, choose the On option against DETAILED DIAGNOSIS. 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:

  • The eG manager license should allow the detailed diagnosis capability.

  • Both the bad and normal frequencies configured for the detailed diagnosis measures should not be 0.

• If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS button will appear in this page. Clicking on this button will allow you to apply the configuration to all/selected components of that type.

• Once the necessary values have been provided, clicking on the UPDATE button will register the changes made.

When changing the configuration for specific servers, a “*” beside the text box corresponding to the parameter signifies that these values have to be manually configured by the user. The parameter values that require to be configured will typically be prefixed with a “$” or contain a series of “*”. A value of “none” in the parameter value indicates that the corresponding parameter value can be changed if required.