sap_hana_update_and_configuration_guide-good.pdf

PUBLICSAP HANA Platform SPS 07Document Version: 1.1 - 13-03-2014

SAP HANA Update and Configuration Guide

Table of Contents1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2 Preparing SAP HANA Lifecycle Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62.1 Getting Started with SAP HANA Lifecycle Manager in the Available Working Modes. . . . . . . . . . . . . . . . .6

2.1.1 Using SAP HANA Lifecycle Manager Through SAP HANA Studio. . . . . . . . . . . . . . . . . . . . . . . 62.1.2 Using SAP HANA Lifecycle Manager in Command Line Mode. . . . . . . . . . . . . . . . . . . . . . . . . .82.1.3 Using SAP HANA Lifecycle Manager in Standalone Browser Mode. . . . . . . . . . . . . . . . . . . . . 102.1.4 Setting up the SAP HANA Studio. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

3 Managing the Lifecycle of SAP HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.1 Reference Operation Scenarios for SAP HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.2 Configuring SAP HANA with SAP HANA Lifecycle Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

3.2.1 Renaming an SAP HANA System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183.2.2 Configuring SAP Landscape Transformation Replication. . . . . . . . . . . . . . . . . . . . . . . . . . . . 213.2.3 Configuring an SAP HANA System to Connect to the System Landscape Directory. . . . . . . . . 213.2.4 Adding a Solution Manager Diagnostics Agent on an SAP HANA System . . . . . . . . . . . . . . . . 233.2.5 Removing a Solution Manager Diagnostics Agent on an SAP HANA System. . . . . . . . . . . . . . 233.2.6 Adding Additional SAP HANA Systems on a Single SAP HANA Appliance . . . . . . . . . . . . . . . . 243.2.7 Removing Additionally Added SAP HANA Systems From a Single SAP HANA Appliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253.2.8 Adding Hosts to and Removing Hosts from an Existing SAP HANA System. . . . . . . . . . . . . . . 263.2.9 Configuring the SAP HANA System Internal Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273.2.10 Managing Products and Transports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28

3.3 Updating an SAP HANA System with the SAP HANA Lifecycle Manager . . . . . . . . . . . . . . . . . . . . . . . . 293.3.1 Performing an Automated Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303.3.2 Performing an Automated Update in a Distributed System and in a Landscape with Multiple SAP HANA Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33

4 Managing SAP HANA Components and Application Content. . . . . . . . . . . . . . . . . . . . . . . . . . . . .344.1 Adding Application Function Libraries on an SAP HANA System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344.2 Performing Automated Updates for Application Function Libraries (AFLs). . . . . . . . . . . . . . . . . . . . . . 344.3 Adding SAP liveCache Applications on an SAP HANA System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354.4 Performing an Automated Update for SAP liveCache Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . 364.5 Adding SAP HANA Smart Data Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .374.6 Deploying SAP HANA Application Content Using SAP HANA Lifecycle Manager. . . . . . . . . . . . . . . . . . 37

5 Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

6 Appendix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .426.1 Manually Adding SAP HANA Lifecycle Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426.2 Optional: Using Own SAP Host Agent Certificates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42

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

SAP HANA Update and Configuration GuideTable of Contents

6.3 SAP HANA Guides. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436.4 Important SAP Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .446.5 Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

7 Important Disclaimers on Legal Aspects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

SAP HANA Update and Configuration GuideTable of Contents

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

1 IntroductionThe SAP HANA lifecycle manager is the tool for customizing your SAP HANA system. This section provides information 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:


SAP HANA Update and Configuration GuideIntroduction

SAP HANA Update and Configuration GuideIntroduction


2 Preparing SAP HANA Lifecycle Manager This section provides information about possible use cases of the SAP HANA lifecycle manager (HLM) and the necessary 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 the Available 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 SAP HANA Studio

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 adm user. Make sure that the communication port 1129 is open. This port is required for the SSL communication with

the SAP Host Agent.


SAP HANA Update and Configuration GuidePreparing SAP HANA Lifecycle Manager

Context

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.

The figure above is described in the following procedure: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 //hdbstudio (usually,/hana/shared//hdbstudio.



2. In the SAP HANA studio, log on to the relevant system. To do so, double click it in the Systems view or from the context menu, choose Log On.

3. From the context menu of the selected system, choose Lifecycle Management. If you have not previously defined them, you need to enter the user credentials for adm user when you call the SAP HANA lifecycle manager user interface for a specific SAP HANA system for the first time. If the editor opens and you see the SAP HANA lifecycle manager, you already have the HLM installed and running in the back-end.

4. You can continue and use the HLM.5. If you do not see the HLM editor, check if your browser is HTML 5-enabled. For more information about the

browser requirements, see the Setting up the SAP HANA Studio section in this guide.6. Check if the HLM is installed. If it is, see the Troubleshooting section in the guide. For more information, see

Troubleshooting [page 39]. If the tool is not installed, continue with this procedure.7. If you have to install the HLM on an installed SAP HANA system, you need to download the latest HLM

installer, 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 42].

8. Upgrade your Web browser to the required version, or use the SAP HANA studio on the server.9. Refer to the Troubleshooting section in the guide. For more information, see Troubleshooting [page 39].

2.1.2 Using SAP HANA Lifecycle Manager in Command Line ModeThis 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:



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, under

//HLM/hlmcli execute: ./hlmcli.sh --helpWe strongly recommend that you call the help to familiarize yourself with the available call options and their descriptions. Keep in mind that if you use special characters in your password, it should be enclosed with quotation marks.

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

6. Start using the HLM from the command line in accordance with the instructions you have reviewed in the help (./hlmcli.sh --help).



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

If your scenario requires it, you can optionally set up an SSH two-factor authentication to distinguish between the users who use HLM command line mode with adm credentials. To do so, you can request SAP HANA administrators to log on to the SAP HANA appliance with their own logon user and use the su or the sudo Linux command to run the hlmcli executable as adm. If needed, checking logs of su or sudo commands may show the original adm user. For more information about the usage of su and sudo commands, see the respective Linux documentation. Use the commands according to the requirements of your scenario.

2.1.3 Using SAP HANA Lifecycle Manager in Standalone Browser ModeThis 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:



Make sure you review the following browser requirements: 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 ToolsCompatibility 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://:1129/lmsl/HLM//ui/index.html



NoteThe URL is case sensitive. Make sure you enter the upper and lower case correctly.

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

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 39]5. If you do not have the tool available, you need to install it. For more information, see Manually Adding SAP

HANA Lifecycle Manager [page 42].6. Review the HLM Troubleshooting section. For more information, see Troubleshooting [page 39]

2.1.4 Setting up the SAP HANA StudioThe following prerequisites have to be fulfilled: The SAP HANA lifecycle manager is installed in the SAP HANA system in the //

HLMdirectory. In most cases it is /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 GeneralNetwork 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 the Active 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 entriesSchema Host Port Provider Auth UserHTTP Manual false



Schema Host Port Provider Auth UserHTTPS Manual falseSOCKS Manual falseHTTP proxy 8080 Native falseHTTPS proxy 8443 Native false

Table 2: Proxy bypassHost ProviderLocalhost Manual127.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 .

Browser Requirements for SAP HANA Studio

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 ToolsCompatibility 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//hdbstudio., or /usr/sap/hdbstudio for older versions.

For iOS and OS X you need Safari 5.1 or higher.

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



Configuring the connection to SAP Service Marketplace Using the Lifecycle Management Perspective in SAP HANA Studio

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.1. Open the SAP HANA studio.2. Choose Window Preferences SAP HANA Lifecycle Management Service Marketplace .3. Choose Use SMP configuration.

Option DescriptionUse SMP configuration The Host Name is set to service.sap.com. This is

the URL of SMP, where the files that are used for the update are located.

Enter your SMP S-User credentials in User Name/Password.

NoteYou can obtain an S-User on SMP at https://service.sap.com -> Registration.

If you use a proxy, choose Use proxy server, and enter Host Name (max. length 64) and Port (port must be a number, maximum length 10).

The Use proxy authentication check box is only enabled if you have selected Use proxy server.

If you have selected Use proxy authentication, enter the User Name (max. length 64) and Password (max. length 64).

4. Choose Apply.5. Choose OK.

NoteTo reset your entries, choose Restore Defaults.



3 Managing the Lifecycle of SAP HANAThis section is the entry point for the possible SAP HANA reference operation scenarios and the available SAP HANA 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 15].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 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].

3.1 Reference Operation Scenarios for SAP HANAThis 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.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:

SAP HANA Update and Configuration GuideManaging the Lifecycle of SAP HANA


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 26] in the Configuring SAP HANA with SAP HANA Lifecycle Manager section .

Multi-SID SAP HANA scenario. The illustrated scenario is typically used for non-productive landscapes. It is suitable 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 24] and Removing Additionally Added SAP HANA Systems From a Single SAP HANA Appliance [page 25] in the Configuring SAP HANA with SAP HANA Lifecycle Manager section .

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 SAP HANA hdblcm or SAP HANA unified installer is finished.

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

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 passwordMake sure you meet the following prerequisites: 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: $ _ #.

If you change the database SYSTEM password you should not use any of the last five used passwords.

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

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.

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

--sid $SID --target_sid $RENAMED_SID --sidadm_pwd ******** --target_password ******** --number $RENAMED_INSTANCE_NUMBER --hostname $RENAMED_HOSTNAME

An automatic rename and move (mv) of data and log path is also supported in the SAP HANA lifecycle manager rename task , if 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:/hana/data/DEL -> /hana/data/P01/hana/log/DEL -> /hana/log/P01



NoteAn automatic rename would be performed if there is only one occurrence of in the absolute path of data and log volume paths.For example, if data path = /hana//data/, no automatic rename would be executed.

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.

SID Mounted in a File Storage on a Different Host (Optional)Context

NoteThe 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 -function StopSystemb) Stop the sapstartsrv service by using the following SAP Host Agent operation:

/usr/sap/hostctrl/exe/sapcontrol -nr function StopServicec) Create a new shared SID directory //.d) Unmount the current SID directory //.

2. On the host used for storage, rename the // to // directory.

3. On the host where SAP HANA is installed, perform the following actions:a) Mount // to the file storage host.b) Create a soft link from // to //.c) Start the sapstartsrv service. To do this, use the following SAP Host Agent operation:/usr/sap/hostctrl/exe/sapcontrol -nr function StartService



Results

Once all steps have been performed, you can proceed with the rename operation.

3.2.2 Configuring SAP Landscape Transformation ReplicationThis 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 servicesThe 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 .To use this feature, follow the procedure below:

Procedure

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

3.2.3 Configuring an SAP HANA System to Connect to the System Landscape DirectoryThis section provides information about how to set up a connection to the System Landscape Directory (SLD).



Context

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

For more information, see SAP Notes 1673424 and 1649323 .

Procedure

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

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

hlmcli.sh configure_sld --sld_user $SLD_USER --sld_password ****** --sld_host=$SLD_HOST --sld_port $SLD_PORT --sld_use_https y --sid $RENAMED_SID --sidadm_pwd ********

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 adm user, execute the following command: /usr/sap/hostctrl/exe/saposcol -b | sldreg -connectfile /usr/sap//SYS/global/slddest.cfg -stdin oldtransferdtd.



3.2.4 Adding a Solution Manager Diagnostics Agent on an SAP HANA System

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

Context

SAP HANA DVD should be owned by the root user.SAP HANA DVD should be on the same SPS level as the SAP HANA lifecycle manager.The SMD 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

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.

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

/hana/shared/$SID/HLM/hlmcli/hlmcli.sh add_smd --dvd_path /root/HANA_DVD/ --sid $SID --sidadm_pwd ******** --smd_sid $SMD_SID --smd_number $SMD_INSTANCE_NUMBER --target_host $HDBHOST --smd_virtual_host $HDBHOST --smd_user_password ******** --configure_sld_connection --smd_sld_host --smd_sld_port 50000 --smd_sld_user Administrator --smd_sld_password ********

3.2.5 Removing a Solution Manager Diagnostics Agent on an SAP HANA System

This section describes how to remove 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.To remove an SMD agent using the SAP HANA lifecycle manager user interface, follow the procedure below.

Procedure

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

ExampleAlternatively, 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:/hana/shared/$SID/HLM/hlmcli/hlmcli.sh remove_smd --dvd_path /root/HANA_DVD/ --sid $SID --sidadm_pwd ******** --smd_sid $SMD_SID --smd_number $SMD_INSTANCE_NUMBER.

3.2.6 Adding Additional SAP HANA Systems on a Single SAP HANA 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

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



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.

Next Steps

NoteYou have the option to specify a dedicated time zone. By default, the time zone is set to UTC (Coordinated Universal Time).

3.2.7 Removing Additionally Added SAP HANA Systems From 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

SAP HANA DVD should be owned by the root user.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

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



Procedure

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.

3.2.8 Adding Hosts to and Removing Hosts from an Existing SAP HANA SystemYou 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.

NoteTo 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

1. Open the SAP HANA lifecycle manager user interface.2. Choose Add Additional Host (or Remove Additional Host), and then choose Next to continue.

When adding an additional host, you need to specify what its role is: worker or standby.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 LandscapeHosts . 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.



3. Specify the required entries.

NoteAfter 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

SAP HANA Server Installation GuideSAP HANA Server Installation Guide (Unified Installer)Configuring the SAP HANA System Internal Network [page 27]

3.2.9 Configuring the SAP HANA System Internal Network

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.

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



Procedure

1. Open the SAP HANA lifecycle manager user interface.2. Choose Configure SAP HANA System Internal Network.3. Enter your adm password.4. From the Network Listen Interface dropdown box, select the required option, as follows:

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

.globalSelect this option to bind the processes to all interfaces. This option does not require an internal network address entry.

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

SAP HANA Master GuideSAP HANA Administration GuideSAP HANA Security Guide

3.2.10 Managing Products and TransportsThis topic provides information about how to manage products and transports.

Context

Currently the corresponding information is part of SAP HANA Developer Guide.For more information, see the lifecycle manager chapter in SAP HANA Developer Guide SAP HANA Developer Guide.



NoteWhen used under Linux, SAP HANA studio blocks pop-up windows and does not allow opening URLs. Therefore, under Linux, you cannot use the Managing Products and Transports options in SAP HANA lifecycle manager (HLM) from SAP HANA studio. To be able to use the the Managing Products and Transports options, connect to HLM from a supported Web browser.

3.3 Updating an SAP HANA System with the SAP HANA Lifecycle Manager 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.

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.

CautionS-User is required



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 the

automated update there is a business downtime for your SAP HANA system. You know the adm, sapadm, and database administrator passwords. Keep in mind that sapadm

password is not controlled by SAP HANA installation or SAP HANA lifecycle manager. It should be maintained on OS level.

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

NoteUse 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 user 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)



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 already available. 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 HANA Lifecycle Manager.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 software components 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. If the stack contains content components for deployment such as SAP HANA Interactive Education (SHINE), SAP HANA EPM Service, SAP HANA UI toolkit for Information Access (INA), SAP HANA River Definition Language (RDL), these components will also be deployed.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. Furthermore, this scenario allows you to update components of an SAP HANA system which is running in a high-availability environment. However, if the system whose components you are updating is running in a high-availability environment, you cannot deploy SAP HANA content components or update the SAP HANA studio repository.The user interface will provide information about installed components versions, as well as 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 the update 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. Therefore, SAP Service Marketplace does not return the latest patch.

Manually downloaded contentIn 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, 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 user.4. Select the proposed software releases.5. Select the type of the source SAP HANA system. You have the following options:

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

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

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

ExampleFor more information about using the command line, see Using SAP HANA Lifecycle Manager in Command Line Mode [page 8].

If you use command line to apply a Single Support Package, see: How to display the detailed help of the task:

hlmcli.sh --help apply_single_support_package Example for update of a primary system from inbox:



hlmcli.sh apply_single_support_package --sidadm_pwd ******** --sapadm_use_master true --sapadm_user sapadm --sapadm_pwd ******** --db_user SYSTEM --db_pwd ******** --instance_Nr --update_source inbox --inbox_directory --system_type primary --confirm_dialog true

Example for update of a secondary system from SAP Service Marketplace:hlmcli.sh apply_single_support_package --sidadm_pwd ******** --sapadm_use_master true --sapadm_user sapadm --sapadm_pwd ******** --db_user SYSTEM --db_pwd ******** --instance_Nr --update_source marketplace --smp_user --smp_pwd ******** --use_proxy true --proxy_host --proxy_port --system_type secondary --confirm_dialog trueThe system_type parameter defines the type of the system. The acceptable values are normal, primary, and secondary.

If you use command line to apply a Support Package Stack, see: How to display the detailed help of the task:

hlmcli.sh --sidadm_pwd - --help apply_support_package_stack Example for update from inbox:

hlmcli.sh apply_support_package_stack --sidadm_pwd ******** --sapadm_use_master true --sapadm_user sapadm --sapadm_pwd ******** --db_user SYSTEM --db_pwd ******** --instance_Nr --update_source inbox --inbox_directory --confirm_dialog true

Example for update from SAP Service Marketplace:hlmcli.sh apply_support_package_stack --sidadm_pwd ******** --sapadm_use_master true --sapadm_user sapadm --sapadm_pwd ******** --db_user SYSTEM --db_pwd ******** --instance_Nr --update_source marketplace --smp_user --smp_pwd ******** --use_proxy true --proxy_host --proxy_port --confirm_dialog true

3.3.2 Performing an Automated Update in a Distributed System and in a Landscape with Multiple SAP HANA SystemsPrerequisitesYou 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 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].



4 Managing SAP HANA Components and Application ContentThis section provides information about how to manage additional SAP HANA components and applications.

4.1 Adding Application Function Libraries on an SAP HANA SystemThis 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.

4.2 Performing Automated Updates for Application Function Libraries (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, 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


SAP HANA Update and Configuration GuideManaging SAP HANA Components and Application Content

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

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

To perform an update of AFLs, follow the procedure below: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 button. For

some of the components you have the option to skip the update.4. Follow the instructions in the wizard.

NoteKeep in mind that, after AFLs are updated, the SAP HANA database server is restarted.

4.3 Adding SAP liveCache Applications on an SAP HANA SystemYou 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.



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. Choose Add liveCache Applications (LCApps).3. Specify the required entries by following the instructions in the wizard.

4.4 Performing an Automated Update for SAP liveCache Applications

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

NoteThe 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 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

button. For some of the components, you have the option to skip the update.4. Follow the instructions in the wizard.



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

4.6 Deploying SAP HANA Application Content Using SAP HANA Lifecycle ManagerThis 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. You have no inactive objects related to the content you want to deploy in your database.

For SAP HANA platform SPS 06 and higher, if there are inactive objects related to the content to be deployed, the successful activation of the deployed SAP HANA content is not possible. For the SAP HANA platform releases prior to SPS 06, the succesfull activation of the deployed content is not possible in case of any type of inactive objcets in the dtabase. For more information about how to activate or delete inactive objects, see the SAP HANA Modeling Guide available in the SAP HANA Knowledge Center on the SAP Help Portal at http://help.sap.com/hana_platform



Context

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

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. The system displays the

content of the archive and the product instances that are already installed. If the archive contains more than one product instances, select the instance that you want to deploy, and then choose Next.You are not allowed to select multiple product instances at once. In case the archive contains more than one product instances, you need to repeat the deploy procedure for each product instance you want to deploy.

4. Choose Run. This transfers the product archive to the SAP HANA lifecycle manager server.The SAP HANA lifecycle manager attempts to deploy and activate the corresponding SAP HANA content. For SAP HANA platform SPS 06 and higher, if there are inactive objects in the database, the successful completion of the task depends on the relationship between these inactive objects and the content to be deployed. If the inactive objects are related to the corresponding content, the deployment and the activation of the content fails. However, if the inactive objects are not related to the content, the task is completed successfully. For the SAP HANA platform releases prior to SPS 06, if there are inactive objects in the database, the successful completion of the task is not possible regardless of the type of the inactive objects. You will receive a notification in the summary page, even if there are activation issues (for example, if there are inactive objects related to the content you want to deploy in your database table).

ExampleYou 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: How to display the detailed help of the task:

hlmcli.sh --sidadm_pwd - --help deploy_hana_content Example for update from inbox:

hlmcli.sh deploy_hana_content --sidadm_pwd ******** --sapadm_use_master true --sapadm_user sapadm --sapadm_pwd ******** --db_user SYSTEM --db_pwd ******** --instance_Nr --content_update_source remote --content_file_path --confirm_dialog true

Related Information

SAP HANA Installation: Content Components and Deployment



5 TroubleshootingMain 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/framework.log.

Main Log File for SAP HANA Studio

The SAP HANA studio has a dedicated view for errors - Error Log view. You can find the same information in the following file:/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

NoteKeep 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/ (usually, /hana/shared/). 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_structureAll new SAP HANA system installations after Single SP 03 for SPS 05 use the new system directory structure.

SAP HANA Update and Configuration GuideTroubleshooting


Updating SAP HANA Systems Older than SPS 06 (Enterprise and Enterprise Extended Editions) to SAP HANA SPS 06 or Higher

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.

Problems Using the SAP HANA Lifecycle Manager:

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

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 studioCheck 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 10].

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.

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

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.

If you need to force stop SAP HANA lifecycle manager, for example in case of a hanging process, run the stop-hlm script located in the //HLM directory with the -f option. Make sure you have closed all browser clients to the HLM which you want to stop beforehand. The execution of the script terminates all running SAP HANA lifecycle manager tasks. Therefore, use this procedure with care.

When adding an additional SAP HANA system on a single SAP HANA appliance or renaming an SAP HANA system, you may experience the following issue: fter entering the required data in the wizard, the progress of the task execution seems to freeze and there is no option to stop or cancel the task. SAP HANA lifecycle manager (HLM) displays a message informing you that the task is being executed.The reason for the issue is that when you are adding an SAP HANA system to the SAP HANA system landscape, the system regenerates the SAP Host Agent certificate. You must accept the new certificate in order the browser session to continue. However, when using HLM from an SAP HANA studio under Linux, the dialog box for accepting the certificate may not appear. To continue with the task, you have to close the HLM perspective in the SAP HANA studio, and then start it again. Then HLM will show the correct status.

After a self update of HLM, you receive the following error message: SAP HANA lifecycle manager did not come up after self update. Check log files for errors. To solve the issue, you have to restart the SAP Host Agent. To do so, log in as root user, and execute the following command: /usr/sap/hostctrl/exe/saphostexe -restart

If the update scenario with HLM is still not working after you have performed the troubleshooting steps relevant for your issue, you can update the SAP HANA platform components with the SAP HANA hdblcm command line tool. For more information about the update procedure with the SAP HANA hdblcm command line tool and the SAP HANA components whose update is supported, see SAP HANA Server Installation Guide.



6 Appendix6.1 Manually Adding SAP HANA Lifecycle ManagerThis 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 . The archive should be named SAPHANALM*.SAR.

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

6.2 Optional: Using Own SAP Host Agent CertificatesDuring 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

You are logged in as root user

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.


SAP HANA Update and Configuration GuideAppendix

Use this procedure if you want to use your own certificates instead of the ones automatically generated by SAP HANA lifecycle manager during operations such as adding additional hosts, renaming a system, adding additional system and so on.

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.

NoteYou 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: To generate your own SAP Host Agent certificate, proceed as follows:

1. Change to the ///HLM directory and run generate_sha_certificate.sh with the host specified: ///HLM/generate_sha_certificate.sh -h

2. When prompted, enter a keystore password.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:1. Make sure they are stored in the /usr/sap/hostctrl/exe/sec directory.2. Grant the SAP Host Agent access to the server PSE. To do so, execute the following: /usr/sap/

hostctrl/exe/sapgenpse seclogin -p SAPSSLS.pse -O sapadm.3. Restart the SAP Host Agent using the following command: /usr/sap/hostctrl/exe/

saphostexec restart.

6.3 SAP HANA GuidesLinks 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:Topic Location Quick Link

SAP HANA landscape, deployment, and installation

SAP HANA Knowledge Center on the SAP Help Portal

http://help.sap.com/hana_platform:



Topic Location Quick Link

SAP HANA Master Guide SAP HANA Server Installation Guide SAP HANA Master Update Guide SAP HANA Update and Configura

tion Guide

SAP HANA administration and security

SAP HANA Knowledge Center on the SAP Help Portal

http://help.sap.com/hana_platform: SAP HANA Technical Operations

Manual SAP HANA Administration Guide SAP HANA Security Guide

SAP HANA documentation for previous Support Package Stacks

SAP HANA Knowledge Center on SAP Service Marketplace

https://service.sap.com/hana

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

SAP Note Number Title

1820588 SAP Release Note for SAP HANA lifecycle manager

1896320 Error occurred while trying to start 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 SecurityUser CredentialsTo 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.htmTo enable internal communication through HTTPS, remove -Dhttp.hostcontrol.connection parameter from /hana/shared//HLM/props.ini .Communication ChannelsThe SAP HANA Lifecycle Manager communicates with the following components: SAP HANA studio SAP Host Agent SAP Service Marketplace



7 Important Disclaimers on Legal AspectsThis document is for informational purposes only. Its content is subject to change without notice, and SAP does not warrant that it is error-free. SAP MAKES NO WARRANTIES, EXPRESS OR IMPLIED, OR OF MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.Coding SamplesAny 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.AccessibilityThe 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 LanguageAs 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 HyperlinksThe 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


SAP HANA Update and Configuration GuideImportant Disclaimers on Legal Aspects

SAP HANA Update and Configuration GuideImportant Disclaimers on Legal Aspects


www.sap.com/contactsap

2014 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 as constituting an additional warranty.SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.Please see http://www.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.

SAP HA

sap_hana_update_and_configuration_guide-good.pdf

Documents

lifecycle of sap hana

sap hana studio

sap hana guides

configured sap hana

existing sap hana system

sap ag

sap hana application

managing sap hana components