Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Sap hana server installation guide

Sap hana server installation guide

  • Be the first to comment

Sap hana server installation guide

  1. 1. PUBLIC SAP HANA Platform SPS 08 Document Version: 1.0 - 2014-05-28 SAP HANA Server Installation and Update Guide
  2. 2. Table of Contents 1 SAP HANA Installation Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 1.1 SAP HANA Software Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 1.2 Software Download. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 2 Before Installing an SAP HANA System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 2.1 SAP HANA System Concepts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 2.2 SAP HANA System Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 2.2.1 Single-Host System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 2.2.2 Multiple-Host (Distributed) System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11 2.3 Hardware and Software Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 2.3.1 Recommended File System Layout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14 3 Installing an SAP HANA System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 3.1 Overview of the LCM Interaction Modes and Parameter Specification Methods. . . . . . . . . . . . . . . . .18 3.2 Installation Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 3.2.1 Mandatory Installation Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 3.3 Interactive Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25 3.3.1 Installing with the Graphical Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 3.3.2 Installing Interactively from the Command Line. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 4 Advanced Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29 4.1 Automating SAP HANA System Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 4.1.1 Automation Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 4.1.2 Automating with the Configuration File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36 4.2 Multiple-Host System Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 4.2.1 Multiple-Host System Concepts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43 4.2.2 Creating a Multiple-Host System During Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 5 Updating the SAP HANA System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 5.1 Updating an SAP HANA System from a Local Host. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 5.1.1 Preparing for Update in the SAP HANA Studio. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49 5.1.2 Prepare for Update Manually. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 5.1.3 Update an SAP HANA System from a Local Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 5.2 Updating an SAP HANA System from a Remote Host. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54 5.2.1 Perform an Automated Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 5.3 Updating SAP HANA System Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 5.3.1 Update SAP HANA System Components from a Local Host. . . . . . . . . . . . . . . . . . . . . . . 58 5.3.2 Update SAP HANA System Components from a Remote Host. . . . . . . . . . . . . . . . . . . . . 60 6 Parameter Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 6.1 action. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 2 P U B L I C © 2014 SAP AG or an SAP affiliate company. All rights reserved. SAP HANA Server Installation and Update Guide Table of Contents
  3. 3. 6.2 addhosts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 6.3 autostart. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 6.4 batch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 6.5 certificates_hostmap. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 6.6 checkmnt. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 6.7 client_path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68 6.8 component_dirs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 6.9 component_medium. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 6.10 component_root. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 6.11 components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 6.12 configfile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 6.13 copy_repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 6.14 datapath. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 6.15 dump_configfile_template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 6.16 groupid. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 6.17 help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 6.18 home. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72 6.19 host_agent_package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72 6.20 hostname. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 6.21 install_hostagent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 6.22 install_ssh_key. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 6.23 internal_network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 6.24 list_systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74 6.25 logpath. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 6.26 max_mem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 6.27 number. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 6.28 print_timezones. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 6.29 read_password_from_stdin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 6.30 repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 6.31 restrict_max_mem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 6.32 root_user. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78 6.33 sapmnt. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 6.34 scope. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 6.35 shell. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 6.36 sid. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79 6.37 storage_cfg. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 6.38 studio_path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 6.39 studio_repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 6.40 system_usage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 6.41 system_user. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 6.42 timezone. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 SAP HANA Server Installation and Update Guide Table of Contents P U B L I C © 2014 SAP AG or an SAP affiliate company. All rights reserved. 3
  4. 4. 6.43 userid. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 6.44 version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 6.45 vm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 7 Tutorials. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 8 Managing the SAP HANA System After Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 8.1 Starting and Stopping the SAP HANA System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90 8.2 Displaying the Process List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 8.3 Creating a Database User for Update and Rename. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92 8.4 Enabling Automatic Start of the SAP HANA Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 8.5 Enable Data Volume Encryption. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94 8.6 Uninstall the SAP HANA System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 9 Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 10 Appendix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101 10.1 Configuration File Template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 10.2 Important SAP Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 11 Important Disclaimers on Legal Aspects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107 4 P U B L I C © 2014 SAP AG or an SAP affiliate company. All rights reserved. SAP HANA Server Installation and Update Guide Table of Contents
  5. 5. 1 SAP HANA Installation Overview This SAP HANA installation guide describes how to install an SAP HANA system with the SAP HANA lifecycle management tool hdblcm(gui), or update an SAP HANA system using hdblcm(gui) or the lifecycle manager. The SAP HANA hdblcm tool is used to install either individual or multiple SAP HANA components in combination with the server. Compared to previous SAP HANA installers, the SAP HANA hdblcm tool provides an efficient and optimized installation path, allowing users to customize their SAP HANA installation by selecting which components should be installed and updated. It is also now possible to perform installation in interactive graphical or interactive command line interfaces, as well as configure the SAP HANA installation to be automated, using command line, the configuration file, and batch mode. It is worth noting, that the SAP HANA component installation concept has changed significantly with the fast- paced development of SAP HANA itself. In the early releases, the SAP HANA components had to be installed individually, which proved to be a time-consuming task. More recently, the SAP HANA unified installer was developed to streamline the installation process by installing all required components from one call to the installer. As of SPS 08, the unified installer is no longer shipped with SAP HANA. With SAP HANA SPS 07, the SAP HANA hdblcm tool was introduced to offer the efficiency of installing all components at one time, while providing further flexibility to customize and automate the installation. The components can now be installed, upgraded, or uninstalled from one tool, in both command-line or graphical interface. As of SAP HANA SPS 08, it is possible to also perform post-installation configurations tasks, such as renaming the system, adding or removing hosts, and reconfiguring the system, using hdblcm(gui). For more information, see the SAP HANA Administration Guide. Before starting the installation of SAP HANA, make sure that you have reviewed the SAP HANA Master Guide. Related Information SAP HANA Master Guide SAP HANA Administration Guide 1.1 SAP HANA Software Components The SAP HANA Platform Edition is composed of the following components: ● SAP HANA database ● SAP HANA client ● SAP HANA client for Microsoft Excel ● SAP HANA studio (including SAP HANA STUDIO RSA PLUGIN) ● SAPUI5 Tools IDE PLUGIN ● SAP Host Agent ● SAP Solution Manager Diagnostics Agent SAP HANA Server Installation and Update Guide SAP HANA Installation Overview P U B L I C © 2014 SAP AG or an SAP affiliate company. All rights reserved. 5
  6. 6. ● SAP HANA information composer ● SAP HANA AFL ● SAP HANA LCApps ● SAP HANA lifecycle manager ● SAP HANA INA Toolkit HTML ● SAP HANA INA Fileloader ● SAP HANA EPM Service ● SAP HANA SHINE cntent ● SAP HANA smart data access ● SAP HANA HW Configuration Check Tool The SAP HANA Platform Edition is bundled together with other products into editions as license bundles for special purposes. This is a subset of the available editions: ● SAP HANA Enterprise Edition (including components for data replication and acquisition) ● SAP HANA Real-time-data edition (includes SAP Replication Server, SAP HANA edition) ● SAP HANA Database edition for BW ● SAP HANA Limited edition for Apps / Accelerators ● SAP HANA EDGE edition Note SAP HANA information composer is a Web-based environment that allows business users to upload data to the SAP HANA database and to manipulate that data by creating information views. The SAP HANA information composer is installed separately from the SAP HANA system. 1.2 Software Download In the SAP Software Download Center, you have access to the installation media and components for SAP HANA. You can find the installation media and components for SAP HANA in the following locations: ● Installation media for an SAP HANA SPS: SAP Software Download Center Installations and Upgrades A-Z Index Installations and Upgrades - H SAP In-Memory (SAP HANA) HANA Platform Edition SAP HANA PLATFORM EDITION SAP HANA PLATFORM EDIT. 1.0 Installation ● Support Packages and Patches for SAP HANA: SAP Software Download Center Support Packages and Patches A-Z Index Support Packages and Patches - H SAP HANA PLATFORM EDITION SAP HANA PLATFORM EDIT. 1.0 The responsibility for acquiring and installing SAP HANA depends on the chosen deployment model: ● If a customer chooses the SAP HANA tailored data center integration, the components of SAP HANA have to be installed on validated hardware by a certified administrator. ● If a customer chooses an SAP HANA appliance, the components of SAP HANA can only be installed by certified hardware partners on validated hardware running a specific operating system. Any other system 6 P U B L I C © 2014 SAP AG or an SAP affiliate company. All rights reserved. SAP HANA Server Installation and Update Guide SAP HANA Installation Overview
  7. 7. or content developed with systems of this type is not supported by SAP. For more information, see the information page of the product version. Support Package Stacks (SPS) can be downloaded and applied to appliances in accordance with agreements with the respective hardware partner. Related Information SAP Software Download Center SAP HANA Server Installation and Update Guide SAP HANA Installation Overview P U B L I C © 2014 SAP AG or an SAP affiliate company. All rights reserved. 7
  8. 8. 2 Before Installing an SAP HANA System Before installing an SAP HANA system, it is important to understand the basic system concepts in order to optimize the installation process and avoid unnecessary reconfiguration. Note The components of SAP HANA can only be installed by certified hardware partners, or any person holding E_HANAINS131 certification, on validated hardware running an approved operating system. 2.1 SAP HANA System Concepts An SAP HANA system is composed of three main components: the host, the system, and the instance. In everyday language, these terms may have different meanings, so it is important to clearly understand what these terms mean when it comes to an SAP HANA installation. Host A host is the operating environment in which the SAP HANA database runs. The host provides all the resources and services (CPU, memory, network, and operating system) that the SAP HANA database requires. The host provides links to the installation directory, data directory, and log directory, or the storage itself. The storage for an installation does not have to be on the host. For multiple-host systems, a shared storage or a storage that is accessible on-demand from all hosts is required. For more information about multiple-host system concepts, see Related Information. Instance An SAP HANA instance is the set of SAP HANA system components that are installed on one host. A system can be distributed as several instances among several hosts, but each instance in a multiple-host system must have the same instance number. System 8 P U B L I C © 2014 SAP AG or an SAP affiliate company. All rights reserved. SAP HANA Server Installation and Update Guide Before Installing an SAP HANA System
  9. 9. A system is one or more instances with the same number. The term "system" is interchangeable with the term "SAP HANA database". If a system has more than one instance, they must be dispersed over several hosts as a multiple-host system. Related Information Multiple-Host System Concepts [page 43] It is important to review multiple-host system concepts like host grouping and storage options before installing a multiple-host system. 2.2 SAP HANA System Types An SAP HANA system can be configured as one of the following types: ● Single-host system - One SAP HANA instance on one host. ● Multiple-host (distributed) system - Multiple SAP HANA instances distributed over multiple hosts, with one instance per host. 2.2.1 Single-Host System If there is only one host in a system, it is called a single-host system. The following graphic shows the file system for a single-host installation: SAP HANA Server Installation and Update Guide Before Installing an SAP HANA System P U B L I C © 2014 SAP AG or an SAP affiliate company. All rights reserved. 9
  10. 10. A single-host system is the simplest system installation type. It is possible to run an SAP HANA system entirely on one host and then scale the system up as needed. Both the hdblcm and hdblcmgui SAP HANA lifecycle management tools can be used to install an SAP HANA single-host system in one of the installer modes, and with a combination of parameter specification methods. Interaction Modes Installation can be performed in one of the following modes: Interactive Mode (Default) Available for hdblcm or hdblcmgui. The person installing the system must enter parameter specifications iteratively until the installation process finishes. For more details, see the Interactive Installation information. Batch Mode Available for hdblcm. The installation accepts the default values for all unspecified parameters, and runs to completion without any additional input required. Batch mode must be explicitly specified when the hdblcm installation tool is called. For more details, see the Enabling Batch Mode information. Parameter Specification Methods Installation parameter values can be entered in one or more of the following methods: Interactively (Default) Using either command line interaction (hdblcm) or graphical interaction (hdblcmgui), most parameters are requested interactively. Parameters that are not requested accept the default value. For more details about which parameters are requested interactively, see the Changeable Default Values information. Command Line Options Installation parameters are given in their accepted syntax as a space delimited list after the program name (hdblcm or hdblcmgui). The specified parameters replace the defaults. If any mandatory parameters are left out, they are requested interactively (unless batch mode is specified). All parameters can be entered from the command line. For more details about the accepted parameter syntax, see the Installation Parameters information. Configuration File The configuration file is a plain text file, of parameters set to their default values, that can be generated, edited, and saved to be called during installation with either the hdblcm or hdblcmgui tool. If any mandatory parameters are left out, they are requested interactively (unless batch mode is specified). All parameters can be entered in the configuration file. The specified parameters replace the defaults, but if you specify the same parameter as a command line option and in the configuration file, the command line version is used by the installer. For more details about the using the configuration file, see the Automating with the Configuration File information. Related Information Interactive Installation [page 25] Interactive mode is an installation mode, which requires the person installing the SAP HANA system to enter parameter specifications as they are requested by the installer. Enabling Batch Mode [page 40] Batch mode installation can be started from the command line alone or in combination with the configuration file. It runs all installation tasks without prompting for additional confirmation or input. Batch mode is designed to automate the installation process. 10 P U B L I C © 2014 SAP AG or an SAP affiliate company. All rights reserved. SAP HANA Server Installation and Update Guide Before Installing an SAP HANA System
  11. 11. Changeable Default Values [page 20] The installer uses the following default values unless you change them during installation. Installation Parameters [page 19] Installation parameters are a fundamental aspect of the SAP HANA lifecycle management tools hdblcm and hdblcmgui, and provide the opportunity to optimize and customize the system during installation. Automating with the Configuration File [page 36] The configuration file is a text document where all available installation parameters can be specified. 2.2.2 Multiple-Host (Distributed) System If there are multiple hosts in a system, it is called a multiple-host (or distributed) system. The following graphic shows the file system for a multiple-host system with three hosts: A multiple-host system is a system with more than one host, which can be configured as active worker hosts or idle standby hosts. Both the hdblcm and hdblcmgui SAP HANA lifecycle management tools can be used to install an SAP HANA multiple-host system in one of the installer modes, and with a combination of parameter specification methods. To add hosts to an existing system, use the SAP HANA lifecycle manager (HLM) tool. For more information about installing a multiple-host system, see the Related Information. Interaction Modes Installation can be performed in one of the following modes: Interactive Mode (Default) Available for hdblcm or hdblcmgui. The person installing the system must enter parameter specifications iteratively until the installation process finishes. For more information about interactive installation, see Related Information. Batch Mode Available for hdblcm. The installation accepts the default values for all unspecified parameters, and runs to completion without any additional input required. Batch mode SAP HANA Server Installation and Update Guide Before Installing an SAP HANA System P U B L I C © 2014 SAP AG or an SAP affiliate company. All rights reserved. 11
  12. 12. must be explicitly specified when the hdblcm installation tool is called. For more information about batch mode, see Related Information. Parameter Specification Methods Installation parameter values can be entered in one or more of the following methods: Interactively (Default) Using either command line interaction (hdblcm) or graphical interaction (hdblcmgui), most parameters are requested interactively. Parameters that are not requested accept the default value. To install a multiple-host system interactively with the hdblcm tool, both the action and the addhosts parameters must be specified from the command line. The rest of the installation can follow interactively. For more information about which parameters are requested interactively and have changeable default values, see Related Information. Command Line Options Installation parameters are given in their accepted syntax as a space delimited list after the program name (hdblcm or hdblcmgui). The specified parameters replace the defaults. If any mandatory parameters are left out, they are requested interactively (unless batch mode is specified). All parameters can be entered from the command line. To install a multiple-host system, the action and addhosts parameters must be specified in combination with hdblcm. For more information about the accepted parameter syntax, see Related Information. Configuration File The configuration file is a plain text file, of parameters set to their default values, that can be generated, edited, and saved to be called during installation with either the hdblcm or hdblcmgui tool. If any mandatory parameters are left out, they are requested interactively (unless batch mode is specified). All parameters can be entered in the configuration file. The specified parameters replace the defaults, but if you specify the same parameter as a command line option and in the configuration file, the command line version is used by the installer. For more information about the using the configuration file, see Related Information. Related Information Multiple-Host System Installation [page 42] It is possible to configure additional hosts for an SAP HANA system both during and after installation. However, there are some slight differences with the tools used depending on when you decide to add a host to the system. Interactive Installation [page 25] Interactive mode is an installation mode, which requires the person installing the SAP HANA system to enter parameter specifications as they are requested by the installer. Enabling Batch Mode [page 40] Batch mode installation can be started from the command line alone or in combination with the configuration file. It runs all installation tasks without prompting for additional confirmation or input. Batch mode is designed to automate the installation process. Changeable Default Values [page 20] 12 P U B L I C © 2014 SAP AG or an SAP affiliate company. All rights reserved. SAP HANA Server Installation and Update Guide Before Installing an SAP HANA System
  13. 13. The installer uses the following default values unless you change them during installation. Installation Parameters [page 19] Installation parameters are a fundamental aspect of the SAP HANA lifecycle management tools hdblcm and hdblcmgui, and provide the opportunity to optimize and customize the system during installation. Automating with the Configuration File [page 36] The configuration file is a text document where all available installation parameters can be specified. 2.3 Hardware and Software Requirements For SAP HANA several hardware and software requirements need to be fulfilled. Note You can find a complete list of all SAP HANA components and the respective SAP HANA hardware and software requirements in the Product Availability Matrix (PAM) on the SAP Service Marketplace and in the SAP Community Network. Software Requirements Note Only the software installed by certified hardware partners, or any person holding the certification, is recommended for use on the SAP HANA system. Do not install additional software on the SAP HANA system. The person performing the SAP HANA installation has passed the certification exam. Check the SAP Education resources for information about the SAP HANA certication exams. Operating System for SAP HANA For the SAP HANA system the following operating systems are available: ● SUSE Linux Enterprise Server (SLES) 11 ● Red Hat Enterprise Linux (RHEL) 6.5 Network Time Protocol (NTP) We strongly recommend that you set up an NTP server for the SAP HANA system landscape. Note If an NTP sever is not available this means that, for example, trace files from distributed hosts cannot be displayed in the correct chronological order. Hardware Requirements During the update and the installation of the SAP HANA database (from the SAP HANA installation manager), a hardware check is performed in order to ensure that problems do not arise due to wrong or unsupported hardware configurations in combination with the SAP HANA platform. The check is a script that is automatically called by the SAP HANA installer and aborts the installation process if it doesn't succeed. SAP HANA Server Installation and Update Guide Before Installing an SAP HANA System P U B L I C © 2014 SAP AG or an SAP affiliate company. All rights reserved. 13
  14. 14. It is not possible to disable the check because SAP HANA is highly optimized for specific hardware configurations which have been designed and tested together with our hardware partners. Outside of these validated configurations, SAP HANA performance and stability cannot be guaranteed. Before installing or updating SAP HANA, consult the SAP HANA Product Availability Matrix (search for HANA) to verify if the hardware you are planning to use is supported by SAP HANA. If the hardware is not supported, the hardware check returns the results "not supported" in the system manufacturer, system product name, CPU model, OS, memory total, or core count check results. The check is automatically delivered with the SAP HANA software and can be executed as a standalone check anytime. Execute the check by going to the /usr/sap/<SID>/HDB<instanceNumber>/exe/ python_support directory and running the Python script named HanaHwCheck.py. Due to some dmidecode commands in the check it has to be executed as root. Hardware Requirements for SAP HANA Network Connection We recommend dedicated server network communication of 10 GBit/s between the SAP HANA landscape and the source system for efficient data replication. Related Information SAP Note 1944799 - SAP HANA Guidelines for SLES Operating System SAP Note 2009879 - SAP HANA Guidelines for RedHat Enterprise Linux (RHEL) SAP Traning & Education Product Availability Matrix (PAM) SAP Community Network - SAP Certified Appliance Hardware for SAP HANA 2.3.1 Recommended File System Layout The SAP HANA lifecycle management tool hdblcm requires certain file systems in order to successfully install an SAP HANA system. The file systems can be defined manually before installation and then specified during installation, or the default file systems can be used. It is important that the file systems listed below are available and have the recommended disk space before starting the hdblcm program. Table 1: Default File Systems File System Default Path Recommendations Root / The recommended disk space is at least 10 GB. Installation path (sapmnt) /hana/shared/ The installation path (mount directory) requires disk space equal to the default system RAM. 14 P U B L I C © 2014 SAP AG or an SAP affiliate company. All rights reserved. SAP HANA Server Installation and Update Guide Before Installing an SAP HANA System
  15. 15. File System Default Path Recommendations The mount directory is used for shared files between all hosts in an SAP HANA system. This directory needs to be accessible to each of the servers in the SAP HANA cluster. Sub-directories: ● /hana/shared/<SID> - Contains executable kernel programs (exe), globally shared data (global), instance profiles (pro­ file), HDB executables (HDB<number>), and uninstallation script and instruntime (hdblcm) ● /hana/shared/<SID>/hdbclient - The SAP HANA client in­ stallation path. ● /hana/shared/<SID>/hdbstudio - The SAP HANA studio installation path. ● /hana/shared/<SID>/hdbstudio_update - The studio re­ pository installation path. The studio repository is used to up­ date the local SAP HANA studio installation. ● /hana/shared/<SID>/HLM - The SAP HANA lifecycle man­ ager can be used to update the components of the SAP HANA installation. System instance /usr/sap The system instance directory requires at least 50 GB disk space. This is the path to the local SAP system instance directories. Sub-directories: ● /usr/sap/hostctrl - The SAP host agent directory. ● /usr/sap/<SID> - Contains system executables (SYS) and the home directory (home) of the <sid>adm user. Data volume /hana/data/ <SID> The data path requires disk space equivalent at least three times the size of the system RAM. The default path to the data directory depends on the system ID of the SAP HANA host. Log volume /hana/log/ <SID> The log path requires disk space at least equivalent to the default system RAM. The default path to the log directory depends on the system ID of the SAP HANA host. It is strongly recommended to use the SAP HANA file system layout shown in the figure below: SAP HANA Server Installation and Update Guide Before Installing an SAP HANA System P U B L I C © 2014 SAP AG or an SAP affiliate company. All rights reserved. 15
  16. 16. Note An SAP HANA system in a production environment must not share any infrastructure with another SAP HANA system. Hosts running more than one SAP HANA system (sometimes referred to as multiple-SID installations) can only be used for non-production purposes such as development, quality assurance, or testing. For production systems with high availability, it is possible to share some temporarily unused resources from the standby hosts. As soon as the standby resources are needed, they must become exclusively available for the production system and no longer shared. For more details, refer to the high availability information in the SAP HANA Administration Guide. The file systems /hana/data/<SID> and /hana/log/<SID> may use shared file systems like NFS, or block storage using the SAP HANA storage connector API with non-shared file systems. For more details, Related Information. The installation path (/hana/shared) is visible on all hosts. By default, the installation path is also used for backup. However, backup directories should be manually configured, and must belong to a shared file system. For more details, refer to the backup information in the SAP HANA Administration Guide. 16 P U B L I C © 2014 SAP AG or an SAP affiliate company. All rights reserved. SAP HANA Server Installation and Update Guide Before Installing an SAP HANA System
  17. 17. Related Information SAP HANA Administration Guide Multiple-Host System Concepts [page 43] It is important to review multiple-host system concepts like host grouping and storage options before installing a multiple-host system. SAP HANA Server Installation and Update Guide Before Installing an SAP HANA System P U B L I C © 2014 SAP AG or an SAP affiliate company. All rights reserved. 17
  18. 18. 3 Installing an SAP HANA System The SAP HANA lifecycle management tools install or update the underlying components of the SAP HANA platform. An SAP HANA system can be installed or updated from the command line interface (hdblcm) or from the graphical user interface (hdblcmgui). Using the SAP HANA hdblcm and hdblcmgui tools, SAP HANA components can by installed, updated, or uninstalled independently of each other. It is possible to perform installation and update tasks in interactive mode or batch mode. 3.1 Overview of the LCM Interaction Modes and Parameter Specification Methods The SAP HANA lifecycle management toolset includes the installation, update, and configuration tool hdblcm(gui) as well as the underlying LCM tools. To interact with the SAP HANA lifecycle management tools, use one interaction mode with a combination of parameter specification methods. Interaction Modes Installation, update, and configuration tasks can be performed in one of the following interaction modes: Interactive Mode (Default) Available for graphical interface and command line interface tools. The person performing system installation, update, or configuration tasks must enter or confirm parameter specifications iteratively until the process finishes. For more information about interactive mode, see Related Information. Batch Mode Available for command line interface tools only. The SAP HANA lifecycle management command line tool accepts the default values for all unspecified parameters, and runs to completion without any additional input required. Batch mode must be explicitly specified when the command line tool is called. For more information about batch mode, see Related Information. Parameter Specification Methods SAP HANA lifecycle management parameter values can be entered in one or more of the following methods: Interactively (Default) Using either command line interface or graphical interface, most parameters are requested interactively. Default parameter values are proposed in brackets and can be changed or confirmed. Parameters that are not requested (or specified via another method) accept the default value. Command Line Options Parameters are given in their accepted syntax as a space delimited list after the program name (for example, hdblcm or hdblcmgui). The specified parameters replace the defaults. If any mandatory parameters are excluded, they are requested interactively (unless batch mode is specified). All parameters can be entered from the command line. For more details about the accepted parameter syntax, see the inline help output (­­help) for the individual SAP HANA lifecycle management tool. 18 P U B L I C © 2014 SAP AG or an SAP affiliate company. All rights reserved. SAP HANA Server Installation and Update Guide Installing an SAP HANA System
  19. 19. Configuration File The configuration file is a plain text file, for which a template of parameter key-value pairs can be generated, edited, and saved to be called in combination with the program call. If any mandatory parameters are not specified, they are requested interactively (unless batch mode is used). All parameters can be entered in the configuration file. For more information about the configuration file, see Related Information. Note If parameters are specified in the command line, they override the corresponding parameters in the configuration file. Parameters in the configuration file override default settings. Order of parameter precedence: Command Line > Configuration File > Default Related Information Interactive Installation [page 25] Interactive mode is an installation mode, which requires the person installing the SAP HANA system to enter parameter specifications as they are requested by the installer. Enabling Batch Mode [page 40] Batch mode installation can be started from the command line alone or in combination with the configuration file. It runs all installation tasks without prompting for additional confirmation or input. Batch mode is designed to automate the installation process. Automating with the Configuration File [page 36] The configuration file is a text document where all available installation parameters can be specified. SAP HANA Server Installation and Update Guide 3.2 Installation Parameters Installation parameters are a fundamental aspect of the SAP HANA lifecycle management tools hdblcm and hdblcmgui, and provide the opportunity to optimize and customize the system during installation. Installation parameters are used for all methods of parameter specification - interactively, as command line options, or with the configuration file. The following information is relevant for either installation mode (interactive mode or batch mode). SAP HANA Server Installation and Update Guide Installing an SAP HANA System P U B L I C © 2014 SAP AG or an SAP affiliate company. All rights reserved. 19
  20. 20. 3.2.1 Mandatory Installation Values The only mandatory parameter without a default value is the SAP system ID (SID, sid), which must be specified. However, it is also recommended to define an instance number (number), since these two parameters are meaningful to the identity of the system. If the installation is run in batch mode from the installation medium, the minimum required parameters are the SID and the passwords (specified in XML syntax and streamed in, or specified in the configuration file). In the case that only the SID and passwords are entered as parameters, the other parameters automatically take their default value. In batch mode, if one of the mandatory parameters, without a default, is not specified, the installation fails with an error. If an installation is not run in batch mode, but in interactive mode (default) instead, the missing mandatory parameters are requested in the console. When building a multiple-host system, the action and addhosts parameters are mandatory command-line specifications for the hdblcm installer. 3.2.1.1 Changeable Default Values The installer uses the following default values unless you change them during installation. Some default values are based on the predefined values on the current host. In a multiple-host system, it is recommended to manually check the mandatory values on each hosts before installation. Table 2: Changeable Parameter Defaults Parameter System Default Value CLI Inter­ active Mode GUI action install (except for multiple-host system installation, for which action must be specified) autostart 0 (off) certificates_host­ map <current host> client_path ${sapmnt}/${SID}/hdbclient components client,hlm,server,studio (dependent on the installer finding installation sour­ ces for the components) copy_repository /hana/shared/${SID}/hdbstudio_update datapath /hana/data/${SID} 20 P U B L I C © 2014 SAP AG or an SAP affiliate company. All rights reserved. SAP HANA Server Installation and Update Guide Installing an SAP HANA System
  21. 21. Parameter System Default Value CLI Inter­ active Mode GUI groupid 79 home /usr/sap/${SID}/home hostname <current host> install_hostagent 1 (on) logpath /hana/log/${SID} number <next successive un-used instance number on the host> root_user root sapmnt /hana/shared shell /bin/sh studio_path ${sapmnt}/${SID}/hdbstudio studio_repository 1 (on) system_usage custom timezone UTC userid <next successive un-used user ID on the host> vm <Java runtime found in environment variable PATH or JAVA_HOME> Note The default paths written in the form ${<parameter>} indicate that substitution of the parameter occurs in the configuration file and in batch mode. Substitution also occurs in interactive mode in order to create a suggested path. The advantage of substitution is that the SAP system ID (sid) and the installation path (sapmnt, which is /hana/shared, by default) only need to be specified once, and are then substituted in to the other parameter values. This ensures that the system has unique file system paths if multiple systems are installed on the same host. However, if it is preferred to deviate from the default paths, it is necessary to pay attention to the settings, especially in the configuration file, and when installing in batch mode. SAP HANA Server Installation and Update Guide Installing an SAP HANA System P U B L I C © 2014 SAP AG or an SAP affiliate company. All rights reserved. 21
  22. 22. Related Information action [page 64] Specifies the action of hdblcm to be either installation or update. autostart [page 65] Restarts instance after machine reboot. certificates_hostmap [page 66] Specifies the hostname used for generation of self-signed SSL certificates for the SAP host agent. This certificate is used by the SAP HANA lifecycle manager (HLM). client_path [page 68] Specifies the installation path for the client. components [page 69] Specifies the components to be installed in combination with the server: studio, client, HLM, AFL, LCAPPS. It is also possible to specify all components, or to specify a combination of components as a comma- separated list. The server is always installed, even if it is not explicitly specified. copy_repository [page 70] Specifies the target path to which the SAP HANA studio repository should be copied. datapath [page 70] Specifies the path to the data directory of the SAP HANA system. groupid [page 71] Specifies the SAP system (sapsys) group ID. This parameter is relevant only if a sapsys group does not already exist on the host. If a sapsys group already exists, passing the groupid parameter does not alter the existing group. home [page 72] Specifies the home directory of the system administrator. This parameter is relevant only if the operating system administrator (<sid>adm) does not exist prior to installation. hostname [page 72] Specifies the host name of the machine. install_hostagent [page 73] Enables the installation or update of the SAP host agent. logpath [page 74] Specifies the path to the log directory of the SAP HANA system. number [page 75] Specifies the instance number of the SAP HANA system. root_user [page 78] Specifies the root user name. sapmnt [page 78] Specifies the path to the SAP mount directory, which can be used as a shared directory between multiple hosts. shell [page 79] Specifies a system administrator login shell. This parameter is relevant only if the operating system administrator (<sid>adm) does not exist prior to installation. studio_path [page 80] 22 P U B L I C © 2014 SAP AG or an SAP affiliate company. All rights reserved. SAP HANA Server Installation and Update Guide Installing an SAP HANA System
  23. 23. Specifies the installation path for the SAP HANA studio. studio_repository [page 81] Enables the copying of the SAP HANA studio repository. When enabled (default), the SAP HANA studio repository is copied to the location defined by copy_repository from the location defined by repository. timezone [page 82] Specifies the timezone for the system administrator. This parameter is relevant only if the operating system administrator (<sid>adm) does not exist prior to installation. userid [page 82] Specifies the user ID of the system administrator. This parameter is relevant only if the operating system administrator (<sid>adm) does not exist prior to installation. vm [page 83] Specifies the path of the Java runtime file. This parameter is only relevant if the SAP HANA studio is selected for installation or update. 3.2.1.2 Users Created During Installation The following users are automatically created during the installation: <sid>adm, sapadm, and SYSTEM. User Description <sid>adm The operating system administrator. ● The user <sid>adm is the operating system user required for administrative tasks such as starting and stopping the system. ● The user ID of the <sid>adm user is defined during the system installation. The user ID and group ID of this operating system user must be unique and identical on each host of a multiple-host system. ● The password of the <sid>adm user is set during installation with the password parameter. sapadm The SAP host agent administrator. ● If there is no SAP host agent available on the installation host, it is created during the installation along with the user sapadm. ● If the SAP host agent is already available on the installation host, it is not modi­ fied by the installer. The sapadm user and password are also not modified. ● The password of the sapadm user is set during installation with the sa­ padm_password parameter. SYSTEM The database superuser. ● Initially, the SYSTEM user has all system permissions. Additional permissions can be granted and revoked again, however the initial permissions can never be re­ voked. ● The password of the SYSTEM user is set during installation with the sys­ tem_user_password parameter. SAP HANA Server Installation and Update Guide Installing an SAP HANA System P U B L I C © 2014 SAP AG or an SAP affiliate company. All rights reserved. 23
  24. 24. 3.2.1.3 Specifying Passwords Passwords are a mandatory parameter for installing an SAP HANA system. There are three methods for configuring passwords. Interactive Mode Interactive installation is available for both graphical interface (hdblcmgui) and command line (hdblcm) tools. Passwords are entered manually one-by-one as they are requested by the installer. This method is preferred for quick, individual system installations. Command Line Configuring passwords in the command line is a two-step process. First, a simple text file with passwords in XML syntax should be created and saved in the home directory of the root user. Then the file can be called using standard input and the read_password_from_stdin parameter in the command line with batch mode. Parameters specified in the command line override parameters specified in the configuration file. Since this method is the most powerful and flexible method, it is often the preferred method for installing multiple SAP HANA systems at one time. Example The following is an example of the password file in XML syntax: Passwords.xml <?xml version="1.0" encoding="UTF-8"?> <Passwords> <password>Adm1234</password> <sapadm_password>Agent1234</sapadm_password> <system_user_password>Sys1234</system_user_password> <root_password>Root1234</root_password> </Passwords> Now, the password file (stored in the root user's home directory) is called from the command line using standard input, the read_password_from_stdin=xml parameter, and batch mode: cat ~/Passwords.xml | ./hdblcm ­­sid=DB1 ­­number=42 ­­ read_password_from_stdin=xml ­b Configuration File It is possible to specify passwords in the configuration file. A configuration file template is created with all the parameters set to their default values. The configuration file is edited to the preferred parameter values, then it is saved, and the values are read by the installer during installation. This method is preferred for a one-step 24 P U B L I C © 2014 SAP AG or an SAP affiliate company. All rights reserved. SAP HANA Server Installation and Update Guide Installing an SAP HANA System
  25. 25. installation that can be re-created several times. If passwords are specified in the configuration file, the configuration file should be stored in the home directory of the root user, for security reasons. Example The following is an example of the configuration file, with configured password parameters: configfile1.cfg # Root User Password root_password=Root1234 ... # SAP Host Agent (sapadm) Password sapadm_password=Agent1234 ... # System Administrator Password password=Adm1234 .... # Database User (SYSTEM) Password system_user_password=Sys1234 Now, the configuration file (stored in the root user's home directory) is called from the command line using the configfile parameter: ./hdblcm ­­sid=DB1 ­­configfile=~/configfile1.cfg 3.3 Interactive Installation Interactive mode is an installation mode, which requires the person installing the SAP HANA system to enter parameter specifications as they are requested by the installer. An SAP HANA system can be installed interactively: ● With command line options, by running the installation tool hdblcm. ● With the graphical installation tool, hdblcmgui, by selecting installation options from a wizard. 3.3.1 Installing with the Graphical Interface It is now possible to install an SAP HANA system from a graphical interface, by running the SAP HANA lifecycle management tool hdblcmgui. Prerequisites ● You are logged in as root user. ● If the SAP HANA studio is selected for installation, the Java Runtime Environment (JRE) is configured as follows: SAP HANA Server Installation and Update Guide Installing an SAP HANA System P U B L I C © 2014 SAP AG or an SAP affiliate company. All rights reserved. 25
  26. 26. ○ The JRE is accessible either via the PATH or JAVA_HOME variable. ○ The JRE is up-to-date (version 1.6 or higher). Verify by calling: java ­version Procedure 1. Change to the following directory on the installation medium: <installation medium>/DATA_UNITS/HDB_LCM_LINUX_X86_64 2. Start the installer: ./hdblcmgui 3. The following parameters can be defined: ○ Software directory The software component directories are detected. Component locations can be added or changed. ○ Action of installation or update ○ Components to be installed or updated ○ Authorization data (passwords) ○ Installation parameters: System type: Single-host system or multiple-host system Installation path (sapmnt) SAP system ID (SID) Instance number Location of data and log volumes Restricted memory allocation User ID User group ID System administrator login shell System administrator home directory 26 P U B L I C © 2014 SAP AG or an SAP affiliate company. All rights reserved. SAP HANA Server Installation and Update Guide Installing an SAP HANA System
  27. 27. Results The installation progress is displayed. The SAP HANA system is now up and running. 3.3.2 Installing Interactively from the Command Line An SAP HANA system can be installed interactively from the command line. When the SAP HANA lifecycle management tool hdblcm tool is called, mandatory parameters are requested by the installer. Prerequisites ● You are logged in as root user. ● If the SAP HANA studio is selected for installation, the Java Runtime Environment (JRE) is configured as follows: SAP HANA Server Installation and Update Guide Installing an SAP HANA System P U B L I C © 2014 SAP AG or an SAP affiliate company. All rights reserved. 27
  28. 28. ○ The JRE is accessible either via the PATH or JAVA_HOME variable. ○ The JRE is up-to-date (version 1.6 or higher). Verify by calling: java ­version Procedure 1. Change to the following directory on the installation medium: <installation medium>/DATA_UNITS/HDB_LCM_LINUX_X86_64 2. Start the installer: ./hdblcm 3. Parameter default values are suggested in brackets, and can be accepted with Enter. Otherwise, enter a non-default value, then select Enter. Results The installation progress is displayed. The SAP HANA system is now up and running. 28 P U B L I C © 2014 SAP AG or an SAP affiliate company. All rights reserved. SAP HANA Server Installation and Update Guide Installing an SAP HANA System
  29. 29. 4 Advanced Installation Advanced installation topics are designed for those who are familiar with SAP HANA, and are installing it regularly, in various production environments. In particular, advanced installation refers to automated installation and the configuration of a multiple-host system using hdblcm. In order to provide flexibility, it is possible to install the same SAP HANA system in several ways. The differences between installation methods are best depicted through a one-to-one comparison of the same system installed with each available method. In the following example, there is a hardware partner who plans to install several SAP HANA single-host systems. His desired system has the following specifications: ● System name: P01 ● Instance number: 01 ● Installation path: /hana/shared ● Data path: /hana/data/P01 ● Log path: /hana/log/P01 ● User group ID: 110 He has several customers who have pre-ordered the single-host SAP HANA P01 system and he is expecting more P01 orders. His goal is to iteratively improve his installation method to the point that he can automate his ideally configured system installation on several hosts at the same time, come back later, and the installed SAP HANA platforms will be finished and ready to ship. To reach his goal, he installs the same system (P01) three times, using: ● Command line options ● Configuration file ● Configuration file in batch mode SAP HANA Server Installation and Update Guide Advanced Installation P U B L I C © 2014 SAP AG or an SAP affiliate company. All rights reserved. 29
  30. 30. Installing the System Using Command Line Options Since the hardware partner is still new to installing SAP HANA, he tries out the installation first from the command line. He reviews the installation parameters and finds the corresponding parameter key-value pairs for his desired P01 single-host system. System Detail Specification Command Line Parameter System name P01 ­­sid=P01 Instance num­ ber 01 ­­number=01 Installation path /hana/shared ­­sapmnt=/hana/shared Data path /hana/data/P01 ­­datapath=/hana/data/P01 Log path /hana/log/P01 ­­logpath=/hana/log/P01 User group ID 110 ­­groupid=110 The hardware partner takes the parameter key-value pairs, and builds the command line input as follows: ./hdblcm ­­sid=P01 ­­number=01 ­­groupid=110 ­­sapmnt=/hana/shared ­­datapath=/ hana/data/P01 ­­logpath=/hana/log/P01 Upon review of the parameter syntax, he realizes he did not need to specify sapmnt, datapath, or logpath parameters because he chose the default values. The rest of the parameters could also have been given the short-form syntax. Therefore, the same P01 system installation could be simplified to the following syntax: ./hdblcm –s P01 –n 01 –G 110 System Detail Specification Simplified Command Line Parameter System name P01 ­s P01 Instance num­ ber 01 ­n 01 Installation path /hana/shared <default> Data path /hana/data/P01 <default> Log path /hana/log/P01 <default> User group ID 110 ­G 110 Installing the System Using the Configuration File Now that the hardware partner successfully installed from the command line, he wants to make use of the configuration file, since his end goal is to automate the installation. He generates a template of the configuration file: ./hdblcm ­­action=install ­­dump_configfile_template=/home/root/HANA_install.cfg 30 P U B L I C © 2014 SAP AG or an SAP affiliate company. All rights reserved. SAP HANA Server Installation and Update Guide Advanced Installation
  31. 31. He opens the blank configuration file template and fills it in as follows: HANA_install.cfg# SAP HANA System ID sid=P01 # Instance Number (Default: 00) number=01 … # ID of User Group 'sapsys' Groupid=110 Since it was already discovered that only the SID, instance number, and group ID differ from the default values, only they are specified in the configuration file. The hardware partner also realizes that there is automatic substitution of the SID (sid) and installation path (sapmnt) throughout the configuration file according to default values (for example, datapath default: /hana/data/${sid}), so he does not need to append the SID (in this case, P01) to the paths. Now, he can start the installer from the command line with the following simple command: ./hdblcm ­­configfile=/home/root/HANA_install.cfg Installing the System Using the Configuration File in Batch Mode Now the hardware partner can take the last step of automation with the SAP HANA lifecycle management tool hdblcm and use batch mode. It is important to note, up this point the hardware partner has been interactively entering passwords and confirming other default parameters as part of interactive mode. Batch mode runs the installer without asking for any confirmation or parameter entry, thereby allowing installation to run to completion from one push of a button. There are two choices for password entry in batch mode. Either the passwords can be stored in an XML file and passed to the installer as a stream by standard input, or they can be specified in the configuration file. Since the hardware partner is already making use of the configuration file, he decides to enter the passwords there. The only mandatory parameters in batch mode are the SID and passwords, so he checks the other defaults of the mandatory installation values before continuing the installation. In batch mode, the installer accepts default values for any unspecified parameters. With the addition of passwords to the configuration file, it now looks like this: HANA_install.cfg# Root User Password root_password=Root1234 ... # SAP HANA System ID sid=P01 # Instance Number (Default: 00) number=01 ... # ID of User Group 'sapsys' Groupid=110 ... # SAP Host Agent (sapadm) Password sapadm_password=Agent1234 ... # System Administrator Password password=Adm1234 .... # Database User (SYSTEM) Password system_user_password=Sys1234 SAP HANA Server Installation and Update Guide Advanced Installation P U B L I C © 2014 SAP AG or an SAP affiliate company. All rights reserved. 31
  32. 32. Now, the partner starts the installer, this time with the addition of the batch mode parameter, ­b (or ­­ batch): ./hdblcm ­­configfile=/home/root/HANA_install.cfg ­b Multiple-Host System Setup A multiple-host SAP HANA system can be installed using all the methods listed above (with command line options, in the configuration file, and in batch mode). Additionally, the graphical interface tool hdblcmgui can also be used to build a multiple-host system. When installing a multiple-host system, the following applies: ● Using the SAP HANA lifecycle management tools, hdblcm or hdblcmgui, multiple hosts can be configured during installation. Additional hosts cannot be added to existing systems with these tools. ● The addhosts parameter must be specified. It is also possible to specify additional options for hosts such as: role, storage_partition, and group. For more details, refer to the addhosts parameter information, and the multiple-host system concepts information. ● The root user on all hosts must be the same. ● If the root user name is something other than the default "root", the root user name must be specified during installation with the parameter root_user. Related Information Installation Parameters [page 19] Installation parameters are a fundamental aspect of the SAP HANA lifecycle management tools hdblcm and hdblcmgui, and provide the opportunity to optimize and customize the system during installation. Multiple-Host System Concepts [page 43] It is important to review multiple-host system concepts like host grouping and storage options before installing a multiple-host system. 4.1 Automating SAP HANA System Installation Installation automation is designed for anyone who wants to install a similar SAP HANA system multiple times or start an unattended installation. With the SAP HANA lifecycle management tool hdblcm, it is now possible to automate installation by using a combination of the configuration file, command line options, and batch mode, so that an SAP HANA system installation can be executed once without any follow-up selection. To illustrate the purpose of installation automation, let us assume there is a hardware partner who offers SAP HANA platforms (SAP HANA system installed on SAP verified hardware) in three sizes: Small, Large, and Extra Large. 32 P U B L I C © 2014 SAP AG or an SAP affiliate company. All rights reserved. SAP HANA Server Installation and Update Guide Advanced Installation
  33. 33. Since the hardware partner prepares the SAP HANA platform on-demand, he needs to be able to react quickly to orders as they are placed. During slow sales periods, manual installation is feasible, however during busy sales periods, manual installation could create too much overhead. In this case, installation automation would allow the hardware partner to start as many installation copies as required, without any further interaction with the installer. It would even be possible for the partner to start the installation near the end of the business day, leave the installation, and ship out the order the next morning. SAP HANA Server Installation and Update Guide Advanced Installation P U B L I C © 2014 SAP AG or an SAP affiliate company. All rights reserved. 33
  34. 34. The hardware partner automates the installation of nine SAP HANA systems (1 Extra Large, 5 Large, and 3 Small). Previously, he has created configuration files for each of the three system types. So, when several orders come in at the same time, he fine tunes his installation script to include the number of systems and calls hdblcm with the configuration file parameter in batch mode. When the installation script is run, SAP HANA is installed on both the single-host and multiple-host systems, without any additional input. By reusing the same configuration files, the installations are reliable, flexible, and efficient. 4.1.1 Automation Checklist Automation is ideal for installations that run unattended. Before you start an automated installation, it is recommended to consider the following. For All System Types Do the operating system and additional software components meet the requirements? Refer to the Hardware and Software Requirements. Do you know where the data volumes and the log vol­ umes will be located? For security reasons, the data device and log device should not be the same. Refer to the SAP HANA Sys­ tem Types. 34 P U B L I C © 2014 SAP AG or an SAP affiliate company. All rights reserved. SAP HANA Server Installation and Update Guide Advanced Installation
  35. 35. Where will the required file systems be located and is the storage sufficient? Refer to the Recommended File System Layout. Have you performed a hardware check? The installer performs a hardware check before in­ stallation, for automated installation it is recom­ mended to perform a manual hardware check first. Refer to the Hardware and Software Requirements. Where will you specify passwords? SYSTEM, <sid>adm, sapadm, and root passwords must be specified in the configuration file or in an XML file. Refer to the Specifying Passwords informa­ tion. For the Multiple-Host System Type Only How many worker hosts and standby hosts will there be? How will they be grouped? System processes and data are distributed among worker hosts, including the original host. Standby hosts do not perform tasks. Refer to the Multiple- Host System Concepts. How will storage devices be configured? External storage can be configured so that hosts have shared or non-shared access. Refer to the Multi­ ple-Host System Concepts. The root user name must be the same for all hosts in a multiple-host system. Will the root user name for all hosts be "root"? If not, the root_user parameter must be specified during installation. Refer to the root_user parameter information. Related Information Hardware and Software Requirements [page 13] For SAP HANA several hardware and software requirements need to be fulfilled. SAP HANA System Types [page 9] An SAP HANA system can be configured as one of the following types: Recommended File System Layout [page 14] The SAP HANA lifecycle management tool hdblcm requires certain file systems in order to successfully install an SAP HANA system. Specifying Passwords [page 24] Passwords are a mandatory parameter for installing an SAP HANA system. There are three methods for configuring passwords. Multiple-Host System Concepts [page 43] It is important to review multiple-host system concepts like host grouping and storage options before installing a multiple-host system. root_user [page 78] Specifies the root user name. SAP HANA Server Installation and Update Guide Advanced Installation P U B L I C © 2014 SAP AG or an SAP affiliate company. All rights reserved. 35
  36. 36. 4.1.2 Automating with the Configuration File The configuration file is a text document where all available installation parameters can be specified. By calling hdblcm with ­­action=install ­­dump_configfile_template=<file> parameters specified, a text file is output to a specified file path. It can then be opened and edited. The template provides the available installation parameter values as well as corresponding information about their purpose and default values. For more information about preparation, see Related Information. When the configuration file has been prepared, it can be used in a number of ways: ● hdblcm with the configuration file - This method is the simplest. The installation parameter values are read by the installer from the configuration file. If all mandatory parameters are specified in the file, minimal interaction is required during installation. For more information, see Related Information. ● hdblcm with the configuration file and command line options - This method offers the most flexibility and is designed to reuse a configuration file for another installation. For more information, see Related Information. ● hdblcm with the configuration file and batch mode - This method is used for automated installation. It can be used to automate installation for several instances in a multiple-host system, or combined with a script to automate installation of several identical systems. For more information, see Related Information. For examples of installing with the configuration file, or for an example of the configuration file itself, refer to the related information. Related Information Preparing the Configuration File [page 37] The configuration file is an installation tool for those who want to install several of the same system, or save configuration parameters for reuse or for quick reference. Using the Configuration File [page 38] By defining a prepared configuration file during installation, specified parameter values are used by the installer to build a customized SAP HANA system. Using the Configuration File with Command Line Options [page 39] By defining a prepared configuration file during installation, specified parameter values are used by the installer to build a customized SAP HANA system. Using the configuration file and command line options at the same time allows for additional flexibility. Enabling Batch Mode [page 40] Batch mode installation can be started from the command line alone or in combination with the configuration file. It runs all installation tasks without prompting for additional confirmation or input. Batch mode is designed to automate the installation process. Tutorials [page 84] The following is a sampling of general use cases, which illustrate the functionality and versatility of the SAP HANA hdblcm lifecycle management tool. Configuration File Template [page 101] The following is the configuration file template that is generated using the dump_configfile_template parameter in combination with the hdblcm installer. 36 P U B L I C © 2014 SAP AG or an SAP affiliate company. All rights reserved. SAP HANA Server Installation and Update Guide Advanced Installation
  37. 37. 4.1.2.1 Preparing the Configuration File The configuration file is an installation tool for those who want to install several of the same system, or save configuration parameters for reuse or for quick reference. Prerequisites Make sure you have done the following before you start preparing the configuration file. ● You have considered how to set up the required systems and directories. For more information, see Related Information. ● You have considered which installation parameters the new system requires. For more information, see Related Information. Context The configuration file is a plain text file of specified installation parameters, written in the same syntax as in the command line (except without the leading two dashes --). A configuration file template can be generated, edited, and saved to be called during installation. The configuration file template provides a brief, commented-out summary of each parameter. Each parameter is set to its default value. The parameters are divided into the following categories: general, server, client, studio, and LifecycleManager. Procedure 1. Change to the following directory on the installation medium: <installation medium>/DATA_UNITS/HDB_LCM_LINUX_X86_64 2. Generate the configuration file template. Run the hdblcm program using the parameter dump_configfile_template. Specify an action and a file path for the template: ./hdblcm ­­action=[install|update] ­­dump_configfile_template=<filepath> 3. Edit the configuration file parameters. Save the file. It is recommended that at least the SAP system ID (sid) and the instance number (number) are uniquely defined. There are several required parameters, that are provided default values in case they are not customized. For more information, refer to the default values. Some file path parameters have automatic substitution values as part of the default file path, using the sid (SAP HANA system ID) and sapmnt (installation path) parameters, so that the substituted values create file paths that are unique and system-specific. For example, the default for the data file path is: datapath=/hana/data/${sid}, where sid is automatically replaced by the unique SAP HANA system ID. SAP HANA Server Installation and Update Guide Advanced Installation P U B L I C © 2014 SAP AG or an SAP affiliate company. All rights reserved. 37
  38. 38. Results You have generated the configuration file template, edited it, and saved it. The configuration file is now ready for use during installation. Related Information Changeable Default Values [page 20] The installer uses the following default values unless you change them during installation. Recommended File System Layout [page 14] The SAP HANA lifecycle management tool hdblcm requires certain file systems in order to successfully install an SAP HANA system. Parameter Reference [page 64] Reference information is provided for each installation parameter. 4.1.2.2 Using the Configuration File By defining a prepared configuration file during installation, specified parameter values are used by the installer to build a customized SAP HANA system. Prerequisites ● You have prepared the configuration file. For more information, see Preparing the Configuration File. ● You are logged in as root user. ● If the SAP HANA studio is selected for installation, the Java Runtime Environment (JRE) is configured as follows: ○ The JRE is accessible either via the PATH or JAVA_HOME variable. ○ The JRE is up-to-date (version 1.6 or higher). Verify by calling: java ­version Procedure 1. Change to the following directory on the installation medium: <installation medium>/DATA_UNITS/HDB_LCM_LINUX_X86_64 2. Start the installer with the prepared configuration file specified: ./hdblcm ­­configfile=<file path> 38 P U B L I C © 2014 SAP AG or an SAP affiliate company. All rights reserved. SAP HANA Server Installation and Update Guide Advanced Installation
  39. 39. Results The installation progress is displayed on the command line. The SAP HANA system is now up and running. Related Information Preparing the Configuration File [page 37] The configuration file is an installation tool for those who want to install several of the same system, or save configuration parameters for reuse or for quick reference. 4.1.2.3 Using the Configuration File with Command Line Options By defining a prepared configuration file during installation, specified parameter values are used by the installer to build a customized SAP HANA system. Using the configuration file and command line options at the same time allows for additional flexibility. Prerequisites ● You have prepared the configuration file. For more information, see Preparing the Configuration File. ● You are logged in as root user. ● If the SAP HANA studio is selected for installation, the Java Runtime Environment (JRE) is configured as follows: ○ The JRE is accessible either via the PATH or JAVA_HOME variable. ○ The JRE is up-to-date (version 1.6 or higher). Verify by calling: java ­version Context If parameter values are specified in both the configuration file and the command line, the command line values override the configuration file values. This feature provides some extra flexibility for reuse, since an existing configuration file could be used for a new installation where most of the values remain unchanged, but some values could be modified on the command line ad-hoc. SAP HANA Server Installation and Update Guide Advanced Installation P U B L I C © 2014 SAP AG or an SAP affiliate company. All rights reserved. 39
  40. 40. Procedure 1. Change to the following directory on the installation medium: <installation medium>/DATA_UNITS/HDB_LCM_LINUX_X86_64 2. Start the installer with the prepared configuration file specified: ./hdblcm ­­configfile=<file path> <additional parameters> Results The installation progress is displayed on the command line. The SAP HANA system is now up and running. Example The following example installs a multiple-host system with the addhosts parameter specified on the command line, but all other parameters specified from the configuration file. If the addhosts parameter is also specified in the configuration file, it is overwritten by the command line specification of addhosts. ./hdblcm ­­action=install ­­ addhosts=hanahost2:group=HA1:storage_partition=3,hanahost3:role=standby:group=H A1 ­­configfile=/var/tmp/H01_configfile Related Information Preparing the Configuration File [page 37] The configuration file is an installation tool for those who want to install several of the same system, or save configuration parameters for reuse or for quick reference. 4.1.2.4 Enabling Batch Mode Batch mode installation can be started from the command line alone or in combination with the configuration file. It runs all installation tasks without prompting for additional confirmation or input. Batch mode is designed to automate the installation process. Prerequisites ● When using batch mode, passwords must either be defined in the configuration file, or passed to the installer using an XML password file and streamed in via standard input. In both cases, it is necessary to prepare the passwords. For more information, see Specifying Passwords. 40 P U B L I C © 2014 SAP AG or an SAP affiliate company. All rights reserved. SAP HANA Server Installation and Update Guide Advanced Installation
  41. 41. ● You are logged in as root user. ● If the SAP HANA studio is selected for installation, the Java Runtime Environment (JRE) is configured as follows: ○ The JRE is accessible either via the PATH or JAVA_HOME variable. ○ The JRE is up-to-date (version 1.6 or higher). Verify by calling: java ­version Context For those new to installation with the SAP HANA lifecycle management tool hdblcm, it is recommended to run some test installations before using batch mode in a production environment. Procedure 1. Change to the following directory on the installation medium: <installation medium>/DATA_UNITS/HDB_LCM_LINUX_X86_64 2. Start the installer with the batch mode parameter specified: ./hdblcm ­­batch <additional parameters> or ./hdblcm ­b <additional parameters> Results The installation runs without any follow-up. Example The following example installs the SAP HANA server, client, and HLM as a single-host system. The SAP system ID and instance number are also specified from the command line. The system passwords are read from a standard input stream by the installer. All other parameter defaults are automatically accepted and no other input is requested in order to complete the installation. cat ~/Passwords.xml | ./hdblcm ­­batch ­­action=install ­­ components=client,hlm,server ­­sid=DB1 ­­number=42 ­­ read_password_from_stdin=xml If a configuration file is used in combination with batch mode, an identical system can be installed with a simplified call from the command line. In the following example, passwords are defined in the configuration file, in addition to the action, components, SAP system ID, and instance number. ./hdblcm ­­batch ­­configfile=/var/tmp/H01_configfile SAP HANA Server Installation and Update Guide Advanced Installation P U B L I C © 2014 SAP AG or an SAP affiliate company. All rights reserved. 41
  42. 42. Related Information Specifying Passwords [page 24] Passwords are a mandatory parameter for installing an SAP HANA system. There are three methods for configuring passwords. 4.2 Multiple-Host System Installation It is possible to configure additional hosts for an SAP HANA system both during and after installation. However, there are some slight differences with the tools used depending on when you decide to add a host to the system. ● The SAP HANA lifecycle management tool (hdblcm) - By specifying the addhosts parameter during installation with the hdblcm tool, it is possible to configure a multiple-host system interactively from the command line, in combination with the configuration file, or in batch mode. Each installation method uses the same addhosts parameter options. For information about the parameter options, see Related Information. ● The SAP HANA lifecycle management tool (hdblcmgui) - It is possible to use the graphical installation tool, alone or in combination with the configuration file, to install a multiple-host system. The host parameters correspond to those used in the command line. For information about the parameter options, see Related Information. The following information only covers building a multiple-host system during installation. Before carrying out the system installation, review the addhosts parameter options and how they can be set to optimize multiple- host system performance. Related Information addhosts [page 64] Specifies additional hosts for the SAP HANA system as a comma-separated list. Individual host options are specified by a colon-separated list.This parameter is used when configuring a multiple-host system during installation. 42 P U B L I C © 2014 SAP AG or an SAP affiliate company. All rights reserved. SAP HANA Server Installation and Update Guide Advanced Installation
  43. 43. 4.2.1 Multiple-Host System Concepts It is important to review multiple-host system concepts like host grouping and storage options before installing a multiple-host system. Host Types When configuring a multiple-host system, the additional hosts must be defined as worker hosts or standby hosts (worker is default). Worker machines process data; standby machines do not handle any processing and instead just wait to take over processes in the case of worker machine failure. Auto-Failover for High Availability Before installing a multiple-host system, it is important to consider whether high availability is necessary and how hosts should be grouped to ensure preferred host auto-failover. For host auto-failover to be successful, if the active (worker) host fails, the standby host takes over its role by starting its database instance using the persisted data and log files of the failed host. The name server of one of the SAP HANA instances acts as the cluster manager that pings all hosts regularly. If a failing host is detected, the cluster manager ensures that the standby host takes over the role and the failing host is no longer allowed write access to the files (called fencing) so that they do not become corrupted. Host Grouping Host grouping does not affect the load distribution among worker hosts - the load is distributed among all workers in an SAP HANA system. If there are multiple standby hosts in a system, host grouping should be considered, because host grouping decides the allocation of standby resources if a worker machine fails. If no host group is specified, all hosts belong to one host group called "default". The more standby hosts in one host group, the more failover security. SAP HANA Server Installation and Update Guide Advanced Installation P U B L I C © 2014 SAP AG or an SAP affiliate company. All rights reserved. 43
  44. 44. If the same system is considered, but the standby hosts are each in a different host group, only one worker host in each group can be compensated if failure occurs. The advantage of this configuration, is that in an SAP HANA system with mixed machine resources, similar sized machines can be grouped together. If a small worker host fails, and a small standby in the same group takes over, the processes are moved to a machine with similar resources, which allows processing to continue as usual with optimal resource allocation. The installer distinguishes between two types of groups: sapsys groups, and host groups. The SAP system group (sapsys group) is the group that defines all hosts in a system. Therefore, all hosts in a multiple-host system must have the same sapsys group ID, which is the default configuration with hdblcm. A host group is group of hosts that share the same standby resources only. Therefore, if the multiple-host system has one standby host, it is important to leave all hosts in the same host group ("default") so that all hosts have access to the standby host in case a worker host fails. Storage Options In single-host SAP HANA systems, it is possible to use plain attached storage devices, such as SCSI hard drives, SSDs, or SANs. However, in order to build a multiple-host system with failover capabilities, the storage must ensure the following: ● The standby host has file access. ● The failed worker host no longer has access to write to files - called fencing. There are two fundamentally different storage configurations which meet the two conditions above: shared storage devices or separate storage devices with failover reassignment. A shared storage subsystem, such as NFS or IBM's GPFS, is the commonly used storage option because it is easy to ensure that the standby host has access to all active host files in the system. In a shared storage solution, the externally attached storage subsystem devices are capable of providing dynamic mount points for hosts. Since shared storage subsystems vary in their handling of fencing, it is the responsibility of the hardware partner and their storage partners to develop a corruption-safe failover solution. A shared storage system could be configured as in the diagram below, however mounts may differ among hardware partners and their configurations. 44 P U B L I C © 2014 SAP AG or an SAP affiliate company. All rights reserved. SAP HANA Server Installation and Update Guide Advanced Installation
  45. 45. It is also possible to assign every SAP HANA host a separate storage, which has nothing mounted except the shared area. This storage solution must be used in combination with the storage connector API, which SAP HANA offers storage technology vendors. During failover, SAP HANA uses the storage connector API to tell the storage device driver to re-mount the required data and logs volumes to the standby host and fence off the same volumes from the failed host. In a non-shared environment, separate storage used in combination with the storage connector API are given logical roles as numbers. If you install a multiple-host system using hdblcm, you must specify the logical role (assigned by the storage connector API) as the storage_partition option in the addhosts parameter during installation so that the storage devices are recognized correctly by the installer. SAP HANA Server Installation and Update Guide Advanced Installation P U B L I C © 2014 SAP AG or an SAP affiliate company. All rights reserved. 45
  46. 46. 4.2.2 Creating a Multiple-Host System During Installation The SAP HANA lifecycle management tools hdblcm and hdblcmgui have the ability to build a multiple-host system during installation in interactive mode, in batch mode, and with the available parameter specification methods: interactively, using command line options, or with the configuration file. Prerequisites ● The shared file systems for the data files and log files are configured so that they are present and mounted on all hosts, including the primary host. The suggested locations for the file systems are as follows: ○ /hana/shared/ ○ /hana/data/<SID> ○ /hana/log/<SID> ● (Optional) Additional storage is configured. ● Root user name must be the same for all hosts in a multiple-host system. ● If the root user name is not root, it must be specified as a parameter during installation using the parameter root_user. ● You are logged in as root user. ● If the SAP HANA studio is selected for installation, the Java Runtime Environment (JRE) is configured as follows: ○ The JRE is accessible either via the PATH or JAVA_HOME variable. ○ The JRE is up-to-date (version 1.6 or higher). Verify by calling: java ­version ● Multiple-host system installation using the hdblcm installation tool requires the parameter action=install to be specified. Procedure 1. Change to the following directory on the installation medium: <installation medium>/DATA_UNITS/HDB_LCM_LINUX_X86_64 2. Start the installer from the command line: ○ Interactive installation from GUI Start the graphical installation tool, and follow the steps to configure the multiple-host system installation: ./hdblcmgui ○ Interactive installation from CLI Start the command line installation tool: ./hdblcm ­­action=install ­­addhosts=<host options> A multiple-host system can be installed interactively from the command line, however the storage and host role parameters cannot be entered interactively. Therefore, to carry out interactive installation from the command line, it required to specify at least the action and addhosts parameters. 46 P U B L I C © 2014 SAP AG or an SAP affiliate company. All rights reserved. SAP HANA Server Installation and Update Guide Advanced Installation
  47. 47. ○ With the configuration file (CLI or GUI) ○ Start the command line installation tool: ./hdblcm ­­action=install ­­configfile=<file path> ○ Start the graphical installation tool: ./hdblcmgui ­­configfile=<file path> It is possible to specify the addhosts parameter, and other required system parameters in the configuration file, and call the configuration file during multiple-host system installation. ○ Command line installation in batch mode Start the command line installation tool: ./hdblcm ­­action=install ­­addhosts=<host options> ­­sid=<SID> ­­ number=<instance number> ­b Multiple-host system installation can be carried out in batch mode. In this case, at least the action, addhosts, sid, and batch parameters must be specified. It is recommended to check the file paths, and specify the instance number (number) as well. Related Information Installation Parameters [page 19] Installation parameters are a fundamental aspect of the SAP HANA lifecycle management tools hdblcm and hdblcmgui, and provide the opportunity to optimize and customize the system during installation. Interactive Installation [page 25] Interactive mode is an installation mode, which requires the person installing the SAP HANA system to enter parameter specifications as they are requested by the installer. Automating with the Configuration File [page 36] The configuration file is a text document where all available installation parameters can be specified. SAP HANA Server Installation and Update Guide Advanced Installation P U B L I C © 2014 SAP AG or an SAP affiliate company. All rights reserved. 47
  48. 48. 5 Updating the SAP HANA System All components of an SAP HANA system, including server, studio, client, HLM, AFL, LCApps, and SDA, can be updated using the SAP HANA lifecycle management tools hdblcm(gui) and lifecycle manager. We recommend to perform an SAP HANA system update from a local host. A local host is defined as a host that is part of the SAP HANA system, which you are logged on to. Performing an update from a local host minimizes the risk of failed update due to network glitches. A remote host is defined as any host which establishes a connection to an SAP HANA host via HTTPS. In the SAP HANA lifecycle management tool set, hdblcm(gui) is responsible for updating a system from a local host, and the lifecycle manager updates from a remote host. Related Information Updating an SAP HANA System from a Local Host [page 48] An SAP HANA system can be updated from a local host using the SAP HANA lifecycle management tool hdblcm(gui). Updating an SAP HANA System from a Remote Host [page 54] You can perform an automated update of an SAP HANA system with the SAP HANA lifecycle manager. The update use cases are applying Support Package Stacks (SPS) for SAP HANA and applying Single Support Packages for SAP HANA. 5.1 Updating an SAP HANA System from a Local Host An SAP HANA system can be updated from a local host using the SAP HANA lifecycle management tool hdblcm(gui). There are three methods for downloading an SAP HANA installation medium: ● Download the installation medium from Service Marketplace (SMP) - This method is only applicable when updating to a new SPS. ● Use the Check for Updates functionality in the SAP HANA studio. See the Download Software Components from SAP Service Marketplace and Prepare the Software Archive for Update information. ● Download individual components from Service Marketplace (SMP). Note The installation medium cannot be patched manually with newer versions of SAP HANA components and used for installation or update. The result is an error-prone installation. 48 P U B L I C © 2014 SAP AG or an SAP affiliate company. All rights reserved. SAP HANA Server Installation and Update Guide Updating the SAP HANA System
  49. 49. Related Information Download Software Components from SAP Service Marketplace [page 49] You can use your SAP HANA studio to check for available software component updates and download them from SAP Service Marketplace. Prepare the Software Archive for Update [page 51] After downloading the software components from SAP Service Marketplace, the software archive must be prepared for the update. Update an SAP HANA System from a Local Host [page 52] It is possible to update an SAP HANA system from a local host using the hdblcm or hdblcmgui lifecycle management tools. 5.1.1 Preparing for Update in the SAP HANA Studio The SAP HANA studio can be configured to check for software updates. Once updates are available, the software must be downloaded, and the archive prepared before the update software can be installed. Related Information Download Software Components from SAP Service Marketplace [page 49] You can use your SAP HANA studio to check for available software component updates and download them from SAP Service Marketplace. Prepare the Software Archive for Update [page 51] After downloading the software components from SAP Service Marketplace, the software archive must be prepared for the update. 5.1.1.1 Download Software Components from SAP Service Marketplace You can use your SAP HANA studio to check for available software component updates and download them from SAP Service Marketplace. Prerequisites ● In the SAP HANA studio preferences, you have configured connection properties to the SAP Service Marketplace. ● Your SAP HANA system must be SPS 08 or newer and must have hdblcm installed. SAP HANA Server Installation and Update Guide Updating the SAP HANA System P U B L I C © 2014 SAP AG or an SAP affiliate company. All rights reserved. 49
  50. 50. ● You need to provide system administrator (<sid>adm) credentials. Context In order to update an SAP HANA system, you first need to download the corresponding update sources (components) from SAP Service Marketplace. The SAP HANA studio provides functionality, which helps you to easily check for available updates of the installed SAP HANA core components and download them locally on the machine where the SAP HANA studio is started or on a shared file system. In addition to the downloaded content you will be provided with a shell script, which can automatically extract the archives in a directory structure, suitable for hdblcm or hdblcmgui. Procedure 1. Right click on an SAP HANA system and choose Lifecycle Management Platform Lifecycle Management Check for available software component updates . 2. Choose which versions of the available components you want to download or choose skip to skip the download of a particular component. The current version column shown the version of the components, which is currently installed on the SAP HANA system. Note that you can also select and download SAP HANA core components which are not currently, but can be installed on the system. 3. Review the selected components and choose a download directory. 4. To start the download process, choose Finish. 5. You can run the download process in background by pressing the Run In Background button. To get the current progress of the download, open the Progress View ( Window Show View Other… Progress ). Next Steps To prepare for the update process, see Related Information. Related Information Prepare the Software Archive for Update [page 51] After downloading the software components from SAP Service Marketplace, the software archive must be prepared for the update. 50 P U B L I C © 2014 SAP AG or an SAP affiliate company. All rights reserved. SAP HANA Server Installation and Update Guide Updating the SAP HANA System

×