The SAP HANA Cockpit is built as an SAP HANA extended application services, advanced model (XSA) solution and it is the web based administration tool for the administration, monitoring and maintenance of SAP HANA systems. In our SAP HANA landscape, we have DEV, QA and PROD and also cockpit itself.
Also Read: SAP HANAIMP 16 Certification Preparation Guide
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 run time 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 shared hardware.
After installation of SAP HANA Cockpit, you need to implement security model. There are 3 key users that you should be aware of for the cockpit.
- Cockpit user
- Technical user
- Database user
These 3 users respectively provide access to the cockpit, access to health data from a resource, and access to resource monitoring and administration. Each of these users operates on a different level of security and it is important to be able to differentiate between them.
SAP provides documents with details how to configure and what type of privileges need to grant to cockpit users. I don’t want to repeat here.
We installed SAP HANA Cockpit 2.0 as shared hardware and the following links are provided after installation.
SAP HANA cockpit: https://<host>:51063
SAP HANA cockpit manager: https://<host>:51065If these two links are not accessible one day, it is most likely SAP HANA cockpit database run into some issues or these cockpit web apps have problems inside XSA runtime environment.
Step 1 ) SSH into your linux server , and switch to the adm user with the su <sid>adm command, The default sid (system id) for cockpit is H4C
Step 2 ) XSA login using the script /hana/shared/<SID>/xs/bin/xs-admin-login
a. If You are prompted for the password of built in cockpit admin user COCKPIT_ADMIN as below, that’s good news because SAP HANA cockpit database is still running fine and most likely those two cockpit web apps run into issues
b. If you run into some issues like SAP DBTech JDBC : Cannot connect to… that means most likely SAP HANA cockpit database stop working.
Step 3 ) You can start or stop your SAP HANA system from the command line in one of ways
- By using the sapcontrol program:
- Log on to the SAP HANA system host as a user with root authorization. sudo -i
- Execute one of the following commands: please note: SAP HANA cockpit database instance number is 96
- Start the SAP HANA system by entering the following command/usr/sap/hostctrl/exe/sapcontrol -nr 96 -function Start
- Stop the SAP HANA system by entering the following command/usr/sap/hostctrl/exe/sapcontrol -nr 96 -function Stop
- By using the HDB program:
- Log on to the SAP HANA system host as user adm. su – h4cadm
- Execute one of the following commands:
- Start the SAP HANA system by entering the following command:/usr/sap/H4C/HDB96/HDB start
- SAP HANA system by entering the following command:/usr/sap/H4C/HDB96/HDB stop
Step 4 ) Run xs verison to find out xs controller url
The following are useful pre-registered service URLs
xsa-cockpit = https://awdi1hnmstr02.dev.hoopp.cloud:51054 (xsa-cockpit admin)
hrtt-core = https://awdi1hnmstr02.dev.hoopp.cloud:51050 (database explorer)
hana-cockpit = https://awdi1hnmstr02.dev.hoopp.cloud:51063 (hana cockpit web app)
hana-cockpit-admin = https://awdi1hnmstr02.dev.hoopp.cloud:51065 (hana cockpit web manager app)
Step 5 ) To see a list of cockpit spaces, execute the xs spaces command. SAP space is built in space and cockpit is custom space
Step 6 ) To see a list of currently running apps, execute the xs apps command. You can see how many apps have been pre-installed in cockpit SAP space.
Step 7 ) Let’s login in xsa-cockpit admin url
https://awdi1hnmstr02.dev.hoopp.cloud:51054User id: COCKPIT_ADMIN and password is one you provide during the cockpit installation
By default there are two spaces under organization: HANACockpit
Step 8 ) Take a look at cockpit users, the user COCKPIT_ADMIN is built in and I have created the other two
Step 9 ) Here we can see the XSA tenant database is mapped to SAP HANA express edition (HANACockpit)
SAP HANA express edition: HANACockpit
SAP space is mapped to HANACockpit
Step 10 ) Let’s take a look at cockpit web app
You can restart your app or scale up by adding instance
Within seconds I am able to boost performance by increasing web app instances from default 1 to 2
Step 11) You can retrieve logs for cockpit web app
XSA app and Component of Cockpit
| If you encounter issues with… | View the application log for… | Corresponding cockpit area on the XSA Logs app |
| Resource registration, resource group management, cockpit user management, or other cockpit manager issues |
|
Resource Management |
| Displaying or retrieving data, or issues related to specific SAP HANA cockpit applications |
|
Specific SAP HANA applications |
| Collections (for example, if you notice that information in Aggregate Health Monitor, or in the alerts does not appear accurate) |
|
Collections |
| Components in the SQL Analyzer |
|
SQL Analyzer |
| Components in the Database Explorer |
|
Database Explorer |
| General errors in the user interface, such as with graphs, list views, or filters. |
|
Generic User Interface Areas |
| Components of the audit log |
|
Audit Log |
Step 12) Lastly we need to connect to SAP HANA express edition by database explorer
hrtt-core: https://awdi1hnmstr02.dev.hoopp.cloud:51050
cockpit database instance: 96
port number: 39613
Click ok to login HANA express edition
Let’s end the great journey to SAP HANA Cockpit 2.0
