Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
cancel
Showing results for 
Search instead for 
Did you mean: 
former_member198774
Active Participant
10,349
In this blog, we would like to explain HANA Installation and how to monitor the HANA Landscape systems using HANA Cockpit.

In older HANA 1.0 SP12 by default cockpit was installed along with HANA Server but the newer version after HANA 2.0 SP01 higher SP level, we must install COCKPIT on a separate server to manage and monitor the HANA Landscape systems.

HANA COCKPIT can be installed on a separate  server, or we can install within the HANA server.

SAP recommended to install the HANA COCKPIT a separate server for production environment.

HANA Deployment procedure.

HANA Cockpit can install separate server Production systems.

 


 

 

Separate hardware

 


 

 

Advantage of HANA Cockpit installation.

  • We can do all the administration activities like Backup & restore, monitoring activities like long running queries, alerts monitoring of multiple HANA systems.


 

SAP HANA Cockpit Installation procedure.

Following hardware and software required for HANA COCKPIT installation.

Hardware Requirements.

Supported hardware platforms.

* Intel-Based Hardware Platforms

*  IBM Power Systems.

Note: SAP HANA cockpit is not supported for IBM Power systems running Red Hat Enterprise Linux.

In the production environments, the SAP HANA cockpit should be installed on dedicated hardware.

A minimum of 16GB of RAM and 16GB of disk space is required for Cockpit installation.

 

Note: We have installed the COCKPIT in Azure free trail environment 

Software  Requirements.

Download HANA COCKPIT media from service marketplace.

 


 

Extract the SAR file.

 


 

We can move the cockpit software from windows to Linux server using WINSP.

Go to software and launch the media using ./hdlcm.sh script.

 


 

Choose the 12 options.

 


 

We must keep on default path on below inputs.

Enter the Installation path /hana/shared

SID H4C

Instance No : 96

 


 

 


 

Launch SAP HANA cockpit by opening https://saplinux1:51026

Launch SAP HANA cockpit manager by opening https://saplinux1:51028

 

Setting up Cockpit with the Cockpit Manager

Manages all resources and creates groups of resources that other cockpit users will be able to access. A resource is an SAP HANA system, identified by a host and instance number.

 

Once installed HANA COCKPT, by default COCKPIT_ADMIN user is created. This user having all the privileges like setup HANA Groups and setup the new users.

Recommended to create a new user and granted the required roles to manage and monitoring the resources.

During the cockpit installation, we got the COCKPIT manager & Launchpad URL’s.

 

Logon with cockpit manager using cockpit_admin user ID to setup the new user account and granted the required privileges to access the resources.

 


 

Click on add the cockpit user.

 


 

We have to provide the below details.


 

Granted the below roles.

 

 


 

Setup the user ..


 

Click on register a database to add the HANA Tenants and once register we have to add those tenants to monitor in the cockpit launchpad.

 


 

We have to provide the required HANA Tenant details like below to register the HANA Teants.

 


 

 


 

After added HANA teants , we can administration of multipile HANA teants from HANA Cockpit.

 

 


 

Here we can see the database status and also see the services are running or not for particular database.

 


 

In the below screen we can see the used & Peak used memory .

 


 

Once click on the memory statics , we can see all the CPU , Memory consumption .

 


 

We see the all the alerts in the below tile.

 

 


After we can see in detailed information about the alert


Please refer the below Standard guide for in detailed HANA Administration activities .

 

https://help.sap.com/docs/SAP_HANA_PLATFORM/6b94445c94ae495c83a19646e7c3fd56/330e5550b09d4f0f8b6cceb...

 

 

 

 
Labels in this area