Hello and welcome to the SAP HANA Academy.
The topic of this video tutorial series is SAP HANA platform Installation and Update
and in this video, I will show you how to install the SAP HANA server.
Hi, I am Denys van Kempen.
In the previous videos of this series, we have discussed the product availability matrix (the PAM),
software downloads, product documentation, and important SAP Notes
which all help you prepare to setup your SUSE or Red Hat Linux properly
before proceeding to install the SAP HANA server.
Now, once you have done your home work, you will find that installing the SAP HANA server
is actually very easy.
I am connected here to a SUSE Linux server and the installation media, you may recall,
we extracted to the /tmp/hana directory.
Then, if we go down the path a bit, DATA_UNITS, HDB_SERVER, then we find the installers here.
In this video, I will use the command-line version for a one/off installation.
We will look into a scripted installation, as well, in the next video.
If you are new to the tool used to install SAP HANA software, hdblcm, the SAP HANA Lifecycle Manager,
you might want to review the video we recorded on this topic.
OK.
First, the installer will scan the path for other software components and here we get
the whole list - these are all our downloads, the full media set - the database, of course,
but also AFL, the application function library, EML AFL, the AFL for External Machine Learning,
the database client, and so on.
When you install the server, you can install all these components at the same time, should
this be the requirement.
Some components are compressed (zip files), so you can also use the installer to extract
components and then maybe import them using the HANA Application Lifecycle Management
tool, for example, to update SAPUI5.
For now, I will just install the server, the database.
Select 1 (install)
Then, we need to decide which components we want to install together with the server.
Enter a comma-separated list.
I will enter 2 (server), no other components
Enter the installation path, defaults to /hana/shared.
For this, let’s briefly return to the SAP HANA Server Installation and Update Guide.
Concepts.
System types.
Here we have an illustration of a single host system and a multiple host system.
When you install the HANA server, you can do so on a single computer, a single host,
or - if you want to scale out - on multiple computers.
Say, your servers have 256 GB each of RAM installed; then with 4 of them, you can now
address 1 TB of RAM.
This is very easy to setup.
SAP HANA is designed to scale.
Works exactly the same.
Which is why a single host installation is identical to a multiple host installation.
Some files reside on a local file system, /usr/sap, for example log and trace files
for this host, but most files will be located on the shared location, shared between all
hosts that is, /hana/shared - by default.
This is just a mount point, you could give it any name you want but, unless you have
a very good reason not to use the default, my recommendation would be to stick with defaults,
where possible, as this will make communication with your colleagues and SAP much easier.
A lot of program files (executables) on /usr/sap are, in fact, just symbolic links to /hana/shared.
The database and redo log files, of course, also reside on the shared storage locations.
Here we see this explained in a bit more detail.
Recommended File System Layout.
/hana/shared installation path, mount directory for shared files between all hosts in an SAP
HANA system.
Here is an illustration.
Left are the local files /usr/sap and to the right the shared files /hana, data, log and
shared.
OK
/hana/shared - assuming the path exists, of course.
This was covered in system preparation.
Enter the local host name, the name of the computer.
The installer will have picked this up with the uname command probably.
In most cases, this will be fine.
It could be that the hosts file contains multiple aliases for the host name and that you want
to use one of the aliases.
For example, at your company, the policy is to name all computers with the serial number
but the alias will be the datacenter location with a 2-digit number appended and that’s
the name that should be used, not the serial number.
Do you want to add hosts to the system?
For a multiple hosts installation, here you would add them.
This is the only difference between a single host installation and multiple hosts: yes
or no.
For now, I will enter no.
In the next video, we will do a yes.
Then, the SAP HANA system ID.
This is the unique identifier.
3 characters, only letters and numbers, not all combinations are allowed.
SAP or IBM will not work and there is an SAP note that spells out the rules.
You can change it afterwards but it is a bit more complex than you might think as the SID
will be used in the path, as directory, and in a number of configuration files (profiles)
and so on.
So, you might want to make sure to enter the correct one.
I will be using HDB.
The instance number together with the SID create a unique system in your landscape.
SID and instance numbers are inherited from the SAP application server, AS ABAP, Netweaver.
You could have multiple systems on a single host with the same SID and different instance
numbers.
For HANA, to my knowledge, this would be less common.
The system starts counting at 00.
For the next installation on this server, it will return 01.
However, most HANA hosts will only have a single system installed, at least for production.
The instance number is also used in the path and profile, by the way.
00 it is.
Then, enter the local host worker group.
Defaults to default.
That’s for a single-host installation.
For multiple-hosts, you could enter values here like ‘standby’, for a standby host
available for take-over in a high-availability environment.
Other examples are extended_storage_worker, when using Dynamic Tiering, or xs_worker to
define the system as a host for the XS Advanced runtime.
We will look into that in another video, as well.
Default for now.
Then we can define a system usage type.
Production, test, development or custom, the default.
Only production actually affects the behaviour of client tools, like HANA studio or cockpit,
for example.
You will get a warning when executing SQL, stuff like that.
I will stick with custom.
Then, we are prompted for the location of the data volumes, defaults to /hana/data with
the SID appended, HDB in our case.
Same for the redo log volumes.
You will also be prompted if you want to restrict memory allocation.
Should your computer have 256 GB of RAM but you have licensed HANA only for 128 GB, then
here you can define that.
It is a system parameter, so you can modify this anytime.
This was probably mostly used when HANA was only available as an appliance, by the hardware
vendor.
No Enter the certificate host name for the host.
Here, the alias is picked up from the hosts file (/etc/hosts), different from the computer
name (sid-hdb).
Most web applications will use HTTPS for secure connections.
HTTPS requires a certificate and your browser will then verify that the name on the certificate
matches the name in the URL.
If not, an error is returned, warning the user of that browser that this website is
unsafe.
You have probably seen this before, hostname mismatch.
Mosts browsers will warn you, some way or the other.
OK.
For production, you probably have to setup certificates properly anyway later on.
For training and testing, this will be less relevant.
We will get a self-signed certificate to start with and this also returns warnings in browsers.
OK Then the operating system administrator password
(adm, hdbadm in our case) and the home directory for this linux account.
Usually this would be in /home but SAP prefers to put it here.
Again, unless you have very good reason to do otherwise, best to accept the default in
the SID home directory.
Same for login shell.
SH is specified but on Linux, BASH will be used.
User ID, should be the same for distributed systems.
HDBLCM starts counting at 1000 here.
Password for the database super user SYSTEM.
The password policy here might be different then for the operating system user.
For production, of course, make sure that you are using different passwords.
SYSTEM will be created on both the system database and the HDB tenant database.
This is also something you want to change A-SAP.
Restart system after machine reboot.
Defaults to no.
You might want to set this to yes.
No is to be safe.
In case you install multiple systems on a single computer.
If they all start up at system boot there may not be enough memory and things might
get messy.
You can define different startup delays, of course, to make sure production starts first
and not your development system, but there is no friendly UI for this currently.
I have only one system, so I will set this to a yes.
Then we get our summary before execution.
As you can see, a couple more parameters have been set without asking: remote execution,
database isolation.
If you want to change this, you have to pass the value to the installer on the command
line or, more likely, use a parameter configuration file.
We will look into this in the next video.
Only the database (the server) will be installed.
Do you want to continue?
yes, I do.
First, files will be extracted (preparing package), then copied to /hana/shared (installing
package) - I will fast forward the installation a bit
- then the HDB instance will be created and
the processes started on host sid-hdb with role worker:
hdbdaemon, the watchdog hdbnameserver - for the system database
And the compile and preprocessor support processes Then the tenant database is added: hdbindexserver
And the XS classic processes: xsengine and the webdispatcher
(we did not select XS Advanced, for installation, maybe as a reminder).
Then the different XS classic applications are imported, most of this is deprecated for
the SPS 02 release, so I will not elaborate.
And the lifecycle manager is installed, this we already covered.
The host agent is configured and we are all set.
SAP HANA Database Installed There is a URL you can use to send feedback.
And the location of the log file is written as well, should you, or SAP support, need
to investigate anything.
Simple, right?
Let’s check if everything is up Substitute user for hdbadm
HDB info Yep.
The SAP Start Service has started the daemon who has started the name server and the other
processes.
In the next video, we will show you how you can add components; AFL or XSA, for example
We will also look into how you can prepare an unattended installation, using a parameter
file, so you perform the same installation multiple times and even 24/7, if need be.
That’s it.
Thanks for watching.
You can find more video tutorials on our YouTube channel.
If you would like to be informed about new video tutorials, please subscribe to our channel.
You can connect with us on LinkedIn or follow us on Twitter - as well for updates -
and we also have a page on Facebook and Google+.
If you are watching this video on YouTube, do not hesitate to leave your comments to
the video page and, if you like, give us your vote on his video.
Thank you for watching.