Skip to Content
Author's profile photo Bhudev Sharma

Create Resource Group and Resources in SAP HANA Cockpit 2.0 SP 06

As we are aware that SAP HANA Cockpit is the new web based HANA administration tool to monitor and manage HANA 2.0 databases, recently we installed the latest release SAP HANA Cockpit 2.0 SP 06 patch 04 for a client so as to monitor the BW/BPC HANA landscape.

To monitor and manage the HANA databases for the complete landscape, we installed HANA Cockpit 2.0 SP 06 patch 04 on a separate/dedicated server with 32 GB of RAM. Once the Cockpit instance is installed, we created resource groups and resources via SAP HANA Cockpit Manager web URL. A resource is the remote HANA database which we want to monitor via HANA Cockpit and a resource group is a group of commonly managed HANA databases for group level monitoring. For e.g. we planned to manage all BW/BPC non production HANA databases via a single resource group. So, we added all non production BPC HANA databases as ‘resources’ in the HANA cockpit and then we assigned these resources to the resource group.

I want to share how we configured the remote BW/BPC development HANA databases in HANA Cockpit Manager. A few prerequisites we should have in place before we configure resources:

  1. HANA cockpit manager is accessible via URL https://fullhostname:510024
  2. We are able to login the cockpit manager via the default cockpit user cockpit_admin or with our individual cockpit user created, for e.g., bsharma.
  3. Logged in user (cockpit_admin or bsharma) should have the authorizations/roles such as Cockpit Resource Administrator and Cockpit User role.

Sequence of activities performed:

  1. Create Resource Group
  2. Register Resource
  3. Assign the resource to a resource group
  4. Validate resource monitoring via HANA Cockpit

Create a Resource Group:

Login SAP HANA Cockpit manager https://fullhostname:510024/ with Cockpit user.

We will see the cockpit manager welcome screen. Only the features available according to the assigned authorizations, for e.g., to create a resource group and register a resource. Click on ‘Create Resource Group’ to create a resource group for group-level monitoring.

Enter the name for resource group according to the planned strategy to manage the customer landscape. For e.g. we created a group BW_BPC_NONPRD to monitor or manage all BW-BPC Non production HANA databases.

There are no resources registered yet, so continue by clicking ‘Step 2’.

Click ‘add cockpit users’ button to browse available users.

Select the new cockpit user, for e.g. bsharma. This user will have access to the resource group BW_BPC_NONPRD so as to monitor and manage all the resources within the group.

Click the button – Create Group – to create the resource group.

Confirmation screen should display the details for new created resource group BW_BPC_NONPRD.


Register a Resource:

As we discussed before, a resource is the remote HANA database which we want to monitor and manage via SAP HANA Cockpit 2.0. Again login to cockpit manager and go to home page. Click on ‘Register a Resource’.

Select ‘System generated’ resource name. It will create a resource name for e.g. SID@SID in case of multiple container HANA database systems. Provide the details for the HANA database to be monitored and managed:

  • Host: full hostname with domain
  • Identifier: Instance Number (or port number)
  • Container: Multiple Containers as our remote HANA database system is multi container. We selected – Tenant Database – so as to add the BW/BPC HANA development tenant database as resource to be monitored via HANA cockpit
  • Database Name: Database name must be provided if we are trying to add a tenant database as a resource.
  • Description: A short description for the remote HANA database we want to monitor

Provide a technical user, a user which exists in the target remote HANA database. For e.g. we created a user COCKPIT_MONITORING in the tenant database. User should have minimum authorizations and can be created in the remote database using following SQL commands:

Select whether to encrypt the connection or not. Check mark the options and continue to step 4.

Click – add group – to assign a particular resource group. So, the resource which we are trying to register will be a member of the resource group BW_BPC_NONPRD.

Select BW_BPC_NONPRD resource group, which we created before.

Continue with the selection after specifying the resource group.

Provide contact details for the person responsible for the resource/database and click Review.

Click the button – Register – to register the Resource.

‘Resource Details’ will show the details about the registered resource. Remote HANA tenant database has been registered a resource GHC@GHC in SAP HANA Cockpit 2.0.


Validate the resource monitoring via SAP HANA Cockpit 2.0

We can click – Go to SAP HANA Cockpit – at the bottom of the screen from Cockpit Manager itself to go to HANA cockpit and to monitor the added resource. Or open SAP HANA Cockpit 2.0 via web URL http://fullhostname:510022

Go to – Resources – to see the details for remote HANA tenant database. Resource state should be ‘Running’.

Click on Resource, for e.g. GHC@GHC, to monitor the resource / HANA tenant database.

I will share further learnings in the next blog. I am happy to learn and discuss more with fellow enthusiasts, please share your feedback and questions in the comments section.

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Xue Ming Huang
      Xue Ming Huang

      Dear Bhudev Sharma,

      Nice blog for SAP HANA Cockpit we known in sap hana cockpit 1.0, there existed embedded cockpit with limit functions.below are my questions.

      1.the url access to hana cockpit is http://<fqdnhostname>:80xx/sap/hana/admin/cockpit.In sap cockpit 2.0 if the access url was changed and we can only deploy the cockpit 2.0 standalone?

      2.what is different between cockpit and cockpit manager?

      Author's profile photo Sergio Guerrero
      Sergio Guerrero

      the cockpit mnanager is a tool accessible to the admins and such users with elevated privileges...  in the cockpit manager, you can manager resources (remote HANA databases).. you can create cockpit users  and set additional cockpit settings.

      the HANA cockpit is the tool where you can see the HANA options like (monitoring and administration such as DB status, memory, cpu and disk usage, security settings like dackups, data encryption, authentication methods, etc), performance management (analyze performance loads), notifications (alerts), and other hana options such as provisioning SKi etc)

      Author's profile photo Atul Kaulgud
      Atul Kaulgud

      Hi Bhudev, It is very nice article. I am new to SAP world, primarily working on AWS cloud. I am looking for information re Automation of DR activities or failover to DR site once DR is triggered. Rather that doing things manually, can we automate those things so that failover to DR is quick, fast and reliable.

      I also read about hooks available, which can be used to automate failover to DR site, once DR is activated


      Could you please share details or connects for above query