Skip to Content
Product Information
Author's profile photo Manjunath Baburao

SAP HANA 2.0 on Neo: Database administration using on-premises SAP HANA Cockpit


This blog aims to outline and demonstrate the procedure to connect SAP HANA 2.0 databases running on the SAP Business Technology Platform, Neo environment to an SAP HANA Cockpit 2.0, installed on-premise.



Recently SAP announced the availability of SAP HANA version 2.0 on the SAP BTP, Neo environment as the ‘go-to’ version for all future database provisioning in the environment.

The release of this version will also help existing SAP HANA 1.0 databases to be upgraded before the End of Maintenance timeline of HANA version 1.0 on June 30, 2021.

Alternatively, Neo customers also have the option to choose migration to SAP HANA Cloud, and this upgrade to SAP HANA 2.0 will serve as a pre-requisite for this migration.

Additionally, in order to make the transition to SAP HANA 2.0 as smooth as possible for existing customers, SAP HANA 2.0 has been released with exceptional support for only eXtended Service Classic (XSC), which was the XS flavor already supported with SAP HANA 1.0 on Neo.

Migration of existing applications and assets to eXtended Service Advanced (XSA) is not mandated and also not supported.


Administration Tools for SAP HANA Service on Neo

If you are familiar with the SAP HANA Service on the SAP BTP, Neo environment, you will be aware that the service provided access to both

  • Administration tools >> SAP HANA Cockpit (1.0) and
  • Development tools >> SAP HANA Web-based Development Workbench

from the SAP BTP Cockpit.

SAP HANA 2.0 is delivered with an updated version of the cockpit – SAP HANA Cockpit 2.0, for all database administration needs. The architecture of SAP HANA Cockpit 2.0 (like most HANA tooling today) is based on the XSA runtime.

As XSA runtime is not supported with the SAP HANA Service on Neo, SAP HANA Cockpit will be not available for HANA databases/database systems running on SAP HANA version 2.0. However, the SAP HANA Web-based Development Workbench (HANA IDE) will still be available as development tooling.

This restriction in administration tooling and recommended alternatives can be found in our help documentation pages.


Data administration of SAP HANA 2.0 databases on Neo using an on-premise SAP HANA Cockpit

One of the recommended alternatives for administrating HANA 2.0 databases in the Neo environment is to install or re-use an existing installation of an on-premise SAP HANA Cockpit 2.0 to monitor cloud databases as well.


Accessing HANA databases on Cloud

In case you have been working with HANA databases on the Neo environment, you will be aware that cloud databases cannot be accessed directly from on-premise networks or systems. This access is only made possible using a ‘Secure Tunnel’ setup from on-premises to the cloud.

The Cloud Connector provided for free, as a part of SAP Connectivity service, can be used to setup and configure this secure channel to SAP BTP. Cloud Connector runs as an on-premise agent and acts as a reverse invoke proxy between the on-premise network and SAP BTP. It allows you to expose only selected on-premise assets without exposing the entire internal landscape.

Cloud Connector provides the concept of a Service Channel which lets you access HANA databases running on SAP BTP, Neo environment from tools/database clients running on-premise or in your local system.

This service channel approach can be used to access and administrate SAP HANA 2.0 databases in the Neo environment from an on-premise (OP) SAP HANA Cockpit or in some cases via a locally installed SAP HANA Studio.



Connect SAP HANA Cockpit (OP) to SAP HANA 2.0 on Neo



This blog assumes the following pre-requisites are already in place and only addresses the aspect of connecting the SAP HANA Cockpit to Neo HANA databases.

  1. SAP HANA 2.0 database system and tenant database(s) have been created and started in an SAP BTP, Neo environment subaccount.
  2. A valid administrator user (SYSTEM) with appropriate privileges is available for the tenant database.
  3. SAP HANA Cockpit 2.0 (latest revision) is installed and running on-premises.
  4. SAP Cloud Connector is installed and running on-premises.
  5. A valid user is available to access both the above tools (3) & (4).
  6. [optional] SAP HANA Studio 2.0 should be installed.



Tool: SAP BTP Cockpit

  1. Login to the cockpit. Navigate to your Neo subaccount – Overview page.
  2. Make a note of the Technical Name of your subaccount. This will be required when configuring a connection from the SAP Cloud Connector.

  1. Navigate to SAP HANA/ASE – Database systems and inspect the database system you wish to connect to.

  1. Verify that the database system is running a Version of SAP HANA 2.0 (SP5 as of this date) and the State is ONLINE.
  2. Click on the numeric link under Tenant Databases.
  3. Click on the link under Database ID. Also note this ID for future reference.
  4. Verify that the Version is SAP HANA 2.0 (SP5 as of this date) and the status is STARTED. You will also notice that, as explained earlier, there is no link/option provided for Administration Tools (unlike with SAP HANA version 1.0).

Useful links:

SAP HANA 2.0 on Neo environment

Tool: SAP Cloud Connector

  1. Login to the Cloud Connector with the Administrator user. Navigate to the Connector overview.

  1. We need to connect the Cloud Connector to our Neo subaccount. To do this, click on + Add Subaccount.

  1. In the pop-up enter the required information:
    • Select the right Region from the value help.
    • Enter the Subaccount information noted in Step 2 of the previous section.
    • Enter the Subaccount User & Password of the user which has access to your Neo subaccount (example: S-user).
    • Click on Save.

  1. If the connection is successful, you will see your subaccount shown in the Subaccount Dashboard with a Connected state. It might show up as an orange diamond because we have not yet exposed any resources. Also, see that the Service Channels Overview is empty.

  1. Click on On-Premise To Cloud in the navigation pane.

  1. Click on + to start the creation of a Service Channel.

  1. In the pop-up, select Type: as ‘HANA Database’. Click on Next.

  1. In the next screen:
    • Type in the tenant database name, noted in Step 6 of the previous section, into HANA Instance Name. NOTE: Do NOT select a value from the dropdown as it only lists database systems, and we need to connect to a particular tenant database.
    • Enter a numeric value between 01 to 97 as the Local Instance Number. This number will be used to generate a port for the cloud HANA system in the format 3<local instance number>15.
    • Click on Finish.

  1. If channel creation is successful, you will see an entry under Service Channels. The Status will show green as the channel is enabled and a Port will be generated as explained above. Note the port for future reference.
  2. Also make a note of the hostname of your Cloud Connector, where it runs – local or in a standalone system.

Useful links:

Cloud Connector on Neo environment

Tool: SAP HANA Cockpit (on-premise)

  1. Login to the HANA Cockpit with the COCKPIT_ADMIN (or similar) user. Under Manage Landscape, select the Manage Cockpit tile to open the SAP HANA Cockpit Manager.

  1. Click on Register a Database link to start the registration process.

  1. In Step 1:
    • Leave the Database Name as system generated.
    • In the Host field enter the hostname of your SAP Cloud Connector, noted in Step 10 of the previous section.
    • As the Identifier select Port Number and enter the port number copied from the Service Channel in step 9 of the previous section. Click on Step 2.

  1. Uncheck the Encrypt SAP Control connection. NOTE: Checking or unchecking the Encrypt the database connection option is based on whether SSL is enabled on the database. Uncheck the Validate the certificate Click on Step 3.

  1. Enter the SYSTEM/similar user details in the User and Password Click on Step4.

  1. Provide your contact information and click on Review.

  1. Review the inputs and click on Register.

  1. If the registration is successful you will see the success message and the database will get added to the list of Registered Databases with the name ‘NEO_<>’.

  1. Click on the name link NEO_<>. The HANA Cockpit for the respective database should open and you should be able to monitor the system details from this view.

Useful links:

SAP HANA Cockpit 2.0

And there you have it!

The connection from an on-premise SAP HANA Cockpit to an SAP HANA 2.0 database on SAP BTP, Neo environment is successful, and we are able to monitor and administer the database.

Similarly, the Service Channel created in the Cloud Connector can also be used to connect other tools like your SAP HANA Studio to a HANA 2.0 database on Neo. But the recommended option will still be to use the SAP HANA Cockpit 2.0 for database administration requirements as much as possible. If not, a combination of existing HANA XS Administration tools + SAP HANA IDE + SAP HANA Studio would be a good setup to aim for.

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Davide Bruno
      Davide Bruno

      Hi, and what about HANA 2.0 in cloud foundry? In which way I can register instances in cloud, to our HANA Cockpit onpremise?

      Many thanks!

      Author's profile photo Manjunath Baburao
      Manjunath Baburao
      Blog Post Author

      Hi Davide,

      Unfortunately, my expertise lies mostly in the HANA flavor available in the Neo environment. I assume the same procedure could also be used for the HANA service on the Cloud Foundry environment.

      But the more important question would be why such a cockpit setup would be necessary. As far as I can see both flavors in the Cloud Foundry environment provide a HANA Cockpit out-of-the-box (links below):

      SAP HANA Service (Multi-Cloud):

      SAP HANA Cloud (Multi-Cloud):




      Author's profile photo Davide Bruno
      Davide Bruno

      Hi thanks for your fast answer.

      The reason is that we prefer to have a unique HANA Cockpit with onprem and ondeman HANA instance to privde to our external dev and tech team, without assigning access to subaccount, and other stuff.

      I tried inserting in cloud connector the HANA instance based on CF environment, in the same way as I did for NEO, but unluckly with CF is not working 🙁 Do you have some suggestion for me?

      Author's profile photo Manjunath Baburao
      Manjunath Baburao
      Blog Post Author

      Thanks for providing the context, Davide.

      I see the following SAP Note provides guidance on opening Service Channels to HANA Service on Cloud Foundry environment.

      Please try it out and let me know if it works. If not, you can drop me an email ( with the results and I will try to connect you to the appropriate team for further analysis/guidance.

      Author's profile photo Alexander Parr
      Alexander Parr

      Hi Manjunath Baburao

      thank you for this great blog post! We evaluating to run advanced Fiori Elements Apps on Neo Stack, which would benefit from CDS Views / XSA model. You state, that XSA is not supported with HANA 2.0 on Neo Stack.

      I found another post stating, that XSA Runtime can be installed afterwards by downloading "SAP Extended APP Service" package from SAP Software Downloads. Would that open up HANA 2.0 on Neo Stack to run XSA?

      Do you see any other 'state of the art' option to generate an OData Service for Fiori Elements on Neo Stack?

      Referring to your statement:"Alternatively, Neo customers also have the option to choose migration to SAP HANA Cloud, and this upgrade to SAP HANA 2.0 will serve as a pre-requisite for this migration." How can we upgrade to HANA Cloud using Neo environment?



      Author's profile photo Manjunath Baburao
      Manjunath Baburao
      Blog Post Author

      Hi Alex,

      Adding additional software packages on top of HANA is not supported in the Cloud environment. This is mostly possible in the HANA on-premise cases. The decision to not support XSA on Neo comes from the fact that XSA runtime was built by bringing the Cloud Foundry paradigm to on-prem.

      We already have a Multi-Cloud environment (CF) on the Business Technology Platform which would the recommendation for using XSA-like capabilities on Cloud. So you may want to consider a migration to Multi-Cloud.

      As for the move from HANA on Neo to SAP HANA Cloud, we are developing a migration path for the same, supported by SAP. But this path expects that the HANA on Neo runs version 2.0. Hence my statement. This is also included as a factor of Multi-Cloud migration.

      Hope this helps.

      Thanks and regards,