Getting Started With SAP HANA 2.0, Express Edition (Virtual Machine Method)
Getting Started With SAP HANA 2.0, Express Edition (Virtual Machine Method)
Getting Started With SAP HANA 2.0, Express Edition (Virtual Machine Method)
PUBLIC
Machine Requirements
Check if your machine has the recommended hardware to successfully install and run the express edition VM image.
Softw are
Java Runtime Environment 8 - The Download Manager requires Java SE Runtime Environment 8 (JRE 8) or higher.
Note: If you are planning to use the SAP HANA, express edition Download Manager for Windows or Linux, you need the 64-bit JRE. If you
are planning to use the platform-independent Download Manager, you can use either the 32- or 64-bit JRE.
Hardw are
RAM - 16 GB RAM minimum. 24 GB RAM recommended.
HDD 120 GB HDD recommended.
Cores - 2 cores (4 recommended).
Hardware Virtualization - (Intel processors only) For Intel processors, virtualization is a BIOS setting known as either Intel Virtualization Technology or
Intel VT. Go to http://www.intel.com/content/www/us/en/support/processors/000005486.html to determine if your processor is capable of supporting
virtualization. If virtualization is turned off on your virtualization-capable machine, consult documentation from your machine vendor on how to enable
virtualization technology (or Intel VT) in the BIOS.
Note: If you have an SAP login, click the Login icon at the top of the page to populate the registration form automatically.
The Registration Success page displays. (You will also receive an email indicating successful registration.)
3. Under SAP HANA 2.0, express edition download manager, click the download manager that matches your system: Linux or Windows.
If you have a Mac, or another type of machine, click Platform-independent for a platform-independent download manager.
4. Save the download manager file to your laptop and open it.
If your system displays a security warning when you open the file, ignore the warning.
Note: If you are inside a corporate firewall, you will be prompted for your proxy settings. Contact your IT administrator.
6. Click Browse and select a directory where your downloads will be saved.
7. Select one or more of the following packages:
Getting Started with SAP HANA, express edition (Virtual Machine Method) - Selected by default. Downloads this document.
Server only virtual machine - Downloads hxe.ova ; the server plus Application Function Library (AFL).
Server + applications virtual machine - Downloads hxexsa.ova ; the server plus XS Advanced, Web IDE, SAP HANA Cockpit, and SAP Enterprise
Architecture Designer.
Note: Although this package will run on a 16 GB machine, SAP recommends 24 GB of RAM for optimum performance using the full
suite of developer applications.
Clients - Downloads clients.zip which contains four compressed client packages. Use the client packages to access developed SAP HANA, express
edition applications from a client PC. See How to Install the SAP HANA, express edition Clients. See the Installing Clients section for installation
steps.
hdb_client_linux.tgz - Reduced HANA client for Linux 64 bit. Contains the HANA client package, drivers, and required licenses.
hdb_client_windows.zip - Reduced HANA client for Windows 64 bit. Contains the HANA client package, drivers, and required licenses.
xs.onpremise.runtime.client_linuxx86_64.zip - Command-line tools for Linux that enable access to (and control of) the SAP HANA XS
Tip: After you develop an application using SAP HANA, express edition, install Download Manager to a client machine and download the
clients only to that client machine. You can then use the clients to connect to -- and test -- your HANA application, emulating a customer.
Text analysis files for additional languages - For languages other than English and German, files required for the HANA Text Analysis function. (The
text analysis files for English and German are already included in the Server only virtual machine and Server + applications virtual machine
packages.) For the text analysis files installation procedure, see the Install Additional Components section.
8. Click the Download button.
Your download is complete when a pop-up message appears confirming successful download. Make sure you wait for this message before accessing the
downloaded files.
2. Browse to the OVA file you downloaded and click Open. The Import Virtual Machine dialog box displays.
3. Accept the defaults and click Import. The VM imports. The import process takes approximately 5 minutes.
4. Power on your VM.
3. When prompted for current (UNIX) password, enter the temporary password again: HXEHana1
4. When prompted for New password, enter a strong password with at least 8 characters. If your password is not strong enough, the system logs you off and
you must log in again.
Tip: Your strong password should contain numbers, upper and lower case letters, and special characters. It cannot contain systematic values, like
strings in ascending or descending numerical or alphabetical order. Strong password example: 5342_E#1_GcbaFd!
Note: Do not use this password example, since it is public and not secure. This example is for illustrative purposes only and must not be used on
your system. Define your own strong password.
5. When prompted to Retype new password, enter your strong password again.
SAP HANA, express edition is now running.
HDB info
hdbwebdispatcher
Note: It can take a few minutes after server startup for all services to start. Allow all services to start running before calling HDB info.
Note: After restarting, allow sufficient time for all services to start running before proceeding.
\q
\q
\q
\q
/sbin/ifconfig
2. Locate the IP address, listed under the eth0 interface as inet addr .
In the following example, the IP address is 172.25.86.13:
Tip: Spacing is important. Make sure your hosts file in Notepad looks like this image.
Test XSC, XSA, and Web IDE (Server + Applications Virtual Machine Only)
If you installed the Server + Applications Virtual Machine package ( hxexsa.ova ), test your XS installations and Web IDE.
Note: Make sure you edited your /etc/hosts file before starting this procedure.
1. Check that the XSEngine is running. From your host OS (not the VM guest) open a browser and enter:
You recorded the IP address earlier in this tutorial in topic Record Your VM's IP Address. A success page displays. This indicates that XSC is running:
3. Check for an API endpoint showing https://hxehost:39030 . If you see this entry, XSA installed correctly.
4. View the list of XSA applications. Enter:
xs apps
Note: When you run the xs apps command for the first time, it may take 1-2 minutes for the system to return the list of XSA applications.
5. Check that the application webide shows STARTED in the list of XSA applications , and has 1/1 instances. (If the list shows 0/1 in the instance column, the
application is not started.)
Make a note of the URL for webide .
Tip: The command xs apps | grep webide returns the webide row only.
6. Test your Web IDE connection. Enter the URL for Web IDE in a browser on your laptop.
Example: https://hxehost:53075
7. Log on to Web IDE using the XSA_DEV user. You specified the password earlier in this tutorial in the section Change the Default Passwords for Other
Users.
8. Go back to your VM. Check that the application cockpit-admin-web-app shows STARTED in the list of XSA applications and has 1/1 instances.
Make a note of the URL for cockpit-admin-web-app .
Tip: The command xs apps | grep cockpit-admin-web-app returns the cockpit-admin-web-app row only.
9. Check that the application xsa-admin shows STARTED in the list of XSA applications and has 1/1 instances.
Make a note of the URL for xsa-admin .
Tip: The command xs apps | grep xsa-admin returns the xsa-admin row only.
10. In a browser on your laptop, enter the cockpit-admin-web-app URL you noted in step 6.
The Cockpit logon page displays.
11. Log on to Cockpit as user XSA_ADMIN . You specified the password earlier in this tutorial in Change the Default Passwords for Other Users.
12. If you are inside a corporate firewall and use a proxy for connecting to http and https servers, you need to identify your proxy settings and add them to
Cockpit.
Note: If you are not inside a firewall, you can ignore this step and skip to the next topic.
In Host, Port, and Non Proxy Hosts, enter the settings provided by your IT administrator.
Make sure the host has a fully qualified domain name.
Click Save.
Download and install the HANA Eclipse Plugin to your host OS (not the VM guest) and connect to SAP HANA, express edition.
1. Download Eclipse IDE for Java EE Developers from Eclipse for Neon or Mars releases to your local file system.
2. Follow the eclipse installer prompts.
3. Launch when prompted, or go to the eclipse folder (example: C:\Users\<path>\eclipse\jee-neon ) and run the eclipse executable file.
4. Follow the tutorial How to download and install the HANA Eclipse plugin.
Configuring Security
Change the SSFS Master Keys and Root Keys
Every user who downloads SAP HANA, express edition receives the same default encryption settings. Use the change_key.sh utility to change encryption
automatically.
Important: SAP recommends you run change_key.sh immediately after installation to ensure your security settings are not known outside your
organization.
/usr/sap/HXE/home/bin/change_key.sh
Description
HANA Instance
Number
-s
<instance
SID>
Database System
user password
Password you set when you changed the default password for SYSTEM user during installation.
The root key backup password is required to securely back up the root keys and subsequently restore the backed-up root keys
during data recovery. For information on root key backup, see Root Key Backup.
Root key
directory
A directory to store the root key backup password securely. Choose a non-temporary directory. For example
/usr/sap/HXE/HDB90 .
Wait for the script to complete (3-5 minutes). The server will restart during script execution.
A Done message displays when the script is finished. New data will now be encrypted with the new keys.
Telemetry
When you install SAP HANA 2.0, express edition, Telemetry is enabled by default. You can disable telemetry after installation is complete. Telemetry sends
anonymous performance statistics and usage statistics to SAP, so that SAP can focus development efforts on areas most vital to the SAP HANA, express edition
customer base.
Important: Your privacy is critical to SAP. Telemetry collects anonymous usage information while ensuring complete privacy. No identifying
information or private information is collected, and you can opt out of telemetry at any time.
Disable Telemetry if you wish to stop sending anonymous telemetry data to SAP.
1. Start SAP HANA 2.0, express edition and log in as hxeadm .
2. Run:
Tip: If you want to learn more about the hxe_telemetry.sh script, type ./hxe_telemetry.sh --help
Installing Clients
Install the clients if you intend to develop XS applications on a machine that will not have a local SAP HANA, express edition installation. The clients let you
access SAP HANA, express edition from your client machine.
You can install the clients on the SAP HANA, express edition server during server installation, but this how-to assumes you are installing the clients on a different
machine than the PC where SAP HANA, express edition is installed.
This how-to refers to the laptop with SAP HANA, express edition as the server machine, and your local machine as the client machine.
xs.onpremise.runtime.client_<version>
2. Check that the XS advanced run time is installed and available on the express edition machine.
Enter the following URL in your Web browser:
https://hxehost:39030/v2/info
The response displayed in the Web browser is a JSON string with details that indicate a successful connection to the XSA controller. This connection test is
important as you want to make sure the connection exists before you attempt it from within the API command.
3. Check that the XS client for XS advanced is installed and available.
The XS client tools are required to connect to the XS advanced run time on SAP HANA and deploy your XS advanced applications.
On your client machine, open a command window and run the following commands:
sudo su -l hxeadm
xs help
xs -v
xs api https://hxehost:39030
Note: This command may fail due to a missing SSL certificate. This note shows you how to set up a certificate on the client so it can connect
to the server. Copy the correct certificate to your client from the SAP HANA, express edition server.
Open a command session on the server machine. From the command prompt, login as sudo and navigate to the certificate. The certificate
default.root.crt.pem is typically located here:
<installation_path>/HXE/xs/controller_data/controller/ssl-pub/router
/hana/shared/HXE/xs/controller_data/controller/ssl-pub/router/default.root.crt.pem
Copy the certificate to a folder on the server where you can easily access it.
Using an FTP client or the scp command, send a copy of the certificate from your server machine to your client machine.
scp example:
Exit your Putty session and return to your client machine. Try the previous command again, but use the -cacert command and specify
the local certificate you just copied.
Note: The password is assigned to the XSA_ADMIN user during express edition installation.
6. Test your connection to XSA. Run the following command to view XS applications on the SAP HANA, express edition server.
xs apps
Available Clients
When you install the SAP HANA client software package, you install the following clients:
SQLDBC
ODBC
JDBC
Python (PyDBAPI)
Node.js
Ruby
hdb_client_windows\HDB_CLIENT_WINDOWS_X86_64
Description
GUI
Command Line
system.
cd <your_destination>
2. Unpack hdb_client_linux.tgz :
cd HDB_CLIENT_LINUX_X86_64
sudo ./hdbinst
(Optional) Install SAP Enterprise Architecture Designer (Server + Applications Virtual Machine Only)
If you installed the Server + Applications Virtual Machine package ( hxexsa.ova ), you have the option of installing the SAP Enterprise Architecture Designer
(SAP EA Designer) tool.
SAP EA Designer lets you capture, analyze, and present your organization's landscapes, strategies, requirements, processes, data, and other artifacts in a shared
environment. Using industry-standard notations and techniques, organizations can leverage rich metadata and use models and diagrams to drive
understanding and promote shared outcomes in creating innovative systems, information sets, and processes to support goals and capabilities.
Install SAP EA Designer in your SAP HANA 2.0, express edition system using the xs command line tool.
1. Log in as hxeadm .
2. Create a text file, copy the following content to it, replacing the variable with your choice of a temporary administrator password for the first login, and save
it as firstTime.mtaext :
2016 SAP SE or an SAP affiliate company. All rights reserved.
_schema-version: "2.0.0"
ID: com.sap.hana.eadesigner.ext
extends: com.sap.hana.eadesigner
modules:
- name: eadesigner-backend
properties:
ADMIN_PASSWORD: <tempPwd>
Note: If you do not specify this temporary password file in your installation command, the installation will proceed normally, but you will not
be able to log into SAP EA Designer. We recommend that your temporary password should contain 8 or more characters including a mix of
numbers and uppercase and lowercase letters. Once installation is complete, you should delete this file.
3. Login to the XSA environment with the following command and enter your credentials when prompted:
xs login -a https://<hostname>:39030
4. Install the SAP EA Designer package using the following command, where firstTime.mtaext is the file containing the temporary administrator password:
5. When the installation is complete enter the following command to confirm the status of SAP EA Designer:
xs apps
The output will include all the applications of your organization and space. You should see:
eadesigner - The SAP EA Designer application
eadesigner-service - The SAP EA Designer Node application
eadesigner-backend - The SAP EA Designer Java application
eadesigner-db - The SAP EA Designer database creation application. This application will have a state of stopped when the installation is complete.
6. Note the URL for eadesigner and enter it in your web browser address bar to go to the SAP EA Designer login screen.
7. Enter the following credentials:
User Name - ADMIN
Password - Enter the temporary administrator password (< tempPwd >) you specified in firstTime.mtaext .
You will be prompted to change the password and then logged in as administrator of SAP EA Designer.
(Optional) Install SAP HANA Interactive Education (SHINE) (Server + Applications Virtual Machine Only)
To install SHINE for XSC, see the SAP HANA Interactive Education (SHINE) guide.
Installation files for SHINE for XSC are located at:
/usr/sap/HXE/home/HANA_EXPRESS_20/DATA_UNITS/HCO_HANA_SHINE
To install SHINE for XSA, see the SAP HANA Interactive Education (SHINE) for SAP HANA XS Advanced Model guide.
If you downloaded the Server + Applications Virtual Machine ( hxexsa.ova ) package, installation files for SHINE for XSA are located at:
/usr/sap/HXE/home/HANA_EXPRESS_20/DATA_UNITS/XSA_CONTENT_10
Best Practices
Deactivate the SYSTEM user
SYSTEM is the database superuser and is not intended for day-to-day activities in production systems. For better security, you can create other database users
with only the privileges that they require for their tasks (for example, user administration), then deactivate the SYSTEM user.
1. In a terminal, log in as the hxeadm user:
sudo su -l hxeadm
2. Create a new admin user with the USER ADMIN system privilege:
/usr/sap/HXE/HDB90/exe/hdbsql -i 90 -d SystemDB -u SYSTEM -p <SYSTEM-password> "CREATE USER <admin-username> PASSWORD <admin-password> NO
FORCE_FIRST_PASSWORD_CHANGE;"
/usr/sap/HXE/HDB90/exe/hdbsql -i 90 -d SystemDB -u SYSTEM -p <SYSTEM-password> "GRANT USER ADMIN TO <admin-username> WITH ADMIN OPTION;"
Backups
Make regular data backups to save your work.
For information on data backup, recovery, and log file growth, see the SAP HANA 2.0 Administration Guide.
Troubleshooting
Virtual Machine: Checking Resource Usage
Issue
You are having memory issues on your VM and want to check resource usage.
Solution
If you have HANA studio, right-click on the system and select Configuration and Monitoring > Open Administration and check the Overview and
Landscape tabs for anything in red.
If you don't have HANA Studio, run the following queries in hdbsql to view SAP HANA resource usage:
select service_name, round(effective_allocation_limit/1024/1024/1024, 1) as MemLimit, round(total_memory_used_size/1024/1024/1024,1) as
MemUsed from m_service_memory;
If the MemUsed is close to the MemLimit , you may encounter problems allocating memory.
Alternatively, you can run the Linux free command at the command line to see free resources:
free -g
The key number is in the second row (-/+ buffers/cache) in the free column. If this number is low, (e.g. 0 GB) you may have run out of memory when
Look for the Use% for the /dev/sda1 filesystem . If it is down to just a few GB, you may have run out of disk space when performing your recent operation.
Solution
Log in to your SAP HANA 2.0, express edition installation as hxeadm .
sudo su -l <sid>adm
xs apps
This operation may take 1-2 minutes to return the list of apps. You should see the following:
xs start <app>
It may take a few minutes for the system to get started. Run xs apps again to see if the app has started and that under instances the app shows 1/1 .
Issue
You are downloading packages using the Download Manager. The Status area and Progress Detail area show the error
Failed to concatenate downloaded files .
Solution
1. Check the log file for details. The log file is in the Temp directory:
Linux: /tmp/hxedm[yymmdd].log
Windows: %TEMP%\hxedm_[yymmdd].log
2. If the log indicates a simple issue such as lack of disk space or file permissions, fix the problem and download again.
3. If the problem is less obvious, do the following:
Go to the Save directory. Delete all downloaded files, including incomplete download files. Download again.
or
Change the Save directory. Download again.
Accessibility
The information contained in the SAP documentation represents SAP's current view of accessibility criteria as of the date of publication; it is in no way intended
to be a binding guideline on how to ensure accessibility of software products. SAP in particular disclaims any liability in relation to this document. This disclaimer,
however, does not apply in cases of wilful misconduct or gross negligence of SAP. Furthermore, this document does not result in any direct or indirect
contractual obligations of SAP.
Gender-Neutral Language
As far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such
as "sales person" or "working days") is used. If when referring to members of both sexes, however, the third-person singular cannot be avoided or a genderneutral noun does not exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains
comprehensible.
Internet Hyperlinks
The SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP
does not warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. SAP shall not be liable
for any damages caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. All links are
categorized for transparency (see: http://help.sap.com/disclaimer).
go.sap.com/registration/
contact.html