PUBLIC

SAP HANA Platform SPS 08
Document Version: 1.1 - 2014-08-21

SAP HANA Master Guide

Table of Contents
1

Getting Started with SAP HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4

1.1

About This Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

1.2

What Is SAP HANA?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2

SAP HANA Use Cases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2.1

SAP HANA as Primary Persistence for SAP NetWeaver-Based Applications. . . . . . . . . . . . . . . . . . . .5

2.2

SAP HANA as Data Mart. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2.3

SAP HANA-Based Accelerators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2.4

SAP HANA Data Provisioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.4.1

Trigger-Based Replication (SAP Landscape Transformation Replication Server). . . . . . . . .12

2.4.2

SAP HANA Direct Extractor Connection (DXC). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2.4.3

ETL-Based Replication (SAP Data Services). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2.4.4

Log-Based Replication (SAP Replication Server). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

2.4.5

SAP Event Stream Processor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

2.5

SAP HANA as Application and Development Platform. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

2.6

SAP HANA Smart Data Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

3

SAP HANA Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

3.1

SAP HANA Technical Deployment Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

3.2

3.1.1

Single Application on One SAP HANA System (SCOS). . . . . . . . . . . . . . . . . . . . . . . . . . . 23

3.1.2

Multiple Applications on One SAP HANA System (MCOD). . . . . . . . . . . . . . . . . . . . . . . . 24

3.1.3

Multiple SAP HANA Systems on One Host (MCOS). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

3.1.4

SAP HANA System Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

3.1.5

SAP HANA with Virtualization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

The SAP HANA Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
3.2.1

Network Zones. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30

3.2.2

Ports and Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

3.2.3

Host Name Resolution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

3.3

SAP HANA Software Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

4

SAP HANA Deployment Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

4.1

On-Premise. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

4.2

In the Cloud. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

5

SAP HANA Implementation and Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

5.1

Sizing SAP HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

5.2

Installing SAP HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

5.3

Administrating SAP HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58

5.4

SAP HANA Lifecycle Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

5.5

SAP HANA Content. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

2

PUBLIC
© 2014 SAP SE or an SAP affiliate company. All rights reserved.

SAP HANA Master Guide
Table of Contents

5.5.1

SAP HANA Content Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

5.5.2

Deploy SAP HANA Content. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

6

Appendix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

6.1

Related Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

6.2

Important SAP Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

6.3

SAP License Key. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

6.4

Software Download. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

6.5

Hardware and Software Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

SAP HANA Master Guide
Table of Contents

PUBLIC
© 2014 SAP SE or an SAP affiliate company. All rights reserved.

3

providing core database technology. 4 PUBLIC © 2014 SAP SE or an SAP affiliate company. bundling additional components for data provisioning. SAP HANA Master Guide Getting Started with SAP HANA . and the SAP HANA Enterprise Edition. in-memory database and platform that is deployable on-premise or in the cloud.1 Getting Started with SAP HANA SAP HANA is a modern. like the SAP HANA Platform Edition. The SAP HANA platform is a flexible data source agnostic in-memory data platform that allows customers to analyze large volumes of data in real-time. and SAP HANA clients. The Master Guide provides the following information about SAP HANA: ● Overview ● Architecture ● Software components ● Deployment scenarios 1. All rights reserved. It is the foundation of various SAP HANA editions. It is also a development platform. SAP HANA studio.1 About This Document This Master Guide is the central starting point for the technical implementation of SAP HANA.2 What Is SAP HANA? SAP HANA is a modern. providing an infrastructure and tools for building high-performance applications based on SAP HANA Extended Application Services (SAP HANA XS). The SAP HANA Platform Edition integrates a number of SAP components. including the SAP HANA database. in-memory database and platform that is deployable on-premise or in the cloud. 1.

and other SAP NetWeaver-based applications have been renovated to run on SAP HANA in a manner that exploits its many advantages. SAP NetWeaver. SAP Business Warehouse (BW). and other SAP enterprise solutions are built on SAP’s pervasive platform. SAP Business Warehouse (BW). SCM. and so on). SAP Business Suite applications (ERP.1 SAP HANA as Primary Persistence for SAP NetWeaverBased Applications SAP Business Suite applications (ERP. SAP NetWeaver has two distinct aspects.2 SAP HANA Use Cases SAP HANA can be used in a variety of use cases and scenarios. While the technical interfaces are available for applications built on SAP NetWeaver AS ABAP and AS Java to run on SAP HANA. CRM. where SAP HANA serves as the sole database in the architecture. SAP HANA and SAP NetWeaver AS ABAP on one Server SAP HANA and SAP NetWeaver AS ABAP deployed on one server is a multi-component. 5 . specific development enablement is normally required for each application to ensure it runs optimally on SAP HANA. SAP HANA Master Guide SAP HANA Use Cases PUBLIC © 2014 SAP SE or an SAP affiliate company. Many applications built on SAP NetWeaver’s ABAP and/or Java application servers are able to run “on” SAP HANA. All rights reserved. CRM. and so on). One restriction to note in the scenario SAP HANA as primary persistence for SAP NetWeaver-based applications: SAP NetWeaver ABAP and Java application servers must run on separate hardware servers from the SAP HANA hardware. Additionally. resource-optimized and cost-optimized deployment approach. and SCM. 2. various components and complimentary applications that are built on SAP NetWeaver can also run on SAP HANA through the use of the provided SAP NetWeaver DB interfaces. ABAP and Java.

content. As new data is added into the relevant tables in the transactional system’s database. or a specific use in another type of application. the data modeling effort involved in developing these views may be significant. With SAP HANA. such as the BI Tool Suite available from SAP BusinessObjects. presentation. designed to serve a particular community of information workers by forming a basis for analytics. 6 PUBLIC © 2014 SAP SE or an SAP affiliate company.Related Information SAP Note 1953429 . All rights reserved. The emphasis of a data mart is on meeting the specific needs of a particular group of users in terms of analysis. are used for analysis and reporting. These replicated tables become the basis for specialized views that are created for analytics purposes.SAP HANA and SAP NetWeaver AS ABAP on one Server End-to-End Implementation Roadmap for SAP NetWeaver AS ABAP on SAP HANA End-to-End Implementation Roadmap for SAP NetWeaver AS Java on SAP HANA End-to-End Implementation Roadmap for SAP NetWeaver BW on SAP HANA 2. Business Intelligence tools. SAP HANA Master Guide SAP HANA Use Cases . In some cases. to convert raw transactional table data into a form that is best suited for analytics.2 SAP HANA as Data Mart A data mart is an industry term for a repository of data gathered from operational data originating in transactional systems (and/or other sources). reporting. operational data marts offer real-time analytics and reporting on data replicated from a transactional system’s database. The raw tables themselves are copied (structure and data) from the transactional system’s database into SAP HANA. copies of those records are automatically transferred immediately into SAP HANA using replication technology. and ease-of-use.

7 . a log-based SAP Replication Server (SRS) can also be used to provide real-time data replication for an SAP Business Suite system. In addition. All rights reserved. SAP HANA Master Guide SAP HANA Use Cases PUBLIC © 2014 SAP SE or an SAP affiliate company.Real-time Operational Data Marts with an SAP Business Suite System SAP Business Suite is a source system for operational data marts in SAP HANA. The SAP Landscape Transformation Replication Server (SLT) is an SAP NetWeaver ABAP-based tool that provides real-time data replication.

SAP Replication Server (SRS) refers to the SAP Replication Server application. which is a tool which provides real-time data replication. All rights reserved. 8 PUBLIC © 2014 SAP SE or an SAP affiliate company. SAP HANA Master Guide SAP HANA Use Cases .Real-time Operational Data Marts with a non-SAP OLTP System A non-SAP transactional source system is used as a basis for real-time operational data marts in SAP HANA.

2. SAP HANA Master Guide SAP HANA Use Cases PUBLIC © 2014 SAP SE or an SAP affiliate company. When deployed in SAP HANA. The typical approach for accelerators involves replicating data for data-intensive operations that are often bottlenecks for the given operation in an SAP HANA table. This is implemented by performing operations for certain parts of computing operations of designated business processes or reports. A type of “switch” is then set in the SAP Business Suite application to indicate that whenever these specified tables are read.Agile Data Marts Agile data marts are a type of data mart that offer analytics and reporting on data acquired from a transactional system. All rights reserved. they may offer advantages of flexibility when compared to taking a more comprehensive approach to organizational information management. 9 . such as deploying data marts within the context of an Enterprise Data Warehouse. the read operation will take place in SAP HANA using a secondary database connection.3 SAP HANA-Based Accelerators SAP HANA-based accelerators are types of applications or scenarios that extend the capabilities of business processes in SAP Business Suite systems by leveraging the performance and scalability advantages that SAP HANA provides.

SAP HANA Master Guide SAP HANA Use Cases . All rights reserved.10 PUBLIC © 2014 SAP SE or an SAP affiliate company.

All rights reserved. The methods for performing data replication are shown in the figure below. User interfaces. consisting of the SAP HANA database and SAP HANA studio. The main components involved in all replication scenarios are: ● SAP HANA. which is an administration tool.4 SAP HANA Data Provisioning In-memory reporting and analysis of business data require data provisioning from a source system to the SAP HANA database. ● Source system ● Software components supporting the data replication SAP HANA Master Guide SAP HANA Use Cases PUBLIC © 2014 SAP SE or an SAP affiliate company. are not part of SAP HANA.2. The figure above focuses on the task of loading business data from a source system to the SAP HANA database. such as SAP BusinessObjects Dashboards or Web Intelligence. 11 .

which in turn passes the initialization message to the ERP system. The system load that this process causes can be controlled by adjusting the number of worker threads performing the initial replication. SAP HANA Master Guide SAP HANA Use Cases . All rights reserved.1 Trigger-Based Replication (SAP Landscape Transformation Replication Server) The Trigger-Based Replication method uses the SAP Landscape Transformation (LT) Replication Server component to pass data from the source system to the SAP HANA database target system. These changes are already recorded in logging tables during the initial load phase and are propagated during the replication phase to the target SAP HANA system after the initial load has been completed. The initial load message is sent from the SAP HANA system to the SLT system. the SLT system begins a multithreaded replication of data to the target system. Furthermore. In parallel to the initial load. The initial load of data can be executed while the source system is active. the SLT system begins detecting any data changes that occur while the initial load process is running.2. which enables high speed data transfer. the SLT system initiates the set-up of replication log tables in the database of the ERP system for each table to be replicated. Initial Load and Simultaneous Delta Replication The initial load of business data is initiated using the SAP HANA studio. After the transaction tables are completed. by means of database-specific triggers. The multi-version concurrency control (MVCC) of the SAP HANA database prevents issues that might be caused by the overlapping of the initial load process and new database transactions Continuous Delta Replication After Initial Load 12 PUBLIC © 2014 SAP SE or an SAP affiliate company.4.

it should be considered as a form of extraction. every 15 minutes). In many cases. the SLT system continues to monitor the transaction tables in the ERP system. transformation and load although its transformation capabilities are limited to user exit for extraction. data from different areas in SAP Business Suite systems requires application logic to appropriately represent the state of business documents. DXC is a batch-driven data acquisition technique. Customer projects may face significant complexity in modeling entities in SAP Business Suite systems. now with DXC. SAP Business Content DataSource Extractors have been available for many years as a basis for data modeling and data acquisition for SAP Business Warehouse. these SAP Business Content DataSource Extractors are available to deliver data directly to SAP HANA.After the initial load process has completed. 13 . You can select between these options depending on your current system landscape and the software versions in your landscape: ● Installation on your ERP system ● Installation on a standalone SAP system (recommended setup) Related Information SAP HANA Installation Guide – Trigger-Based Replication (SLT) 2. Overview of the DXC Rationale ● Leverage pre-existing foundational data models of SAP Business Suite entities for use in SAP HANA data mart scenarios: ○ Significantly reduces complexity of data modeling tasks in SAP HANA ○ Speeds up timelines for SAP HANA implementation projects SAP HANA Master Guide SAP HANA Use Cases PUBLIC © 2014 SAP SE or an SAP affiliate company. A key point about DXC is that in many use cases. and replicates data changes in the source system to the SAP HANA system in near real time. Required Software Components This replication method requires the following component: ● SAP Landscape Transformation: this controls the entire replication process by triggering the initial load and coordinating the delta replication.2 SAP HANA Direct Extractor Connection (DXC) The SAP HANA Direct Extractor Connection (DXC) provides SAP HANA with out-of-the-box foundational data models based on SAP Business Suite entities. batch-driven data acquisition at certain intervals is sufficient (for example. and is a data acquisition method as well. Installation considerations The SLT system can be installed in the ways shown below.4. All rights reserved.

SAP Business Warehouse (BW) is part of SAP NetWeaver itself. but do not utilize its other aspects such as storing data. An SAP Business Suite system is based on SAP NetWeaver. which means a BW system exists inside SAP Business Suite systems such as ERP (ECC 6. Typically. ● The alternative configuration is available for SAP Business Suite systems based on releases lower than SAP NetWeaver 7. for example. transformation. 14 PUBLIC © 2014 SAP SE or an SAP affiliate company.0 or higher).6. SAP HANA Master Guide SAP HANA Use Cases .● ● ● Provide semantically rich data from SAP Business Suite to SAP HANA: ○ Ensures that data appropriately represents the state of business documents from ERP ○ Application logic to give the data the appropriate contextual meaning is already built into many extractors Simplicity/Low TCO: ○ Re-uses existing proprietary extraction. since most customers who run BW have it installed on a separate server. The following illustration depicts the default configuration of DXC. DXC extraction processing essentially bypasses the normal dataflow. All rights reserved. and instead sends data to SAP HANA. and they rely on that one. With the default DXC configuration. this embedded BW system inside SAP Business Suite systems is actually not utilized.0 – such as SAP ERP 4. or reporting / BI. we utilize the scheduling and monitoring features of this embedded BW system.0 or higher – such as ECC 6. and load mechanism built into SAP Business Suite systems over a simple http(s) connection to SAP HANA ○ No additional server or application needed in system landscape Change data capture (delta handling): ○ Efficient data acquisition – only bring new or changed data into SAP HANA ○ DXC provides a mechanism to properly handle data from all delta processing types Default DXC Configuration for SAP Business Suite DXC is available in different configurations based on the SAP Business Suite system: ● The default configuration is available for SAP Business Suite systems based on SAP NetWeaver 7. This BW system is referred to as an “embedded BW system”. data warehousing.0. As of SAP NetWeaver version 7.0.

You deploy this method by defining data flows in Data Services and scheduling the replication jobs. the data load monitor. The active data table of the IMDSO can be utilized as a basis for building data models in SAP HANA (attribute views. etc. Related Information SAP HANA Direct Extractor Connection Implementation Guide Editing DataSources and Application Component Hierarchies Enhancing DataSources 2. analytical views. This lets you read the business data on the application layer level. data is not loaded into the embedded BW system. and the merging of data streams. transformations. Instead. Data is transferred from the source SAP Business Suite system using an HTTP connection.4. data is redirected into SAP HANA. – which are all well-known from operating SAP Business Warehouse. All rights reserved. process chains. and calculation views). Since this method uses batch processing.3 ETL-Based Replication (SAP Data Services) Extraction-Transformation-Load (ETL) based data replication uses SAP Data Services (also called Data Services) to load relevant business data from SAP ERP to the SAP HANA database. Generally. 15 . the extraction and load process is virtually the same as when extracting and loading SAP Business Warehouse – you rely on InfoPackage scheduling.An In-Memory DataStore Object (IMDSO) is generated in SAP HANA. synchronizing with additional data providers. Note DXC does not require BW on SAP HANA. Also with DXC. it also permits data checks. which directly corresponds to the structure of the DataSource you are working with. SAP HANA Master Guide SAP HANA Use Cases PUBLIC © 2014 SAP SE or an SAP affiliate company. This IMDSO consists of several tables and an activation mechanism.

SAP HANA Master Guide SAP HANA Use Cases . you can determine the business data to be replicated. Additional settings depend on the type of SAP ERP objects to be read. the user name and password allowing Data Services to access the system. All rights reserved. Data Services can connect to the source system by RFC. the SAP HANA database. Data Services offers replication functions for a variety of data source types.The figure above gives an overview of the ETL-based replication method. where you model the data flow. Based on the metadata imported from the ABAP Data Dictionary to Data Services. Utilizing Data Services you have to set up datastores to define such parameters. data replication is operated by Data Services. Its main components are the Data Services Designer. choose SAP Applications for the type of datastore. Datastore Setup Setting up a datastore for the source system SAP ERP. Here. However. and specify the address of the system. 16 PUBLIC © 2014 SAP SE or an SAP affiliate company. Data Flow As for any replication scenario you have to define a series of parameters for the two systems involved. An additional repository is used to store the metadata and the job definitions. For the target system of the replication. and the Data Services Job Server for the execution of the replication jobs. you have to set up a separate datastore as done for the source system. Data Flow Modeling Once datastores are set up. You use the Designer to set up datastores. for the replication of SAP ERP data to SAP HANA database. we recommend you to use extractors.

You can also use the Management Console to monitor the replication process.NetWeaver Support Package requirement for Data Services SAP Extractor support SAP HANA Master Guide SAP HANA Use Cases PUBLIC © 2014 SAP SE or an SAP affiliate company. Model the data flow for each extractor you have selected: indicate the source for the data flow. Required Software Components This replication method requires the following main components: ● SAP HANA database ● SAP Data Services (contains Information Platform Services) Related Information Product Availability Matrix (PAM) (search for SAP HANA) Enterprise Information Management on SAP Help Portal SAP Note 1522554 . this method is suitable where the source system must be protected from additional load during the main business hours. As a result. For the update. It depends on the environment and the requested setup of the target tables which data flow design best serves your requirements.Note ● You must apply SAP Note 1522554 . choose a template table. ● In the source system. In this way. Use the Management Console. Replication Job Schedule Since you can schedule the replication jobs when using Data Services.NetWeaver Support Package requirement for Data Services SAP Extractor support to fully benefit from the extractor support. to enable the correct replication. to the night. ● The extractors must support delta handling. Choose the extractors that are relevant for the replication job. in most cases. In addition. All rights reserved. 17 . You can choose from different tools and methods for the scheduling. the data flow is enhanced by a delta handling element. for example. the extractors must be released for the replication access by Data Services. such as the GUID. Data Flow for Initial Load and Update Both the initial load of business data from the source system into SAP HANA database as well as updating the replicated data (delta handling) is done using SAP Data Services. you have to indicate the primary key. which is then used in the SAP HANA database to store the replaced data. you can shift the replication workload. Although we recommend you to use delta supporting extractors. the data that is available for reporting always represents the state reached by the time when the latest replication job was started. to schedule replication jobs. which comes with Data Services. you can also use SAP ABAP tables. For the target of the replication. The initial load can be set up modeling a simple data flow from source to target. such as Map_CDC_Operation or Table_Comparison Transform. which is the extractor.

initial load materialization of data as well as continuous real-time transactional replication are supported. Microsoft SQL Server. SAP HANA Master Guide SAP HANA Use Cases . The initial load materialization feature allows you to set up replication without any downtime of the primary data server and offers high performance. Oracle. providing low impact. guaranteed data delivery. and zero operational downtime. SAP HANA®.4 Log-Based Replication (SAP Replication Server) SAP Replication Server (SRS) moves and synchronizes transactional data including DML and DDL across the enterprise. from these primary databases: ● SAP Adaptive Server Enterprise ● Oracle ● Microsoft SQL Server ● DB2 UDB LUW ● SAP Business Suite running on SAP ASE. at both table and database level. Additionally. primarily used for real time data distribution and real time reporting. SRS includes Replication Agent for SAP HANA (RAH). You can use SAP Replication Server to do an initial load as well as replication in real time to SAP HANA. SRS supports log-based replication from and to heterogeneous databases. a light-weight server that replicates data from a primary SAP HANA to a replicate SAP HANA database using trigger-based replication. or Oracle databases in a heterogeneous comparison environment. MSSQL Server or DB2 UDB LUW ● SAP HANA database Also. reports and rectifies discrepancies. You can set up the replication environment for replication into the SAP HANA database using the Replication Management Agent (RMA). SRS offers the Data Assurance that compares row data and schema between two or more databases. 18 PUBLIC © 2014 SAP SE or an SAP affiliate company. You can compare row data between any combinations of SAP® Adaptive Server® Enterprise (SAP® ASE). except for the homogeneous SAP HANA to SAP HANA replication. which is trigger-based. real-time business intelligence. For all of the above primary databases. All rights reserved. IBM DB2 Universal Database(UDB).2.4.

or MSSQL into the SAP HANA database. enterprise edition. All rights reserved. SAP HANA edition. Oracle. Oracle. Individual components can also be licensed separately for replication from UDB DB2. ● Alternatively. SAP HANA edition. for replicating from multiple data sources. option for SAP HANA.These are the components required to implement a PrimaryDB-to-SAP-HANA database replication system: ● A primary data server ● A replicate SAP HANA database data server ● A Replication Server® (with ExpressConnect for SAP HANA database) ● The Replication Server Options component (this component is not required for ASE Primary DB to SAP HANA): Replication Agent for MSSQL or DB2 or Oracle ● Replication Agent for SAP HANA (RAH) Note License Requirements: You can use these licenses for replication into the SAP HANA database: ● Separately purchase SAP Replication Server. or MSSQL into the SAP HANA database through the SAP Replication Server. you automatically receive a license for SAP Replication Server. This license includes all components required to provision data from UDB DB2. SAP HANA Master Guide SAP HANA Use Cases PUBLIC © 2014 SAP SE or an SAP affiliate company. 19 . A prerequisite for this is that you must have SAP Replication Server. when you buy the Real-time-data edition for SAP HANA.

Input data streams can come from a variety of sources such as data feeds.html . and to combine data from different sources. there are two different types of applications that can be designed in this manner: native SAP HANA applications.infocenter.5 SAP Event Stream Processor SAP Event Stream Processor is used for real-time processing of high-velocity and high-volume data streams modeled as event streams. it is also much more than that. ESP transforms the input data streams into output data streams by applying event-driven “continuous queries”.sybase. a web server. SAP HANA. such as financial trade and risk monitoring. for example. It can be used. It is targeted for a variety of applications. All rights reserved. Within this category. to detect patterns. Related Information Sybase Product Documentation 2. SAP HANA edition at http:// service. and applications with another application server that connects to SAP HANA: ● 20 Native SAP HANA Applications While SAP HANA is a database comprised of innovative technology. and a repository for content. to filter. aggregate and enrich raw data. SAP HANA edition. For information on generating license keys and how to generate subcapacity license keys . which PUBLIC © 2014 SAP SE or an SAP affiliate company. For details see the SAP Event Stream Processor documentation on the Sybase product documentation page. The license for ExpressConnect for SAP HANA Database (ECH) is distributed with Replication Server and is enabled when you purchase SAP Replication Server.com/help/topic/ com. where myriad different types of applications can be built on.dc32237.sap. SAP HANA includes a small-footprint application server. and so on. sensors. monitoring machine/sensor data.5 SAP HANA as Application and Development Platform SAP HANA provides the basis for an application development platform. see http://infocenter. and run on.4.sybase. and tailoring responses to user actions. Related Information Documentation on SAP Help Portal 2.com/licensekeys . SAP HANA Master Guide SAP HANA Use Cases . business applications.Generate license keys for various components in SAP Replication Server. You can develop custom input adapters for additional sources.1571200/doc/html/ang1278662839532. IT monitoring infrastructure. ESP can capture output streams in the SAP HANA database at very high speeds.

implementation-agnostic C-based API for accessing a database. Together with development tools. update. without copying the data into SAP HANA.6 SAP HANA Smart Data Access SAP HANA smart data access enables remote data to be accessed as if they were local tables in SAP HANA. which functions similarly to ODBC in principle. these components form an application development platform and runtime that can be used to build.NET are integrated with SAP HANA using Open Database Connectivity (ODBC). Applications written using . or JDBC can integrate with SAP HANA.NET or Java) Various types of applications can be built on. or simply XS. these methods map directly to the underlying SQL semantics. SAP HANA utilizing the architecture of other widely-known application servers and languages. transactions. and other mechanisms for create. and run on. Related Information SAP HANA Developer Information Roadmap SAP HANA Developer Guide 2. but most importantly it supports the development and deployment of the next generation of analytical applications which require the ability to access. These interface types provide methods for creating and maintaining connections. and operate SAP HANA-based software applications of all kinds. These applications normally have an HTML or mobile app user interface that connects to SAP HANA using HTTP. and delete operations in SAP HANA. hiding the actual communication details. . read. any application that can utilize ODBC. which is a standard. Essentially. ● SAP HANA-based Applications with Another Type of Application Server (for example.provides lifecycle management functionality for development artifacts. Applications written using Java integrate using Java Database Connectivity (JDBC). ODBO. 21 . synthesize and integrate data from multiple systems in real-time regardless of where the data is located or what systems are generating it. The name for these described capabilities is SAP HANA Extended Application Services. deploy. Not only does this capability provide operational and cost benefits. All rights reserved. SAP HANA Master Guide SAP HANA Use Cases PUBLIC © 2014 SAP SE or an SAP affiliate company.

which could operate on virtual tables. and completes the operation. The SAP HANA query processor optimizes these queries. and executes the relevant part of the query in the target database. All rights reserved. you can create virtual tables which point to remote tables in different data sources. in SAP HANA. Related Information SAP HANA Security Guide (see "Secure Storage of Passwords in SAP HANA" and "Secure Internal Credential Store") SAP HANA Administration Guide (see "About SAP HANA Smart Data Access") 22 PUBLIC © 2014 SAP SE or an SAP affiliate company. Customers can then write SQL queries in SAP HANA. SAP HANA Master Guide SAP HANA Use Cases . returns the results of the query to SAP HANA.Specifically.

3

SAP HANA Architecture

Various aspects are relevant to the SAP HANA architecture.

3.1

SAP HANA Technical Deployment Options

The technical deployment options determine how SAP HANA systems, hosts used for SAP HANA systems,
and applications running on SAP HANA are deployed.

3.1.1

Single Application on One SAP HANA System (SCOS)

A single application on one SAP HANA system is also known as Single Component on One System (SCOS).
To more readily describe the various other options for technical deployment, it is useful to first illustrate the
simple, straightforward approach to deploying an application on an SAP HANA system. This will be useful for
comparison purposes.

SAP HANA Master Guide
SAP HANA Architecture

PUBLIC
© 2014 SAP SE or an SAP affiliate company. All rights reserved.

23

In this configuration, a single application runs in a single schema, in a single SAP HANA database as part of an
SAP HANA system. This is a simple, straightforward scenario that is supported for all scenarios without
restriction.

3.1.2
Multiple Applications on One SAP HANA System
(MCOD)
Multiple applications on one SAP HANA system is also known as Mulitple Components on One Database
(MCOD).

The technical deployment type MCOD refers to the scenario where more than one application, scenario, or
component runs on one SAP HANA system. This deployment type is available, with restrictions, for production
SAP HANA systems.

Related Information
SAP Note 1661202 - Support for multiple applications on SAP HANA
SAP Note 1826100 - Multiple applications SAP Business Suite powered by SAP HANA

24

PUBLIC
© 2014 SAP SE or an SAP affiliate company. All rights reserved.

SAP HANA Master Guide
SAP HANA Architecture

3.1.3

Multiple SAP HANA Systems on One Host (MCOS)

Multiple SAP HANA systems on one host are also known as Multiple Components on One System (MCOS).

The technical deployment of multiple SAP HANA systems on one host is currently only available with
restrictions; in particular, this configuration is presently only supported for non-production SAP HANA
systems.

Related Information
SAP Note 1681092 - Multiple SAP HANA databases on one SAP HANA system
SAP Note 1666670 - BW on SAP HANA - landscape deployment planning

3.1.4

SAP HANA System Types

The number of hosts in a SAP HANA system landscape determines the SAP HANA system type.
The host is the operating environment in which the SAP HANA database runs. The host provides all the
resources and services (CPU, memory, network, and operating system) that the SAP HANA database

SAP HANA Master Guide
SAP HANA Architecture

PUBLIC
© 2014 SAP SE or an SAP affiliate company. All rights reserved.

25

requires. An SAP HANA system can be configured as one of the following types: ● Single-host system . SAP HANA Master Guide SAP HANA Architecture . shared data storage is required for distributed systems. it is called a single-host system. data directory. The host provides links to the installation directory.One SAP HANA instance on one host. ● Distributed system (multiple-host system) . For more information about SAP HANA system types.4. The storage needed for an installation does not have to be on the host. In particular. The following graphic shows the file system for a single-host installation: Related Information SAP HANA Server Installation and Update Guide SAP HANA LCM Tools Reference Guide SAP HANA Administration Guide 26 PUBLIC © 2014 SAP SE or an SAP affiliate company. with one instance per host.Multiple SAP HANA instances distributed over multiple hosts. and log directory or to the storage itself.1 Single-Host System If the system consists of only one host. see the SAP HANA Server Installation and Update Guide and SAP HANA LCM Tools Reference Guide Related Information SAP HANA Server Installation and Update Guide SAP HANA LCM Tools Reference Guide 3.1. All rights reserved.

or by adding hosts to the system to deal with larger workloads.1. slave. ● Distributed systems can be used for failover scenarios and to implement high availability. it is called a distributed system. Individual hosts in a distributed system have different roles (master. and high availability. For more information about scaling. This allows you to go beyond the limits of a single physical server. 27 .2 Distributed System (Multiple-Host System) If the system consists of multiple connected hosts. failover scenarios. All rights reserved. worker. Related Information SAP HANA Administration Guide SAP HANA Server Installation and Update Guide SAP HANA LCM Tools Reference Guide SAP HANA Master Guide SAP HANA Architecture PUBLIC © 2014 SAP SE or an SAP affiliate company. see the SAP HANA Administration Guide.4. The following graphic shows the file system for a distributed installation: A distributed system might be necessary in the following cases: ● You can scale SAP HANA either by increasing RAM for a single server. standby) depending on the task.3.

For information about SAP HANA with virtualization. SAP HANA Master Guide SAP HANA Architecture .SAP and VMware Announce SAP HANA for Production Use on VMware vSphere 5. All rights reserved.Overview SAP HANA Guidelines for being virtualized with VMware vSphere SAP Note 1788665 .5 SAP HANA with Virtualization The technical deployment type SAP HANA with Virtualization refers to the scenario where one or more SAP HANA database SIDs are deployed on one or more Virtual Machines running on SAP HANA server hardware. see SAP Note 1788665 .3.1.5 SAP HANA virtualized .SAP HANA Support for VMware vSphere Environments.SAP HANA Support for VMware vSphere Environments SAP on VMware 28 PUBLIC © 2014 SAP SE or an SAP affiliate company. Related Information Press announcement .

All rights reserved. application servers. and within SAP HANA and which ports to configure for them. depends on your company's environment and implementation considerations. from. SAP HANA-based applications can be integrated with external services such as e-mail. while ensuring the required communication between all components in the SAP HANA network. SAP HANA can be integrated with transaction-oriented databases using replication services. In addition. Host Name Resolution [page 42] The assignment of multiple host names to the same host supports performance optimization as well as the security of your SAP HANA system. SAP HANA supports the isolation of internal communication from outside access. In terms of network connectivity. certified SAP HANA hosts use a separate network adapter with a separate IP address for each of the different networks.2 The SAP HANA Network An SAP HANA data center deployment can range from a database running on a single host to a complex distributed system with multiple hosts located at a primary and one or more secondary sites. Related Information Network Zones [page 30] Separate network zones. SAP HANA supports traditional database client connections and. and support for disaster recovery through the use of multiple datacenters ● Security and performance SAP HANA has different types of network communication channels to support the different SAP HANA scenarios and setups: ● Channels used for external access to SAP HANA functionality by end-user clients. for communication between hosts To separate external and internal communication. in a distributed scenario. as well as with high-speed event sources. and supporting a distributed multi-terabyte database with full high availability and disaster recovery. you'll want to get an overview of the different types of connections to. Some of these considerations are: ● Support for traditional database clients. allow you to control and limit network access to SAP HANA to only those channels required for your scenarios. and R-code execution. ranging from a single-host system to a complex distributed system with multiple hosts ● Support for high availability through the use of standby hosts. Web. with SAP HANA Extended Application Services (SAP HANA XS). administration clients. The setup of an SAP HANA system. and administrative connections ● The number of hosts used for the SAP HANA system. Ports and Connections [page 31] Before you start configuring the network for SAP HANA. and for data provisioning via SQL or HTTP ● Channels used for SAP HANA internal communication within the database or.3. SAP HANA Security Guide SAP HANA Administration Guide SAP HANA Master Guide SAP HANA Architecture PUBLIC © 2014 SAP SE or an SAP affiliate company. 29 . Web-based clients. and the corresponding data center and network configurations. Web-based clients. each with its own configuration. SAP HANA can be configured to use SSL for secure communication.

allow you to control and limit network access to SAP HANA to only those channels required for your scenarios.2. ● Storage zone This zone refers to the network connections for backup storage and enterprise storage. by clients such as the SAP HANA studio or Web applications running against the SAP HANA XS server. 30 PUBLIC © 2014 SAP SE or an SAP affiliate company. externally attached storage subsystem devices that are capable of providing dynamic mount-points for the different hosts. See also Related Information below. SAP HANA Master Guide SAP HANA Architecture . according to the overall landscape.3. All rights reserved.1 Network Zones Separate network zones. ● Internal zone This zone covers the interhost network between hosts in a distributed system as well as the SAP HANA system replication network. each with its own configuration. and by other data sources such as SAP NetWeaver Business Warehouse. the preferred storage solution involves separate. These network zones can be basically described as follows: ● Client zone The network in this zone is used by SAP application servers. In most cases. while ensuring the required communication between all components in the SAP HANA network.

2. Host Name Resolution for Client Communication [page 50] Client applications communicate with SAP HANA servers from different platforms and types of clients via a client library (such as SQLDBC. you'll want to get an overview of the internal connections between server components. Internal Zone Connections for Distributed SAP HANA Systems [page 36] Before you start configuring the network for SAP HANA. you'll want to get an overview of the external client connections to SAP HANA . you'll want to get an overview of the external client connections to SAP HANA . Host Name Resolution for System Replication [page 48] The correct mapping of internal host names between primary and secondary systems is required for system replication. Host names are mapped to these IP addresses through internal host name resolution. server components are distributed across multiple hosts for the purposes of scalability and availability.Related Information Client Zone Connections from Database Clients and Web Clients to SAP HANA [page 32] Before you start configuring the network for SAP HANA. Related Information Connections from Database Clients and Web Clients to SAP HANA [page 32] Before you start configuring the network for SAP HANA. DBSL.NET) for SQL or MDX access. from. SAP HANA Master Guide SAP HANA Architecture PUBLIC © 2014 SAP SE or an SAP affiliate company. and within SAP HANA and which ports to configure for them. 31 . you'll want to get an overview of the different types of connections to.2 Ports and Connections Before you start configuring the network for SAP HANA. server components are distributed across multiple hosts for the purposes of scalability and availability.Storage Requirements FAQ . a technique by which the use of specific and/or fast networks can be enforced and communication restricted to a specific network. Storage Zone SAP HANA . All rights reserved. In SAP HANA. ODBC. ODBO or ADO. Internal Host Name Resolution [page 45] The SAP HANA services use IP addresses to communicate with each other. JDBC.SAP HANA Tailored Data Center Integration FAQ 3. Connections for Distributed SAP HANA Systems [page 36] Before you start configuring the network for SAP HANA. you'll want to get an overview of the internal connections between server components. In SAP HANA.

you'll want to get an overview of the external client connections to SAP HANA . The xx in the port numbers stands for your SAP HANA instance number. Network connections are depicted by dashed arrows. The direction of each arrow indicates which component is the initiator (start of arrow) and which component is the listener (end point of arrow).2. SAP HANA Master Guide SAP HANA Architecture . All rights reserved.3. Moreover.2. Administrative access to and from SAP HANA is depicted by the blue dashed arrows. the diagram shows a single host installation of SAP HANA.1 Connections from Database Clients and Web Clients to SAP HANA Before you start configuring the network for SAP HANA. you must also ensure that every database client can connect to every host (not shown in the diagram). However. additional network channels are required in distributed scenarios for communication between the different hosts of a HANA system or between the different sites. The connections between SAP HANA and external components and applications can be classified as follows: ● Connections that are used for administrative purposes ● Connections that are used for data provisioning ● Connections from database clients that access the SQL/MDX interface of the SAP HANA database ● Connections from HTTP/S clients ● Outbound connections You can see an example of what these connections look like in the diagram below. Note In distributed scenarios. 32 PUBLIC © 2014 SAP SE or an SAP affiliate company. the connections shown apply equally to a distributed scenario. For purposes of illustration. Port numbers are shown with a pink background. The diagram shows all the network channels used by the SAP HANA software.

You can change the default mapping. For more information.The following tables explain the diagram and the different categories described above in more detail. 3xx15 Examples: SAP NetWeaver Business Warehouse and one or more compo­ nents of SAP Business Suite External and internal host names are mapped for the purposes of database client access. End-user clients that access the SAP HANA database directly 3xx17 The protocol used for database client access is SQLDBC (ODBC/JDBC). Example: Microsoft Excel SAP HANA studio SAP HANA Master Guide SAP HANA Architecture PUBLIC © 2014 SAP SE or an SAP affiliate company. see the SAP HANA Administration Guide. Database Client Access Client Protocol and additional information TCP port Application servers that use SAP HANA as a database You must enable SQL/MDX access for all database clients. All rights reserved. 33 .

HTTP/S Client Access Client Additional information Examples: a Web browser or a mo­ Access for applications based on SAP HANA Extended bile device Application Services (SAP HANA XS).Client Protocol and additional information TCP port This connection is used for administra­ tive purposes (for example. see the SAP HANA Direct Extrac­ tor Connection Implementation Guide. SAP HANA Direct Extractor Con­ nection (DXC) TCP port 80xx (HTTP) 43xx (HTTPS) This connection is used for ETL-based data acquisition. To find out how to open a support con­ nection. see the SAP HANA Developer Guide. 34 PUBLIC © 2014 SAP SE or an SAP affiliate company. Similar to the client libraries. All rights reserved. For more infor­ mation. This web dispatcher is used for load balancing. the high availability of the load balancer is supported by the use of an external cluster manager as well as by virtual host names. It can be either SAP Web Dispatcher (sapwebdisp) or a third-party tool. SAP HANA studio The connection to the instance agent acts as an administrative channel for low-level access to the SAP HANA instance to allow features such as starting or stopping of the SAP HANA database. the HTTP load balancer has its own ini file in which the available SAP HANA XS engines are configured. Administrative Tasks Client Protocol and additional information TCP port SAP support The connection is not active by default because it is required only in certain support cases. UI toolkit for SAP HANA Info Ac­ cess Each SAP HANA host comes with an SAP HANA XS engine and a local SAP web dispatcher (sapwebdisp). Typically. For more information. 3xx09 An internal SAP protocol is used for this connection. In addition. configuration data or trace files) or for modeling purposes (to ac­ cess data models). to access user data. see the SAP HANA Administration Guide. the clients in distributed or system replication landscapes typically connect through a web dispatcher that is external to SAP HANA. 5xx13 5xx14 (SSL) The protocol used for this connection is SQLDBC (ODBC/JDBC). SAP HANA Master Guide SAP HANA Architecture .

SAP HANA Master Guide SAP HANA Architecture PUBLIC © 2014 SAP SE or an SAP affiliate company. For more information about SAP HANA lifecycle man­ ager. SAP HANA lifecycle manager to SAP Service Marketplace For information about software updates. use the SQL/MDX channel of the database. 1128 1129 (SSL) The protocol used for this connection is SQLDBC (ODBC/JDBC). This technology uses HTTP/S access. Outbound Connections Connection Additional information From the SAP Solution Manager diagnostics (SMD) agent to SAP Solution Manager For information about how to install the SAP Solution Man­ ager diagnostics agent.Client Protocol and additional information TCP port SAP HANA studio This is the connection to SAP HANA lifecycle manager via SAP Host Agent. mainly database administration. 35 . Calls from SAP HANA Extended Application Services to external servers Examples: a Web server or an e-mail server (depends on what applications your company has deployed) Smart data access from SAP HANA to exter­ nal data sources for data federation purposes Smart data access for SAP HANA is described elsewhere in this document. ● SAP Data Services (DS) The protocol is SQLDBC (ODBC/JDBC). 3xx15 The protocol is SQLDBC (ODBC/JDBC). ● SAP Replication Server (not included with all li­ censed editions of SAP HANA) The protocol is SQLDBC (ODBC/JDBC). Data Provisioning Client Protocol and additional information TCP port SAP Event Stream Processor (SAP ESP) (not included with all licensed editions of SAP HANA) This connection is used for event streaming. 3xx17 Replication systems for external data sources ● The following replication technologies may be used: ● SAP Landscape Transformation (SLT) The protocol is SQLDBC (ODBC/JDBC). see the SAP HANA Server Installation and Update Guide. see the SAP HANA Administration Guide. Other administrative tasks. see SAP Note 1858920. ● SAP HANA Direct Extractor Connection (DXC). All rights reserved.

For more information. In SAP HANA. All rights reserved.2. server components are distributed across multiple hosts for the purposes of scalability and availability. It is perceived as one unit from the perspective of the administrator. JDBC. The different services of the system share the same metadata. ODBC. ODBO or ADO. see the SAP HANA R Integration Guide. update. Related Information Host Name Resolution for Client Communication [page 50] Client applications communicate with SAP HANA servers from different platforms and types of clients via a client library (such as SQLDBC. There are two types of internal communication: ● 36 Distributed scenarios Internal network communication takes place between the hosts of a distributed system on one site. server components are distributed across multiple hosts for the purposes of scalability and availability. Certified SAP HANA hosts contain a separate network interface card that is configured as part of a private network. you'll want to get an overview of the internal connections between server components. SAP HANA Master Guide SAP HANA Architecture . PUBLIC © 2014 SAP SE or an SAP affiliate company. using separate IP addresses and ports. shut down. SAP Help Portal (including the above-mentioned guides) SAP Note 1858920 SAP HANA Smart Data Access [page 21] SAP HANA smart data access enables remote data to be accessed as if they were local tables in SAP HANA. Otherwise it is a single-host system. In addition to external network connections. and requests from client applications are transparently dispatched to the different services in the system. without copying the data into SAP HANA. An installed SAP HANA system is identified by a system ID (SID). start up.NET) for SQL or MDX access. who can install. you'll want to get an overview of the internal connections between server components.Connection Additional information From SAP HANA to the R environment Only required for scenarios which use the R integration sup­ ported by SAP HANA. Connections for Distributed SAP HANA Systems [page 36] Before you start configuring the network for SAP HANA.2 Connections for Distributed SAP HANA Systems Before you start configuring the network for SAP HANA. or back up the system as a whole. SAP HANA uses separate. In SAP HANA. A distributed SAP HANA system is a system that is installed on more than one host.2. dedicated connections exclusively for internal communication. 3. DBSL. An SAP HANA instance is a set of components of a distributed system that are installed on one host.

after n->1 recov­ ery System replication Internal network communication for system replication takes place between a primary site and a secondary site. on hardware vendor delivered options. The preferred method depends on the data center configuration. In this case. There are a number of ways to isolate internal network ports from the client network. see the SAP HANA Security Guide. must be secured in separate steps. see the SAP HANA Security Guide. see the SAP HANA Administration Guide. 37 . For additional security it is possible to encrypt the internal communication using SSL. Table 1: Ports for Distributed Scenarios The xx in the port numbers stands for your SAP HANA instance number. For more in­ formation. SAP HANA Master Guide SAP HANA Architecture PUBLIC © 2014 SAP SE or an SAP affiliate company. For more information about configuring SSL for internal communication as well as securing communication between sites in system replication scenarios. and data replication and log replication channels on the other. 3xx07 xsengine 3xx10 compileserver 3xx40-3xx99 indexservers Optional. between the tier-2 and tier-3 secondary systems. You can secure system replication connections using the Secure Sockets Layer (SSL) protocol. Before SPS 06. and on the high availability implementation.Note In single-host scenarios. these ports were by default bound to all network interfaces. the same communication channels are used for communication between the different processes on a single host and the internal IP addresses/ports are by default bound to the localhost interface. In a multitier setup. For more information about system replication and multitier setups. asynchronously. Applying network separation for the internal communication prevents unauthorized access from outside networks. By default. landscape topology communication on the one hand. For more information about security. see SAP Note 1917938. All rights reserved. this communication takes place between the tier-1 primary system and tier-2 secondary system as well as. ● Client TCP port Service Use Hosts of a distrib­ uted system on one site 3xx00 daemon 3xx01 nameserver 3xx02 preprocessor 3xx03 indexserver 3xx04 scriptserver Optional 3xx05 statisticsserver Applicable only if you do not use the embedded sta­ tistics server. SSL is turned off.

fully system-replicated to a secondary site to provide full disaster recovery support. Hosts on primary and secondary sites 3xy01 nameserver Log and data shipping 3xy02 nameserver Metadata communication 3xy03 indexserver Log and data shipping 3xy04 scriptserver Log and data shipping (optional) 3xy05 statisticsserver Log and data shipping Applicable only if you do not use the embedded sta­ tistics server. 3xy07 xsengine Log and data shipping 3xy40-3xy99 indexservers Log and data shipping (optional. see SAP Note 1917938. Client TCP port Service Used for.Table 2: Ports for System Replication The xy in the port numbers stands for your SAP HANA instance number plus 1. after n->1 recov­ ery) Example 1 The following diagram shows a distributed SAP HANA system with two active hosts and an extra standby host... SAP HANA Master Guide SAP HANA Architecture . 38 PUBLIC © 2014 SAP SE or an SAP affiliate company. For more in­ formation. All rights reserved.

all instances communicate with all other instances of a distributed system on one site. The HTTP load balancer can also be used to provide load-balanced access to multiple distributed SAP HANA Extended Application Services (XS) servers. which can be either a network attached storage device (NAS) or a storage area network (SAN). The details of system replication configuration depend on the specific network setup of your company. The horizontal blue dashed lines show the initial connection for system replication communication between services on hosts on the primary site and the corresponding services on hosts of the secondary site (typically over a high-performance fiber network). SAP HANA Master Guide SAP HANA Architecture PUBLIC © 2014 SAP SE or an SAP affiliate company. The diagram shows two additional components that can be used to handle client reconnection: ● An HTTP load balancer (such as SAP Web Dispatcher) acts as a reverse proxy for HTTP connections and exposes a consistent external network address to the client network. Also shown is the connection to a storage subsystem.The vertical blue dashed lines show the communications between the services of the system. All rights reserved. which can be used in conjunction with DNS or virtual IP redirection For information about how to set up multiple XS instances as well as client connection recovery. 39 . ● A network device (router and/or switch). see the SAP HANA Administration Guide. One of the most critical aspects of the network design of a highly available distributed system is the question of how the different clients manage to reconnect to the system when its topology changes due to the recovery operations following a failure or disaster.

Connections from Database Clients and Web Clients to SAP HANA [page 32] Before you start configuring the network for SAP HANA. Host Name Resolution for System Replication [page 48] The correct mapping of internal host names between primary and secondary systems is required for system replication. SAP HANA Administration Guide SAP HANA Security Guide SAP Note 1917938 40 PUBLIC © 2014 SAP SE or an SAP affiliate company. Host names are mapped to these IP addresses through internal host name resolution. you'll want to get an overview of the external client connections to SAP HANA . All rights reserved.Example 2 The following diagram shows an example of multitier system replication: Related Information Internal Host Name Resolution [page 45] The SAP HANA services use IP addresses to communicate with each other. SAP HANA Master Guide SAP HANA Architecture . a technique by which the use of specific and/or fast networks can be enforced and communication restricted to a specific network.

Fault recovery is the process of recovering and resuming operations after an outage due to a fault. ○ Storage replication: Continuous replication (mirroring) between primary storage and backup storage over a network (may be synchronous). This improves the availability by significantly reducing the recovery time from an outage. software and network components. 3. and uninterrupted power supply (UPS). 2. All rights reserved.3. network redundancy and data center redundancy. with minimal delay and without loss of data. Disaster recovery is the process of recovering operations after an outage due to a prolonged data center or site failure. 41 . in case of failure of the primary. SAP HANA High Availability Support As an in-memory database. Additionally. Disk storage systems use batteries to guarantee writing even in the presence of power failure. including hardware redundancy. Software – SAP HANA is based on SUSE Linux Enterprise 11 for SAP and includes security preconfigurations (for example. SAP HANA supports the following recovery measures from failures: ● ● Disaster recovery support: ○ Backups: Periodic saving of database copies in safe place. SAP HANA is not only concerned with maintaining the reliability of its data in the event of failures. savepoints and snapshots to support system restart and recovery from host failures. The key to achieving high availability is redundancy. the SAP HANA system software also includes a watchdog function.2. ○ System replication: Continuous update of secondary systems by primary system. High availability is the name given to a set of techniques. which automatically restarts configured services (index server. to disasters that decommission an entire data center. name server. active hosts. and so on). but also with resuming operations with most of that data loaded back in memory as quickly as possible. and providing the ability to rapidly resume operations after a system outage with minimal business loss (fault resilience). Fault recovery support: ○ Service auto-restart: Automatic restart of stopped services on host (watchdog). High availability is achieved by eliminating single points of failure (fault tolerance). all these redundancy solutions are transparent to SAP HANA's operation. and may thus be more complex. Standby and Failover – Separate. dedicated standby hosts are used for failover. in case of detected stoppage (killed or crashed).1 High Availability for SAP HANA SAP HANA is fully designed for high availability. engineering practices and design principles that support the goal of business continuity. Generally speaking. but they form part of the defense against system outage due to single component failures. SAP HANA provides several levels of defense against failure-related outages: 1. 4. Hardware Redundancy – SAP HANA appliance vendors offer multiple layers of redundant hardware. Persistence – SAP HANA persists transaction logs. minimal network services). SAP HANA Master Guide SAP HANA Architecture PUBLIC © 2014 SAP SE or an SAP affiliate company.2. and use striping and mirroring to provide redundancy for automatic recovery from disk failures. including inmemory table loading. Preparing for disasters may require backing up data across longer distances.2. It supports recovery measures ranging from faults and software errors. enterprise grade errorcorrecting memories. such as redundant power supplies and fans. fully redundant network switches and routers.

System replication is flexible enough that it can also be used for both fault and disaster recovery to achieve high availability.3 Host Name Resolution The assignment of multiple host names to the same host supports performance optimization as well as the security of your SAP HANA system. In the case of single node systems this means. the local disk infrastructure needs to be doubled. Using Secondary Servers for Non-Productive systems With SAP HANA system replication you can use the servers on the secondary system for non-productive SAP HANA systems under the following conditions: ● Table pre-load is turned off in the secondary system. ○ System replication: Continuous update of secondary systems by primary system. SAP HANA Master Guide SAP HANA Architecture . ● The non-productive systems are stopped with the takeover to the productive secondary. The data pre-load option can be used for fault recovery to enable a quicker takeover than with Host Auto-Failover. ● The secondary system uses its own disk infrastructure. in the following files: /usr/sap/sapservices /usr/sap/<SID>/HDB<instance_number>/<hostname>/sapprofile. Default Host Names The default host names if nothing else is configured during the installation of SAP HANA are the host names defined at operating system level. All rights reserved. the names of the SAP HANA instances) and stores them in the sapstart service profiles. Related Information SAP HANA Administration Guide 3. You can build a solution with single node systems and do not need a scale out system and the additional storage and associated costs.2. that is. The installation extracts the host names known to the operating system (that is.○ Host auto-failover: Automatic failover from crashed host to standby host in the same system.ini 42 PUBLIC © 2014 SAP SE or an SAP affiliate company. including inmemory table loading.

Host names specified in this manner must be resolvable during installation time as well as when SAP HANA is in operation.91.226 SAP HANA Master Guide SAP HANA Architecture localhost virtualhost1. for example. Virtual host names must also be unique across multiple SAP HANA systems if more than one data center or site is used. SAP HANA system views with a HOST column show these host names. Virtual Host Names Another approach is to specify alternative host names during installation.1 10. by adding an <ip> <hostname> line to the operating system file /etc/hosts that contains the hostname-to-IP address mappings for the TCP/IP subsystem.wdf.0. 43 . indexserver.68. All rights reserved.sap. and so on) and the SAP start service (sapstartsrv).corp virtualhost1 PUBLIC © 2014 SAP SE or an SAP affiliate company. Here is an example of what this might look like at operating system level for one host: 127. This is achieved.Figure 1: Example of Default Host Names for SAP HANA These host names are then used for all internal communications between the SAP HANA services (nameserver. In addition. These are referred to as virtual hostnames.0.

0.68. It is also possible to assign virtual hostnames once the system is up and running. The /etc/hosts file for each host must include the corresponding lines: host1 127.Virtual hostnames are assigned as part of the installation process with the LCM command line tool hdblcm using the following parameter: hdblcm … --hostname=<virtualhostname> The <virtualhostname> is then stored as the internal hostname in the sapstart service profiles and shows up in the HOST column of any system view. using the LCM command line tool hdbrename. All rights reserved.1 10.wdf.0.226 10. the host names of all hosts must be known to each SAP HANA host.corp virtualhost1 virtualhost2.1 localhost 44 PUBLIC © 2014 SAP SE or an SAP affiliate company.68. SAP HANA Master Guide SAP HANA Architecture .91.sap.227 localhost virtualhost1. Figure 2: Example of Virtual (Internal) Host Names for SAP HANA Distributed Landscapes In multiple-host systems used for scale-out.corp virtualhost2 host2 127.0.sap.91.wdf.0.

a technique by which the use of specific and/or fast networks can be enforced and communication restricted to a specific network. SAP HANA Master Guide SAP HANA Architecture PUBLIC © 2014 SAP SE or an SAP affiliate company.ini files.0.10. This can be achieved by manually adding all hosts to each /etc/hosts file on the operating system of each host.ini [communication] listeninterface=. JDBC.wdf.wdf. 45 .226 10. the [communication] listeninterface is set to .1). a technique by which the use of specific and/or fast networks can be enforced and communication restricted to a specific network. Host names are mapped to these IP addresses through internal host name resolution.0. Host Name Resolution for System Replication [page 48] The correct mapping of internal host names between primary and secondary systems is required for system replication.227 virtualhost1. Host Name Resolution for Client Communication [page 50] Client applications communicate with SAP HANA servers from different platforms and types of clients via a client library (such as SQLDBC.91. no additional configuration is required.91. The services listen on the loopback interface only (IP address 127.local In a distributed scenario with multiple hosts.corp virtualhost2 Related Information Internal Host Name Resolution [page 45] The SAP HANA services use IP addresses to communicate with each other. the network needs to be configured so that interservice communication is operational throughout the entire landscape. In the global.NET) for SQL or MDX access. ODBC. ODBO or ADO.1 Internal Host Name Resolution The SAP HANA services use IP addresses to communicate with each other.corp virtualhost1 virtualhost2. All rights reserved. In this setup. DBSL.sap.local : global.2. Single Host Versus Multiple Hosts For single-host systems.3. A distributed system can run with or without a separate network definition for interservice communication. SAP HANA Server Installation and Update Guide SAP HANA LCM Tools Reference Guide 3.68. Host names are mapped to these IP addresses through internal host name resolution.68. the host names (these could be virtual host names) of all hosts must be known to each other and thus to the SAP HANA system.sap.

Distributed System Without a Separate Internal Network If no separate network is defined for internal communication.ini [communication] listeninterface=<.ini [communication] listen_interface=.ini file parameters (the [internal_hostname_resolution] section must be created manually): global. by adapting the following global. All rights reserved.internal in the global.internal/CIDR netmask> [internal_hostname_resolution] <ip-address_internal_network>=<internal_hostname> The installer automatically chooses on each host a network interface within the allowed network mask. SAP HANA Master Guide SAP HANA Architecture . In the global.ini file. the SAP HANA services listen on all available network interfaces. post installation.internal 46 PUBLIC © 2014 SAP SE or an SAP affiliate company.0/20 ● manually.global: global.ini [communication] listen_interface=.66. the listening interface is set to . the SAP HANA services listen on this interface only : global./hdblcm --internal_network=10.global Distributed System with a Separate Internal Network A distributed system can be configured with a dedicated internal network in either of the following ways: ● at installation time. using the hdblcm command line option as in the following example: .ini file. If the network interface is defined as .128.

All rights reserved. SAP HANA Administration Guide SAP HANA Master Guide SAP HANA Architecture PUBLIC © 2014 SAP SE or an SAP affiliate company. 47 . see the SAP HANA Administration Guide. commands from outside the SAP HANA system.This illustration shows how a separate internal network might be configured for a SAP HANA database with three hosts: Figure 3: Example of a Separate Internal Network for a Distributed SAP HANA System Only the SAP start service (sapstartsrv) still listens on all interfaces.. to accept start/stop/. Related Information Example of Host Name Resolution [page 49] The following example shows the host name resolution configuration for a distributed system with a separate internal network as well as a dedicated network for system replication to a secondary site.. For more information about configuring the network for multiple hosts.

depending mainly on the distance between the two sites. Registration is one step in the process of configuring the secondary system. through configuration in SAP HANA or corresponding entries in the /etc/hosts file. For multitier system replication. Note The settings in the global. For a full description of system replication. Related Information Example of Host Name Resolution [page 49] The following example shows the host name resolution configuration for a distributed system with a separate internal network as well as a dedicated network for system replication to a secondary site. SAP HANA Administration Guide White paper "Introduction to High Availability for SAP HANA" 48 PUBLIC © 2014 SAP SE or an SAP affiliate company. only direct neighbors have to be listed.2.ini file must be done prior to registering the secondary system. The replication of the transactional load can be configured to work in synchronous or asynchronous mode. see the SAP HANA Administration Guide. Communication between the primary and the secondary system is based on internal host names. To enforce specific networks and to avoid issues with host name resolution (for example.2 Host Name Resolution for System Replication The correct mapping of internal host names between primary and secondary systems is required for system replication.3. because SAP HANA was installed with short names) without the need to adapt the entries in the /etc/hosts file.3. SAP HANA Master Guide SAP HANA Architecture . With SAP HANA system replication.ini [system_replication_hostname_resolution] <ip-address_other_site>=<internal_host_other_site> The section [system_replication_hostname_resolution] contains only hosts from other sites. for example. For information about configuring the secondary system. The host names of the other site must always be resolvable. All rights reserved. because the sr_register command uses this mapping. see the SAP HANA Administration Guide and the white paper Introduction to High Availability for SAP HANA. internal hostnames can be mapped to IP addresses in the global. each SAP HANA instance communicates on the service level with a corresponding peer in the secondary system to persist the same data and logs as in the primary system.ini file as follows: global.

49 .2.2. indexserver. and so on) in a distributed system.internal parameter in the [communication] section is required for the communication between SAP HANA services (nameserver. But the addition of the virtual host names to the global. it is not specific to SAP HANA system replication. Figure 4: Multiple-Host System Replication over a Separate Network with an Internal Network The two systems cannot communicate with each other directly because they use virtual host names.1 Example of Host Name Resolution The following example shows the host name resolution configuration for a distributed system with a separate internal network as well as a dedicated network for system replication to a secondary site.3.global/.3.ini file ensures that each site can resolve the host name of the other site. All rights reserved. Related Information Host Name Resolution for System Replication [page 48] The correct mapping of internal host names between primary and secondary systems is required for system replication. Note The listeninterface=. SAP HANA Master Guide SAP HANA Architecture PUBLIC © 2014 SAP SE or an SAP affiliate company.

50 PUBLIC © 2014 SAP SE or an SAP affiliate company. statements may be sent to any of these hosts. making the first statement run very slowly. the user doesn't normally notice this.Internal Host Name Resolution [page 45] The SAP HANA services use IP addresses to communicate with each other. ● In distributed systems.3 Host Name Resolution for Client Communication Client applications communicate with SAP HANA servers from different platforms and types of clients via a client library (such as SQLDBC.NET) for SQL or MDX access. Public Host Name Resolution An SQL client library always connects to the first available host specified in the connect string. From this host. For more information. ODBO or ADO.3. see Related Information below. If a hostname or IP address is unresolvable.ini [public_hostname_resolution] use_default_route=ip This works as long as there is only one external network. as configured in the following parameter: global. By default. Host names are mapped to these IP addresses through internal host name resolution. In rare cases. which enables access to SAP HANA Extended Application Services (SAP HANA XS). the application has a logical connection to the SAP HANA system: that is. All rights reserved. In distributed systems. The client library supports load balancing and minimizes communication overhead by: ● Selecting connections based on load data ● Routing statements based on information about the location of data Communication with SAP HANA hosts from a Web browser or a mobile application is requested using the HTTP protocol. the client library falls back on the host names in the connect string: ● In single-host systems. a technique by which the use of specific and/or fast networks can be enforced and communication restricted to a specific network. SAP HANA Master Guide SAP HANA Architecture . ODBC. the client library may in fact use multiple connections to different servers or change to a different underlying connection. JDBC.2. 3. the IP address of the primary network interface is returned to the clients. performance is impaired because statements must first be sent to the initial host and then forwarded on the server side to the right host. the connection attempt does not fail immediately but waits for a tcp timeout. DBSL. During operations. the client library then receives a list of all the hosts.

see the SAP HANA Administration Guide. use SAP HANA Master Guide SAP HANA Architecture PUBLIC © 2014 SAP SE or an SAP affiliate company. Figure 5: Example of Auto Host-Failover One way to look up the master candidates in your distributed SAP HANA database is to use the following SQL statement: select HOST from SYS.host2:30015. The connect string for JDBC. a list of hosts ( host:port ) is specified in the SQL client library connect string. Connect String for SAP HANA System Replication If system replication is used. we recommend that you do not specify physical host names in the SQL client connect string. Host 2). 51 . these hosts do not contain any data and do not accept requests or queries. even after failover. for example. and the standby host takes over its role by starting its database instance using the persisted data and log files of the failed host. An active host fails (in this example. a standby host automatically takes its place. because they are one of the three configured master candidates. When an active (worker) host fails. As long as they are in standby mode. Inclusion of the standby hosts in the connect string is mandatory if they are master candidates. could look like this: jdbc:sap://host1:30015. must be listed in the connect string to allow an initial connection to any of them in the event of a host auto-failover. otherwise optional.M_LANDSCAPE_HOST_CONFIGURATION where NAMESERVER_CONFIG_ROLE like 'MASTER%' order by NAMESERVER_CONFIG_ROLE For more information about configuring clients for failover. you would have to reconfigure all of your applications after a takeover.Connect String with Multiple Hostnames In a distributed SAP HANA system consisting of more than one host. Otherwise.host3:30015/ All hosts that could become the active master. ensuring that the clients can always access the SAP HANA database. Instead. The following diagram illustrates how host auto-failover works. One (or more) standby hosts are added to a SAP HANA system and configured to work in standby mode. All rights reserved. The client connection code (ODBC/JDBC) uses a "round-robin" approach to reconnection. A host auto-failover is an automatic switch from a crashed host to a standby host in the same system.

corp Disable feature and use internal host name hananode01 52 use_default_route = no PUBLIC © 2014 SAP SE or an SAP affiliate company. System replication takeover hooks can be implemented to provide notification about the takeover. see the SAP HANA Administration Guide. or multiple external networks. a [public_hostname_resolution] section in the global.2. Each host identifies the network interface and thus the default route for the connection: Description Parameter Example IP address of the interface use_default_route = ip 10.ip. SAP HANA Administration Guide SAP Note 1780950 SAP Note 1876398 3.2. network address translation (NAT) types.ini file is used with: use_default_route = ip # values: no.lnd.abc. SAP HANA Master Guide SAP HANA Architecture . By default. such as for certain firewall configurations.3. Exact mappings have higher priority than pattern mappings.fqdn optional pattern mapping: map_<internal-prefix>* = <public-prefix>*<publicsuffix> optional exact mapping: map_<internal-name> = <public-name> The optional mappings are considered only if use_default_route is set to no.1 Mapping Host Names for Database Client Access Clients communicate with the database through external hostnames or external IP addresses. and manage it using an external cluster manager. Related Information Mapping Host Names for Database Client Access [page 52] Clients communicate with the database through external hostnames or external IP addresses. This virtual host name or IP address must point to the active master host on the active primary site.name.71 Host name of the interface use_default_route = name lnd8520 Fully qualified name of the interface use_default_route = fqdn lnd8520. A default mapping of external hostnames to internal hostnames enables statement routing and automatic reconnection in the event of a failover.3. A default mapping of external hostnames to internal hostnames enables statement routing and automatic reconnection in the event of a failover. For more information about takeover hooks and client connection recovery.4.a virtual host name or virtual IP address. the IP address of the primary network interface is used but there may be situations where you need to change this configuration. All rights reserved. For this purpose.

ODBO or ADO.4.2.2.. JDBC.abc.4. SAP HANA Security Guide SAP HANA Master Guide 3.72 map_hananode03 = 10. You need to specify your own mapping only if the default route mechanisms do not fit your network requirements Example Here are some examples of how you might customize this parameter: [public_hostname_resolution] use_default_route = no map_hananode* = myservername* [public_hostname_resolution] use_default_route = no map_hananode* = hananode*.In most cases. WITH RECONFIGURE .corp [public_hostname_resolution] use_default_route = no map_hananode01 = 10.74 [public_hostname_resolution] use_default_route = no map_hananode0* = 10.4. DBSL. Related Information Host Name Resolution for Client Communication [page 50] Client applications communicate with SAP HANA servers from different platforms and types of clients via a client library (such as SQLDBC. 53 .3 SAP HANA Software Components The SAP HANA Platform Edition is composed of the following components: ● SAP HANA database ● SAP HANA client SAP HANA Master Guide SAP HANA Architecture PUBLIC © 2014 SAP SE or an SAP affiliate company.NET) for SQL or MDX access.7* map_hananode1* = 10. All rights reserved.73 map_hananode04 = 10.71 map_hananode02 = 10.2.4. see if you can use one of the default route mechanisms..4. If you do need to configure something.4. you do not need to configure anything.2. ODBC.2.lnd.8* Changes to configuration and default routes are checked once a minute and become effective within a minute after the SQL system management statement ALTER SYSTEM ALTER CONFIGURATION .2.

SAP HANA edition) ● SAP HANA Database edition for BW ● SAP HANA Limited edition for Apps / Accelerators ● SAP HANA EDGE edition Note SAP HANA information composer is a Web-based environment that allows business users to upload data to the SAP HANA database and to manipulate that data by creating information views. This is a subset of the available editions: ● SAP HANA Enterprise Edition (including components for data replication and acquisition) ● SAP HANA Real-time-data edition (includes SAP Replication Server.● SAP HANA client for Microsoft Excel ● SAP HANA studio (including SAP HANA STUDIO RSA PLUGIN) ● SAPUI5 Tools IDE PLUGIN ● SAP Host Agent ● SAP Solution Manager Diagnostics Agent ● SAP HANA information composer ● SAP HANA AFL ● SAP HANA LCApps ● SAP HANA lifecycle manager ● SAP HANA INA Toolkit HTML ● SAP HANA INA Fileloader ● SAP HANA EPM Service ● SAP HANA SHINE cntent ● SAP HANA smart data access ● SAP HANA HW Configuration Check Tool The SAP HANA Platform Edition is bundled together with other products into editions as license bundles for special purposes. SAP HANA Master Guide SAP HANA Architecture . All rights reserved. 54 PUBLIC © 2014 SAP SE or an SAP affiliate company. The SAP HANA information composer is installed separately from the SAP HANA system.

2 In the Cloud In the cloud.4 SAP HANA Deployment Options SAP HANA is a modern. ● Compared with the appliance delivery approach. SAP HANA tailored data center integration is a more open and flexible approach to serve your needs regarding the integration of SAP HANA in the data center.SAP HANA tailored data center integration 4.1 On-Premise In an on-premise deployment. SAP HANA is deployed through the following cloud offerings: ● SAP HANA Cloud Platform ○ SAP HANA Infrastructure Services High-performance cloud infrastructure to quickly deploy existing SAP HANA licenses Infrastructure-only on a monthly subscription (license bought separately) ○ SAP HANA DB Services Fully-featured SAP HANA hosted in the public cloud Infrastructure and license on a monthly subscription ○ SAP HANA App Services SAP HANA Platform-as-a-Service (PaaS) in a cloud environment SAP HANA Master Guide SAP HANA Deployment Options PUBLIC © 2014 SAP SE or an SAP affiliate company. 4. in-memory database and platform that is deployable on-premise or in the cloud. ○ The storage solution has successfully passed SAP HANA hardware certification. On-premise SAP HANA is deployed through the following offerings: ● As an appliance. The requirements for this deployment option are as follows: ○ The server is listed in the SAP HANA product availability matrix. SAP HANA combines software components from SAP optimized on proven hardware provided by SAP’s hardware partners. SAP HANA is offered as a comprehensive infrastructure combined with managed services. All rights reserved. Check the SAP Education resources for information about the SAP HANA certification exams. ○ The person performing the SAP HANA installation has passed the certification exam. SAP HANA runs on dedicated hardware. Related Information SAP Traning & Education Overview . 55 .

SAP HANA Master Guide SAP HANA Deployment Options . All rights reserved.Infrastructure and license on a monthly subscription ● SAP HANA Enterprise Cloud Enterprise-class SAP HANA managed cloud offering Infrastructure and managed services on a monthly subscription (license bought separately) ● SAP HANA One Fully-featured SAP HANA hosted in the public cloud Infrastructure and license on an hourly subscription 56 PUBLIC © 2014 SAP SE or an SAP affiliate company.

Context For information about sizing SAP HANA.SAP BW on HANA: Sizing SAP HANA Database SAP HANA Master Guide SAP HANA Implementation and Operation PUBLIC © 2014 SAP SE or an SAP affiliate company.SAP HANA: Sizing SAP HANA SAP Note 1704499 . All rights reserved.System Measurement for License Audit ● SAP Note 1637145 .com/quicksizing . powered by SAP HANA are available in the Quick Sizer tool: https://service. 57 . see the following SAP Notes: ● SAP Note 1514966 . 5.SAP BW on HANA: Sizing SAP HANA Database Note SAP HANA and SAP NetWeaver BW 7.System Measurement for License Audit SAP Note 1637145 . Related Information SAP Note 1514966 .3.5 SAP HANA Implementation and Operation The implementation and operation of SAP HANA depends on the chosen use case and the technical deployment.sap.1 Sizing SAP HANA SAP HANA needs to be sized according to the system requirements.SAP HANA: Sizing SAP HANA ● SAP Note 1704499 .

3 Administrating SAP HANA The SAP HANA Technical Operations Manual and the SAP HANA Administration Guide provide information about administering and operating your SAP HANA system landscape. All rights reserved. see the SAP HANA documentation on SAP Help Portal: ● SAP HANA Server Installation and Update Guide This guide describes how to install and update an SAP HANA system with the SAP HANA lifecycle management tools.5. However. ● SAP HANA Client Installation and Update Guide ● SAP HANA Studio Installation and Update Guide Data Provisioning Technologies You can find the documentation for the data provisioning technologies on different publication channels: ● SAP HANA Installation Guide – Trigger-Based Replication (SLT) ● SAP HANA Direct Extractor Connection Implementation Guide ● SAP HANA smart data access SAP HANA smart data access is part of SAP HANA. SAP HANA Platform Edition For information about installing SAP HANA. see the SAP HANA Administration Guide. it is not installed during the installation of the SAP HANA Platform Edition. SAP HANA Master Guide SAP HANA Implementation and Operation . ● Log-Based Replication (SAP Replication Server) See the SAP Replication Server documentation on SAP Help Portal. ● ETL-Based Replication (SAP Data Services) See the Enterprise Information Management page on SAP Help Portal. depending on the data provisioning technology you use or other components you want to add to your SAP HANA landscape. 58 PUBLIC © 2014 SAP SE or an SAP affiliate company. You need to check specific installation information. ● SAP Event Stream Processor See the SAP Event Stream Processor documentation on SAP Help Portal. The central part is the installation of the SAP HANA Platform Edition.2 Installing SAP HANA The installation of SAP HANA comprises several steps. For more information about installing SAP HANA smart data access. 5.

a stand-alone Web browser. ● Adapting the topology of your SAP HANA platform by adding or removing additional SAP HANA systems or by adding or removing additional SAP HANA hosts. delivery units and packages. For product management tasks. such as Application Functional Library (AFL). This is used for updating the SAP HANA platform. such as: ● The initial configuration of your SAP HANA platform to integrate it into your landscape (for example. including SAP systems running on SAP HANA. ● Adding additional SAP HANA components or libraries. you can use it on the development SAP HANA system to manage products. Application Lifecycle Management Aspects Application lifecycle management aspects are offered via an interface that runs as an SAP HANA XS application in a web browser. 59 .Related Information SAP HANA Technical Operations Manual SAP HANA Administration Guide 5. registering it in a system landscape directory or configuring SAP Landscape Transformation replication). which are used in the SAP HANA Web IDE. you can use it on the target SAP HANA system to trigger an export from the source system as well as automatic import and activation of the SAP HANA content on the target system. or with the command line interface. For more information. which allow you to easily perform platform lifecycle management tasks. by renaming your SAP HANA system. For transport management tasks. Platform Lifecycle Management Aspects You can customize platform lifecycle management aspects of your SAP HANA system by accessing SAP HANA lifecycle management with either SAP HANA studio. All rights reserved. SAP HANA Master Guide SAP HANA Implementation and Operation PUBLIC © 2014 SAP SE or an SAP affiliate company. ● Updating your SAP HANA system.4 SAP HANA Lifecycle Management SAP HANA lifecycle management covers two aspects: platform lifecycle management for customizing and updating your SAP HANA platform and application lifecycle management for managing SAP HANA content products and transports. A number of tools are integrated into SAP HANA lifecycle management. see the SAP HANA Server Installation and Update Guide and the SAP HANA Administration Guide. This procedure must be done in addition to the standard maintenance procedures for updating SAP systems.

All rights reserved.With this. SAP HANA Master Guide SAP HANA Implementation and Operation . Table 3: Transport Scenarios Use case Transport Management Native SAP HANA content SAP HANA Application Lifecycle Manager Native SAP HANA content or as part of a solution SAP HANA content exclusively used by ABAP (ABAP for SAP HANA) ● SAP HANA stand-alone transport management ● No need for ABAP-footprint ● Lightweight and easy-to-use transport tool Enhanced CTS (CTS+) ● Transported like any other non-ABAP content ● Integrated in existing CTS transport landscape ● Integrated in SAP process tools (ChaRM. QGM) SAP HANA Transport Container ● Transported with standard ABAP transports ● Integrated in existing CTS transport landscape ● Integrated in SAP process tools (ChaRM. QGM) Related Information SAP HANA Server Installation and Update Guide SAP HANA Administration Guide SAP HANA Developer Guide How to Configure SAP HANA for CTS+ How-To Guides How to transport ABAP for SAP HANA applications with HTC 60 PUBLIC © 2014 SAP SE or an SAP affiliate company. administrators can perform the following application lifecycle management tasks: ● Designate source and target systems for transports ● Assign the appropriate delivery units to a transport route ● Execute exports and imports (uploads and downloads) ● Start transports and monitor the transport processes For more information. see the section Implementing Lifecycle Management in the SAP HANA Developer Guide. The table shows the transport management possibilities depending on the use case.

61 . DUs are used to group SAP HANA content artefacts. A DU is used to deliver one or more software components from SAP (or a partner) to a customer.5.0 (HANA_DXC. 5.2 Deploy SAP HANA Content The following deployment methods are provided: The following deployment methods are provided for SAP HANA content: ● SAP HANA application lifecycle management ○ UPLOAD/DOWNLOAD function This tool is available on the SAP HANA XS Web server. SAP HANA content add-ons are developed as part of the SAP HANA platform or as part of an application that runs on top of SAP HANA. The SAP HANA content types are differentiated by the method of deployment and when the content is deployed.5. The following DUs are non-automated content: ● ○ HCO INA SERVICE 1. For more information. All rights reserved. which is developed on SAP HANA Extended Application Services (SAP HANA XS) can also be grouped in a DU.5 SAP HANA Content SAP HANA content is contained in delivery units (DUs). Automated content is located on the SAP HANA system in the following folder: /usr/sap/<SID>/SYS/global/hdb/auto_content. Non-automated content is located on the SAP HANA system in the following folder: /usr/sap/<SID>/SYS/global/hdb/content.tgz) SAP HANA content that can be downloaded independently SAP HANA content that is not part of the SAP HANA database is called SAP HANA content add-on. ○ Non-automated content is installed with SAP HANA but it needs to be manually imported into the SAP HANA repository by the system administrator. SAP HANA content.0 (HCO_INA_SERVICE. see Import a Delivery Unit in the SAP HANA Developer Guide. It is used for integral parts of the SAP HANA database but is only used by a minority of customers.1 SAP HANA Content Types There are different types of SAP HANA content packages (DUs). 5.5. The following SAP HANA content types are available: ● SAP HANA content as part of the SAP HANA database ○ Automated content is installed together with SAP HANA and imported into the SAP HANA repository during the installation.tgz) ○ SAP HANA DXC 1. SAP HANA Master Guide SAP HANA Implementation and Operation PUBLIC © 2014 SAP SE or an SAP affiliate company. It is an integral part of the SAP HANA database and is used by every SAP HANA database customer.

○ Command line tool hdbalm This tool is installed together with the SAP HANA client. For more information. Related Information SAP HANA Developer Guide SAP HANA Modeling Guide SAP HANA Administration Guide 62 PUBLIC © 2014 SAP SE or an SAP affiliate company. Deploy HANA Content function This function is called from the SAP HANA lifecycle manager user interface. see Installing and Updating Products in the SAP HANA Developer Guide. For more information. All rights reserved. see Deploy SAP HANA Application Content from a Remote Host in the SAP HANA Administration Guide. ● SAP HANA studio ○ Import function of the SAP HANA Modeler Choose ○ File Import SAP HANA Content Delivery Unit . SAP HANA Master Guide SAP HANA Implementation and Operation .

com/security Unicode SAP systems and their availability https://service.sap. https://service.sap. Content Location Latest documentation for SAP HANA http://help.sap.sap. disk.com/hana* Sybase product documentation http://help.6 Appendix The appendix provides additional information. calculation of hardware requirements.com/securityguide High availability http://scn. calculation of hardware requirements .com/sizing SAP BusinessObjects installation and deployment guides http://help.sap.sap.sap.with the QuickSizer tool Released platforms and technology-related topics such as maintenance strategies and language support – Platform Availability Matrix (PAM) https://service.com/docs/DOC-7848 Security https://service. and memory resources https://service.sap.sap.com/database Sizing.com/unicode (*) You need an authorized user ID to access this information.com/incident SAP HANA Master Guide Appendix PUBLIC © 2014 SAP SE or an SAP affiliate company.com/analytics SAP BusinessObjects support https://service. Do you need to register for an SAP Service Marketplace login ? Did you forget your password ? The following table lists further useful links on SAP Service Marketplace: Content Location on SAP Service Marketplace SAP incident wizard https://service.1 Related Information Links are provided to documentation on planning your deployment that is useful to know but not necessarily directly connected to SAP HANA. such as CPU. All rights reserved.com/bosap-support Sizing. 63 .com/quicksizer disk and memory resources .sap.com/pam Network security https://service. 6.such as CPU.sap.sap.sap.com/hana_platform Previous documentation releases for SAP HANA https://service.

sap.com/rkt Important SAP Notes Read the following SAP Notes before you start the installation.com/swdc ordering of software SAP Online Knowledge Products (OKPs) – role-specific learning maps 6. All rights reserved.com/notes SAP Software Distribution Center – software download and https://service.sap.sap. which you can find on SAP Service Marketplace at https://service.Content Location on SAP Service Marketplace SAP Notes search https://service.sap. SAP Note Number Title 1514967 SAP HANA: Central Note 2004651 SAP HANA Platform SPS 08 Release Note 1523337 SAP HANA Database: Central Note 2000003 FAQ: SAP HANA 1944799 SAP HANA Guidelines for SLES Operating System 2009879 SAP HANA Guidelines for RedHat Enterprise Linux (RHEL) 1681092 Support for multiple SAP HANA databases on a single SAP HANA appliance 1976729 Application Component Hierarchy for SAP HANA 1661202 Support for multiple applications on SAP HANA 1828400 SAPUI5 tools disappeared after updating HANA Studio 1917938 Migrating the Statistic Server During Update to SPS 07 1927949 Standard Behavior for SAP Logon Tickets 1577128 Supported clients for SAP HANA 1514966 SAP HANA: Sizing SAP HANA Database 64 PUBLIC © 2014 SAP SE or an SAP affiliate company.com/notes . Make sure that you have the most up-to-date version of each SAP Note.2 https://service. These SAP Notes contain the latest information about the installation. SAP HANA Master Guide Appendix . as well as corrections to the installation documentation.

65 . Fiori Search UI ● HAN-AS-RPO SAP HANA Repository ● HAN-AS-RST SAP HANA Development Environment REST API ● HAN-AS-RUL SAP HANA Rules Framework ● HAN-AS-XS SAP HANA Extended Application Services ● HAN-AS-XS-ADM SAP HANA XS Administration ● HAN-AS-XS-JOB SAP HANA XS Scheduled Jobs ● HAN-AS-XSA SAP HANA XS Basis Applications ● HAN-AS-XSA-TM SAP HANA Task management SAP HANA Database ● HAN-DB SAP HANA Database ● HAN-DB-AFL SAP HANA Application Function Library ● HAN-DB-AFL-DQ SAP HANA Data Quality Library ● HAN-DB-AFL-PAL SAP HANA Predictive Analysis Library ● HAN-DB-AFL-SAL SAP HANA Self Service Analytics Library ● HAN-DB-AFL-SCA SAP HANA Supply Chain Algorithm Library ● HAN-DB-AFL-SOP SAP HANA Sales and Operations Planning ● HAN-DB-AFL-UDF SAP HANA Unified Demand Forecast ● HAN-DB-BAC SAP HANA Backup and Recovery ● HAN-DB-CDS SAP HANA Core Data Services ● HAN-DB-CLI SAP HANA Clients (JDBC.SAP Note Number Title 1637145 SAP BW on HANA: Sizing SAP HANA Database 1793345 Sizing for Suite on HANA 1824819 Optimal settings for SLES 11 SP2 and SLES 11 for SAP SP2 1597355 Swap space recommendation for Linux For the SAP HANA system there are no special requirements regarding swap space. Check the current SAP Notes for the various parts of SAP HANA by searching for any of the following application areas: SAP HANA Application Services ● HAN-AS SAP HANA Application Services ● HAN-AS-INA SAP HANA InA Tools and Infrastructure ● HAN-AS-INA-FLY SAP HANA InA Firefly ● HAN-AS-INA-MDS SAP HANA InA Multidimensional Service ● HAN-AS-INA-SCV SAP HANA InA Service ● HAN-AS-INA-UI SAP HANA InA Toolkit. ODBC) ● HAN-DB-ENG SAP HANA DB Engines ● HAN-DB-ENG-BW SAP HANA BW Engine ● HAN-DB-ENG-GPH SAP HANA Graph Engine SAP HANA Master Guide Appendix PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

● HAN-DB-ENG-GPH-API SAP HANA Graph Engine API ● HAN-DB-ENG-GPH-WIP SAP HANA Graph Engine Wipe ● HAN-DB-ENG-PLE SAP HANA Planning Engine ● HAN-DB-ENG-SPA SAP HANA Spatial Engine ● HAN-DB-ENG-TXT SAP HANA Text Engine ● HAN-DB-ENG-VE SAP HANA Velocity Engine ● HAN-DB-EPM SAP HANA Enterprise Performance Management Platform ● HAN-DB-EPM-PLT SAP HANA EPM Platform ● HAN-DB-EPM-XSL SAP HANA EPM XSJS library ● HAN-DB-HA SAP HANA High Availability ● HAN-DB-LVC SAP HANA integrated liveCache ● HAN-DB-MDX SAP HANA MDX Engine/Excel Client ● HAN-DB-MON SAP HANA Monitoring ● HAN-DB-PER SAP HANA Database Persistence ● HAN-DB-R SAP HANA Integration with R ● HAN-DB-SCR SAP HANA SQL Script ● HAN-DB-SDA SAP HANA Smart Data Access ● HAN-DB-SEC SAP HANA Security and User Management ● BC-DB-LCA SAP HANA liveCache Applications ● BC-CCM-HAG SAP Host Agent ● SV-SMG-DIA SAP Solution Manager Diagnostics Agent SAP HANA Data Provisioning Services ● HAN-DP SAP HANA Data Provisioning Services ● HAN-DP-DS SAP Data Services ● HAN-DP-DXC SAP HANA Direct Extractor Connector ● HAN-DP-LTR SAP Landscape Transformation Replication Server ● HAN-DP-REP SAP Replication Server SAP HANA Information Composer ● HAN-IC SAP HANA Information Composer SAP HANA Lifecycle Management ● HAN-LM SAP HANA Lifecycle Management ● HAN-LM-APP SAP HANA Application Lifecycle Management ● HAN-LM-INS SAP HANA Installation ● HAN-LM-INS-DB Installation of HANA Database ● HAN-LM-INS-SAP Installation of SAP Systems on HANA ● HAN-LM-PLT SAP HANA Platform Lifecycle Management ● HAN-LM-UPG SAP HANA Upgrade ● HAN-LM-UPG-DB Upgrade of HANA Database ● HAN-LM-UPG-SAP Upgrade of SAP Systems on HANA SAP HANA Studio (Eclipse) ● HAN-STD SAP HANA Studio (Eclipse) ● HAN-STD-ADM SAP HANA Administration 66 PUBLIC © 2014 SAP SE or an SAP affiliate company. SAP HANA Master Guide Appendix . All rights reserved.

the Customer Interaction Center (CIC) is available 24 x 7 in every region to help you resolve any issues you may run into (https://service. so you can. BI-BIP-CRS SAP Crystal Reports ● BI-RA-XL Dashboard Designer ● BI-BIP-IDT Information design tool ● BI-RA-WBI Web Intelligence ● BI-RA-AO-XLA MS Excel Add-In The search also supports using the wildcard asterisk (*).sap. for example. All rights reserved. Porting and DB Interface) ● BC-DB-HDB-CCM CCMS for SAP HANA ● BC-DB-HDB-POR DB Porting for SAP HANA ● BC-DB-HDB-SYS SAP HANA database interface/DBMS End User Clients ● BI-BIP.com/incident .com/supportcenters SAP HANA Master Guide Appendix ).Server Component ● HAN-STD-DEV-RUL SAP HANA Rules Editor ● HAN-STD-DEV-SCR SAP HANA SQL Script Editor/Debugger ● HAN-STD-DEV-TP SAP HANA Tools Platform / Team Provider ● HAN-STD-DEV-TP-CM SAP HANA Development Change Management ● HAN-STD-DEV-UIS SAP HANA UI Integration Services ● HAN-STD-DEV-XS SAP HANA XS Editors and Wizards SAP HANA Web IDE ● HAN-WDE SAP HANA Web IDE SAP HANA Database (CCMS.sap. PUBLIC © 2014 SAP SE or an SAP affiliate company.● HAN-STD-ADM-BAC SAP HANA Backup and Recovery (Studio) ● HAN-STD-ADM-DBA SAP HANA Database Administration and Monitoring ● HAN-STD-ADM-PVZ SAP HANA Plan Visualizer ● HAN-STD-ADM-SEC SAP HANA Security and User Management (Studio) ● HAN-STD-DEV SAP HANA Development Tools ● HAN-STD-DEV-CDS SAP HANA CDS Tools ● HAN-STD-DEV-CDS-GRA SAP HANA CDS Graphical Modeler ● HAN-STD-DEV-DP SAP HANA Data Provisioning Modeler ● HAN-STD-DEV-EPM SAP HANA EPM Modeler ● HAN-STD-DEV-MOD SAP HANA Analytical Modeling ● HAN-STD-DEV-MOD-CLT SAP HANA Analytical Modeling . 67 . In addition. report an incident on the SAP Service Marketplace at http:// service. also search for BC-DB-HDB* or similar and you will get results for all sub-components.Client Component ● HAN-STD-DEV-MOD-SRV SAP HANA Analytical Modeling . Reporting Incidents If you encounter any problems with the software. BI-BIP-CMC Business intelligence platform (formerly known as BOE) ● BI-RA-EXP SAP BusinessObjects Explorer ● BI-RA-CR.

follow the steps in this guide (SAP Active Global Support Reference Guide ). For more information. see the information page of the product version. Related Information SAP HANA Administration Guide 6. ● If a customer chooses an SAP HANA appliance. When you install your SAP system.0 ● Installations and Upgrades HANA Platform Edition A-Z Index Installations and Upgrades - SAP HANA PLATFORM EDITION SAP Installation Support Packages and Patches for SAP HANA: SAP Software Download Center Patches . the components of SAP HANA have to be installed on validated hardware by a certified administrator. the components of SAP HANA can only be installed by certified hardware partners on validated hardware running a specific operating system. We recommend that you apply for a permanent license key as soon as possible after installing your system. SAP HANA Master Guide Appendix .0 The responsibility for acquiring and installing SAP HANA depends on the chosen deployment model: ● If a customer chooses the SAP HANA tailored data center integration. you have access to the installation media and components for SAP HANA. You can find the installation media and components for SAP HANA in the following locations: ● Installation media for an SAP HANA SPS: SAP Software Download Center H SAP In-Memory (SAP HANA) HANA PLATFORM EDIT. Any other system or content developed with systems of this type is not supported by SAP.4 Software Download In the SAP Software Download Center. When reporting an incident. you can choose from the above list of components for the relevant software part. Before the temporary license expires. Support Package Stacks (SPS) can be downloaded and applied to appliances in accordance with agreements with the respective hardware partner.The CIC requires a valid S-user number. To create an S-user ID. you must apply for a permanent license key from SAP.3 SAP License Key You must install a permanent SAP license for the SAP HANA database. 68 PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved. 6. 1.H Support Packages and Patches SAP HANA PLATFORM EDITION A-Z Index Support Packages and SAP HANA PLATFORM EDIT. a temporary license is automatically installed. 1.

Note If an NTP sever is not available this means that.5 Hardware and Software Requirements For SAP HANA several hardware and software requirements need to be fulfilled. Outside of these validated configurations. Software Requirements Note Only the software installed by certified hardware partners. or any person holding the certification. The check is a script that is automatically called by the SAP HANA installer and aborts the installation process if it doesn't succeed. Hardware Requirements During the update and the installation of the SAP HANA database (from the SAP HANA installation manager). Operating System for SAP HANA For the SAP HANA system the following operating systems are available: ● SUSE Linux Enterprise Server (SLES) 11 ● Red Hat Enterprise Linux (RHEL) 6.Related Information SAP Software Download Center 6. 69 . is recommended for use on the SAP HANA system. Do not install additional software on the SAP HANA system. Note You can find a complete list of all SAP HANA components and the respective SAP HANA hardware and software requirements in the Product Availability Matrix (PAM) on the SAP Service Marketplace and in the SAP Community Network. It is not possible to disable the check because SAP HANA is highly optimized for specific hardware configurations which have been designed and tested together with our hardware partners.5 Network Time Protocol (NTP) We strongly recommend that you set up an NTP server for the SAP HANA system landscape. SAP HANA performance and stability cannot be guaranteed. for example. All rights reserved. trace files from distributed hosts cannot be displayed in the correct chronological order. Check the SAP Education resources for information about the SAP HANA certication exams. a hardware check is performed in order to ensure that problems do not arise due to wrong or unsupported hardware configurations in combination with the SAP HANA platform. The person performing the SAP HANA installation has passed the certification exam. SAP HANA Master Guide Appendix PUBLIC © 2014 SAP SE or an SAP affiliate company.

Due to some dmidecode commands in the check it has to be executed as root. Hardware Requirements for SAP HANA Network Connection We recommend dedicated server network communication of 10 GBit/s between the SAP HANA landscape and the source system for efficient data replication. SAP HANA Master Guide Appendix .SAP Certified Appliance Hardware for SAP HANA 70 PUBLIC © 2014 SAP SE or an SAP affiliate company. memory total. system product name.SAP HANA Guidelines for SLES Operating System SAP Note 2009879 .Before installing or updating SAP HANA. The check is automatically delivered with the SAP HANA software and can be executed as a standalone check anytime. CPU model. Execute the check by going to the /usr/sap/<SID>/HDB<instanceNumber>/exe/ python_support directory and running the Python script named HanaHwCheck. All rights reserved. the hardware check returns the results "not supported" in the system manufacturer.SAP HANA Guidelines for RedHat Enterprise Linux (RHEL) SAP Traning & Education Product Availability Matrix (PAM) SAP Community Network . or core count check results. consult the SAP HANA Product Availability Matrix (search for HANA) to verify if the hardware you are planning to use is supported by SAP HANA. OS.py. Related Information SAP Note 1944799 . If the hardware is not supported.

These hyperlinks are intended to serve as a hint about where to find related information. SAP MAKES NO WARRANTIES. OR OF MERCHANTABILITY. Accessibility The information contained in the SAP documentation represents SAP's current view of accessibility criteria as of the date of publication. Depending on the context. EXPRESS OR IMPLIED.sap. the third-person singular cannot be avoided or a gender-neutral noun does not exist. or a gender-neutral noun (such as "sales person" or "working days") is used. see: http://help. SAP does not warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. SAP reserves the right to use the masculine form of the noun and pronoun.Important Disclaimers on Legal Aspects This document is for informational purposes only. If when referring to members of both sexes. Coding Samples Any software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system environment. however. the reader is addressed directly with "you". and SAP shall not be liable for errors or damages caused by the usage of the Code. Internet Hyperlinks The SAP documentation may contain hyperlinks to the Internet. 71 . Its content is subject to change without notice. it is in no way intended to be a binding guideline on how to ensure accessibility of software products.com/disclaimer. SAP does not warrant the correctness and completeness of the Code given herein. SAP documentation is gender neutral. This is to ensure that the documentation remains comprehensible. OR FITNESS FOR A PARTICULAR PURPOSE. Regarding link classification. Gender-Neutral Language As far as possible. 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. unless damages were caused by SAP intentionally or by SAP's gross negligence. and SAP does not warrant that it is error-free. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP HANA Master Guide Important Disclaimers on Legal Aspects PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved. 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.

National product specifications may vary.sap. Nothing herein should be construed as constituting an additional warranty. The information contained herein may be changed without prior notice. All rights reserved.epx for additional trademark information and notices. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries.com/corporate-en/legal/copyright/ index. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. without representation or warranty of any kind. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services. These materials are provided by SAP SE or an SAP affiliate company for informational purposes only.com/contactsap © 2014 SAP SE or an SAP affiliate company.www. Please see http://www. All other product and service names mentioned are the trademarks of their respective companies. and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. if any. .sap.