Skip to Content

In this blog, I would like to provide a step-by-step procedure to install and configure new SAP HANA 2.0 Cockpit to monitor and maintain multiple SAP HANA databases.  SAP HANA 2.0 Cockpit is a native web based centralized HANA administrator tool used to perform all database management and monitoring of multiple SAP HANA 2.0 and SAP HANA 1.0 SPS 12 databases.

HANA 2.0 Cockpit was introduced in SAP HANA 2.0 SPS 00 and absorbs functionalities of SAP DB Control Center.  This tool is built as an SAP HANA XS Advanced application and uses SAPUI5 user interfaces.  HANA 2.0 Cockpit is installed as a single stack but does not require a dedicated instance of SAP HANA to operate.

In the future, the SAP HANA 2.0 Cockpit will be the main and only native tool for administration and monitoring of SAP HANA databases, running both on-premise and the cloud.

Unlike the previous release SAP HANA Cockpit 1.0, cockpit 2.0 comes as a separate SAP HANA system.  It runs on a special version of SAP HANA, Express edition with an XS advanced runtime environment included.  You can’t deploy cockpit as an XS Advanced application on an existing SAP HANA instance nor can you deploy XSA applications to HANA Cockpit.  It is recommended for a production environment to install the SAP HANA Cockpit on a dedicated hardware.  For non-production, you can deploy on an existing SAP HANA server as discussed in the   SAP HANA Cockpit Installation and Update Guide.

 

SAP HANA 2.0 Cockpit requires a minimum of 16GB RAM but may need more depends on the number of systems monitored.  It is important to review installation and upgrade guide and SAP Notes to get hardware and operating system requirements before installation.

The following users with the privileges need to exists in the monitored resources:

User: COCKPIT_TECH_USER (to gather information such as state, status, and other generalized KPIs)

Roles:

sap.hana.ide.roles::SecurityAdmin

sap.hana.ide.roles::TraceViewer

System Privileges:

CATALOG READ

Object Privileges:

SELECT on _SYS_STATISTICS

User: COCKPIT_ADMIN_USER (for remote DB login to manage)

System Privileges:

CATALOG READ

DATABASE ADMIN

BACKUP ADMIN

Object Privileges:

SELECT on _SYS_STATISTICS

HANA 2.0 Cockpit can be installed using hdblcm tool in command line or GUI.  The installation includes a special version of SAP HANA Express edition with an XS advance runtime engine, which you can monitor and administer using the Cockpit.  The following screenshots provides some of the installation steps:

Once you successful install HANA Cockpit, you need to login to Cockpit Manager portal to configure Resource Groups, Register Resources, and Cockpit users.

You will monitor and administer registered resources using Cockpit User portal.  The  user portal will provide resource information in tabs for performance and monitoring KPIs, Security, and other SAP HANA options like Application Lifecycle Management, Platform Lifecycle Management, and etc.,

You can download the complete document here .  Hope you can follow the document to install and configure HANA 2.0 Cockpit in your environment and successfully monitor and administer multiple HANA databases.

If you have any questions or comments, please post in the comments section.

 

Thank you.

S/4HANA RIG

 

To report this post you need to login first.

6 Comments

You must be Logged on to comment or reply to a post.

  1. Krzysztof Strakowski

    Nice document!

    But I can’t add resource. Any created user on HANA db is rejected:

    Technical user authentication failed
    Authentication failed

    …while I can log on with  him via HANA Studio. It is possible only on the SYSTEM user (not recommended). I still don’t find answer why.

    BR

    Krzysztof (KST)

    (0) 
    1. Agatha Yeung

      For a user to qualified to be a technical user, he needs CATEGORY READ permission, and also best give him _SYS_STATISTICS object privilege also.

       

      You should able to find the information from the Hana Cockpit’s help: The question mark on the upper right, then select ‘Register a Resource’

       

      CREATE USER <username> PASSWORD <password> NO FORCE_FIRST_PASSWORD_CHANGE;
      GRANT CATALOG READ to <username>;
      GRANT SELECT on SCHEMA _SYS_STATISTICS to <username>

      (0) 

Leave a Reply