SAP HANA Master Guide en

PUBLIC
SAP HANA Platform SPS 07 Document Version: 1.0 - 27-11-2013
SAP HANA Master Guide
Table of Contents
1 1.1 1.2 1.3 1.4 1.5 1.6 1.7 1.8 1.9 2 2.1 2.2 Getting Started with SAP HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 About This Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 What Is SAP HANA?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 SAP HANA Guides. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Related Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Important SAP Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6 Software Download. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Software Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Hardware and Software Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 SAP License Key. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 The SAP HANA Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Connections from Database Clients and Web Clients to SAP HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . 15 The Network for Distributed SAP HANA Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 2.2.1 3 3.1 3.2 3.3 High Availability for SAP HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
SAP HANA Data Provisioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 SAP Sybase Event Stream Processor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 SAP HANA Smart Data Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 SAP HANA Replication Technologies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 3.3.1 3.3.2 3.3.3 3.3.4 3.3.5 3.3.6 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Trigger-Based Replication (SAP Landscape Transformation (LT) Replication Server). . . . . . . 28 SAP HANA Direct Extractor Connection (DXC). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29 ETL-Based Replication (SAP Data Services). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32 Log-Based Replication (SAP Sybase Replication Server). . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Comparison of Replication Methods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
4 4.1 4.2 4.3 4.4
SAP HANA End-To-End Roadmap. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Sizing SAP HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Installing SAP HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Integrating SAP HANA into Customer Landscapes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 SAP HANA Data Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 4.4.1 4.4.2 4.4.3 Configuring Data Replication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Modeling Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Modeling and Data Provisioning for ETL-Based Replication (SAP Data Services). . . . . . . . . . . 43 Installing and Using the SAP HANA ODBO Client for MS EXCEL. . . . . . . . . . . . . . . . . . . . . . . 44 Installing and Using the SAP HANA ODBC Client for MS EXCEL. . . . . . . . . . . . . . . . . . . . . . . 48 Using MS Excel to Create a Pivot Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Using SAP BusinessObjects BI Clients for SAP HANA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60
4.5
Configuring End-User Clients. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 4.5.1 4.5.2 4.5.3 4.5.4
PUBLIC 2013 SAP AG or an SAP affiliate company. All rights reserved.
SAP HANA Master Guide Table of Contents
4.6 4.7
Administrating SAP HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Using SAP HANA with End-User Clients. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
SAP HANA Master Guide Table of Contents
PUBLIC
2013 SAP AG or an SAP affiliate company. All rights reserved.
1
1.1
Getting Started with SAP HANA

About This Document
This Master Guide is the central starting point for the technical implementation of SAP HANA. The Master Guide provides the following information about SAP HANA: Overview Architecture Software components Deployment scenarios
1.2
What Is SAP HANA?
SAP HANA is a modern in-memory database and platform. SAP HANA is deployed on-premise and in the cloud: On-premise SAP HANA is deployed through the following offerings: As an appliance, SAP HANA combines software components from SAP optimized on proven hardware provided by SAPs hardware partners. 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. The requirements for this deployment option are as follows: The server is listed in the SAP HANA product availability matrix. The storage solution has successfully passed SAP HANA hardware certification. The person performing the SAP HANA installation has passed the certification exam (E_HANAINS131).
In the cloud, SAP HANA is offered as a comprehensive infrastructure combined with managed services. SAP HANA is also deployed through the following cloud offerings: SAP HANA One SAP HANA Cloud Platform SAP HANA Enterprise Cloud
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. It is also a development platform, providing an infrastructure and tools for building high-performance applications based on SAP HANA Extended Application Services (SAP HANA XS). It is the foundation of various SAP HANA editions, like the SAP HANA Platform Edition, providing core database technology, and the SAP HANA Enterprise Edition, bundling additional components for data provisioning. The SAP HANA Platform Edition integrates a number of SAP components, including the SAP HANA database, SAP HANA studio, and SAP HANA clients.
PUBLIC
SAP HANA Master Guide Getting Started with SAP HANA
1.3
SAP HANA Guides
Documentation for the current Support Package Stack of the SAP HANA Platform Edition can be found on the SAP Help Portal. SAP HANA documentation for previous Support Package Stacks can be found on the SAP HANA Knowledge Center on SAP Service Marketplace. For information about SAP HANA landscape, security, installation, and administration, see the resources listed below: Topic Location Quick Link http://help.sap.com/hana_platform: SAP HANA Master Guide SAP HANA Server Installation Guide SAP HANA Master Update Guide SAP HANA Update and Configuration Guide
SAP HANA landscape, deployment, SAP HANA Knowledge Center and installation on the SAP Help Portal
SAP HANA administration and security
SAP HANA Knowledge Center on the SAP Help Portal
http://help.sap.com/hana_platform: SAP HANA Technical Operations Manual SAP HANA Administration Guide SAP HANA Security Guide
SAP HANA documentation for previous Support Package Stacks
SAP HANA Knowledge Center on SAP Service Marketplace
https://service.sap.com/hana
1.4
Related Information
There are a number of available resources, which although not directly connected to SAP HANA are useful for planning your deployment. Content Latest documentation for SAP HANA Location https://service.sap.com/hana* http://help.sap.com/hana_platform Sybase product documentation Sizing, calculation of hardware requirements, such as CPU, disk, and memory resources SAP BusinessObjects installation and deployment guides http://sybooks.sybase.com/nav/base.do https://service.sap.com/sizing
https://service.sap.com/bosap-instguides
PUBLIC
Content SAP BusinessObjects support Sizing, calculation of hardware requirements - such as CPU, disk and memory resources - with the QuickSizer tool Released platforms and technology-related topics such as maintenance strategies and language support Platform Availability Matrix (PAM) Network security High availability Security Unicode SAP systems and their availability Information about Support Package Stacks, latest software versions and patch level requirements
Location https://service.sap.com/bosap-support https://service.sap.com/quicksizer
https://service.sap.com/pam
https://service.sap.com/securityguide http://scn.sap.com/docs/DOC-7848 https://service.sap.com/security https://service.sap.com/unicode https://service.sap.com/sp-stacks
(*) You need an authorized user ID to access this information. 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 SAP incident wizard SAP Notes search SAP Software Distribution Center software download and ordering of software SAP Online Knowledge Products (OKPs) role-specific learning maps Location on SAP Service Marketplace https://service.sap.com/incident https://service.sap.com/notes https://service.sap.com/swdc
https://service.sap.com/rkt
1.5
Important SAP Notes
Read the following SAP Notes before you start the installation. These SAP Notes contain the latest information about the installation, as well as corrections to the installation documentation. Make sure that you have the most up-to-date version of each SAP Note, which you can find on SAP Service Marketplace at https://service.sap.com/notes .
SAP Note Number

1514967 1921675 1523337 1681092
Title
SAP HANA: Central Note SAP HANA Platform SPS 07 Release Note SAP HANA Database: Central Note Support for multiple SAP HANA databases on a single SAP HANA appliance
1661202 1828400 1917938 1645183 1823343 1927949 1577128 1514966 1637145 1793345 1824819 1597355
Support for multiple applications on SAP HANA SAPUI5 tools disappeared after updating HANA Studio Migrating the Statistic Server During Update to SPS 07 Changing log mode for SAP HANA DB Deactivate log mode LEGACY with SAP HANA SPS 07 Standard Behavior for SAP Logon Tickets Supported clients for SAP HANA SAP HANA: Sizing SAP HANA Database SAP BW on HANA: Sizing SAP HANA Database Sizing for Suite on HANA Optimal settings for SLES 11 SP2 and SLES 11 for SAP SP2 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 Platform BC-DB-HDB SAP HANA Database BC-DB-HDB-AFL SAP HANA Application Function Library BC-DB-HDB-AFL-DQ SAP HANA Data Quality Library BC-DB-HDB-AFL-PAL SAP HANA Predictive Analysis Library BC-DB-HDB-AFL-SOP SAP HANA Sales and & Operations Planning BC-DB-HDB-BAC SAP HANA Backup & Recovery BC-DB-HDB-CCM CCMS for SAP HANA BC-DB-HDB-CLI SAP HANA Clients (JDBC, ODBC) BC-DB-HDB-DBA SAP HANA database administration (DBA cockpit)
PUBLIC
BC-DB-HDB-DXC SAP HANA direct extractor connector BC-DB-HDB-ENG SAP HANA database engine BC-DB-HDB-MDX MDX Engine / MS Excel client BC-DB-HDB-PER SAP HANA database persistence BC-DB-HDB-PLE Planning Engine BC-DB-HDB-POR DB Porting for SAP HANA BC-DB-HDB-R SAP HANA Integration with R BC-DB-HDB-SCR SAP HANA SQL Script BC-DB-HDB-SCR-CLT SAP HANA SQL Script Editor/Debugger Client BC-DB-HDB-SEC SAP HANA Security & User Management BC-DB-HDB-SYS SAP HANA database interface/DBMS BC-DB-HDB-TXT SAP HANA Text & Search Features BC-DB-HDB-XS SAP HANA Application Services BC-DB-HDB-XS-WB Workbench / Team Provider SAP HANA DB BC-DB-LCA SAP HANA liveCache Applications BC-HAN-MOD SAP HANA studio / information modeler BC-HAN-3DM SAP HANA information composer BC-HAN-SRC SAP HANA UI Toolkit BC-CCM-HAG SAP Host Agent SV-SMG-DIA SAP Solution Manager Diagnostics Agent EP-HAN SAP HANA UI Integration Services
SAP HANA Lifecycle Management BC-HAN-SL-STP SAP HANA unified installer BC-DB-HDB-INS SAP HANA database installation (hdbinst) BC-HAN-UPDSAP HANA lifecycle manager / SAP HANA software update manager BC-DB-HDB-UPG SAP HANA database upgrade (hdbupd)
SAP HANA Enterprise BC-HAN-LOA SAP HANA load controller (log-based replication) BC-HAN-REP Sybase rep. server (log-based replication) BC-HAN-LTR SAP Landscape Transformation (trigger-based replication) BC-HAN-DXC SAP HANA Direct Extractor Connection EIM-DS Data Services (ETL-based replication)
End User Clients BI-BIP, BI-BIP-CMC Business intelligence platform (formerly known as BOE) BI-RA-EXP SAP BusinessObjects Explorer BI-RA-CR, 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 (*), so you can, for example, also search for BC-DB-HDB* or similar and you will get results for all sub-components.
Reporting Incidents
If you encounter any problems with the software, report an incident on the SAP Service Marketplace at http:// service.sap.com/incident .
In addition, 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.sap.com/supportcenters ).
The CIC requires a valid S-user number. To create an S-user ID, follow the steps in this guide (https:// service.sap.com/~sapidp/011000358700000905192010E.pdf ).
When reporting an incident, you can choose from the above list of components for the relevant software part.
1.6
Software Download
In the SAP Software Download Center, you have access to the installation media and components for SAP HANA. You can find the installation media and components for SAP HANA in the following locations: Installation media for an SAP HANA SPS: SAP Software Download Center SAP In-Memory (SAP HANA) PLATFORM EDIT. 1.0 Installation Support Packages and Patches A-Z Index Installations and Upgrades Installations and Upgrades A-Z Index Installations and Upgrades - H SAP HANA HANA Platform Edition SAP HANA PLATFORM EDITION
Support Packages and Patches for SAP HANA: SAP Software Download Center -H SAP HANA PLATFORM EDITION SAP HANA PLATFORM EDIT. 1.0
The responsibility for acquiring and installing SAP HANA depends on the chosen deployment model: If a customer chooses the SAP HANA tailored data center integration, the components of SAP HANA have to be installed on validated hardware by a certified administrator. If a customer chooses an SAP HANA appliance, the components of SAP HANA can only be installed by certified hardware partners on validated hardware running a specific operating system. Any other system or content developed with systems of this type is not supported by SAP. For more information, see the information page of the product version. Support Package Stacks (SPS) can be downloaded and applied to appliances in accordance with agreements with the respective hardware partner.
Related Information
SAP Software Download Center
PUBLIC
1.7
Software Components
The SAP HANA Platform Edition is the foundation of various other SAP HANA editions, like the SAP HANA Enterprise Edition. These editions bundle additional components that customers might require, for example, for data replication. The SAP HANA Platform Edition is composed of the following components: SAP HANA database SAP HANA client SAP HANA client for Microsoft Excel SAP HANA studio (including SAP HANA STUDIO RSA PLUGIN) SAPUI5 Tools IDE PLUGIN SAP Host Agent Diagnostics Agent SAP HANA information composer SAP HANA AFL SAP HANA LCApps SAP HANA lifecycle manager SAP HANA RDL SAP HANA INA Toolkit HTML SAP HANA EPM Service SAP HANA Demo Modell SAP HANA smart data access SAP HANA HW Configuration Check Tool
The SAP HANA Platform Edition is bundled together with other products into editions as license bundles for special purposes. This is a subset of the available editions: SAP HANA Enterprise Edition (including components for data replication and acquisition) SAP HANA Real-time-data edition (includes SAP Sybase Replication Server, SAP HANA edition) SAP HANA Database edition for BW SAP HANA Limited edition for Apps / Accelerators SAP HANA EDGE edition
Note
SAP HANA information composer is a Web-based environment that allows business users to upload data to the SAP HANA database and to manipulate that data by creating information views. The SAP HANA information composer is installed separately from the SAP HANA system.
Related Information
SAP HANA Information Composer Installation and Configuration Guide
10
1.8
Hardware and Software Requirements
For SAP HANA several hardware and software requirements need to be fulfilled.
Note
You can find a complete list of all SAP HANA components and the respective SAP HANA hardware and software requirements in the Product Availability Matrix (PAM) Software Requirements on the SAP Service Marketplace.
Note
Only the software installed by certified hardware partners, or any person holding E_HANAINS131 certification, is recommended for use on the SAP HANA system. Do not install additional software on the SAP HANA system. Operating System for SAP HANA SUSE Linux Enterprise Server (SLES) 11 (see Product Availability Matrix (PAM) installing SLES 11 in an SAP environment, see SAP Note 1310037 SLES 11, see SAP Note 1824819 . ). ) for information about
. For information about optimal settings for
For the SAP HANA system there are no specific requirements regarding swap space (see SAP Note 1597355 The following additional components need to be installed on the SAP HANA system: gtk2 (use version as provided with operating system distribution)
java-1_6_0-ibm (use version as provided with operating system distribution, necessary for the SAP HANA studio on the SAP HANA system) libicu (use version as provided with operating system distribution) mozilla-xulrunner192-1.9.2.xx-x.x.x (use version as provided with operating system, but at given minimum version) ntp sudo syslog-ng (use version as provided with operating system distribution) tcsh libssh2-1 autoyast2-installation yast2-ncurses
Observe the following requirements: Turn off the SLES kernel dump function (kdump) if not needed for specific reasons (for example, root cause analysis). Configure the following SLES kernel parameter as follows: net.ipv4.tcp_slow_start_after_idle=0 Adhere to the following shared memory settings (if not already set during installation):
PUBLIC
11
Size
Small Medium Large
SHMMNI Value
4096 65536 524288
Physical Memory
24 GB RAM < 64 GB 64 GB < RAM < 256 GB 256 GB < RAM
When using unixODBC for ODBC on Linux, install release 2.3.0 or higher (check with command isql -version).
Network Time Protocol (NTP) We strongly recommend that you set up an NTP server for the SAP HANA system landscape.
Note
If an NTP sever is not available this means that, for example, trace files from distributed hosts cannot be displayed in the correct chronological order. Hardware Requirements For a new installation, you need to have at least 20 GB RAM in total just for the software - 15 GB for the basic software plus 5 GB for programs as well as some space for trace files. The additional memory required for data and log volumes varies according to your requirements. For an update, you also need to allow the space stated above, since the old software version is not deleted. Hardware Check During the update and the installation of the SAP HANA database (from the SAP HANA installation manager), a hardware check is performed in order to ensure that problems do not arise due to wrong or unsupported hardware configurations in combination with the SAP HANA platform. The check is a script that is automatically called by the SAP HANA installer and aborts the installation process if it doesn't succeed. It is not possible to disable the check because SAP HANA is highly optimized for specific hardware configurations which have been designed and tested together with our hardware partners. Outside of these validated configurations, SAP HANA performance and stability cannot be guaranteed. Before installing or updating SAP HANA, consult the SAP HANA Product Availability Matrix (search for HANA) to verify if the hardware you are planning to use is supported by SAP HANA. If the hardware is not supported, the hardware check returns the results "not supported" in the system manufacturer, system product name, CPU model, OS, memory total, or core count check results. To ensure that both the data device check and log device check pass, make sure that the free disk space of the data volume is at least four times the size of the physical memory and the free disk space of the log volume is at least equal to the size of the physical memory otherwise a volume size error appears. You can check the free memory on your mount points with a df -h command. Device Data Log Free Disk Space 4 * RAM 1 * RAM
The check is automatically delivered with the SAP HANA software and can be executed as a standalone check anytime. Execute the check by going to the /usr/sap/<SID>/HDB<instanceNumber>/exe/python_support
12
PUBLIC
directory and running the Python script named HanaHwCheck.py. Due to some dmidecode commands in the check it has to be executed as root. Hardware Requirements for SAP HANA Network Connection We recommend dedicated server network communication of 10 GBit/s between the SAP HANA landscape and the source system for efficient data replication.
Note
For more information about validated hardware configurations see the Product Availability Matrix (PAM) on SAP Service Marketplace at https://service.sap.com/pam .
1.9
SAP License Key
You must install a permanent SAP license for the SAP HANA database. When you install your SAP system, a temporary license is automatically installed. Before the temporary license expires, you must apply for a permanent license key from SAP. We recommend that you apply for a permanent license key as soon as possible after installing your system.
Related Information
SAP HANA Administration Guide
PUBLIC
13
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, and supporting a distributed multi-terabyte database with full fault and disaster recovery. In terms of network connectivity, SAP HANA supports traditional database client connections and, with SAP HANA Extended Application Services (SAP HANA XS), Web-based clients. SAP HANA can be integrated with transaction-oriented databases using replication services, as well as with high-speed event sources. SAP HANAbased applications can be integrated with external services such as e-mail, Web, and R-code execution. The setup of an SAP HANA system, and the corresponding data center and network configurations, depends on your company's environment and implementation considerations. Some of these considerations are: Support for traditional database clients, Web-based clients, and administrative connections The number of hosts used for the SAP HANA system, ranging from a single-host system to a complex distributed system with multiple hosts Support for high availability and disaster recovery through the use of secondary sites, or multiple secondary sites, and data centers 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, administration clients, application servers, and for data provisioning via SQL or HTTP Channels used for SAP HANA internal communication within the database or, in a distributed scenario, for communication between hosts
Related Information
Connections from Database Clients and Web Clients to SAP HANA [page 15] Before you start configuring the network for SAP HANA, you'll want to get an overview of the external client connections to SAP HANA . The Network for Distributed SAP HANA Systems [page 19] Before you start configuring the network for SAP HANA, you'll want to get an overview of the internal connections between server components. SAP HANA supports distribution of its server components across multiple hosts for the purposes of scalability and availability. High Availability for SAP HANA [page 23] SAP HANA is fully designed for high availability. It supports recovery measures ranging from faults and software errors, to disasters that decommission an entire data center. High availability is the name given to a set of techniques, engineering practices and design principles that support the goal of business continuity. SAP HANA Security Guide SAP HANA Administration Guide
14
SAP HANA Master Guide The SAP HANA Network
2.1 Connections from Database Clients and Web Clients to SAP HANA
Before you start configuring the network for SAP HANA, you'll want to get an overview of the external client connections to SAP HANA . The connections between SAP HANA and external components and applications can be categorized 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. 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). Administrative access to and from SAP HANA is depicted by the blue dashed arrows. Port numbers are shown with a pink background. The xx in the port numbers stands for your SAP HANA instance number. The diagram shows all the network channels used by the SAP HANA software. The SAP HANA appliance has additional network services such as SSH for administrative access. For purposes of illustration, the diagram shows a single host installation of SAP HANA. However, the connections shown apply equally to a distributed scenario.
Note
In distributed scenarios, you must also ensure that every database client can connect to every host (not shown in the diagram). Moreover, additional network channels are required in distributed scenarios for communication between the different hosts of a HANA system or between the different sites. A default mapping of external hostnames to internal hostnames enables statement routing and automatic reconnection in the event of a failover. Clients communicate with the database through external hostnames or external IP addresses. By default, the IP address of the primary network interface is used but you can change this configuration if required. For more information about mapping host names for database client access, see the SAP HANA Administration Guide.
PUBLIC
15
The following tables explain the diagram and the different categories described above in more detail.
Database Client Access

Client Application servers that use SAP HANA as a database Protocol and additional information You must enable SQL/MDX access for all database clients. TCP port 3xx15 3xx17
Examples: SAP NetWeaver Business External and internal host names are mapped for the Warehouse and one or more components purposes of database client access. You can change of SAP Business Suite the default mapping. For more information, see the SAP HANA Administration Guide. End-user clients that access the SAP The protocol used for database client access is HANA database directly SQLDBC (ODBC/JDBC). Example: Microsoft Excel SAP HANA studio
16
Client This connection is used for administrative purposes (for example, to access user data, configuration data or trace files) or for modeling purposes (to access data models).
Protocol and additional information
TCP port
HTTP/S Client Access

Client Examples: a Web browser or a mobile device SAP HANA Direct Extractor Connection (DXC) UI toolkit for SAP HANA Info Access Additional information Access for applications based on SAP HANA Extended Application Services (SAP HANA XS). For more information, see the SAP HANA Developer Guide. This connection is used for ETL-based data acquisition. For more information, see the SAP HANA Direct Extractor Connection Implementation Guide. TCP port 80xx (HTTP) 43xx (HTTPS)
Administrative Tasks
Client SAP support Protocol and additional information TCP port
The connection is not active by default because it is required only in 3xx09 certain support cases. To find out how to open a support connection, see the SAP HANA Administration Guide. An internal SAP protocol is used for this connection.
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 protocol used for this connection is SQLDBC (ODBC/JDBC).
5xx13 5xx14 (SSL)
SAP HANA studio
This is the connection to SAP HANA lifecycle manager via SAP Host Agent. For more information about SAP HANA lifecycle manager, see SAP HANA Update and Configuration Guide. The protocol used for this connection is SQLDBC (ODBC/JDBC).
1128 1129 (SSL)
Other administrative tasks, mainly database administration, use the SQL/MDX channel of the database.
PUBLIC
17
Data Provisioning
Client SAP Sybase Event Stream Processor (ESP) (not included with all licensed editions of SAP HANA) Replication systems for external data sources Protocol and additional information This connection is used for event streaming. The protocol is SQLDBC (ODBC/JDBC). The following replication technologies may be used: SAP Landscape Transformation (SLT) The protocol is SQLDBC (ODBC/JDBC). SAP Data Services (DS) The protocol is SQLDBC (ODBC/JDBC). SAP Sybase Replication Server (not included with all licensed editions of SAP HANA) The protocol is SQLDBC (ODBC/JDBC). SAP HANA Direct Extractor Connection (DXC). This technology uses HTTP/S access. TCP port 3xx15 3xx17
Outbound Connections
Connection From the SAP Solution Manager diagnostics (SMD) agent to SAP Solution Manager SAP HANA lifecycle manager to SAP Service Marketplace Calls from SAP HANA Extended Application Services to external servers Smart data access from SAP HANA to external data sources for data federation purposes From SAP HANA to the R environment Additional information For information about how to install the SAP Solution Manager diagnostics agent, see the SAP HANA Update and Configuration Guide. For information about software updates, see the SAP HANA Update and Configuration Guide. Examples: a Web server or an e-mail server (depends on what applications your company has deployed) For more information about SAP HANA smart data access, see SAP HANA Smart Data Access [page 25]. Only required for scenarios which use the R integration supported by SAP HANA. For more information, see SAP HANA R Integration Guide.
Related Information
The SAP HANA Network [page 14] 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, and supporting a distributed multi-terabyte database with full fault and disaster recovery.
18
PUBLIC
The Network for Distributed SAP HANA Systems [page 19] Before you start configuring the network for SAP HANA, you'll want to get an overview of the internal connections between server components. SAP HANA supports distribution of its server components across multiple hosts for the purposes of scalability and availability.
2.2
The Network for Distributed SAP HANA Systems
Before you start configuring the network for SAP HANA, you'll want to get an overview of the internal connections between server components. SAP HANA supports distribution of its server components across multiple hosts for the purposes of scalability and availability. An installed SAP HANA system is identified by a system id (SID). It is perceived as one unit from the perspective of the administrator, who can install, update, start up, shut down, or back up the system as a whole. The different services of the system share the same metadata, and requests from client applications are transparently dispatched to the different services in the system. A distributed SAP HANA system is a system that is installed on more than one host. Otherwise it is a single-host system. An SAP HANA instance is a set of components of a distributed system that are installed on one host. In addition to external network connections, SAP HANA uses separate, dedicated connections exclusively for internal communication. There are two types of internal communication: Distributed scenarios Internal network communication takes place between the hosts of a distributed system on one site. Certified SAP HANA hosts contain a separate network interface card that is configured as part of a private network, using separate IP addresses and ports.
Note
In single-host scenarios, 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. Before SPS 06, these ports were by default bound to all network interfaces. There are a number of ways to isolate internal network ports from the client network. The preferred method depends on the data center configuration, on hardware vendor delivered options, and on the high availability implementation. Applying network separation for the internal communication prevents unauthorized access from outside networks. For additional security it is possible to encrypt the internal communication using SSL. For more information about security, see the SAP HANA Security Guide. Table 1: Ports for Distributed Scenarios The xx in the port numbers stands for your SAP HANA instance number. Client TCP port Service daemon nameserver preprocessor Use
Hosts of a 3xx00 distributed system 3xx01 on one site 3xx02
PUBLIC
19
Client
TCP port 3xx03 3xx04 3xx05 3xx07 3xx10 3xx40-3xx99
Service indexserver scriptserver statisticsserver xsengine compileserver indexservers
Use
Optional
Optional, after n->1 recovery
System replication Internal network communication for system replication takes place between a primary site and a secondary site. In a multitier setup, this communication takes place between the tier-1 primary system and tier-2 secondary system as well as, asynchronously, between the tier-2 and tier-3 secondary systems. For more information about system replication and multitier setups, see the SAP HANA Administration Guide. We recommend that you secure system replication connections using the Secure Sockets Layer (SSL) protocol. Landscape topology communication on the one hand, and data replication and log replication channels on the other, must be secured in separate steps. By default, SSL is turned off. For more information about configuring SSL for internal communication as well as securing communication between sites in system replication scenarios, see the SAP HANA Security Guide. Table 2: Ports for System Replication The xy in the port numbers stands for your SAP HANA instance number plus 1. Client Hosts on primary and secondary sites TCP port 3xy01 3xy02 Service nameserver nameserver Used for... Log and data shipping Landscape topology shipping Log and data shipping Log and data shipping (optional) 3xy05 3xy07 3xy40-3xy99 statisticsserver xsengine indexservers Log and data shipping Log and data shipping Log and data shipping (optional, after n->1 recovery)
3xy03 3xy04
indexserver scriptserver
20
Example 1
The following diagram shows a distributed SAP HANA system with two active hosts and an extra standby host, fully system-replicated to a secondary site to provide full disaster recovery support.
The vertical blue dashed lines show the communications between the services of the system; all instances communicate with all other instances of a distributed system on one site. 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). The details of system replication configuration depend on the specific network setup of your company. Also shown is a shared network-attached storage device (NAS). One of the purposes of network-attached storage in SAP HANA is to support host auto-failover to the standby host if one of the active hosts fails. 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. 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. The HTTP load balancer can also be used to provide load-balanced access to multiple distributed SAP HANA Extended Application Services (XS) servers.
PUBLIC
21
A network device (router and/or switch), 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, see the SAP HANA Administration Guide.
Example 2
The following diagram shows an example of multitier system replication:
Related Information
The SAP HANA Network [page 14] 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, and supporting a distributed multi-terabyte database with full fault and disaster recovery. Connections from Database Clients and Web Clients to SAP HANA [page 15] Before you start configuring the network for SAP HANA, you'll want to get an overview of the external client connections to SAP HANA .
22
PUBLIC
SAP HANA Administration Guide SAP HANA Security Guide
2.2.1
High Availability for SAP HANA
SAP HANA is fully designed for high availability. It supports recovery measures ranging from faults and software errors, to disasters that decommission an entire data center. High availability is the name given to a set of techniques, engineering practices and design principles that support the goal of business continuity. High availability is achieved by eliminating single points of failure (fault tolerance), and providing the ability to rapidly resume operations after a system outage with minimal business loss (fault resilience). Fault recovery is the process of recovering and resuming operations after an outage due to a fault. Disaster recovery is the process of recovering operations after an outage due to a prolonged data center or site failure. Preparing for disasters may require backing up data across longer distances, and may thus be more complex. The key to achieving high availability is redundancy, including hardware redundancy, network redundancy and data center redundancy. SAP HANA provides several levels of defense against failure-related outages: 1. Hardware Redundancy SAP HANA appliance vendors offer multiple layers of redundant hardware, software and network components, such as redundant power supplies and fans, enterprise grade error-correcting memories, fully redundant network switches and routers, and uninterrupted power supply (UPS). Disk storage systems use batteries to guarantee writing even in the presence of power failure, and use striping and mirroring to provide redundancy for automatic recovery from disk failures. Generally speaking, all these redundancy solutions are transparent to SAP HANA's operation, but they form part of the defense against system outage due to single component failures. Software SAP HANA is based on SUSE Linux Enterprise 11 for SAP and includes security pre-configurations (for example, minimal network services). Additionally, the SAP HANA system software also includes a watchdog function, which automatically restarts configured services (index server, name server, and so on), in case of detected stoppage (killed or crashed). Persistence SAP HANA persists transaction logs, savepoints and snapshots to support system restart and recovery from host failures, with minimal delay and without loss of data. Standby and Failover Separate, dedicated standby hosts are used for failover, in case of failure of the primary, active hosts. This improves the availability by significantly reducing the recovery time from an outage.
2.
3. 4.
SAP HANA High Availability Support

As an in-memory database, SAP HANA is not only concerned with maintaining the reliability of its data in the event of failures, but also with resuming operations with most of that data loaded back in memory as quickly as possible. SAP HANA supports the following recovery measures from failures: Disaster recovery support: Backups: Periodic saving of database copies in safe place. Storage replication: Continuous replication (mirroring) between primary storage and backup storage over a network (may be synchronous).
PUBLIC
23
System replication: Continuous update of secondary systems by primary system, including in-memory table loading. Service auto-restart: Automatic restart of stopped services on host (watchdog). Host auto-failover: Automatic failover from crashed host to standby host in the same system.
Fault recovery support:
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. The secondary system uses its own disk infrastructure. In the case of single node systems this means, the local disk infrastructure needs to be doubled. The non-productive systems are stopped with the takeover to the productive secondary.
Related Information
SAP HANA Administration Guide
24
3
3.1
SAP HANA Data Provisioning

SAP Sybase Event Stream Processor
SAP Sybase Event Stream Processor is used for real-time processing of high velocity and high volume data streams modeled as event streams. It is targeted for a variety of applications, for example for financial trade and risk monitoring, monitoring machine/sensor data, and tailoring responses to user actions. Input data streams can come from a variety of sources such as data feeds, business applications, sensors, IT monitoring infrastructure, and so on. You can develop custom input adapters for additional sources. ESP transforms the input data streams into output data streams by applying event-driven continuous queries. It can be used, for example, to filter, aggregate and enrich raw data, to detect patterns, and to combine data from different sources. ESP can capture output streams in the SAP HANA database at very high speeds. For details see the SAP Sybase Event Stream Processor documentation on the Sybase product documentation page.
Related Information
Sybase Product Documentation
3.2
SAP HANA Smart Data Access
SAP HANA smart data access enables remote data to be accessed as if they are local tables in SAP HANA, without copying the data into SAP HANA. Not only does this capability provide operational and cost benefits, but most importantly it supports the development and deployment of the next generation of analytical applications which require the ability to access, synthesize and integrate data from multiple systems in real-time regardless of where the data is located or what systems are generating it. Specifically, in SAP HANA, you can create virtual tables which point to remote tables in different data sources. Customers can then write SQL queries in SAP HANA, which could operate on virtual tables. The SAP HANA query processor optimizes these queries, and executes the relevant part of the query in the target database, returns the results of the query to SAP HANA, and completes the operation.
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")
SAP HANA Master Guide SAP HANA Data Provisioning
PUBLIC
25
3.3 3.3.1
SAP HANA Replication Technologies Introduction
In-memory reporting and analyzing of business data requires the replication of the data from a source system to the SAP HANA database. This section provides an overview of the possible replication methods that are available for the SAP HANA. It also describes the application fields and lists the main components required for each method.
The figure above focuses on the task of loading business data from a source system to the SAP HANA database. The methods for performing data replication are shown in the figure below. The main components involved in all replication scenarios are: SAP HANA, consisting of the SAP HANA database and SAP HANA studio, which is an administration tool. User interfaces, such as SAP BusinessObjects Dashboards or Web Intelligence, are not part of SAP HANA. Source system Software components supporting the data replication
The software components that support different methods of data replication are described in the following replication scenarios.
26
The figure above gives an overview of the alternative methods for data replication from a source system to the SAP HANA database. Each method handles the required data replication differently, and consequently each method has different strengths. It depends on your specific application field and the existing system landscape as to which of the methods best serves your needs. Trigger-Based Replication Trigger-Based Data Replication Using SAP Landscape Transformation (LT) Replication Server is based on capturing database changes at a high level of abstraction in the source ERP system. This method of replication benefits from being database-independent, and can also parallelize database changes on multiple tables or by segmenting large table changes. ETL-Based Replication Extraction-Transformation-Load (ETL) Based Data Replication uses SAP Data Services to specify and load the relevant business data in defined periods of time from an ERP system into the SAP HANA database. You can reuse the ERP application logic by reading extractors or utilizing SAP function modules. In addition, the ETL-based method offers options for the integration of third-party data providers. Extractor-Based Data Acquisition The SAP HANA Direct Extractor Connection (DXC) is a means for providing out-of-the-box foundational data models to SAP HANA, which are based on SAP Business Suite entities. DXC is also a data acquisition method. The rationale for DXC is essentially simple, low TCO data acquisition for SAP HANA leveraging existing delivered data models. Log-Based Replication (for non-SAP systems)
PUBLIC
27
SAP Sybase Replication Server (SRS) is a sophisticated transactional data movement product that moves and synchronizes data across the enterprise without the limitation of geographical distance, to meet demanding requirements in the enterprise such as guaranteed data delivery, real-time business intelligence and zero operational downtime. SRS facilitates this by non-intrusively handling data at the source and target, while ensuring high performance and transactional integrity.
Related Information
Product Availability Matrix (PAM) (search for SAP HANA)
3.3.2 Trigger-Based Replication (SAP Landscape Transformation (LT) 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.
Initial Load and Simultaneous Delta Replication The initial load of business data is initiated using the SAP HANA studio. The initial load message is sent from the SAP HANA system to the SLT system, which in turn passes the initialization message to the ERP system.
28
PUBLIC
Furthermore, the SLT system initiates the set-up of replication log tables in the database of the ERP system for each table to be replicated. After the transaction tables are completed, the SLT system begins a multi-threaded replication of data to the target system, which enables high speed data transfer. The initial load of data can be executed while the source system is active. The system load that this process causes can be controlled by adjusting the number of worker threads performing the initial replication. In parallel to the initial load, by means of database-specific triggers, the SLT system begins detecting any data changes that occur while the initial load process is running. 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 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 After the initial load process has completed, the SLT system continues to monitor the transaction tables in the ERP system, 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.
Installation considerations The SLT system can be installed in the ways shown below. 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)
3.3.3
SAP HANA Direct Extractor Connection (DXC)
The SAP HANA Direct Extractor Connection (DXC) is a means for providing out-of-the-box foundational data models to SAP HANA, which are based on SAP Business Suite entities. DXC is also a data acquisition method for SAP HANA. The rationale for DXC is essentially simple, low TCO data acquisition for SAP HANA leveraging existing delivered data models. Customer projects may face significant complexity in modeling entities in SAP Business Suite systems. In many cases, data from different areas in SAP Business Suite systems requires application logic to appropriately represent the state of business documents. SAP Business Content DataSource Extractors have been available for many years as a basis for data modeling and data acquisition for SAP Business Warehouse; now with DXC, these SAP Business Content DataSource Extractors are available to deliver data directly to SAP HANA. DXC is a batch-driven data acquisition technique; it should be considered as a form of extraction, transformation and load although its transformation capabilities are limited to user exit for extraction.
PUBLIC
29
A key point about DXC is that in many use cases, batch-driven data acquisition at certain intervals is sufficient (for example, every 15 minutes).
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 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 Re-uses existing proprietary extraction, transformation, 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 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
Provide semantically rich data from SAP Business Suite to SAP HANA:
Simplicity/Low TCO:
Change data capture (delta handling):
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.0 or higher such as ECC 6.0. The alternative configuration is available for SAP Business Suite systems based on releases lower than SAP NetWeaver 7.0 such as SAP ERP 4.6, for example.
An SAP Business Suite system is based on SAP NetWeaver. As of SAP NetWeaver version 7.0, SAP Business Warehouse (BW) is part of SAP NetWeaver itself, which means a BW system exists inside SAP Business Suite systems such as ERP (ECC 6.0 or higher). This BW system is referred to as an embedded BW system. Typically, this embedded BW system inside SAP Business Suite systems is actually not utilized, since most customers who run BW have it installed on a separate server, and they rely on that one. With the default DXC configuration, we utilize the scheduling and monitoring features of this embedded BW system, but do not utilize its other aspects such as storing data, data warehousing, or reporting / BI. DXC extraction processing essentially bypasses the normal dataflow, and instead sends data to SAP HANA. The following illustration depicts the default configuration of DXC.
30
An In-Memory DataStore Object (IMDSO) is generated in SAP HANA, which directly corresponds to the structure of the DataSource you are working with. This IMDSO consists of several tables and an activation mechanism. The active data table of the IMDSO can be utilized as a basis for building data models in SAP HANA (attribute views, analytical views, and calculation views). Data is transferred from the source SAP Business Suite system using an HTTP connection. Generally, the extraction and load process is virtually the same as when extracting and loading SAP Business Warehouse you rely on InfoPackage scheduling, the data load monitor, process chains, etc. which are all well-known from operating SAP Business Warehouse.
Note
DXC does not require BW on SAP HANA. Also with DXC, data is not loaded into the embedded BW system. Instead, data is redirected into SAP HANA.
PUBLIC
31
Related Information
SAP HANA Direct Extractor Connection Implementation Guide Editing DataSources and Application Component Hierarchies Enhancing DataSources
3.3.4
ETL-Based Replication (SAP Data Services)
Extraction-Transformation-Load (ETL) based data replication uses SAP Data Services (referred to as Data Services from now on) to load the relevant business data from the source system, SAP ERP, and replicate it to the target, SAP HANA database. This method enables you to read the required business data on the level of the application layer. You deploy this method by defining data flows in Data Services and scheduling the replication jobs. Since this method uses batch processing, it also permits data checks, transformations, synchronizing with additional data providers, and the merging of data streams.
The figure above gives an overview of the ETL-based replication method. Here, data replication is operated by Data Services. Its main components are the Data Services Designer, where you model the data flow, and the Data Services Job Server for the execution of the replication jobs. An additional repository is used to store the metadata and the job definitions. Data Flow
32
PUBLIC
As for any replication scenario you have to define a series of parameters for the two systems involved. Utilizing Data Services you have to set up datastores to define such parameters. You use the Designer to set up datastores. Datastore Setup Setting up a datastore for the source system SAP ERP, choose SAP Applications for the type of datastore, and specify the address of the system, the user name and password allowing Data Services to access the system. Additional settings depend on the type of SAP ERP objects to be read. For the target system of the replication, the SAP HANA database, you have to set up a separate datastore as done for the source system. Data Flow Modeling Once datastores are set up, Data Services can connect to the source system by RFC. Based on the metadata imported from the ABAP Data Dictionary to Data Services, you can determine the business data to be replicated. Data Services offers replication functions for a variety of data source types. However, for the replication of SAP ERP data to SAP HANA database, we recommend you to use extractors.
Note
You must apply SAP Note 1522554 - NetWeaver Support Package requirement for Data Services SAP Extractor support to fully benefit from the extractor support. In the source system, the extractors must be released for the replication access by Data Services. In addition, you have to indicate the primary key, such as the GUID, to enable the correct replication. The extractors must support delta handling.
Choose the extractors that are relevant for the replication job. Model the data flow for each extractor you have selected: indicate the source for the data flow, which is the extractor. For the target of the replication, choose a template table, which is then used in the SAP HANA database to store the replaced data. 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. The initial load can be set up modeling a simple data flow from source to target. For the update, in most cases, the data flow is enhanced by a delta handling element, such as Map_CDC_Operation or Table_Comparison Transform. It depends on the environment and the requested setup of the target tables which data flow design best serves your requirements. Although we recommend you to use delta supporting extractors, you can also use SAP ABAP tables. Replication Job Schedule Since you can schedule the replication jobs when using Data Services, this method is suitable where the source system must be protected from additional load during the main business hours. In this way, you can shift the replication workload, for example, to the night. As a result, the data that is available for reporting always represents the state reached by the time when the latest replication job was started. Use the Management Console, which comes with Data Services, to schedule replication jobs. You can choose from different tools and methods for the scheduling. You can also use the Management Console to monitor the replication process. Required Software Components
PUBLIC
33
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 - NetWeaver Support Package requirement for Data Services SAP Extractor support
3.3.5
Log-Based Replication (SAP Sybase Replication Server)
SAP Sybase Replication Server (SRS) is a sophisticated transactional data movement product that moves and synchronizes data across the enterprise without the limitation of geographical distance, to meet demanding requirements in the enterprise such as guaranteed data delivery, real-time business intelligence and zero operational downtime. SRS facilitates this by non-intrusively handling data at the source and target, while ensuring high performance and transactional integrity. SRS enables you to replicate data into an SAP HANA database from these primary databases: Adaptive Server Oracle Microsoft SQL Server DB2 UDB
It also supports the initial load of data as well as continuous real-time transactional replication from these databases to the SAP HANA database. SRS supports replication of data from non-SAP applications.
34
These are the components required to implement a PrimaryDB-to-SAP-HANA database replication system: A primary data server (SAP Sybase Adaptive Server, Oracle, DB2 UDB, MSSQL 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
Note
License Requirements: You can use these licenses for replication into the SAP HANA database: Separately purchase SAP Sybase Replication Server, SAP HANA edition, for replicating from multiple data sources. This license includes all components required to provision data from UDB DB2, Oracle, or MSSQL into the SAP HANA database. Alternatively, when you buy the Real-time-data edition for SAP HANA, you automatically receive a license for SAP Sybase Replication Server, SAP HANA edition.
Individual components can also be licensed separately for replication from UDB DB2, Oracle, or MSSQL into the SAP HANA database through the SAP Sybase Replication Server, option for SAP HANA. A prerequisite for this is that you must have SAP Sybase Replication Server, enterprise edition.
PUBLIC
35
Related Information
Sybase Product Documentation
3.3.6
Comparison of Replication Methods
This table compares the key features of each replication method. Capability Trigger-Based Replication (SLT Replication) Release coverage SAP R/3 4.6C - SAP ERP 6.0 (EHP06) All other ABAP-based SAP Applications (Basis 4.6CNW7.02) Unicode/Non-Unicode MDMP Yes Partial (If table contains only ASCII characters or language key is included) Yes Yes Partial (1) ETL-Based Replication (Data Services 4.0 SP2) ERP 4.6c - SAP ERP 6.0 Extractor-based Data Acquisition (DXC) SAP Business Suite systems based on NetWeaver ABAP 4.6C or higher
Yes Yes via How to Guide
Transparent Tables
Yes
Yes- via generic Data Source Yes- via generic Data Source No
Cluster & Pool Tables
Yes
Yes
Non-SAP Sources
Yes (for SAP supported DBs only) Yes
Yes
Compressed Values DB Table Row Compression DB Table DB Support (Source side)
Yes
Yes- via generic Data Source Yes- via generic Data Source All SAP supported DBs
Yes
Yes
All SAP supported DBs, incl. ASE
All SAP supported DBs, incl. ASE, and others: see PAM for full list (no MaxDB support)
36
Capability
Trigger-Based Replication (SLT Replication)
ETL-Based Replication (Data Services 4.0 SP2) All OS supported under ERP (NO impact of source OS on Data Services) No Multiple source systems
Extractor-based Data Acquisition (DXC) All OS supported under SAP Business Suite systems Yes Multiple source systems
OS Support (Source side)
All SAP supported OS
Transactional Integrity Multi-System Support
No Multiple source systems to multiple SAP HANA instances Yes
Workload balancing (parallelization of replication) Real-time and/or scheduled replication Initial Load & Delta replication
Yes
Yes
Real-time and scheduled (on table level) Initial load, initial load + delta replication for relevant tables
Scheduled
Scheduled or Event driven
Initial load + delta replication (for table based needs delta information through timestamp column or through delta enabled extractors) Not recommended for use with DataSource extractors with delta processing types AIM, AIE, AIED, AIMD, ADD, ADDD, and CUBE
Initial load + delta replication, for all delta processing types including AIM, AIE, AIED, AIMD, ADD, ADDD, CUBE etc.
Transformation capabilities
Capabilities for filtering and transforming data, as well as data scrambling. Data filtering can be done either via selective triggers or via replication configuration settings Support dashboard
Complete ETL engine from Limited for extraction, via simple functions to very user exits complex transformations
Access to performance statistics
Via Data Services own Management Console or through the integration with SAP Solution Manager
Via Monitoring details Tr: RSMO and via Table View: M_Extractors in SAP HANA studio
PUBLIC
37
Capability
Trigger-Based Replication (SLT Replication)
ETL-Based Replication (Data Services 4.0 SP2) Via Data Services own Management Console or through the integration with SAP Solution Manager
Extractor-based Data Acquisition (DXC) Yes, Via Monitoring details Tr: RSMO, via Table View: M_Extractors in SAP HANA studio, and alerts which can be set in statistics server configuration
Access to trouble shooting Yes feature
(1) SAP Data Services will need a fixed code page for each run. In order to process MDMP, the same job will need to get executed multiple times, each time with a different code page and with a WHERE clause on the language key. This would only be manageable for a limited number of code pages. This table gives an overview of the capabilities of SAP Sybase Replication Server (SRS): Feature/Capability SAP Sybase Replication Server (SRS) Applications (SAP/non-SAP) Table/Database Level Replication Extractors/Data Access @Interface Technology Connectivity Optimized to SAP HANA SAP/Non-SAP Data Sources Transformations/Mapping Real Time Reporting/Distribution Use Cases Bulk Data Loading Delta Loading/CDC SAP HANA Studio Integration User Security/Authorizations Event Streams/Patterns Unicode/Non-Unicode Flexible Deployment topology w/o Geographical restriction Data Definition Language replication (DDL) Publish-subscribe Paradigm Application-independent, DB-specific. However, SAP Business Suite is not supported. Yes Log-based ODBC Both Yes Yes Yes Yes Yes Planned Yes Yes Yes (for non-SAP applications) Yes Planned Yes
38
PUBLIC
Feature/Capability
SAP Sybase Replication Server (SRS)
Transactional Consistency
Yes
PUBLIC
39
4
4.1
SAP HANA End-To-End Roadmap

Sizing SAP HANA
SAP HANA needs to be sized according to the system requirements.
Context
For information about sizing SAP HANA, see the following SAP Notes: SAP Note 1514966 SAP Note 1704499 SAP Note 1637145 SAP HANA: Sizing SAP HANA System Measurement for License Audit SAP BW on HANA: Sizing SAP HANA Database
Note
SAP HANA and SAP NetWeaver BW 7.3, powered by SAP HANA are available in the Quick Sizer tool: https:// service.sap.com/quicksizing .
4.2
Installing SAP HANA
The installation of SAP HANA comprises several steps. The central part is the installation of the SAP HANA Platform Edition. You need to check specific installation information, depending on the data provisioning technology you use or other components you want to add to your SAP HANA landscape.
SAP HANA Platform Edition

For information about installing SAP HANA, see the SAP HANA documentation on SAP Help Portal: SAP HANA Server Installation Guide This guide describes how the components of the SAP HANA Platform Edition are installed with the recommended installation method (hdblcm, hdblcmgui). SAP HANA Server Installation Guide (Unified Installer) This guide describes how the components of the SAP HANA Platform Edition are installed with the SAP HANA unified installer. The SAP HANA unified installer is shipped with SPS 07, but is listed as deprecated as of SPS 07. The SAP HANA unified installer will not be shipped with future releases. SAP HANA Database - Client Installation and Update Guide SAP HANA Database - Studio Installation and Update Guide
40
PUBLIC
SAP HANA Master Guide SAP HANA End-To-End Roadmap
SAP HANA Update and Configuration 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. However, it is not installed during the installation of the SAP HANA Platform Edition. For more information about installing SAP HANA smart data access, see the SAP HANA Update and Configuration Guide. ETL-Based Replication (SAP Data Services) See the Enterprise Information Management page on SAP Help Portal. Log-Based Replication (SAP Sybase Replication Server) See the SAP Sybase Replication Server documentation on the Sybase product documentation page SAP Sybase Event Stream Processor See the Sybase Event Stream Processor documentation on the Sybase product documentation page . .
4.3
Integrating SAP HANA into Customer Landscapes
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 a secondary site and supporting a distributed multi-terabyte database with full fault and disaster recovery.
Related Information
The SAP HANA Network [page 14] 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, and supporting a distributed multi-terabyte database with full fault and disaster recovery.
4.4
SAP HANA Data Management
You use the SAP HANA modeler, which is accessible as a perspective of the SAP HANA studio, for modeling and managing SAP HANA data. It allows technical users to create new or modify existing models of data. In addition, the initial configuration of the data replication is done in the SAP HANA modeler.
PUBLIC
41
4.4.1
Configuring Data Replication
Configure data replication to provide the necessary metadata and data to the SAP HANA system.
Context
You need to perform the following steps: Load table metadata from the data provider systems (source systems) into the SAP HANA database (target system) for all tables of the source system or for a subset of tables Load data (initial load) from the data provider systems (source systems) into the SAP HANA database (target system) for a selection of tables Start continuous replication of data changes from the data provider systems (source systems) into the SAP HANA database (target system) for a selected subset of tables
Once the metadata and data are loaded to the SAP HANA system, you can create views and reports based on these metadata and data. For more information, see the SAP HANA Developer Guide, chapters: Importing Metadata Mass Import of Metadata Selective Import of Metadata
Provisioning Data
Related Information
Modeling Data [page 42] You use the SAP HANA modeler for modeling and managing SAP HANA data. SAP HANA Developer Guide
4.4.2
Modeling Data
You use the SAP HANA modeler for modeling and managing SAP HANA data.
Related Information
SAP HANA Developer Guide
42
4.4.3 Modeling and Data Provisioning for ETL-Based Replication (SAP Data Services)
When using the ETL-Based Replication technology by SAP Data Services, you can also model ERP data by means of Data Services modeling tools. The following documents describe the modeling and data provisioning steps you have to do in SAP Data services: SAP Data Services Administrators Guide -> Server Management -> To configure SAP HANA ODBC SAP Data Services Reference Guide -> SAP HANA target table options SAP Data Services Reference Guide -> Database datastores -> SAP HANA Designer Guide SAP Data Services Describes how to set up a job in the Designer to connect to any database Reference Guide SAP Data Services Describes the options for setting up connections to the SAP HANA database Supplement for SAP Data Services Describes all interactions with other SAP applications
Related Information
Enterprise Information Management on SAP Help Portal
4.5
Configuring End-User Clients
The SAP HANA client provides interfaces for end-user clients to access SAP HANA.
Context
Microsoft (MS) Excel as an end-user client for SAP HANA, and the SAP BusinessObjects BI Clients can access SAP HANA by means of the SAP HANA database client. The SAP HANA client comprises the following interfaces or drivers: SAP HANA ODBO SAP HANA ODBC SAP HANA JDBC SAP HANA SQLDBC
PUBLIC
43
4.5.1 Installing and Using the SAP HANA ODBO Client for MS EXCEL
Customers who intend to use Microsoft (MS) EXCEL as an end-user client for SAP HANA need to install the SAP HANA client on a host where MS EXCEL has been installed and is running.
Context
Prerequisites You have downloaded the SAP HANA client software from SAP Service Marketplace.
Note
Do not use the SYSTEM user for this procedure. Instead, use a dedicated database user to perform this procedure. Procedure Install the SAP HANA ODBO driver on the host where MS EXCEL has been installed and is running. 1. 2. 3. 4. For more information about installing the SAP HANA client, see the SAP HANA Database - Client Installation and Update Guide. Follow the instructions displayed by the installation tool. Set the PATH environment variable to the installation path. For information on setting environment variables, see the documentation for your operating system. Create a connection to the SAP HANA database: a. Create a connection to an external data source:
44
b.
Select the OLE DB Provider for the SAP HANA database from the list and choose Next:
PUBLIC
45
c.
On the Connection tab, specify the connection parameters: a. b. c. d. DataSource: localhost (or another hostname for an externally hosted system, such as luvm1234) Instance number: 00, 01, 02..... User: user ID Password: password
d.
After specifying the connection parameters, select the Foodmart cube (or any other cube that you may have modeled and deployed):
46
PUBLIC
e.
On the next screen, press Finish.
f.
Confirm the following screen with OK. :
PUBLIC
47
You now see a blank pivot table.
Related Information
Software Download [page 9] In the SAP Software Download Center, you have access to the installation media and components for SAP HANA. SAP HANA Client Installation and Update Guide SAP HANA Security Guide
4.5.2 Installing and Using the SAP HANA ODBC Client for MS EXCEL
Customers who intend to use Microsoft (MS) EXCEL as an end-user client for SAP HANA needs to install the SAP HANA client on the host where MS EXCEL has been installed and is running.
Context
Prerequisites You have downloaded the SAP HANA client software from SAP Service Marketplace.
Note
If you use 32-bit Microsoft Excel on a 64-bit machine you have to use %WINDIR%\SysWOW64\odbcad32.exe
48
Note
For security reasons, we recommend to use the secure user store (hdbuserstore). For more information, see the SAP HANA Security Guide.
Note
Do not use the SYSTEM user for this procedure. Instead, use a dedicated database user to perform this procedure. Procedure Install the SAP HANA ODBC driver on the host, where MS EXCEL has been installed and is running. You perform the following steps for consuming SAP HANA data in MS EXCEL: 1. 2. Create an ODBC data source for SAP HANA database. Analyze SAP HANA database data in Excel.
1. Create an ODBC Data Source for SAP HANA Database 1. 2. Search for and start the executable odbcad32.exe, which is normally located in C:\WINDOWS\system32. Choose Add to create SAP HANA database ODBC data source.
PUBLIC
49
3.
Choose the SAP HANA database driver and choose Finish:
4.
Enter your server details:
The port is derived from your SAP HANA database instance. For example, if the database instance is 40, the port number is 34015. 5. Choose Connect to verify your connection:
50
6.
Enter user ID and password and choose OK. Make sure that you see a message confirming successful connection:
2. Analyze SAP HANA Database Data in MS Excel Before you can analyze data, make sure that you have table and data initially loaded and replicated into the SAP HANA database. 1. Launch SAP HANA studio.
PUBLIC
51
As an example, we are using FCT_SVE_SLS_PERFORMANCE_AGG table as shown here:
2.
In the context menu, choose Content and validate the sample data:
3. 4.
Launch MS EXCEL. Make sure you have a blank new MS EXCEL sheet open and then choose Data -> From Other Sources -> From Microsoft Query
52
5.
Select the data source created in the previous section and choose OK:
6.
Enter server details, user ID and password, and choose OK:
7.
Scan through Available tables and columns and locate the table you want to pull the data from:
PUBLIC
53
8.
Click on the move (>) button to select the required tables and columns, and then choose Next:
9.
Define filters as required and choose Next:
54
PUBLIC
10. Define sort order as required and choose Next:
11. Select Return Data to Microsoft Office Excel and choose Finish:
PUBLIC
55
12. Select PivotTable Report and the required worksheet to import data, and choose OK:
MS Excel now requires you to reselect the data source. 13. Choose the Machine Data Source tab:
56
14. Choose your SAP HANA database data source, and choose OK:
PUBLIC
57
15. Enter your user ID and password, and choose OK:
58
16. Choose the required columns and rows from the pivot table, and view the data:
17. You further analyze data from here.
Related Information
Software Download [page 9] In the SAP Software Download Center, you have access to the installation media and components for SAP HANA.
PUBLIC
59
SAP HANA Client Installation and Update Guide SAP HANA Developer Guide SAP HANA Security Guide
4.5.3
Using MS Excel to Create a Pivot Table
You can use MS Excel to create a pivot table and use it as an external data source.
Prerequisites
The SAP HANA ODBO driver is installed on the host where Microsoft (MS) EXCEL is installed and running. The ERP data has been successfully initially loaded to SAP HANA and is continuously replicated. The replicated ERP data has been successfully modeled with the SAP HANA modeler.
Context
1. 2. Start MS EXCEL (see the MS EXCEL documentation). Create an EXCEL PIVOT table. a. b. Insert -> Create PivotTable. Use an external data source.
For more information, see the MS EXCEL documentation.
4.5.4
Using SAP BusinessObjects BI Clients for SAP HANA
You can use SAP BusinessObjects BI clients to create a connection to the SAP HANA database.
Context
Creating the SAP HANA JDBC Connection to the SAP HANA Database The SAP BusinessObjects BI Clients access SAP HANA via the SAP HANA JDBC interface. Once the connection is defined, you need to create a Data Foundation (UNX file) to which the clients connect.
60
Note
With the Explorer, you can also create a native connection from the SAP HANA database to the Explorer application, by configuring the Explorer application settings in the SAP BusinessObjects Central Management Console (CMC). When this type of native connection is used for Explorer, a UNX file is not necessary. To set up the SAP HANA JDBC connection to the SAP HANA database: 1. Copy the file ngdbc.jar to the appropriate folder under /dataAccess/ConnectionServer/jdbc/ drivers/newdb If this directory structure does not exist, you need to create it under ../dataAccess/connectionSrever/ jdbc and then move the jdbc jar file into this directory. 2. 3. 4. 5. 6. 7. 8. Launch the SAP BusinessObjects information design tool. Create a new local project. In this project, create a new relational connection. Name it. Select SAP HANA database as the data source. Enter DB credentials and test. Choose Finish.
Creating a Data Foundation (UNX file) This procedure is not necessary if you want to use the Explorer with a native connection (described below). To create a Data Foundation on a SAP HANA database data source: 1. 2. 3. 4. 5. 6. Launch the information design tool. In your local project, create a new Data Foundation. For more information, see the Information Design Tool User's Guide. Name it. For now select Single Source. Select the data source you just created. Choose Finish to create it.
Creating the Native Connection for the Explorer Application 1. 2. 3. Launch the SAP BusinessObjects Central Management Console. Choose Application -> Explorer -> Advanced properties. Enter the connection information for your SAP HANA system:
PUBLIC
61
4.6
Administrating SAP HANA
The SAP HANA Technical Operations Manual provides information about administering and operating your SAP HANA system landscape.
Related Information
SAP HANA Technical Operations Manual
4.7
Using SAP HANA with End-User Clients
For information about using SAP HANA with end-user clients, see the product documentation provided with the end-user client, such as SAP BusinessObjects Explorer or Microsoft Excel.
62
www.sap.com/contactsap
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Please see http://www.sap.com/corporate-en/legal/copyright/ index.epx for additional trademark information and notices.

SAP HANA Master Guide en

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SAP HANA Master Guide en

Uploaded by

Copyright:

Available Formats

PUBLIC

SAP HANA Platform SPS 07 Document Version: 1.0 - 27-11-2013

SAP HANA Master Guide

4 4.1 4.2 4.3 4.4

Configuring End-User Clients. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 4.5.1 4.5.2 4.5.3 4.5.4

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

SAP HANA Master Guide Table of Contents

Administrating SAP HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Using SAP HANA with End-User Clients. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

SAP HANA Master Guide Table of Contents

Getting Started with SAP HANA

What Is SAP HANA?

SAP HANA Master Guide Getting Started with SAP HANA

SAP HANA Guides

SAP HANA administration and security

SAP HANA Knowledge Center on the SAP Help Portal

SAP HANA documentation for previous Support Package Stacks

SAP HANA Knowledge Center on SAP Service Marketplace

SAP HANA Master Guide Getting Started with SAP HANA

Location https://service.sap.com/bosap-support https://service.sap.com/quicksizer

https://service.sap.com/securityguide http://scn.sap.com/docs/DOC-7848 https://service.sap.com/security https://service.sap.com/unicode https://service.sap.com/sp-stacks

Important SAP Notes

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

SAP HANA Master Guide Getting Started with SAP HANA

SAP Note Number

SAP HANA Master Guide Getting Started with SAP HANA

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

SAP HANA Master Guide Getting Started with SAP HANA

SAP Software Download Center

SAP HANA Master Guide Getting Started with SAP HANA

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

SAP HANA Master Guide Getting Started with SAP HANA

Hardware and Software Requirements

. For information about optimal settings for

SAP HANA Master Guide Getting Started with SAP HANA

SAP HANA Master Guide Getting Started with SAP HANA

SAP License Key

SAP HANA Master Guide Getting Started with SAP HANA

The SAP HANA Network

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

SAP HANA Master Guide The SAP HANA Network

SAP HANA Master Guide The SAP HANA Network

Database Client Access

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

SAP HANA Master Guide The SAP HANA Network

Protocol and additional information

HTTP/S Client Access

SAP HANA studio

5xx13 5xx14 (SSL)

SAP HANA studio

1128 1129 (SSL)

SAP HANA Master Guide The SAP HANA Network

SAP HANA Master Guide The SAP HANA Network

The Network for Distributed SAP HANA Systems

Hosts of a 3xx00 distributed system 3xx01 on one site 3xx02

SAP HANA Master Guide The SAP HANA Network

TCP port 3xx03 3xx04 3xx05 3xx07 3xx10 3xx40-3xx99

Service indexserver scriptserver statisticsserver xsengine compileserver indexservers

Optional, after n->1 recovery

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

SAP HANA Master Guide The SAP HANA Network

SAP HANA Master Guide The SAP HANA Network

SAP HANA Master Guide The SAP HANA Network

SAP HANA Administration Guide SAP HANA Security Guide