sap hana update and configuration guide en

7/21/2019 SAP HANA Update and Configuration Guide En

1/34

PUBLIC

SAP HANA Platform SPS 06Document Version: 1.0 - 26-06-2013

SAP HANA Update and Configuration Guide


2/34


3/34

1 Introduction

The SAP HANA lifecycle manager is the tool for customizing your SAP HANA system. This section providesinformation about the general use cases of the SAP HANA lifecycle manager and its positioning among the SAP

HANA components.

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:


Introduction

P U B L I C 2013 SAP AG or an SAP affiliate company. All rights reserved. 3


4/34

4P U B L I C 2013 SAP AG or an SAP affiliate company. All rights reserved.


Introduction


5/34

2 Preparing SAP HANA Lifecycle Manager

This section provides information about possible use cases of the SAP HANA lifecycle manager (HLM) and thenecessary initial and preparation steps.

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.

2.1 Getting Started with SAP HANA Lifecycle Manager in theAvailable Working Modes

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:

Using SAP HANA studio

Using the command line Using a standalone browser

2.1.1 Using SAP HANA Lifecycle Manager Through SAPHANA Studio

This section provides information on how to use the SAP HANA lifecycle manager (HLM) through the SAP HANA

studio.

Context

Keep in mind that, to work with the HLM, you need to make certain configuration settings for the SAP HANA

studio. There are also certain browser restrictions. For more information, seeSetting up the SAP HANA Studio

[page 10].

The figure below shows how to ensure you have the HLM, which you intend to use through the SAP HANA studio.


Preparing SAP HANA Lifecycle Manager



6/34

The figure above is described in the following procedure:

1. Install/update to the latest available SAP HANA studio. You need SAP HANA studio revision 60 as aminimum. For more information, see SAP HANA Studio Installation 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 chooseAdd

System. Alternatively, you can use the SAP HANA studio that is installed by default on the SAP HANA system

in /hana/shared//hdbstudio. In that SAP HANA studio, call the context menu for the selected SAPHANA system, and choose Lifecycle Management.

2. In the SAP HANA studio, call the context menu for the selected SAP HANA system, and choose LifecycleManagement. If the editor opens and you see the SAP HANA lifecycle manager, you already have the HLM

installed and running in the back end.

3. You can continue and use the HLM.4. If you do not see the HLM editor, check if your browser is HTML 5-enabled. You need as a minimum Internet

Explorer version 9 or Firefox version 13.

5. Check if the HLM is installed. If it is, see the Troubleshooting section in the guide. For more information, seeTroubleshooting [page 29]. If the tool is not installed, continue with this procedure.



http://help.sap.com/hana/SAP_HANA_Studio_Installation_Guide_en.pdf


7/34

6. If you have to install the HLM on an installed SAP HANA system, you need to download the latest HLMinstaller, which is available on SAP Service Marketplace, and start the installation on the SAP HANA system.

For more information, see Manually Adding SAP HANA Lifecycle Manager [page 32].

7. Upgrade your Internet Explorer (IE) to version 9 (or higher), or use the SAP HANA studio on the server.8. Refer to the Troubleshooting section in the guide. For more information, see Troubleshooting [page 29].

2.1.2 Using SAP HANA Lifecycle Manager in Command LineMode

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:





8/34

Procedure

1.Log on as the adm user.2. Navigate to the SAP HANA installation folder. In most cases, it is the default one: /hana/shared/.

3. Check whether the /HLM subfolder exists.4. If the /HLM subfolder does not exist, install the latest HLM (see step 7). If the subfolder exists, execute : ./

hlmcli.sh --help sidadm_pwd .

We strongly recommend that you call the help to familiarize yourself with the available call options and their

descriptions.

5. Check that the help is displayed properly. If not, review the Troubleshooting section.Troubleshooting [page29]

6. Start using the HLM from the command line in accordance with the instructions you have reviewed in the help(./hlmcli.sh --help sidadm_pwd ) . If you do not want to enter your password here, enter ahyphen (-) at the end of the command, and the tool requests the password interactively.

7. Install the HLM. For more information, see Manually Adding SAP HANA Lifecycle Manager [page 32].8. Review the Troubleshooting section. For more information, see Troubleshooting [page 29]

2.1.3 Using SAP HANA Lifecycle Manager in StandaloneBrowser Mode

This section provides details about how to use the SAP HANA lifecycle manager (HLM) in a standalone browser.

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:





9/34

Make sure you review the following browser requirements:

For Microsoft Windows, you need Internet Explorer version 9 or above. 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 above. We recommend that you install XULRunner 1.9.2 (or newer)

separately, but if you have already installed Firefox 3.6 (or newer), it contains XULRunner 1.9.2.

To use the tool from a standalone browser, call the following URL:

https://:1129/lmsl/HLM//ui/?sid=.

Make sure you use the fully qualified name of the SAP HANA system, such as myhost.sap.com (not just myhost).

You need to start the HLM in advance. You might need to wait for a minute while the necessary data is loaded and

then choose Refresh in your browser.





10/34

Procedure

1. Enter the HLM URL in your HTML5-enabled browser.2. Check if the HLM start page is displayed.3. If it is, start using the HLM in the browser.4. If the HLM start page is not displayed, check that you have the HLM installed. If it is, see the HLM

Troubleshooting section. For more information, see Troubleshooting [page 29]

5. If you do not have the tool available, you need to install it. For more information, see Manually Adding SAPHANA Lifecycle Manager [page 32].

6. Review the HLM Troubleshooting section. For more information, see Troubleshooting [page 29]

2.1.4 Setting up the SAP HANA Studio

The following prerequisites have to be fulfilled:

The SAP HANA lifecycle manager is installed in the SAP HANA system in the directory /hana/shared/

/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.

1. Choose Manual from theActive Provider list.2. Click on HTTPS and choose Edit.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:

Table 1: Proxy entries

Schema Host Port Provider Auth UserHTTP Manual false

HTTPS Manual false

SOCKS Manual false

HTTP proxy 8080 Native false

HTTPS proxy 8443 Native false

Table 2: Proxy bypass

Host ProviderLocalhost Manual





11/34

Host Provider127.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 .

Using Required Browsers

Direct access to the SAP HANA lifecycle manager is only possible using SAP HANA studio, which is only

compatible with certain web browser versions.

For Microsoft Windows, you need Internet Explorer version 9 or above. 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 newer. We recommend that you install XULRunner 1.9.2 (or above)

separately but if you have already installed Firefox 3.6 (or above), it contains XULRunner 1.9.2.

The system propertyorg.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//hdbstudio,

or /usr/sap/hdbstudio for older versions.

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, when you perform this step.

Configuring the connection to SAP Service Marketplace Using the Lifecycle

Management Perspective

You need to perform this configuration before you open the HLM editor. If you have access to the Internet on your

SAP HANA appliance and you intend to use the SAP Service Marketplace, perform the following configuration.

1. Open the SAP HANA studio.2. Choose Window Preferences Lifecycle Management Service Marketplace .3. Choose Use SMP configuration.





12/34


13/34

3 Managing the Lifecycle of SAP HANA

This section is the entry point for the possible SAP HANA reference operation scenarios and the available SAPHANA lifecycle management options.

Before you customize your SAP HANA system, review the possible reference scenarios. For more information,

see Reference Operation Scenarios for SAP HANA [page 13].

Afterwards, you can continue with the following options:

You can perform custom configuration of your SAP HANA system. For more information, see Configuring SAP

HANA with SAP HANA Lifecycle Manager [page 15].

You can update your SAP HANA system. For more information, see Updating an SAP HANA System with the

SAP HANA Lifecycle Manager [page 21].

You can manage SAP HANA components and application content. For more information, see Managing SAPHANA Components and Application Content [page 25].

3.1 Reference Operation Scenarios for SAP HANA

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 stronglyrecommended options for your SAP HANA system.

You can operate SAP HANA in one of the following scenarios:

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:


Managing the Lifecycle of SAP HANA



14/34

For more information about how to set up a scenario of this type, see Adding Hosts to and Removing Hosts

from an Existing SAP HANA System [page 20] in the Configuring SAP HANA with SAP HANA Lifecycle

Managersection .

Multi-SID SAP HANA scenario. The illustrated scenario is typically used for non-productive landscapes. It issuitable for test purposes with restricted hardware parameters. The figure below provides an example of a

scenario of this type:

For more information about how to set up a scenario of this type, see Adding Additional SAP HANA Systems

on a Single SAP HANA Appliance [page 18] and Removing Additionally-Added SAP HANA Systems From a

Single SAP HANA Appliance [page 19] in the Configuring SAP HANA with SAP HANA Lifecycle Manager

section .





15/34

Hybrid SAP HANA scenario. This scenario is a combination of the two scenarios above. It provides more

flexibility and customization in relatively complex SAP HANA scenarios. The figure below provides an example

of a scenario of this type:

3.2 Configuring SAP HANA with SAP HANA Lifecycle

Manager

You can use the SAP HANA lifecycle manager to customize your SAP HANA system. You can do so after the initial

installation with the SAP HANA unified installer is finished. 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.

3.2.1 Renaming an SAP HANA System

Context

You can use the rename feature to:

Change the SID, instance number, and host name

Change the system administrator password

Change the database user password

Make sure you meet the following prerequisites:





16/34

The target system ID (SID) must not exist.

The target instance number must not exist.

The root password is not mandatory because if a trusted connection is available, the password is not needed.

The adm user password must contain only ASCII symbols and be at least 8 characters long, and

must contain at least one digit, one lowercase character, and one uppercase character. Only the following

three special characters are allowed: $ _ #.

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 (under /hana/shared//hdbstudio), as this could lead to inconsistency.

To rename your SAP HANA system, follow the procedure below.

If you specify the host name, make sure that it is fully qualified, such as myhost.sap.com (not just myhost).

Procedure

1. Open the SAP HANA lifecycle manager user interface.2. Choose Rename SAP HANA System.3. Specify the required entries by following the instructions in the wizard.

3.2.2 Configuring SAP Landscape TransformationReplication

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 process Configure SAP Landscape Transformation (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



http://help.sap.com/hanahttp://help.sap.com/hana


17/34

Activation of ICF and Web Dynpro services

The process automates the post-installation configuration steps after obtaining the required input from the end

user in consecutive steps. The process currently only automates the configuration of one SAP source system at a

time .

To use this feature, follow the procedure below:

Procedure

1. Open the SAP HANA lifecycle manager user interface.2. Choose Configure SAP Landscape Transformation Replication.3. Specify the required entries by following the instructions in the wizard.

3.2.3 Configuring an SAP HANA System to Connect to theSystem Landscape Directory

This section provides information about how to set up a connection to the System Landscape Directory (SLD).

Prerequisites

You can use the function provided to configure the connection parameters for 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.

For more information, see SAP Notes1673424 and1649323.

Procedure

1. Open the SAP HANA lifecycle manager user interface.2. Choose Register in System Landscape Directory.3. Specify the required entries by following the instructions in the wizard.

3.2.4 Adding a Solution Manager Diagnostics Agent on anSAP HANA System

This section describes how to add a Solution Manager Diagnostics (SMD) agent using the SAP HANA lifecycle

manager.



https://service.sap.com/sap/support/notes/1649323https://service.sap.com/sap/support/notes/1673424


18/34

Context

To add an SMD agent using the SAP HANA lifecycle manager user interface, follow the procedure below.

If you specify the host name, make sure that it is fully qualified, such as myhost.sap.com (not just myhost). The

SMD adm user password must contain only ASCII characters and must be at least 8 characters long.

Procedure

1. Open the SAP HANA lifecycle manager user interface.2. Choose Add Solution Manager Diagnostics Agent (SMD).3. Specify the required entries by following the instructions in the wizard.

3.2.5 Adding Additional SAP HANA Systems on a Single SAPHANA Appliance

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

To add additional SAP HANA systems on a single appliance using the SAP HANA lifecycle manager user interface,

follow the procedure below.

If you specify the host name, make sure that it is fully qualified, such as myhost.sap.com (not just myhost).

Context

Procedure

1. Open the SAP HANA lifecycle manager user interface.2. Choose Add SAP HANA System.3. Specify the required entries by following the instructions in the wizard.





19/34

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).

3.2.6 Removing Additionally-Added SAP HANA SystemsFrom a Single SAP HANA Appliance

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.

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.

We strongly recommend not to remove a SAP HANA system using SAP HANA studio belonging to this SAP

HANA system (under /hana/shared//hdbstudio), as this could lead to some inconsistency.

Procedure

1. Open the SAP HANA lifecycle manager user interface.2. Choose Remove SAP HANA System, and choose Next to continue.3. Specify the required entries by following the instructions in the wizard.





20/34


21/34

Context

Currently the corresponding information is part of SAP HANA Developer Guide.

For more information, see the SAP HANA lifecycle manager chapter in SAP HANA Developer Guide SAP HANA

Developer Guide.

3.3 Updating an SAP HANA System with the SAP HANALifecycle Manager

You can perform an automated update of an SAP HANA system with the SAP HANA lifecycle manager. Theupdate 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 inyour 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 17]. 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.

Prerequisites for SAP HANA Lifecycle Manager

In the SAP HANA system, the following prerequisites have to be fulfilled:

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



http://help.sap.com/saphelp_sm71_sp05/helpdata/en/af/50658171124b94bfa8afc004ffe693/frameset.htmhttp://help.sap.com/saphelp_sm71_sp05/helpdata/en/af/50658171124b94bfa8afc004ffe693/frameset.htmhttp://help.sap.com/hana/SAP_HANA_Developer_Guide_en.pdfhttp://help.sap.com/hana/SAP_HANA_Developer_Guide_en.pdf


22/34

For more information about downloading the required content if you do not use SAP Service Marketplace, see

step 2 of Performing an Automated Update.

You have stopped the data replication before you start the automated update.

You have performed a system backup before you start the automated update. Also note that during theautomated update there is a business downtime for your SAP HANA system.

You know the adm, sapadm, and database administrator passwords.

You have applied a valid license key to the SAP HANA system.

The SAP HANA database is up and running.

The SAP Host Agent is up and running.

3.3.1 Performing an Automated Update

You can perform an automated update of SAP HANA using the SAP HANA lifecycle manager (HLM) user interface

(which you can access using the SAP HANA studio or in a standalone browser), or with the command line

interface. For more information about using the command line interface, see the dedicated topic that describes

this working mode, where you can find instructions on how to display the help and on how to review the available

options. 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 adm when you call

the SAP HANA lifecycle manager user interface for a specific SAP HANA system for the first time.

The following users and settings are needed:

User 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:

Update SAP HANA Lifecycle Manager (HLM)





23/34

We strongly recommend that you execute the tool self-update using the Update SAP HANA Lifecycle

Manager user interface option.

Keep in mind that if you do not have Internet access (for example, for security reasons), you need to

select Manually downloaded content as the source, and you need to have the relevant file alreadyavailable. You can download the newest archive available for this file, SAPHANALM*.SAR, in advance.

You have to download SAPHANALM*.SAR separately using 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.

Note that you need to provide the full path to the file, not the containing directory.

If you have Internet access, the self-update of the HLM can be executed automatically when you choose

the Update SAP HANA Lifecycle Manager (HLM) option. In this case, the SAP HANA studio needs to be

configured to work properly with SAP Service Marketplace.

Apply Support Package Stack (SPS - recommended scenario)

You can update all software components of SAP products that are deployed on the system by applying a

support package stack. Support package stacks are collections of support packages for softwarecomponents defined by SAP that work best together.

With this scenario, you can execute an update to a set of SAP HANA components defined by the SPS. This

scenario ensures smooth and consistent update.

Apply Single Support Packages (Single SP)

If you want to update only particular software components that are deployed on the system and do not

want to apply complete support package stacks, you can apply single support packages.

The user interface will provide information about installed components versions, as well the newer

(target) ones that are available. You can select the component version to which you want to update. If you

have selected SAP Service Marketplace as an update source, the SAP HANA lifecycle manager offers

updates only for components that are part of the SAP HANA product.

After you have selected the update scenario (apply SPS or Single SP), you need to select the source for theupdate from the Select the update source field:

Automatically downloaded content (SAP Service Marketplace)

The content is automatically downloaded from SAP Service Marketplace. In this case, SAP Service

Marketplace offers new SP versions, not Single SPs.

Manually downloaded content

In this case, you need to manually download the following files to any directory accessible by the

adm user in the SAP HANA system:

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-> Browse our Download Catalog -> SAP

NetWeaver and complementary products -> SAP HANA -> SAP HANA Platform Edition ->Support Package

Stack Download.

When updating to a Single SP (this means different components' versions) use:

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,



http://service.sap.com/swdchttp://service.sap.com/swdchttp://service.sap.com/swdc


24/34

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 adm.4. Select the proposed software releases.5. Follow the instructions of the wizard.6. 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.

3.3.2 Performing an Automated Update in a DistributedSystem and in a Landscape with Multiple SAP HANA Systems

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 20].

This section provides additional details when you have a distributed SAP HANA landscape. In a landscape of thistype, 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 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 u pdates only one SID. For more

information about how to create such system, seeAdding Additional SAP HANA Systems on a Single SAP HANA

Appliance [page 18].



http://help.sap.com/hana/SAP_HANA_Studio_Installation_Guide_en.pdfhttp://help.sap.com/saphelp_sm71_sp05/helpdata/en/af/50658171124b94bfa8afc004ffe693/frameset.htm


25/34

4 Managing SAP HANA Components andApplication Content

This section provides information about how to manage additional SAP HANA components and applications.

4.1 Adding Application Function Libraries on an SAP HANASystem

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.

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 Functional Library (AFL).3. Specify the required entries by following the instructions in the wizard.

4.2 Performing Automated Updates for Application FunctionLibraries (AFLs)

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, seeAdding Application Function Libraries on an SAP HANA System [page 25].

This also means that you do not receive AFLs when you perform an automated update of your SAP HANA systemto 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 using the general update options, either using SPS, or

Single Support Packages.

For more information about these options, see Performing an Automated Update [page 22].

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)


Managing SAP HANA Components and Application Content



26/34

The SAP HANA lifecycle manager will not allow you to update SAP HANA AFLs and SAP HANA DATABASE to

different SP (revision) numbers.

To perform an update of AFLs, follow the procedure below:

1. Follow the procedure in Performing an Automated Update [page 22] 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 thebutton. 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.

4.3 Adding SAP liveCache Applications on an SAP HANASystem

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.

Context

To add SAP LCA using the SAP HANA lifecycle manager user interface, follow the procedure below:

Procedure

1. Open the SAP HANA lifecycle manager user interface.2. ChooseAdd liveCache Applications (LCApps).3. Specify the required entries by following the instructions in the wizard.





27/34

4.4 Performing an Automated Update for SAP liveCacheApplications

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 26].

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 22].

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.

To perform an update of SAP LCA, follow the procedure below:

1. Follow the procedure in Performing an Automated Update [page 22] 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

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 SAP LCA are updated, the SAP HANA database server is restarted.

4.5 Adding SAP HANA Smart Data Access

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 datab ase should be SPS 06.





28/34

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.

4.6 Deploying SAP HANA Application Content Using SAPHANA Lifecycle Manager

This section describes how to deploy application content with the SAP HANA lifecycle manager (HLM).

Prerequisites

SAP HANA database should be started

Make sure you are not using an SAP HANA database older than SPS 05.

Make sure you do not have inactive objects in your database before you deploy the content. You need to

activate or delete objects of this type.

Context

HLM provides the possibility of deploying additional content to your SAP HANA system.

The following procedure describes the general method of content deployment. You can use this function to deploy

content such as Business Suite New Analytics applications. Use the DVD ZIP file format.

Procedure

1. Open the SAP HANA lifecycle manager user interface.2. Choose Deploy HANA Content.3. Enter the required credentials and specify the location of the content archive.4. Choose the Run button. This transfers the product archive to the SAP HANA lifecycle manager server.

The SAP HANA lifecycle manager attempts to activate and deploy the corresponding SAP HANA content. You

will receive a notification in the summary page, even if there are activation issues.





29/34

5 Troubleshooting

Main Log File for SAP HANA Lifecycle Manager

The main log file in which issues are recorded is /usr/sap/hlm_bootstraps//HLM/log/hlm.log.

The log file with more technical information is /usr/sap/hlm_bootstraps//HLM/log/ljs.log.

Main Log File for SAP HANA Studio

The SAP HANA studio has a dedicated view for errors -view. You can find the same information in

the following file:

/hdbstudio/.metadata/.log.

Central SAP Note

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.

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 directorystructure 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 /hana/shared/ directory. This is also relevant for

SAP HANA lifecycle manager SPS 06. For example:

/hana/shared//hdbclient

/hana/shared//hdbstudio

/hana/shared//hdbstudio_update

/hana/shared//lm_structure

All new SAP HANA system installations after Single SP 03 for SPS 05 use the new system directory structure.


Troubleshooting

https://service.sap.com/sap/support/notes/1836498https://service.sap.com/sap/support/notes/1820588


30/34

Updating of SAP HANA Systems Older than SPS 06 (Enterprise and Enterprise

Extended Editions) to SAP HANA SPS 06

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.

Problems Using the SAP HANA Lifecycle Manager:

You can use the following CSN component for error messages BC-DB-HDB-HLM.

If SAP HANA Lifecycle manager (HLM) is not installed on the SAP HANA system, download latest version of

HLM from SAP Service Marketplace (SMP). Extract archive on temporary folder, using SAPCAR. Start

installation of HLM, using /installer/hdbinst s

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 system (OS), we recommend you to use SAP HANA studio working mode. In case of

problems, you can use the standalone browser working mode as a workaround. We recommend you not to use SUM and HLM at the same time, as this could lead to inconsistency.

If your SAP HANA studio does not start check the version of installed XULRunner.

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=/

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 on host com.sun.xml.internal.ws.client.ClientTransportException: HTTP

transport error: java.io.IOException: HTTPS hostname wrong: should be

The reason could be that the provided host name, when the system is added in the SAP HANA studio does not

match the host name in the generated certificate.

In order to solve this issue, check the host in the certificate and add the system in SAP HANA studio with the

same host name. In order to check the certificate, connect to SAP HANA lifecycle manager via standalone

browser. For more information, see Using SAP HANA Lifecycle Manager in Standalone Browser Mode [page 8].

Keep in mind that you can only work with one HLM at a time in a defined host landscape. Using more than one

HLM simultaneously, could lead to inconsistency and errors.



Troubleshooting
https://service.sap.com/sap/support/notes/1794465


31/34

If you open SAP HANA lifecycle manager editor and execute an operation, it will continuously use the focus

from the other views or editors in the studio, even if the editor is not currently visible. Wait for the operation to

finish before using the other SAP HANA studio functionality. If you want to use the SAP HANA studio while the

operation is running start SAP HANA lifecycle manager outside the SAP HANA studio, using HTML5-enabled browser. For more information, seeUsing SAP HANA Lifecycle Manager in Standalone Browser Mode

[page 8].

If you use HLM through SAP HANA studio, and if HLM does not start from the first time, you need to try

starting it again. This is a known issue relevant for SAP Host Agent version 152. In the upcoming versions this

issue will be fixed.


Troubleshooting



32/34

6 Appendix

6.1 Manually Adding SAP HANA Lifecycle Manager

This section describes how to manually add SAP HANA lifecycle manager (HLM) to your SA P 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. The archive should be named SAPHANALM*.SAR.

2. Extract the archive.3. Run the command as root user: //hdbinst

6.2 More Information

For more information about the SAP HANA landscape, security, installation, and administration, see the

resources listed in the table below.

Topic Guide/Tool Quick LinkSAP HANA Landscape Deployment

& Installation

SAP HANA Knowledge Center on

SAP Service MarketplaceSAP Service Marketplace

SAP HANA Administration &

Security

SAP HANA Knowledge Center on

SAP Help Portalhttp://help.sap.com/hana

SAP HANA Administration

Guide SAP HANA

Administration Guide

SAP HANA Security Guide SAP

HANA Security Guide

SAP HANA Master Guide

SAP HANA Installation Guide



Appendix
http://help.sap.com/hana/SAP_HANA_Installation_Guide_en.pdfhttp://help.sap.com/hana/SAP_HANA_Installation_Guide_en.pdfhttp://help.sap.com/hana/SAP_HANA_Master_Guide_en.pdfhttp://help.sap.com/hana/SAP_HANA_Security_Guide_en.pdfhttp://help.sap.com/hana/SAP_HANA_Security_Guide_en.pdfhttp://help.sap.com/hana/SAP_HANA_Administration_Guide_en.pdfhttp://help.sap.com/hana/SAP_HANA_Administration_Guide_en.pdfhttp://help.sap.com/hanahttps://websmp103.sap-ag.de/swdchttp://service.sap.com/swdc


33/34

6.3 Important SAP Notes

Caution: Check regularly to see which SAP Notes are available for the SAP HANA lifecycle manager.

SAP Note Number Title1820588 SAP Release Note for SAP HANA lifecycle manager

Check the current SAP Notes for the SAP HANA lifecycle manager by searching for the following CSS/CSN

components:

BC-DB-HDB-HLM.

6.4 Security

User Credentials

To perform its tasks, the SAP HANA lifecycle manager needs credentials for the following users:

sapadm used to authenticate with the SAP Host Agent

adm required by SAP HANA server update

SAP Service Marketplace user used to authenticate at SAP Service Marketplace

You can enter these credentials in the SAP HANA studio, where you have the option to save them in the Secure

Storage. For more information, see to the SAP HANA studio help. To do this, navigate to Workbench User Guide >

Reference > Secure Storage.

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

To enable internal communication through HTTPS, remove -Dhttp.hostcontrol.connection parameter from /

hana/shared//HLM/props.ini .

Communication Channels

The SAP HANA Lifecycle Manager communicates with the following components:

SAP HANA studio

SAP Host Agent

SAP Service Marketplace


Appendix

http://help.sap.com/saphelp_nw74/helpdata/en/6a/ac42c2e742413da050eaecd57f785d/content.htm?frameset=/en/f9/50aeeb64604e818b24626d287b63b0/frameset.htmhttp://help.sap.com/saphelp_nw74/helpdata/en/6a/ac42c2e742413da050eaecd57f785d/content.htm?frameset=/en/f9/50aeeb64604e818b24626d287b63b0/frameset.htmhttp://help.sap.com/saphelp_nw74/helpdata/en/6a/ac42c2e742413da050eaecd57f785d/content.htm?frameset=/en/f9/50aeeb64604e818b24626d287b63b0/frameset.htmhttp://help.sap.com/saphelp_nw74/helpdata/en/6a/ac42c2e742413da050eaecd57f785d/content.htm?frameset=/en/f9/50aeeb64604e818b24626d287b63b0/frameset.htmhttp://help.sap.com/saphelp_nw74/helpdata/en/6a/ac42c2e742413da050eaecd57f785d/content.htm?frameset=/en/f9/50aeeb64604e818b24626d287b63b0/frameset.htmhttp://help.sap.com/saphelp_nw74/helpdata/en/6a/ac42c2e742413da050eaecd57f785d/content.htm?frameset=/en/f9/50aeeb64604e818b24626d287b63b0/frameset.htmhttps://service.sap.com/sap/support/notes/1820588


34/34

www.sap.com/contactsap

2013 SAP AG or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any

form or for any purpose without the express permission of SAP AG.

The information contained herein may be changed without prior

notice.

Some software products marketed by SAP AG and its distributors

contain proprietary software components of other software

vendors. National product specifications may vary.

These materials are provided by SAP AG and its affiliated

companies ("SAP Group") for informational purposes only, without

representation or warranty of any kind, and SAP Group shall not be

liable for errors or omissions with respect to the materials. The only

warranties for SAP Group products and services are those that are

set forth in the express warranty statements accompanying such

products and services, if any. Nothing herein should be construed asconstituting an additional warranty.
http://www.sap.com/contactsap

sap hana update and configuration guide en

Documents