Skip to Content
Author's profile photo Elitsa Semerdzhieva

OpenSAP Course: SAP HANA Cloud Platform: Week3 Unit 1: Local Deployement Scenario

After executing all the steps shown in the video for unit 1 of week 3 (opening tunnel and configuring and requesting the application currently you see a response with an empty table for database entries.

But the video material on 20:01min shows a list of all the names added from the ejb and jdbc applications deployed in the cloud.


After recent changes in the Persistence Service introducing a development user concept it became no longer possible a locally deployed application to use the same schema as the application deployed in SAP HANA Cloud Platform.

Technical details

When a database tunnel connects to a schema in the cloud a new development user (DEV_<GUID>) is created while the application in the cloud is using another user (NEO_GUID). Every user in the database has also default schema corresponding to the user name.

The application is by default using the default schema of the user with which the connection to the database is made. When the application is deployed to the cloud this is the NEO_GUID schema. In the local development scenario this is the DEV_GUID schema. This is the reason to see empty table in case of a locally deployed application.

Since the DEV_GUID user has the permissions to access the NEO_GUID schema the solution is to change the default schema used by the locally deployed application with NEO_GUID schema.


The solution is provided together with the SAP HANA Cloud Platform SDK version which you can get at the SAP Development Tools For Eclipse webpage.

Steps to apply the solution: The same steps as shown in the video should be executed but with the use of the newest version of the HANA Cloud Platform SDK (min version:

1. Download the latest SAP HANA Cloud Platform SDK (min version:

2. In Eclipse create a new Runtime Environment or change the current one to use the newly downloaded and unzipped SDK.

3. Open the db-tunnel from the “tools” folder of the new SDK and connect to your schema in the cloud. The result should be like:

The difference with the previous version of the db tunnel is that  the JDBC url has an additional parameter: currentschema=NEO_E7PL7GIVVQJZWQZ6L6NMPK239 which specifies the default schema which will be used in the database connection.

4. Run the application on a new Server created using the new Runtime (SDK: Set up the connection properties using the new JDBC Url. You should get something like:

5. Restart the server and request the application. The result should be the same as shown in the video – the table should contain the database entries added from the jdbc application deployed in the cloud.

Assigned Tags

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

      Thanks Eli for helping the participants with your hints.


      Author's profile photo Vladimir Pavlov
      Vladimir Pavlov

      Great blog, Eli - very nice and clear explanation!

      Author's profile photo Abhijeet Kulkarni
      Abhijeet Kulkarni

      Excellent blog Elitsa. I can confirm that using the new SDK, the results match that of video.

      Many thanks to openSAP and SAP for acting so promptly (under a week) to fix this issue. 🙂

      Here are the screenshots:

      The port 8085 is hosted with runtime of console client version 2.19 and connected accordingly with the version 2.19 neo.bat. The 8090 is with version 2.20.

      Author's profile photo Former Member
      Former Member

      Hi Elitsa,

      Thanks very much for this helpful information. I imported all the Samples for demos of week 3 and 4 from this new SDK version Samples folder, and all of them worked perfectly.

      Thanks very much again.