Professional Documents
Culture Documents
SAP HANA Update and Configuration Guide Good PDF
SAP HANA Update and Configuration Guide Good PDF
5 Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
6 Appendix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
6.1 Manually Adding SAP HANA Lifecycle Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
6.2 Optional: Using Own SAP Host Agent Certificates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
The figure below shows an example of a configured SAP HANA system and its components, including the SAP
HANA lifecycle manager:
The SAP HANA lifecycle manager provides a simple, user-friendly user interface with which you can customize
your system. The figure below shows the starting page of the SAP HANA lifecycle manager:
The HLM is a tool that enables flexible customizations of an existing SAP HANA system. You can review the
examples of SAP HANA reference operation scenarios in the guide, and use them to define your own scenarios.
For more information about the SAP HANA reference operation scenarios, see Managing the Lifecycle of SAP
HANA in this guide. The current section focuses on how to prepare the tool for initial usage.
This section provides instructions on how to ensure you have the SAP HANA lifecycle manager available on your
SAP HANA system.
The necessary preparation steps for each available working mode are described in a separate topic.
There are three available working modes for the SAP HANA lifecycle manager:
This section provides information on how to use the SAP HANA lifecycle manager (HLM) through the SAP HANA
studio.
Prerequisites
● To access SAP HANA lifecycle manager through SAP HANA studio, you require an <SID>adm user.
● Make sure that the communication port 1129 is open. This port is required for the SSL communication with
the SAP Host Agent.
Keep in mind that, to work with HLM, you need to make certain configuration settings for the SAP HANA Studio.
There are also certain browser restrictions. For more information, see Setting up the SAP HANA Studio [page
12].
Keep in mind that the Lifecycle Management perspective in the SAP HANA studio requires version of Java Virtual
Machine equal or higher to 1.6.0_12.
The figure below shows how to ensure you have the HLM, which you intend to use through the SAP HANA studio.
1. Install or update to the latest available SAP HANA studio. You need SAP HANA studio revision 60 as a
minimum. For more information, see SAP HANA Database - Studio Installation and Update Guide. Add the SAP
HANA system, if it has not already been added. To do this, call the context menu in the SAP HANA Systems
view and choose Add System. Alternatively, you can use the SAP HANA studio that is installed by default on
the SAP HANA system in <shared_directory>/<SID>/hdbstudio (usually,/hana/shared/<SID>/
hdbstudio.
This section provides details about how to use the SAP HANA lifecycle manager (HLM) in command line mode.
Context
The figure below shows how to ensure you have the SAP HANA lifecycle manager (HLM), which you intend to use
in command line mode:
This section provides details about how to use the SAP HANA lifecycle manager (HLM) in a standalone browser.
Prerequisites
Make sure that the communication port 1129 is open. This port is required for the SSL communication with the
SAP Host Agent. Hence, you need the 1129 communication port to use HLM in a standalone browser via HTTPS.
Context
The figure below shows how to ensure that you have the SAP HANA lifecycle manager (HLM), which you intend to
use in standalone browser mode:
● For Microsoft Windows, you need Internet Explorer version 9 or higher, Mozilla Firefox 13 or higher, or Safari
5.1 or higher. If you are running Internet Explorer version 9, make sure that your browser is not running in
compatibility mode with your SAP HANA host. You can check this in your browser by choosing Tools
Compatibility View Settings .
● For Linux, you need XULRunner 1.9.2 or higher. We recommend that you install XULRunner 1.9.2 (or above)
separately but if you have already installed Mozilla Firefox 3.6 (or higher), it contains XULRunner 1.9.2.
● For iOS and OS X you need Safari 5.1 or higher.
To use the tool from a standalone browser, call the following URL:
https://<host>:1129/lmsl/HLM/<SID>/ui/index.html
Make sure you use the fully qualified SAP HANA system host name, such as myhost.sap.com (not just myhost).
You might need to wait for a minute while the necessary data is loaded. If you are still not seeing the HLM start
page, choose Refresh in your browser.
Procedure
● The SAP HANA lifecycle manager is installed in the SAP HANA system in the <shared_directory>/<SID>/
HLMdirectory. In most cases it is /hana/shared/<SID>/HLM.
● You have latest available SAP HANA studio installed
● To connect the SAP HANA lifecycle manager through the SAP HANA studio, do the following:
Check your proxy settings in the SAP HANA studio by choosing Window Preferences General
Network Connections .
Change the proxy settings in accordance with your system landscape.
If you are connecting using a proxy, you must have enabled an HTTPS schema and provided the correct proxy
settings. Make sure you configure the connection to both domains service.sap.com and *.sap-ag.de.
The default ports are 8080 for HTTP and 8443 for HTTPS.
If you are not using a proxy, disable the HTTPS schema by choosing Direct as the Active Provider.
The other values should be as follows:
Localhost Manual
127.0.0.1 Manual
For more information about how to configure the proxy settings, see the documentation that is integrated into
the SAP HANA studio. Choose Help Help Contents Workbench User Guide Reference Preferences
Network Connections .
Direct access to the SAP HANA lifecycle manager is possible only through an SAP HANA studio, which is
compatible with the following Web browser versions:
● For Microsoft Windows, you need Internet Explorer version 9 or higher, Mozilla Firefox 13 or higher, or Safari
5.1 or higher. If you are running Internet Explorer version 9, make sure that your browser is not running in
compatibility mode with your SAP HANA host. You can check this in your browser by choosing Tools
Compatibility View Settings .
● For Linux, you need XULRunner 1.9.2 or higher. We recommend that you install XULRunner 1.9.2 (or above)
separately but if you have already installed Mozilla Firefox 3.6 (or higher), it contains XULRunner 1.9.2.
The system property org.eclipse.swt.browser.XULRunnerPath should be set in hdbstudio.ini to
point to the path of XULRunner, for example:
-Dorg.eclipse.swt.browser.XULRunnerPath=/usr/lib64/xulrunner-1.9.2.13.
This hdbstudio.ini file is located in the same folder as the executable that is used to start the SAP HANA
studio (including the SAP HANA Update UI). For Linux, the default location is hana/shared/<SID>/
hdbstudio., or /usr/sap/hdbstudio for older versions.
● For iOS and OS X you need Safari 5.1 or higher.
Note
Keep in mind that the HLM engine updates the SAP HANA studio repository (update site), not the SAP HANA
studio itself. More information about how to update the SAP HANA studio itself is provided at the end of the
SAP HANA system update procedure.
If you have access to the Internet on your SAP HANA appliance and you intend to use SAP Service Marketplace
(SMP), configure the connection to SMP first. You need to perform this configuration before you open the HLM
editor.
Option Description
Note
You can obtain an S-User on SMP at https://
service.sap.com -> Registration.
4. Choose Apply.
5. Choose OK.
Note
To reset your entries, choose Restore Defaults.
Before you customize your SAP HANA system, review the possible reference scenarios. For more information,
see Reference Operation Scenarios for SAP HANA [page 15].
● You can perform custom configuration of your SAP HANA system. For more information, see Configuring SAP
HANA with SAP HANA Lifecycle Manager [page 18].
● You can update your SAP HANA system. For more information, see Updating an SAP HANA System with the
SAP HANA Lifecycle Manager [page 29].
● You can manage SAP HANA components and application content. For more information, see Managing SAP
HANA Components and Application Content [page 34].
This section provides information about the possible scenarios in which you can operate SAP HANA.
Keep in mind that these are example scenarios, which you can use for reference. Do not regard them as strongly
recommended options for your SAP HANA system.
● Distributed SAP HANA scenario. You can use this scenario in productive landscapes. With the illustrated
design, you can ensure high availability at all times. The figure below provides an example of a scenario of this
type:
You can use the SAP HANA lifecycle manager to customize your SAP HANA system. You can do so after the initial
installation with SAP HANA hdblcm or SAP HANA unified installer is finished.
Recommendation
For new installations of an SAP HANA system, we recommend that you use SAP HANA hdblcm. The SAP HANA
unified installer is available as part of SAP HANA SPS 07 and earlier releases, but is listed as deprecated as of
SAP HANA SPS 07.
The sections that follow describe how to use the SAP HANA lifecycle manager user interface.
For more information about using the command line interface, see the dedicated section that describes this
working mode, where you can find instructions on how to display the help and on how to review the available
options.
Context
Note
If you rename an SAP HANA system, this normally invalidates the permanent SAP license. You therefore need
to reinstall the SAP license. For more information about how to install the license key, see the SAP HANA
Database Administration Guide at http://help.sap.com/hana.
We strongly recommend not to perform a SAP HANA system rename using SAP HANA studio belonging to this
SAP HANA system, as this could lead to inconsistency.
If you specify the host name, make sure that it is fully qualified, such as myhost.sap.com (not just myhost).
Procedure
Example
You can also rename your SAP HANA system using command line. For more information about this mode, see
Using SAP HANA Lifecycle Manager in Command Line Mode [page 8]. You can also review the following
example:
An automatic rename and move (mv) of data and log path is also supported in the SAP HANA lifecycle manager
rename task , if <SID> is detected by the tool in data or log path.
For example, an automatic rename of data and log paths would be performed for source system id DEL and
target system id P01, as follows:
Also, if an automatic rename is to be performed the target values for data and log path are resolved and
presented in the respective user interface page of SAP HANA lifecycle manager. Validation for existence of
these folders would not be performed, because these would be created by SAP HANA lifecycle manager during
automatic rename.
Context
Note
The following information is only relevant if your SAP HANA system is distributed between two or more
separate hosts (for example, one host where the SAP HANA system is installed, and one that is used only for
storage, and so on).
If your SID is mounted to a file storage on a different host, perform the following manual steps before starting the
rename operation:
Procedure
1. On the host where SAP HANA is installed, perform the following actions:
a) Stop the SAP HANA system. To do this, in the SAP Host Agent perform the following operation:
/usr/sap/hostctrl/exe/sapcontrol -nr <InstanceNumber> -function StopSystem
b) Stop the sapstartsrv service by using the following SAP Host Agent operation:
/usr/sap/hostctrl/exe/sapcontrol -nr <InstanceNumber> –function StopService
c) Create a new shared SID directory /<hana shared>/<new SID>.
d) Unmount the current SID directory /<hana shared>/<current SID>.
2. On the host used for storage, rename the /<hana shared>/<current SID> to /<hana shared>/<new
SID> directory.
3. On the host where SAP HANA is installed, perform the following actions:
a) Mount /<hana shared>/<new SID> to the file storage host.
b) Create a soft link from /<hana shared>/<current SID> to /<hana shared>/<new SID>.
c) Start the sapstartsrv service. To do this, use the following SAP Host Agent operation:
/usr/sap/hostctrl/exe/sapcontrol -nr <InstanceNumber> –function StartService <SID>
Once all steps have been performed, you can proceed with the rename operation.
This section provides information about how to configure SAP Landscape Transformation (LT) Replication.
Context
SAP LT Replication Server is an SAP system that facilitates the replication of data from one or more source
systems to one or more target systems. The source systems can be SAP or non-SAP systems.
In the SAP HANA lifecycle manager, the task Configure SAP Landscape Transformation (SAP LT) Replication is
used to perform the post-installation configuration of the SAP LT Replication Server. As described in the
installation guide of the SAP LT Replication Server, the following post-installation configuration steps typically
need to be performed:
● Creation of a user with the required role on the SAP source system
● Creation of a type 3 (ABAP) RFC destination on the SAP LT Replication Server, which connects to the SAP
source system
● Activation of ICF and Web Dynpro services
The task automates the post-installation configuration steps after obtaining the required input from the end user
in consecutive steps. The task currently only automates the configuration of one SAP source system at a time .
Procedure
This section provides information about how to set up a connection to the System Landscape Directory (SLD).
SLD serves as a central information repository for your system landscape. Data suppliers collect and send system
data to SLD on a regular basis. The SLD data supplier for SAP HANA systems is implemented within the name
server of the SAP HANA system. However, to enable the data collection process for your SAP HANA system, you
must first configure the system’s connection to the SLD.
You can use SAP HANA lifecycle manager to configure the connection parameters for the central SLD system.
Note that SAP HANA lifecycle manager provides only the functionality to configure the parameters for the
connection to the SLD, the actual registration is performed automatically by the SLD data supplier afterwards.
Therefore, it may take some time for the SAP HANA system whose SLD connection parameters you have
configured to be registered in the central SLD system.
When an SAP HANA system is connected to the SLD, it can report its status and provide details and information
about the system itself. To do this, follow the procedure below, using the SAP HANA lifecycle manager user
interface.
Procedure
Example
You can also perform this task using command line. For more information about this mode, see Using SAP
HANA Lifecycle Manager in Command Line Mode [page 8]. You can also review the following example:
Next Steps
After you have configured the connection parameters, you can manually push the registration of the SAP HANA
system in the central SLD system instead of waiting for the SAP HANA system to be registered automatically at a
later point in time. To do so, as a <SID>adm user, execute the following command: /usr/sap/hostctrl/exe/
saposcol -b | sldreg -connectfile /usr/sap/<SID>/SYS/global/slddest.cfg -stdin –oldtransferdtd.
This section describes how to add a Solution Manager Diagnostics (SMD) agent using the SAP HANA lifecycle
manager.
Context
SAP HANA DVD should be on the same SPS level as the SAP HANA lifecycle manager.
The SMD <SID>adm user password must contain only ASCII characters and must be at least 8 characters long.
To add an SMD agent using the SAP HANA lifecycle manager user interface, follow the procedure below.
Procedure
Example
You can also add SMD agent using command line. For more information about this mode, see Using SAP HANA
Lifecycle Manager in Command Line Mode [page 8]. You can also review the following example:
This section describes how to remove a Solution Manager Diagnostics (SMD) agent using the SAP HANA Lifecycle
Manager.
SAP HANA DVD should be on the same SPS level as the SAP HANA lifecycle manager.
To remove an SMD agent using the SAP HANA lifecycle manager user interface, follow the procedure below.
Procedure
Example
Alternatively, you can also remove the SMD agent by using a command line prompt. For more information, see
Using SAP HANA Lifecycle Manager in Command Line Mode. Review the following example to remove the SDM
agent:
This section provides information about how to add additional SAP HANA systems on a single appliance. This can
be executed from the SAP HANA lifecycle manager (HLM). This scenario is also known as a multi-SID scenario.
Prerequisites
● Make sure there is a Java 1.6.0 or newer installed on the host that you are about to add as an additional
system, and Java executable is included in the root user’s path.
● SAP HANA DVD should be owned by the root user.
Context
To add additional SAP HANA systems on a single appliance using the SAP HANA lifecycle manager user interface,
follow the procedure below.
Next Steps
Note
You have the option to specify a dedicated time zone. By default, the time zone is set to UTC (Coordinated
Universal Time).
This section describes how to remove systems that you have already added with the SAP HANA lifecycle manager
(HLM).
Prerequisites
If you choose to remove additionally added SAP HANA systems with the HLM user interface, you are prompted to
enter the required parameters.
To remove an SAP HANA system you must use the HLM which belongs to this system. Therefore, you can only
remove a system whose HLM you are currently using.
Context
Note
Keep in mind that the originally installed SAP HANA systems cannot be uninstalled by the SAP HANA lifecycle
manager. You can only remove the additionally installed systems with the SAP HANA lifecycle manager.
When removing an SAP HANA system using the SAP HANA studio belonging to this SAP HANA system (under
<shared_directory>/<SID>/hdbstudio), the SAP HANA studio may experience some inconsistencies.
Therefore, we recommend that you use HLM browser mode or HLM command line mode to perform this task.
1. Open the SAP HANA lifecycle manager user interface of the system you want to remove.
2. Choose Remove SAP HANA System, enter the credentials for the system and the path to the installation
folder.
3. Choose Next to continue.
4. Specify the required entries by following the instructions in the wizard.
You can add additional hosts or remove redundant hosts in your SAP HANA system using the SAP HANA lifecycle
manager. This is also known as a distributed SAP HANA system. To do this, follow the procedure below:
Context
Prerequisites
● For information about performing a distributed system installation, see Performing a Distributed System
Installation (Optional) in the SAP HANA Server Installation Guide.
Note
To configure SAP HANA to monitor all network interfaces, proceed as described in Configuring the SAP
HANA System Internal Network and configure SAP HANA to do so.
● Ensure that the sapsys user group exists and has the same ID on all hosts.
● On the secondary (additional) hosts, install the SAP Host Agent using the rpm package on the DVD. On the
primary host, it is installed by SAP HANA hdblcm or the SAP HANA unified installer.
● The additional hosts require an SAP Host Agent with a minimum version of 153.
Procedure
Before removing a host from SAP HANA lifecycle manager, you need to select and remove this host in the
SAP HANA studio. To do so, on the system administration panel of SAP HANA studio, choose Landscape
Hosts . From the list of available hosts, select the one you want to remove, and then choose Remove Host
from the context menu of the selected host. This is a prerequisite for removing a host in all working modes of
SAP HANA lifecycle manager.
Note
After you remove a host from your system, you must perform a data backup to ensure that you can
recover the database to a point in time after you removed the host. When you remove a host you also need
to choose Remove Host from the system administration panel of the SAP HANA studio.
Related Information
Context
In addition to external network connections, SAP HANA uses separate, dedicated connections exclusively for
internal communication. In a distributed system environment, internal network communication takes place
between the hosts of a distributed system on one site. Certified SAP HANA hosts contain a separate network
interface card that is configured as part of a private network, using separate IP addresses and ports.
To prevent unauthorized access to the database via the internal communication channels in distributed systems,
you can isolate internal network ports from client network. To do so, you route communication between the hosts
of a distributed environment onto a specified network and bind those internal network services exclusively to the
network interface.
In addition, this feature can now be used in the presence of a secondary site (system replication scenario).
However, note that additional ports used for communication between primary and secondary sites are opened on
the network interface. These ports need to be protected.
Note
In single-host scenarios, the same communication channels are used for communication between the different
processes on a single host. The internal IP addresses/ports are by default bound to the .local interface. Before
SPS 06, these ports were by default bound to all network interfaces.
Proceed as follows:
○ .local
Select this option to open the communication ports for internal usage on the local interfaces. This
configuration is only an option for single installations as the server is not reachable from outside. This
option does not require an internal network address entry.
○ .global
Select this option to bind the processes to all interfaces. This option does not require an internal network
address entry.
○ .internal
Select this option to bind the processes to this address only and to all localhost interfaces. This option
requires an internal network address entry.
If you select an option other than .local, the local interfaces will always be open.
5. Following the instructions in the wizard to execute the task.
You will find more information about SAP HANA system internal network and the network security
recommendations, in SAP HANA Update Master, SAP HANA Security Guide, and SAP HANA Administration
Guide.
Related Information
This topic provides information about how to manage products and transports.
Context
For more information, see the lifecycle manager chapter in SAP HANA Developer Guide SAP HANA Developer
Guide.
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. The necessary update content can be provided to the SAP HANA lifecycle manager in
the following ways:
● If the SAP HANA appliance has Internet access, the SAP HANA lifecycle manager can find and download
available updates from SAP Service Marketplace. In this case, you can update your SAP HANA system
without leaving the SAP HANA studio. This is described in the section Performing an Automated Update.
● If the SAP HANA appliance does not have Internet access, you can find and download the updates manually
from SAP Service Marketplace. In this case, you have to provide the location of the downloaded content to the
SAP HANA lifecycle manager for SAP HANA. This is described in the section Performing an Automated
Update.
● If you have SAP Solution Manager, you can use it to update your SAP HANA system like other SAP systems in
your landscape. In this case, you have to register your SAP HANA system using the System Landscape
Directory (SLD). For more information, see Configuring an SAP HANA System to Connect to the System
Landscape Directory [page 21]. Once this configuration is performed, the SAP HANA database server will
regularly update the SLD with data about your SAP HANA system. Afterwards, SAP Solution Manager can
access this data to calculate updates for this system. You can then use the Maintenance Optimizer (MOPZ) in
SAP Solution Manager to generate an SPS and download the necessary archives to a specified location. For
more information, see SAP Solution Manager documentation. You can then provide the SPS location to the
SAP HANA lifecycle manager and it will apply it on the system.
● If you intend to execute the use case with Internet access, perform the following configuration. The SAP
HANA system needs access to the SAP Service Marketplace using HTTPS, unless you have already
downloaded and copied the target stack to your SAP HANA system. For more information about using HTTPS
to connect to SAP Service Marketplace, see: Setting Up the SAP HANA Studio.
Caution
S-User is required
You can perform an automated update of SAP HANA using the SAP HANA lifecycle manager (HLM) user
interface, or with the command line interface. More information and examples for the command line you can find
at the end of this topic. To perform an automated update using the HLM user interface, typically through SAP
HANA studio, follow the procedure below:
Procedure
1. In your SAP HANA studio, add the system to which you want to connect.
Note
Use the fully qualified host name for all configuration actions (including Add System).
2. In the context menu of the system node in the SAP HANA Systems view, choose Lifecycle Management.
If you have not previously defined them, you need to enter the user credentials for <SID>adm user when you
call the SAP HANA lifecycle manager user interface for a specific SAP HANA system for the first time.
○ User <SID>adm
○ You need to enter the user and password when calling the SAP HANA Update user interface for the
first time.
○ You can change the user and password in the context menu for the added system under Properties
SAP System Logon .
○ You can delete the user and password under Windows Preferences General Security
Secure Storage .
On the HLM user interface, you can choose the following options in the Update SAP HANA System field:
After you have selected the update scenario (apply SPS or Single SP), you need to select the source for the
update from the Select the update source field:
○ Stack.xml file – XML file containing a model of SAP HANA in the form of product instances,
components, and their versions.
○ IMDB_SERVER*.SAR, IMDB_CLIENT*.SAR, IMC_STUDIO*.SAR, HANALDCTR*.SAR (optionally,
if you need it), SAPHOSTAGENT*.SAR – archives containing new content needed for the update
of the SAP HANA instances.
When updating to an SPS, you can download the files listed above from the SAP Service Marketplace at:
http://service.sap.com/swdc -> Support Packages and Patches-> Search for Support Packages and
Patches ->Search for IMDB Server for example. Make sure you do the same for the required archives,
depending on the component you want to update (IMDB_SERVER*.SAR, IMDB_CLIENT*.SAR,
IMC_STUDIO*.SAR, HANALDCTR*.SAR, SAPHOSTAGENT*.SAR). When downloading your preferred version,
make sure that the selected archive is suitable for your operating system.
All archives must be located in the same directory as the stack.xml file.
For information about using the Maintenance Optimizer (MOPZ) in SAP Solution Manager to generate an SPS
and download the necessary archives, see SAP Solution Manager documentation.
3. During the update, if you are prompted for them, enter the user name and password for the <SID>adm user.
4. Select the proposed software releases.
5. Select the type of the source SAP HANA system. You have the following options:
○ Normal
Select this option if you are updating components of a regular SAP HANA system that is not running in a
high-availability environment. The system database must be running.
○ Primary
Select this option if the SAP HANA system whose components you are updating is a primary system in a
high-availability setup. This scenario requires you to stop your system database before you perform the
update. During the update, SAP HANA content such as SAP HANA SHINE, SAP HANA EPM Service, SAP
HANA INA toolkit, and SAP HANA RDL cannot be deployed. Be aware that in this scenario you cannot
update your SAP HANA studio repository.
○ Secondary
Select this option if the SAP HANA system whose components you are updating is a secondary system in
a high-availability setup. During the update, SAP HANA content such as SAP HANA SHINE, SAP HANA
EPM Service, SAP HANA INA toolkit, and SAP HANA RDL cannot be deployed. Be aware that in this
scenario you cannot update your SAP HANA studio repository.
6. Follow the instructions of the wizard.
7. If you want to update your SAP HANA studio to the same version as your SAP HANA system, you need to
refer to the corresponding documentation.
For more information, see SAP HANA Database - Studio Installation and Update Guide.
Example
For more information about using the command line, see Using SAP HANA Lifecycle Manager in Command Line
Mode [page 8].
Prerequisites
You can use the SAP HANA lifecycle manager to update a distributed system (one SID on multiple hosts).
For more information about how to install a distributed system, see Adding Hosts to and Removing Hosts from an
Existing SAP HANA System [page 26].
This section provides additional details when you have a distributed SAP HANA landscape. In a landscape of this
type, you have one primary SAP HANA host and several secondary SAP HANA hosts.
Depending on your SAP Host Agent version, for each host of the distributed system, you might need to enter the
SAP <SID>adm password in the user interface.
You can also use the SAP HANA lifecycle manager in the case of additionally added SAP HANA systems on a
single SAP HANA appliance (multiple SIDs on one host). In this case, the tool updates only one SID. To update the
rest of the SIDs, you need HLM installed per each SID. For more information about how to create such a system,
see Adding Additional SAP HANA Systems on a Single SAP HANA Appliance [page 24].
This section describes how to add an Application Function Library (AFL) using the SAP HANA lifecycle manager.
The AFL archive should be owned by the root user.
Prerequisites
The AFL component should have the same version as the SAP HANA DATABASE component. This leads to the
following possible variants:
● Patch SAP HANA AFLs to a higher patch number within the same SP (revision)
● Update both SAP HANA AFLs and SAP HANA DATABASE to higher SP (revision)
The SAP HANA lifecycle manager will not allow you to update SAP HANA AFLs and SAP HANA DATABASE to
different SP (revision) numbers.
Procedure
To add an AFL using the SAP HANA lifecycle manager user interface, follow the procedure below:
1. Open the SAP HANA lifecycle manager user interface.
2. Choose Add Application Function Library (AFL).
3. Specify the required entries by following the instructions in the wizard.
AFLs are not installed by default on your SAP HANA system. They can be added only with the SAP HANA lifecycle
manager. For more information, see Adding Application Function Libraries on an SAP HANA System [page 34].
This also means that you do not receive AFLs when you perform an automated update of your SAP HANA system
to a higher Support Package Stack (SPS) or Single Support Package, either. You need to add them with the SAP
For more information about these options, see Performing an Automated Update [page 30].
Note
The AFL component should have the same version as the SAP HANA DATABASE component. This leads to the
following possible variants:
● Patch SAP HANA AFLs to a higher patch number within the same SP (revision)
● Update both SAP HANA AFLs and SAP HANA DATABASE to higher SP (revision)
The SAP HANA lifecycle manager will not allow you to update SAP HANA AFLs and SAP HANA DATABASE to
different SP (revision) numbers.
1. Follow the procedure in Performing an Automated Update [page 30] until step 4.
2. Select the update source and browse to the location of the AFL.
3. Once the components' versions are displayed, including the version of the AFL, choose the <Run> button. For
some of the components you have the option to skip the update.
4. Follow the instructions in the wizard.
Note
Keep in mind that, after AFLs are updated, the SAP HANA database server is restarted.
You can add SAP liveCache applications (SAP LCA) using the SAP HANA lifecycle manager. This is currently only
supported for the integrated SAP liveCache, single-host scenario. The SAP LCA archive should be owned by the
root user.
Prerequisites
The SAP HANA LCAPPS component should be on the same SP (revision) as the SAP HANA DATABASE
component. This leads to the following possible variants:
● Patch SAP HANA LCAPPS to a higher patch number within the same SP (revision)
● Update both SAP HANA LCAPPS and SAP HANA DATABASE to a higher SP (revision)
The SAP HANA lifecycle manager will not allow you to update SAP HANA LCAPPS and SAP HANA DATABASE to
different SP (revision) numbers.
To add SAP LCA using the SAP HANA lifecycle manager user interface, follow the procedure below:
Procedure
SAP liveCache applications (SAP LCA) are not installed by default on your SAP HANA system. They can be added
only with the SAP HANA lifecycle manager. For more information, see Adding SAP liveCache Applications on an
SAP HANA System [page 35].
This also means that you do not receive SAP LCA when you perform an automated update of your SAP HANA
system to a higher Support Package Stack (SPS) or Single Support Package, either. You need to add them with
the SAP HANA lifecycle manager, and you can then update them with the general options, either using SPS, or
Single Support Package.
For more information about these options, see Performing an Automated Update [page 30].
Note
The SAP HANA LCAPPS component should be on the same SP (revision) as the SAP HANA DATABASE
component. This leads to the following possible variants:
● Patch SAP HANA LCAPPS to a higher patch number within the same SP (revision)
● Update both SAP HANA LCAPPS and SAP HANA DATABASE to a higher SP (revision)
The SAP HANA lifecycle manager will not allow you to update SAP HANA LCAPPS and SAP HANA DATABASE
to different SP (revision) numbers.
1. Follow the procedure in Performing an Automated Update [page 30] until step 4.
2. Select the update source and browse to the location of SAP LCA.
3. Once the components' versions are displayed, including the version of the SAP LCA, choose the <Run>
button. For some of the components, you have the option to skip the update.
4. Follow the instructions in the wizard.
Procedure
To add SAP HANA smart data access (SDA), use the SAP HANA lifecycle manager. To do this using the tool's user
interface, follow the procedure below. The version of the SAP HANA database should be SPS 06 or higher. The
SDA archive should be owned by the root user. You can also execute an update of this component by following the
general update procedure.
1. Open the SAP HANA lifecycle manager user interface.
2. Choose Add SAP HANA smart data access (SDA).
3. Specify the required entries by following the instructions in the wizard.
This section describes how to deploy application content with the SAP HANA lifecycle manager (HLM).
Prerequisites
HLM provides the possibility of deploying additional content to your SAP HANA system.
The following procedure describes the general method of SAP HANA content deployment.
Use the DVD ZIP file format. In case the archive contains more than one product instances, select the product
instance to be deployed.
Procedure
Example
You can also use command line to deploy SAP HANA content. For more information, see Using SAP HANA
Lifecycle Manager in Command Line Mode [page 8]. You can also review the following examples:
Related Information
The SAP HANA studio has a dedicated view for errors - Error Log view. You can find the same information in the
following file:
<user_home_dir>/hdbstudio/.metadata/.log.
SAP Notes
You can also refer to the central SAP HANA lifecycle manager (HLM) SAP Note 1820588 .
For more information about how HLM replaces SUM for SAP HANA, see SAP Note 1836498 .
For more information about how to proceed in case of issues when starting SAP HANA lifecycle manager from
SAP HANA studio, see SAP Note 1896320 .
Important Notes
Note
Keep in mind that if you use SUM for HANA, in all versions after Single SP 03 for SPS 05, the system directory
structure of the SAP HANA system is changed, and the SAP HANA client, SAP HANA studio, SAP HANA studio
repository, and lm_structure file are moved under the shared_directory/<SID> (usually, /hana/shared/
<SID>). This is also relevant for SAP HANA lifecycle manager SPS 06. For example:
● /hana/shared/<SID>/hdbclient
● /hana/shared/<SID>/hdbstudio
● /hana/shared/<SID>/hdbstudio_update
● /hana/shared/<SID>/lm_structure
All new SAP HANA system installations after Single SP 03 for SPS 05 use the new system directory structure.
Since SPS 06 SAP HANA systems can be only Platform edition. You have the following cases:
● Updating from SAP HANA SPS 05 Enterprise edition to SAP HANA SPS 06. In this case you need to use the
SAP HANA On-Site Configuration tool to change the SAP HANA edition to Platform.
● Updating from a version prior to SAP HANA SPS 05. You also need to change the system edition to Platform.
In this case, refer to the following SAP Note:1794465 .
● You have installed SAP HANA lifecycle manager SPS 06 or SPS 07 in your system. In this case, the edition has
been adjusted to Platform automatically, during the HLM installation.
● You can use the following CSS component for error messages BC-HAN-UPD.
● In case of a landscape with multiple SAP HANA systems, make sure you have HLM isntalled per each SID.
Otherwise, the update of the landscape is not possible.
● If SAP HANA lifecycle manager (HLM) is not installed on the SAP HANA system, download the latest version
of HLM from SAP Service Marketplace (SMP). Extract the archive in the temporary folder, using SAPCAR.
After that, start installation of HLM as a root user, using <extracted_hlm>/hdbinst –s <SID_ID>.
● SAP HANA database versions before revision 20 do not support direct update to the latest revision. In such
cases first update your SAP HANA database to revision 20.
● If you receive a message saying that you are unable to connect to SAP HANA lifecycle manager, make sure
you add the SAP HANA system using its fully qualified name.
● For Windows operating systems (OS), we recommend that you use SAP HANA studio working mode. In case
of problems, you can use the standalone browser working mode as a workaround.
● For Linux-based systems only: If during an update choosing SAP Notes on dialogs or opening links does not
work, connect to HLM by using a supported standalone Web browser. The reason for this is that as of SPS07,
SAP HANA studio blocks pop-up windows and does not allow opening URLs when used under Linux.
● We recommend you not to use the Software Update Manager (SUM) and HLM at the same time, as this could
lead to inconsistencies in the system.
● If your SAP HANA studio does not start check the version of installed XULRunner, proceed as follows:
Open hdbstudio.ini file and add the following row:
If you have a version lower than 1.9.2, you have to set the correct version:
-Dorg.eclipse.swt.browser.XULRunnerPath=<xulrunner path>/<xulrunner version>
● To refresh the Lifecycle Management perspective, close it and start it again. We recommend that you restart
the perspective in situations where the executed scenario UI does not react as expected. Or in case you see a
blank screen in the place of the scenario UI, from its context menu choose Refresh. The system reloads the
scenario UI. In situations where you get a system message like “Cannot start new operation. Operation 'XXX'
is already running.”, you will only be able to restart and reconnect to the SAP HANA lifecycle manager once
the specified operation has ended.
● Unable to start SAP HANA lifecycle manager from SAP HANA studio
Check in the error log if the following error occurred:
com.sap.ndb.studio.lcm.upd.ui.hostcontrol.ex.SAPHostControlException: Could not check credentials
provided for user <user> on host <host> com.sun.xml.internal.ws.client.ClientTransportException: HTTP
transport error: java.io.IOException: HTTPS hostname wrong: should be <host>
This section describes how to manually add SAP HANA lifecycle manager (HLM) to your SAP HANA system. In
this case, you download the HLM archive from SAP Service Marketplace.
Context
Procedure
1. Download the latest SAP HANA lifecycle manager (HLM) archive from SAP Service Marketplace. To do this,
use the following link in the SAP Service Marketplace: http://service.sap.com/swdc -> Support Packages
and Patches-> Search for Support Packages and Patches, where you need to search for <HANA Lifecycle
Manager>. The archive should be named SAPHANALM*.SAR.
2. Extract the archive.
3. Run the command as root user: /<HLM_extracted_dir>/hdbinst
During the manual installation of SAP HANA lifecycle manager, you can optionally configure the tool to skip the
generation of SAP Host Agent certificates so that you can use your own ones.
Prerequisites
Context
By default, SAP HANA lifecycle manager generates SAP Host Agent certificates and stores them in
the /usr/sap/hostctrl/exe/sec directory. Custom SAP Host Agent certificates already available in
the /usr/sap/hostctrl/exe/sec directory are kept unless these certificates are for a host different from the
host of the SAP HANA lifecycle manager.
Procedure
1. Skip the generation of SAP Host Agent certificates. To do so, during the manual installation of SAP HANA
lifecycle manager, execute the following command: ./hdbinst --skip_certificates_generation.
Note
You can configure SAP HANA lifecycle manager to skip the generation of SAP Host Agent certificates only
during the manual installation of the tool.
2. Generate your own SAP Host Agent certificate or use an already existing one:
The SAP Host Agent is restarted. The newly created SAP Host Agent certificate is stored in
the /usr/sap/hostctrl/exe/sec directory.
○ To use already existing SAP Host Agent certificates, proceed as follows:
Links are provided here to documentation for the current Support Package Stack of the SAP HANA Platform
Edition, on the SAP Help Portal, and for previous Support Package Stacks, on the SAP HANA Knowledge Center
on SAP Service Marketplace.
For information about SAP HANA landscape, security, installation, and administration, see the resources listed
below:
SAP HANA administration and se SAP HANA Knowledge Center http://help.sap.com/hana_platform:
curity on the SAP Help Portal
● SAP HANA Technical Operations
Manual
● SAP HANA Administration Guide
● SAP HANA Security Guide
SAP HANA documentation for pre SAP HANA Knowledge Center https://service.sap.com/hana
vious Support Package Stacks on SAP Service Marketplace
Caution: Check regularly to see which SAP Notes are available for the SAP HANA lifecycle manager.
Check the current SAP Notes for the SAP HANA lifecycle manager by searching for the following CSS
components:
● BC-HAN-UPD
● BC-DB-HDB-HLM (for releases prior to SAP HANA SPS 07)
6.5 Security
User Credentials
To perform its tasks, the SAP HANA lifecycle manager needs credentials for the following users:
The SAP HANA lifecycle manager does not save these credentials. These credentials are sent only through
encrypted communication channels using HTTPS. For more information about how to perform SSL configuration
for SAP Host Agent, see http://help.sap.com/saphelp_nw74/helpdata/en/6a/
ac42c2e742413da050eaecd57f785d/content.htm?frameset=/en/f9/50aeeb64604e818b24626d287b63b0/
frameset.htm
Communication Channels
The SAP HANA Lifecycle Manager communicates with the following components:
Coding Samples
Any software coding and/or code lines / strings ("Code") included in this documentation are only examples and
are not intended to be used in a productive system environment. The Code is only intended to better explain and
visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness
of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code,
unless damages were caused by SAP intentionally or by SAP's gross negligence.
Accessibility
The information contained in the SAP documentation represents SAP's current view of accessibility criteria as of
the date of publication; it is in no way intended to be a binding guideline on how to ensure accessibility of software
products. SAP specifically disclaims any liability with respect to this document and no contractual obligations or
commitments are formed either directly or indirectly by this document.
Gender-Neutral Language
As far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed
directly with "you", or a gender-neutral noun (such as "sales person" or "working days") is used. If when referring
to members of both sexes, however, the third-person singular cannot be avoided or a gender-neutral noun does
not exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the
documentation remains comprehensible.
Internet Hyperlinks
The SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint
about where to find related information. SAP does not warrant the availability and correctness of this related
information or the ability of this information to serve a particular purpose. SAP shall not be liable for any damages
caused by the use of related information unless damages have been caused by SAP's gross negligence or willful
misconduct. Regarding link classification, see: http://help.sap.com/disclaimer