Skip to Content
Author's profile photo Former Member

HANA and PowerBuilder: Setting Up Your SAP HANA Cloud Server

Part 02 of a 5 part series

In this document and its accompanying video I’ll describe, define and illustrate how to set up a HANA Cloud server on AWS.  This document is mostly a confirmation of steps and procedures that are already well documented here and here as well as in many other places. In fact, Most of the steps I enumerate contain links to the resources I relied on.  In general, HANA Academy is a great source of How-To videos. There is nothing PowerBuilder specific in setting up a server.  I added a few screen shots and clarifications of things that I found unclear as I set up my server. 

One caution when searching for online resources (and there are many).  HANA is a rapidly developing technology. Lots of video tutorials are outdated.  The release current to this document’s publication in June 2013 is SPS5 version (Rev 52). While writing this, I got word that SPS6 is on its way.  Chances are high that videos and tutorials illustrating prior versions will be somewhat outdated.  In general, a nice thing I discovered is that in addition to technical enhancements, successive recent releases have improved GUI functionality and usability.

Pre-Installation Steps

Prepare these two assets before starting: 

  1. An account
  2. An AWS account at

Here’s mine:


Once your account is established you’ll need to view your Access Credentials.  Get to them using the link on the left side navigation panel. Take a moment to familiarize yourself with your Access Key ID and Secret Access Key You’ll need them to configure your HANA server.

Next prepare three strong passwords. Record them for safe keeping and have them handy.

  1. SAP Hana Linux hdbadm User:
  2. SAP One Hana Management Console:
  3. SAP Hana database SYSTEM user:

Another important asset to acquire is an Elastic IP address. Note: There is a fee for owning an Elastic IP. You’ll want to associate it with your server instance every time you start it up.  Why? The server is given a new IP address every time it is started.  Associating your elastic IP address provides you with a fixed IP address that you can embed in all your clients.   Every time you start your server you’ll need to re-assign the elastic IP.  Follow this link to learn more about elastic IP addresses.

This image shows the steps to allocate an elastic IP:


Starting your server instance

As shown here, use the link in the left side Navigation Bar, navigate to your Instances page


(You can use a context menu to name your instance, if you wish.)

Right click on the instance and choose Start


This will load the server image on Amazon’s system.  It does NOT start HANA!

Once the instance is in ‘Running’ mode, associate your elastic IP address with it (you will have to do this every time you start your server)


Give the internet a few minutes after the elasticIP association for the elasticIP address to be accessible. What is most likely happening is that Amazon is using Network Address Translation (NAT) within their own network to associate the external (“elastic”) IP they gave you to the instance of a VM on a server in their server farm that they fired up for you.  Before it’s registered you’ll get 404 errors in your browser.

Next log in to your server administration console using the SAP One Hana Management Administrator password you configured when you created your image.   The URL you navigate to will be in the form: <<your elastic ip address >>/login.html  For example (sometimes) my test server is

Once the login page displays, enter your SAP One Hana Management Console password to access the console. Navigate to the Administration page. You’ll need to enter your Access Key ID and Secret access key as noted above to begin to configure your server.  You can copy and paste these credentials from your AWS account.

Next you’ll need to enter and confirm the Management Console and SYSTEM user passwords you selected above.  You will then be able to click Configure HANA.

After configuration, you’ll be able to Start your server.

Once your HANA server is up and running, navigate in the console to the downloads page.  Download, install and configure the SAP HANA Studio application as illustrated and described in same document located here   . I’ll not repeat the details. 

One important point the article takes for granted.  You’ll need administration rights to alter the Hosts file located at C:\Windows\System32\drivers\etc\hosts. Run NotePad as administrator and you’ll be able to make the required entry.

Don’t forget to stop HANA and your AWS instance when you’re done.

Here’s a  video showing me starting and stopping my instance and server as well as logging in as SYSTEM to HANA Studio

In my next article I’ll illustrate how to download and install client drivers, use the PowerBuilder IDE to configure an ODBC and JDBC connection to your HANA Cloud server as well as sharing a few tips and tricks I figured out along the way.

ToDo Checklist

  1. Follow the steps in this document and its referenced documents to configure a HANA Cloud server on AWS
  2. Start your instance & Start your HANA database
  3. Access your database from HANA Studio and examine data in the demo schema
  4. Stop your database and stop your instance

Assigned Tags

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

      Thanks for sharing

      Author's profile photo Witalij Rudnicki
      Witalij Rudnicki

      Great effort to marry PB and HANA technologies. Thanks for that!

      The only comment I would make is "SAP HANA Cloud" is something different than "SAP HANA in the cloud", and it is the latter you are describing here.

      SAP HANA Cloud is an mPaaS solution. More here:

      Author's profile photo Bruce Armstrong
      Bruce Armstrong

      Good point.  But I think it also illustrates a problem.  At one point "HANA" meant the database.  Now "HANA" seems to get tagged onto a lot of stuff.

      Some time ago, Microsoft developed a new abstract API layer to run on top of the Windows SDK called .Net.  Initially that made sense, but then they started tagging anything that suppoted web services with .Net as well, and the term started to lose meaning.  Eventually they figured that out, and restricted it back to it's original meaning.,2817,1125399,00.asp

      Seems like SAP may be heading the same direction with "HANA".  Just a thought.

      Author's profile photo Former Member
      Former Member
      Blog Post Author

      I am in awe of the immense effort and amount of resources SAP is putting into HANA.  It a it developing at breakneck speed. I began my tutorial at SP5 v48 while viewing tutorials about SP4.  Then SP5v52 rolled out.  The week after I posted my series SP6 rolled out. and those enhancements are just a portion of what is new.  Unless one is a full time HANA professional or a devoted HANA student, it's difficult to keep pace.  I'd focus on acquiring solid core skills and concepts that are sure to be version-proof