You want to install several SAP HANA systems and need insight to the advanced, batch-oriented installation methods that are available for installing multiple SAP HANA systems.
Installation automation is designed for those who are familiar with SAP HANA and are installing it regularly in various production environments. It refers to the installation of SAP HANA database systems using the batch mode, with a combination of a configuration file and call options passed on to the command line.
To provide flexibility, you can install the same SAP HANA database system in several ways. The differences between the installation methods are best shown by a one-to-one comparison of the same system installed with each available method. The following figure shows the specifications for an installation as an example. These parameters reflect a minimalistic approach by providing at least all mandatory parameters and their values, in order to execute an unattended installation without the need of further user interaction. For such a demand, various installation methods can be used. The follow-up examples show the use of the command line with fully qualified options, and even the batch execution of an installation with a formerly created (and maintained) parameter installation file.
Using the Command Line
The hdblcm tool on the command line can be used in the two different ways. Both methods can be used in a batch mode, which does not require any user interaction, as the following options show:
Command line options (in batch mode)
Configuration file (in batch mode)
Using the Command Line with Parameters in Batch Mode
When using the option
--batch, the parameters specified on the command line are used and the default parameters are accepted without conformation. As shown in the figure, it is even possible to provide the mandatory parameters for the passwords on the command line. However, avoid providing the password on the command line like this because the statement is stored in the history file on Linux. Instead, create a configuration file that holds all the required parameters and values, including passwords. Alternatively, there are safeguarding options to store the passwords in an explicit xml-file and start the installation in batch mode with a parameter, which reads the passwords from this file.
If you do not use the
--batch option, the SAP HANA installation is performed semi-automatically. The parameters specified on the command line are used, but the installer must still confirm the default parameter values.
Generating a Configuration File with Installation Parameters
The SAP HANA database lifecycle manager (HDBLCM) uses default values during installation, unless you decide to change them via the command line options, or via a configuration file that contains the parameters you want to change.
To generate a configuration file template using the SAP HANA platform lifecycle management tool, execute the following command:
The parameter template file lists parameters in sections like General, Server, Client, and some others. Within those sections, the corresponding parameters can be found with a short description and possible values, which is useful as a kind of value help. For some generic use cases, this function might be sufficient. Nevertheless, the parameters are described in the SAP HANA Server Installation and Update Guide.
Using a Configuration File in Batch Mode
To perform an automated installation with the SAP HANA lifecycle management hdblcm tool, you must combine the configuration file and the batch mode.
Note that until now, you had to enter passwords interactively or specify them on the command line. Batch mode is designed to automate the installation process.
Batch mode runs the installer without asking for any confirmation or parameter entry. This allows the installation to run to completion without any user interaction. It can be started from the command line with the use of a configuration file.
With the configuration file and batch mode, the SAP HANA installation is installed completely without user interaction. This is useful if you want to set up many systems with a standard setup, or if you want to redeploy a system on a weekly basis because of system copies.