tzh200 en col96 ol fv show

7/21/2019 Tzh200 en Col96 Ol Fv Show

http://slidepdf.com/reader/full/tzh200-en-col96-ol-fv-show 1/516

TZH200SAP HANA - Installation & Administration

1



© 2012 SAP AG. All rights reserved. 2RKT

Agenda

Unit 1: Install SAP HANA

Unit 2: Implement SAP HANA

Unit 3: Operate SAP HANA

Unit 4: Monitor and Troubleshoot SAP HANA

Unit 5: Software Lifecycle Management

2




3






Lesson 1: Planning SAP HANA Installation

Lesson 2: Preparing SAP HANA Installation

Lesson 3: Installing SAP HANA

Lesson 4: Enabling High Availability for SAP HANA

4




Unit Objectives

After completing this unit, you will be able to:

Describe key technologies behind SAP HANA like Column store and In-Memory computing

Plan for SAP HANA installation, understanding SAP HANA architecture,landscape and inter-link with other SAP and non-SAP Enterprise softwaresolutions

Understand how to size SAP HANA Prepare for SAP HANA installation, checking and meeting prerequisites of

SAP HANA installation

Install SAP HANA

Explain advanced topics like SAP HANA high-availability installation andconfiguration

5



Planning SAP HANA Installation

6




Objectives

After completing this lesson, you will be able to:


Plan for SAP HANA installation, understanding SAP HANA architecture,landscape and inter-link with other SAP and non-SAP Enterprise softwaresolutions

Understand how to size SAP HANA

7




Agenda

Lesson 1: Planning SAP HANA installation

SAP HANA technology overview, architecture and key technologies

SAP HANA editions

SAP HANA sizing

Where to get further knowledge about SAP HANA

8




What is SAP HANA?

SAP In-Memory Appliance (SAP HANA)

SAP HANA is a hardware and software combination that integrates a number of SAPcomponents including the SAP In-Memory Database.

SAP HANA is a flexible, data-source-agnostic appliance that allows customers to analyzelarge volumes of Enterprise (i.e. SAP ERP) data in real-time, avoiding the need tomaterialize transformations.

SAP HANA is delivered as an optimized appliance in conjunction with leading SAPhardware partners.

9




Hardware-Innovations

64bit address-space – 2TBin current servers

100 GB/s Data throughput

Prices for RAM are

decreasingImprovememt of

Price/Performance

Multi-Core Architecture(8 x 10 core CPU per Server)

Massive parallel scaling withmany nodes

RAM-Locality improved

Row andColumn Store

Compression

Partitioning

No aggregates

neccessary

Avoid expensivedatabase operations

Software-Innovations

In-Memory Computing

10




SAP HANA Simplified architecture

An appliance forprocessing high volumesof transactional data inreal time

Includes tools for datamodeling, data andlifecycle management,security, operations

Provides support for

multiple interfaces basedon industry standards

SAP HANA

SAPBusinessSuite

SAPBusinessSuite

SAP NetWeaverBusiness

Warehouse

Other data

sources

Real-timeReplication

Batch bulkuploads

SAP HANAmodeling

SAP BusinessObjectstools

SAP BusinessObjectstools

Other query tools(i.e. MS Excel via

HANA client)

HANA Admin andDevelopment

11




SAP HANA Extended Architecture

Data Providers

SAP HANA appliance software

• MS Excel / AAO• SAP HANA client

• SAP HANA studio• SAP HANA client

Developer End User

• SBOP BI Platform• SBOP BI Clients

(Explorer, XCelsius,Dashboard)

Access End UserClients via Browser

• SAP ERP System• (*) additional components

depending on real-timereplication requirements

and scenario • SAP HANA database, studio, client• (*) additional components depending on real-

time replication requirements and scenario

• SBOP DataServices Designer • SBOP DataServices Job Server

SBOP Data ServicesSAP BW System

3rd Party System

SAP ERP System

Legend:

Existing SAP systems

SAP HANA Corecomponents

SAP HANA Extendedcomponents by SAPBusiness Object

Non-SAP source

• SAP NetWeaver 7.02• DMIS 2010 Add-on

SAP LT Controller

12




Business Intelligence Clients with SAP HANAStandard Interfaces

SAP BusinessObjectsBI 4.0

Semantic Layer

CrystalReports

WebI Dashboards

Explorer Analysis

Office

SQL(ODBC/JDBC)

BICS

MicrosoftExcel

MDX(ODBO)

DBSQL

CrystalReports

SQL(ODBC/JDBC)

SQL

Other querytoolsTool-

dependent –not certified

13




SAP HANA Columnar Store

Conventional databases store records in rows

Storing data in columns enables faster in-memoryprocessing of operations such as aggregates

Columnar layout supports sequential memory access

A simple aggregate can be processed in one linear scan

A 10 € B 35 $ C 2 € D 40 € E 12 $

A B C D E 10 35 2 40 12 € $ € € $

memoryaddress

organize by row

organize by column

A 10 €

B 35 $

C 2 €

D 40 €

E 12 $

conceptual view

mapping to memory

14




SAP HANA Row Store .vs. Columnar Store

Column wise

stores tables by column

Columns can be accessed in one read.

Columns contain only one data type,enabling very high compression (10x)

Row wise

stores tables by row

Data records are available as completetuples in one read.

Compression is limited.

Accessing only few attributes for each tuple

is an expensive operation.

Accessing all attributes for one tuple(record) is an expensive operation.

Tuple1

Tuple2Att1

Att2

Att3 Att5

Att4

15




Understand Columnar Data Storage

16




SAP HANA Editions

17




SAP HANA Platform Edition

The SAP HANA appliance software platform edition is intended forcustomers who want to use the ETL-Based Replication and already have alicense for SAP BusinessObjects Data Services.

It comprises the following components:

SAP HANA database

SAP HANA studio SAP HANA client

SAP Host Agent 7.20

SAP HANA information composer

18




SAP HANA Enterprise Edition

The SAP HANA appliance software enterpirse edition is intended forcustomers who want to use either Trigger-Based Replication or ETL-BasedReplication and do not already have all necessary licenses for SAPBusinessObjects Data Services.


SAP HANA database

SAP HANA studio

SAP HANA client

SAP Host Agent 7.20


LT Replication AddOn

LT Replication Server SAP BusinessObjects Data Services 4.0

19




SAP HANA Enterprise Extended Edition

The SAP HANA appliance software enterprise extended edition is intendedfor customers want to use the full potential of all available replicationscenarios including the Log-Based Replication.


SAP HANA database

SAP HANA studio

SAP HANA client

SAP Host Agent 7.20


LT Replication AddOn

LT Replication Server

SAP BusinessObjects Data Services 4.0

Sybase Adaptive Server Enterprise (ASE) 15.5 Sybase Replication Server 15 (incl. ECDA)

Sybase Replication Server Agent 15

SAP HANA load controller

20




SAP HANA In-Memory Database Sizing Elements

Refer to OSS note 1514966 for latest HANA sizing

SAP HANA sizing consists of

Memory sizing for static data

Memory sizing for objects created during runtime (data load and query execution)

Disk sizing

CPU Sizing

21




SAP HANA In-Memory Database Sizing: Summary

1. RAM

RAM = Source data footprint *2 / 7

2. DISK

DISK persistence = 4* RAM

DISK log = 1 * RAM

3. CPU

CPU : 300 SAPS / per active user

22




Memory Sizing: Static Data

Memory requirements for static data is derived from the database footprint of thecorresponding tables of the source database system

Database footprint in source system must be determined using database specificcatalog information (e.g. in Oracle: dba_segments; in DB2:syscat.tables).Database specific scripts and more details on how to determine thedatabase footprint can be found in note 1514966.

Average compression factor database table size: HANA memory = 7 : 1

Note that this compression factor refers to uncompressed database tables, andspace for database indexes is to be excluded.

RAM static= Source data footprint / 7

RAM static= Source data footprint / 7

23




Memory Sizing: Runtime Objects

Additional memory required for objects that are created dynamically

when loading new data

when executing queries

We recommend to reserve as much memory for dynamic objects as for static

objects:

RAM dynamic = RAM static

So the total RAM is

RAMdynamic= RAMstaticRAM

= RAMdynamic+ RAMstatic

= Source data footprint * 2 / 7

RAM dynamic = RAM static

RAM = RAM dynamic + RAM static

= source footprint *2 / 7

24




Disk Sizing

Disk size for persistence layer:

This space does not cover requirement for backup.

Disk size for log files /operational disk space:

Disk persistence = 4 * RAM

Disk log = 1 * RAM

25




Disk Sizing - Details

Disk space is required to persistenly store data that is kept in memory.

The space to be provided must be capable to hold:

Data in before- and after-image) versions (2x)

Space for at least one process image in case of software failure (1x)

Space for one data export (1x)

The latter two components are essential to provide support. So a total of 4xthe size of the data in memory is required on disk.

Note that any backup data must NOT be stored in this space, but shouldrather be moved to external storage media.

26




CPU Sizing

Sizing approach similar to user based CPU sizing of BW and BWA

Maximize query throughput by multiuser scenarios with queries of different

complexity out of delivered content, 10-20 million records

Assumptions:

Three different query complexity classes

Three different user profiles (click rate, query complexity)

Same distribution of user classes and query complexities as in BW

Normalization to query throughput per core resp. active user per core

Note that the CPU sizing has to be adjusted so that the server load does not

exceed 65% in average (i.e. to obtain the maximum number of users per

server, the absolute server SAPS capacitiy has to be multiplied by .65).

CPU: 300 SAPS / active user

27




Example from sizing script output in OSS note 1514966

....

ZZYPLANRES .0625

ZZYPLANRESALL .5

ZZYPROT .0625

ZZYTRACE .0625

----------

sum 186348.438

Table footprint of source database: 186348 MB = 182 GB

RAM = Source data footprint * 2 / 7 = 182 GB * 2 / 7 = 52 GB

Disk persistence = 52 GB * 4 = 208 GB

Disk log = 52 GB

28




Important Links

www.sap.com/hana - official SAP HANA page with customer testimonials

www.experiencesaphana.com - SAP HANA collaboration space forcustomers

http://service.sap.com/HANA - Installation and Implementation knowledge

http://help.sap.com/HANA - SAP Help HANA

http://www.sdn.sap.com/irj/sdn/in-memory - SAP Developer Network forHANA

http://help.sap.com/boall - SAP Help BusinessObjects Knowledge Center

29




You should now be able to


Plan for SAP HANA installation, understanding SAP HANA architecture,

landscape and inter-link with other SAP and non-SAP Enterprise softwaresolutions

How to size SAP HANA

Summary

30



Preparing SAP HANA Installation

31




Objectives


Prepare for SAP HANA installation, checking and meeting prerequisites ofSAP HANA installation

32




Agenda

Lesson 2: Preparing SAP HANA installation

Checking prerequisites

Prepare file systems and directories

Prepare installation parameters

Users created during installation

Required installation media

Prepare installer configuration file

33




Prerequisites

SAP HANA Hardware and Software requirements

SAP HANA can only be installed and run on certified hardware.

Visit https://service.sap.com/pam Search for “HANA”

During install a hardware check script will determine if the hardware satisfy certificationrequirements

SAP recommends a dedicated server network of 10Gbit/s between SAP HANA landscape

and the source system for efficient data replication

SAP HANA requires SUSE Linux Enterprise Server (SLES) 11 SP1 or SUSELinux Enterprise Server for SAP Applications 11 SP1

Refer to SAP OSS Note 1310037 for detail of SUSE Linux Enterprise Server installationrequirements

Do *NOT* install additional software on the SAP HANA box!

34




Prepare File Systems and Directories

These directories are required by HANA installer

/sapmnt and /user/sap will be created under /, if do not exist

Data and log directory will not be created automatically by the installer

File System Description Minimum spacerequired

/ The root partition 32GB

/<sapmnt> The file system for the SAP mount directory for global fi les and profilesThe default name for the SAP mount directory is sapmnt, however you canalso specify another name.

5GB

/usr/sap The file system for local SAP system instance directories 2GB

/<path>/data The directory for data-volumes for SAP HANA system.Must be created before start the installer

Must be able towrite at least800MB/s

/<path>/log The directory for log-volumes for SAP HANA system.Must be created before start the installer

Must have acapacity of at least100,000 I/O ops

<WORKING_DIRECTORY>

Temporary directory for the installer to work in.Must be empty when the installer starts

200MB

35




Prepare Installation Parameters

Collect parameter for installing SAP HANA

The parameters to the right need to be inserted in the configuration file

Parameter Description Example

sid The SAP system ID (SAPSID) is the identifier for the SAP HANA system, mustbe unique though out your SAP system instal lation landscape

han

Instancenr The instance number of the SAP HANA system.Two-digit number between 00—97

00

sapmntPath The path to the global SAP mount directory /sapmnt

dataPath The path to the data directory of he SAP HANA systemMust be created manually before start installer

/data

logPath The path to the data directory of he SAP HANA systemMust be created manually before start installer

/log

hdbHost The fully qualified host name of the SAP HANA system A fully qualified host name is assigned to the local host

wdflbmd0327.wdf.sap.com

36




Prepare Installation Parameters

Collect parameter for installing SAP HANA

The parameter to the right need to be entered on the command line during install

Parameter Description Example

Master password A password used for all users created during installation.Must consist of at least eight characters

Must contain at least one lowercase character, one uppercase character andone number.

HANApass1

37




Users created during Installation

The users to the right will be created during installation

Check if the users already exist, and check the user ID and group ID are unique inyour Linux landscape, and are available on all hosts you plan to add to the SAPHANA system

User Description Type of user

<sapsid>adm The system admin is the OS user required for administrative tasks such as

starting and stopping the system.The user ID and group ID of this operating system user must be unique andidentical on each host of a distributed system.

OS

Sapadm The SAP Host Agent administrator If there is no SAP Host Agent available on the installation host, it is createdduring the installation along with user sapadm.If the host agent is already available on the installation host, the installerneither modifies the host agent, nor its sapadm user, nor the sapadm user'spassword.

OS

SYSTEM The database super user.Initially the SYSTEM user has all system permissions.

HANA DB

38




Required Installation Media

The media to the right are required for the installation

Download the installation media from https:/service.sap.com/swdc to downloadthe latest installation media and Support Packages

Medium Folders

SAP HANA Platform EDITION HANA_IM_LINUX__X86_64Contains the instal lation master

HDB_SERVER_LINUX_X86_64Contains the SAP HANA database software

HDB_CLIENT_LINUX_X86_64Contains the SAP HANA database client software

HDB_STUDIO_LINUX_X86_64Contains the SAP HANA studio repository software

SAP_HOST_AGENT_LINUX_X64Contains the SAP Host Agent software

SUM4HANAContains the SUM for SAP HANA deployment archive

39




Preparing the Installer Configuration File

Prerequisites

Created file system and directory according to previous section

Specified installation parameters according to previous section

Required installation media are available

Procedure

Copy the file setuphana.slmodel.template, which is available in theHANA_IM_LINUX__X86_64 folder on the installation medium, to a local directory.Note that the target file must only have the extension .slmodel:

Example:cp /mnt/HANA_DVD/DATA_UNITS/HANA_IM_LINUX_X86_64/setuphana.slmodel.template /tmp/setuphana.slmodel

40




Preparing the Installer Configuration File – cont’d

Procedure – cont’d

Edit the setuphana.slmodel file and insert the required installation parameters by filling in all empty fieldsmarked with ${...}:

Insert the path to the data directory for the SAP HANA system :

Example: <StringParameter name="dataPath" value="/data"/>

Insert the path to the log directory for the SAP HANA system :

Example: <StringParameter name="logPath" value="/log"/>

Insert the path to the SAP mount directory for the SAP HANA system:

<StringParameter name="sapmntPath" value="/sapmnt"/>

Insert a valid instance number for the SAP HANA system:

Example: <StringParameter name="instancenr" value="00"/>

Insert a valid SAP system ID (SAPSID):

Example: <StringParameter name="sid" value="HAN"/>

Insert the fully qualified host name of the SAP HANA system:Example: <StringParameter name="hdbHost“ value="wdflbmd0327.wdf.sap.com"/>

You have prepared the setuphana.slmodel file.

41





Prepare for SAP HANA installation, checking and meeting prerequisites ofSAP HANA installation

Summary

42



Installing SAP HANA

43




Objectives


Install SAP HANA with Unified Installer

44




Agenda

Lesson 3: Install HANA SAP HANA Unified Installer Tool

Running Unified Installer to install the SAP HANA Server

Install HANA Client

Install HANA Studio

Post-Installation steps

45




SAP HANA Unified Installer Tool

The SAP HANA unified installer was first shipped with SPS02. It is a tool to install theSAP HANA appliance software in a single, unified and predefined way. It’s targeted to beused by the SAP HANA hardware partners within their factory process

With SPS03 the SAP HANA unified installer now also …

– Installs the Software Update Manager (SUM) for SAP HANA

– Configures SSL to be used for internal communication between SUM for SAP HANA & SAP Hostagent

– Allows also uninstall of SAP HANA appliance software

Detailed instructions on how to use SAP HANA unified installer can be found in the “SAPHANA 1.0 Overall Installation Guide”, available at SAP Service Marketplace onhttp://service.sap.com/hana

46




Running the Unified Installer

PrerequisitesFollow steps in lesson 2 to check all prerequisites.

Procedure

Log on to the installation host as a user with root authorizations

Start the installer in one of the following ways:

– To run the installer from the installation medium, proceed as follows:

Change to the directory HANA_IM_LINUX_X86_64 on the installation medium where thesetup.sh script is located

Start the installer from command line by entering:

– ./setup.sh <WORKING_DIRECTORY> <MODEL_FILE>Example: ./setup.sh /tmp/hanainst /tmp/setuphana.slmodel

To run the installer from the downloaded installer ZIP file, proceed as follows:

– Change to the directory where you unpacked the installer ZIP – Start the installer from the command line by entering the following command:

47




Running the Unified Installer – cont’d

Procedure – cont’d – /setup.sh –d <MEDIUM_LOCATION> <WORKING_DIRECTORY> <MODEL_FILE>

Example: ./setup.sh -d /mnt/HANA_DVD /tmp/hanainst /tmp/setuphana.slmodel

Enter Master Password when prompted by the installer.

Result

The installation progress is displayed on the command line If the installation is successful, you see the message Finished successfully at the end

of the command line output and the SAP HANA system is up and running

48




Components installed by the installer

Check and confirm the installer installed the following components

Component Directory Description

SAP Host Agent

/usr/sap/hostctrl For more information about the host agent and its elements, seeSAP Note 1031096 – Installing Package SAPHOSTAGENT

SAP HANA

database

/usr/sap/<SAPSID> Contains the following sub-directories: home, SYS, exe, global,

profile, lm_structureSAP HANAclient

/usr/sap/hbdclient Only the client on the SAP HANA system, not clients on relatedSAP ERP systems

SAP HANAstudiorepository

/usr/sap/hdbstudio_update

The SAP HANA studio repository is installed (not the completeSAP HANA studio). Users can use this repository to update theirlocal SAP HANA studio installation.

SUM for

SAP HANA

/usr/sap/<SAPSID>/S

UM

The Software Update Manager (SUM) for SAP

HANA downloads new Support Package Stacks(SPS) for SAP HANA from the SAP ServiceMarketplace (SMP) and updates the componentson your SAP HANA system.

49




Install SAP HANA Client

To enable a server other than SAP HANA Server to communicate with SAPHANA Database client software needs to be installed on this server

Available Clients on Linux:

SQLDBC

ODBC

JDBC

Available Clients on MS Windows:

SQLDBC

ODBC

ODBO

JDBC

50




Install SAP HANA Client on a Linux host

Procedure Log on to a Linux shell as the user root

Download and extract the software to an empty directory

In this directory call the program hdbsetup (GUI installation) or hdbinst (command-lineinstallation) by entering one of the following command

Follow the instructions displayed by the installation tool

For the users that will use the client, including the user <SID>adm, set the environmentvariable LD_LIBRARY_PATH to the installation path

Installation logs can be found in /var/tmp/hdb_client_<time_stamp>

Option Command to run

GUI ./hdbsetup –a client

Command Line ./hdbinst -a client [<option_list>]

51




Install SAP HANA Client on a Windows host

Procedure Log on to a Windows as a local administrator


Open a command prompt and go to this directory, call the program hdbsetup (GUIinstallation) or hdbinst (command-line installation):


Set the PATH environment variable to include the installation path

Installation logs can be found in %TEMP%\hdb_client_<time_stamp>


GUI ./hdbsetup –a client

Command Line ./hdbinst -a client [<option_list>]

52




Install SAP HANA Studio

The HANA administrator and HANA modelers will require SAP HANA Studioto perform their job, the SAP HANA Studio can be installed on a Linux or aWindows host

SAP HANA Studio can be installed and updated by Installation Managerhdbsetup

SAP HANA Studio can also be updated by SUM for SAP HANA which will offer updates to all SAP HANA Studio installations once

SAP HANA system is updated, or

Setup the repository manually using the hdbinst program on any server then manuallyconfigure it to be available to the SAP HANA Studio installations. This is no dependencyon SUM for SAP HANA.

53




Install SAP HANA Studio

System Requirements JRE 1.6 must be installed to run HANA studio

The java runtime must be accessible for the user that runs the studio via the PATHvariable.

Make sure that you choose the correct Java variant for your installation of SAP HANAstudio:

For a 32-bit installation, choose a 32-bit Java variant.

For a 54-bit installation, choose a 64-bit Java variant.

Supported Platforms

Microsoft Windows x32 and x64 version of:Windows XPWindows VistaWindows 7

SUSE Linux Enterprise Server SLES 11: x86 64-bit

54




Install SAP HANA Studio on a Linux host

Prerequisites GTK2 is installed (this is contained in SLES11)

You have authorization to use a display

Java run time is accessible via PATH, JAVA_HOME, or --vm parameter

Procedure

Log on to a Linux shell as user root Download and extract the software to an empty directory

In this directory call:


Installation logs can be found in /var/tmp/hdb_studio_<time_stamp>


GUI hdbsetup -a studio

Command Line hdbinst -a studio [<option_list>]

55




Install SAP HANA Studio on a Windows host

Prerequisites Java run time is accessible via PATH, JAVA_HOME, or --vm parameter

Procedure

Log on to the Windows host as a local administrator


In this directory call:


Installation logs can be found in %TEMP%\hdb_studio_<time_stamp>


GUI ./hdbsetup -a studio

Command Line ./hdbinst -a studio [<option_list>]

56




Post-Installation procedure

PrerequisitesSAP HANA installer has finished completely.

Procedure

Starting and stopping the SAP HANA system

Displaying the process List

Logging on to the SAP HANA system using the SAP HANA Computing Studio

Ensuring User Security

Configuring the Software Update Manager for SAP HANA

Accessing the SAP HANA Studio p2 Repository

Enabling Automatic Start of the SAP HANA Database

Applying Updates and Support Packages

Monitoring the SAP HANA System Landscape

57




Stop and Starting SAP HANA database

Stopping SAP HANA database

•Using sapcontrol as root

/usr/sap/hostctrl/exe/sapcontrol -nr <Instance_Number> –function Stop

•Using HDB as <sapsid>adm

/usr/sap/<SAPSID>/<Instance_Name>/HDB stop

Starting SAP HANA database

•Using sapcontrol as root

/usr/sap/hostctrl/exe/sapcontrol -nr <Instance_Number> –function Start

•Using HDB as <sapsid>adm

/usr/sap/<SAPSID>/<Instance_Name>/HDB start

58




Displaying the Process List

Displaying process list at command line

•Log on to Linux command line as root

/usr/sap/hostctrl/exe/sapcontrol -nr <instancenr> -functionGetProcessList

Displaying Process list in GUI

•You can also use SAP Microsoft Management console (SAP MMC) fromWindows PC to display SAP HANA process list

59




Logging on to the SAP HANA system

Logging on to the SAP HANA system using SAP HANA Computing Studio Launch SAP HANA Computing Studio on your PC

Open the “Administration Console perspective”

On the right hand Navigator pane right-click and select “Add System”

Enter required parameters, hostname, instance number and SAP system ID

Choose Authentication by database user” and enter SYSTEM for “User Name”

Enter the master password your set during installation

You see your newly installed SAP HANA system in the “Navigator” view

60





The SUM uses a key pair for HTTPS connections to host agent, and anotherkey pair for accepting connection from user PC (to update Uses’ Studio)

The following diagram shows the key pair usage

61





The following steps need to be done on each SAP HANA Studio installationwhere the SAP HANA Update UI will be used

• Copy the server from /usr/sap/<SID>/SUM/config/sumforhancertificatesumforhana.cer a.cer to the host where the SAPHANA Studio is installed.

• Run the following command from the directory where you have copied

sumforhana.cer:keytool -importcert -keystore "<JRE_DIR>\lib\security\cacerts" -aliassumforhana_$<hostname>_$<SAPSID> -file sumforhana.cer

Restart the SAP HANA Studio

62





Prerequisite You have configured SUM for SAP HANA as previous step.

Procedure

Log on to SAP HANA system using SAP HANA Computing Studio

Use the “Lifecycle Managemetn Perspective” in the SAP HANA studio to update yoursystem.

63





By default the SAP HANA database is configured that it is not startedautomatically when the SAP HANA host is rebooted, to enable auto start

Log on to the SAP HANA host as a user with root authorization

Change to the system profile directory /usr/sap/<SAPSID>/SYS/profile

Edit the <SAPSID>_HDB<Instance_No>_<host_name>profile

Change the parameter setting Autostart = 0 to Autostart = 1

Save the profile <SAPSID>_HDB<Instance_No>_<host_name>

The SAP HANA database will start automatically next time SAP HANA hostis rebooted

64




Monitoring the SAP HANA System landscape

Perform regular system monitoring task

Check the system status on the Overview tab page of the Administration screen in the“Administrative Perspective”, for important system information

Overall system state

General system information (software version, etc)

Warnings (generated by statistics server which is a monitoring tool for the db)

System resources on the bar view (available memory, CPU and storage space)

Services (preprocessor, name server, index server for each host; the statistic server runson each host but only the one on master server is actually running)

Diagnosis Files shows server side logs

65





Install SAP HANA

Summary

66



Enabling High Availability for SAP HANA

67




Objectives


Explain advanced topics like SAP HANA high-availability installation andconfiguration

68




Agenda

Lesson 4: High-availability Concept of HANA high-availability

Install HANA distributed systems

69




High Availability Features

Scenarios One data center fails (due to fire, power outage, earthquake, etc.)

One node fails (hardware failure)

Concept Redundant data center (including redundant HANA system) – Hot Standby

– Synchronous mirroring

Standby system within one NewDB landscape – Cold Standby

– Failover is triggered automatically

70




Disaster ToleranceRedundant Hardware

2 Independent Landscapes

Data Center 1 Data Center 2

Source System Source System

NewDB NewDB

Storage System

Node 4

Node 1

Node 2

Node 3

Node 4

Node 1

Node 2

Storage System

Node 3

Switchover

Mirroring

Mirroring

PROXY

71




Distributed system and Standby Host

Distributed System SAP HANA server software is based on a flexible architecture that enables a distributed

installation. This means that load can be balanced between different hosts. If you want tocreate a distributed system, make sure that you set it up in a safe environment.

The server software has to be installed in a file system where all hosts that are part of thesystem can be mounted. You use the hdbsetup or hdbinst program for the installation.You can then use the hdbaddhost program to add more hosts to the master instance.

Standby Host

In a distributed system, some of the servers are designated as worker hosts, and otherservers are designated as standby hosts. Multiple servers can be grouped together toallow a dedicated standby host to be assigned to each group. You can assign multiplestandby hosts to each group.

SAP HANA database supports cold standby hosts, where a standby host is kept ready for

the event that a failover situation occurs during production operation. A standby host isnot used for database processing. All the database processes run on the standby host,but they are idle and do not allow SQL connections. It is not possible to configureindividual services on a standby host; all the services are configured together.

72




Distributed system

Multiple nodes utilizing shared filer for workload distribution

Confidential

73




Installation Planning for a distributed system

Prerequisites The user ID of <sid>adm and group ID of sapsys is available on all hosts

The instance number to be assigned to the distributed system is available on all hosts

The same mount point definitions can be used on all hosts

Sufficient storage space to mount the logical data and log volumes below the mount point

– normall /sapmnt

An SAP HANA system is installed with its server software on a shared file system

74




Install a distributed system

Procedure Logon to the new host shell as root

Change to the following mounted shared directory /<sapmnt>/<SID>/global/hdb/install/bin

Call the hdbadhost program./hdbaddhost

Specify the data when requested by the program

75




What to check for distributed installation?

Adding a node using hdbaddhost: A system has been installed with its server software on a sapmnt shared file system

(export options rw, no_root_squash).

This system is running.

You are logged on to the new host as the root user.

You have mounted the current host to the shared file system.

Consistent user environment (uid, gid, system number).

In an SAP system, the requirements for host names of SAP servers are met (SAPNote 611361)

76




Monitoring and configuring Standby Hosts

To view the configuration In SAP HANA Studio, choose Landscape -> Configuration

Or query the Monitoring view SYS.M_LANDSCAPE_HOST_CONFIGURATION

To change the configuration

Use the stored procedure SYS.UPDATE_LANDSCAPE_CONFIGURATION

Configuration is performed for the name server and the index server. The statistics serverand the tenant services are not configured individually, as they are always failed overtogether with the index server.

When the name server configuration is changed, the new configuration is activated whenthe service is restarted or in a failover situation.

77




You should now be able to:

Explain advanced topics like SAP HANA high-availabilityinstallation and configuration

Summary

78




79



© 2012 SAP AG. All rights reserved. 2


Unit 2: Implement SAP HANA Lesson 1: Configuring Data Replication with SLT

Lesson 2: Configuring Data Replication with BODS

80



Configuring Data Replication with SLT

81



Positioning and Key Concepts

82




At the end of this Lesson you will be able to:

• Know how to position SAP LT Replication Server

• Understand the key concepts and features

• Know the technical prerequisites and how to set up the SAP LTReplication Server

• Name the benefits of the trigger-based replication approach

Objectives

Configuring Data Replication with SAP BusinessObjects Data Services


Describe the cooperation of SAP HANA and SAP BusinessObjects Data Services

Configure SAP BusinessObjects Data Services for Metadata Import

Configure SAP HANA Studio for Metadata Import

Import Metadata via Data Services into SAP HANA

Load Data via Data Services into SAP HANA

83

O i




This module covers the following topics:

• Product name, positioning and key benefits

• Commercial aspects and software shipment

• Overview on key concepts, features and user interfaces

• Overview on key installation and configuration steps

• Customer and Project Examples

OverviewPositioning and Key Concepts

84




Product Name

SAP Landscape

Transformation

Replication Server

for SAP HANA

85

SAP LT R li ti S f SAP HANA L




SAP LT Replication Server for SAP HANA Leverages

Proven SLO Technologies

Application Lifecycle Management• SLO* technologies have been usedsince more than 10 years in hundred

of projects per year

• Key offerings foster SAP‘s Application

Lifecycle Management concept

• SAP LT Replication Server - as a new

use case - leverages several SLO

technologies

*) System Landscape Optimization

86

P iti i d K B fit f SAP LT R li ti




Positioning and Key Benefits of SAP LT Replication

Server for SAP HANA

Key Benefits of the Trigger-Based Approach:• Allows real-time (and scheduled) data replication, replicating only relevant data into

HANA

• Ability to migrate data into HANA format while replicating data in real-time

• „Unlimited“ release coverage (from SAP R/3 4.6C onwards) sourcing data from SAP

ERP (and other ABAP based SAP applications)

• Leverages proven SLO technology (Near Zero Downtime, TDMS, SAP LT)

• Simple and fast set-up of LT replicator (initial installation and configuration in less than

1day) and fully integrated with HANA modeler UI

SAP LT Replication Server is the ideal solution for all HANA customers who

need real-time or scheduled data replication sourcing from SAP and NON-SAP sources

87




Commercial Aspects and Software Shipment

Commercial Aspects

SAP LT Replication Server for SAP HANA will be

part of SAP HANA software license model

Software Shipment

SAP LT Replication Server for SAP HANA will be

part of SAP HANA software shipment and fully

integrated into the SAP HANA modeler UI

88

C t O i T i B d A h




Concept: Overview - Trigger-Based ApproachPositioning and Key Concepts

SAP HANA systemSAP source system SAP LT Replication Server

Application Table

Trigger Based

Delta Recording

Replication

Engine

Application Table

RFC

Connection

HANA Studio

DB

Connection

Replication Configuration

Connection(s) between source system and SAP HANA system are

defined as “Configuration” on the SAP LT Replication Server

Data load and replication are

triggered via SAP HANA Studio

SAP LT Replication Server does not have to be a separate

SAP system and can run on any SAP system with SAPNetWeaver 7.02 ABAP stack (Kernel 7.20EXT)

89

Concept: Architecture and Key Building Blocks




Concept: Architecture and Key Building BlocksPositioning and Key Concepts

SAP HANA systemSAP LT Replication Server SAP source system

Efficient initialization of data

replication based on DB trigger

and delta logging concept

(as with NearZero downtime approach)

Flexible and reliable replication

process, incl. data migration

(as used for TDMS and SAP LT)

Fast data replication via DB connect

LT replication functionality is fully

integrated with HANA Modeler UI

Application table Logging table

DB trigger

Read module Structure mapping &

Transformation

Application table

Write module

RFC

Connection

DBConnection

90

Concept: Architecture for Non SAP Source Replication




Concept: Architecture for Non-SAP Source ReplicationPositioning and Key Concepts

In a first step, SAP LT Replication Server transfers all metadata table definitions from the non-SAP

source system to the HANA system. From the HANA Studio perspective, non-SAP source replicationworks as for SAP sources. When a table replication is started, SAP LT Replication Server creates

logging tables within the source system. As a difference, the read modules are created in the SAP LT

Replication Server. The connection the non-SAP source system is established as a database connection.

SAP HANA systemSAP LT Replication Server Non SAP source system

Application table Logging table

DB trigger

Read module

Structure mapping &

Transformation

Application table

Write module

DB

Connection

DB

Connection

91

Concept: Multi System Support




Concept: Multi System SupportPositioning and Key Concepts

SAP HANA systemSource systems

System A

System B

Schema 1

Schema 2

Source systems are

connected to separate

HANA schema on the

same HANA System


System A

System B

Schema 1

Schema 1

Source systems are

connected to separateHANA systems.

Schema name can be

equal or different


System A

System B

Schema 1

Source systems are

connected to same

HANA system andalso the same

schema

92

Procedure: Set up of LT Replication Server




Procedure: Set-up of LT Replication ServerPositioning and Key Concepts

Configuration steps for SAP LT Replication Server

Define a schema for each source system

Define connection to source system

Define DB connection into SAP HANA

Define replication frequency (real-time; frequency for scheduled replication)

Define maximum number of background jobs for data replication

Installation aspects

Source system(s): use respective DMIS add-on

LT replication server: use add-on DMIS_2010_1_700 with SP05;

other system requirements (NW 7.02; SAP Kernel 7.20EXT) apply

Apply SPS03 for SAP HANA 1.0

Set-up of data replication in SAP HANA

Select relevant source system

Start (initial load only and / or continuous replication)

93

Procedure: Key Configuration Steps




Procedure: Key Configuration StepsPositioning and Key Concepts

Call SAP LT Replication Server

Configuration (Transaction: LTR)

Define configuration data

94

Procedure: Starting the Data Replication




Procedure: Starting the Data ReplicationPositioning and Key Concepts

Choose data provisioning to

launch SAP HANA Modeler UI

1. 1. Select source system as defined in SAP

LT Replication Server; related system

information and schema will be displayed

2. 2. Use button Load and / or Replicate to set

up the data replication

3. 3. Use button Stop Replication to finish

replication

4. 4. Use button Suspend to pause replication

5. 5. Use button Resume to continue replication

95

References: Customer and Project Examples




References: Customer and Project ExamplesPositioning and Key Concepts

SAP HANA customers are already live using SAP LT

Replication Server for data replication

A lot of prototyping projects are in process

-> many more live customers expected in 2012

Real-time data replication is a key capability requested by

HANA customers

SAP LT Replication Server was quickly adopted and

is today the default solution for real-time integration

of SAP sources into SAP HANA

96

Database - Supportability Matrix




Database - Supportability MatrixSAP LT Replication Server for SAP HANA

Database

Technical availability

SAP Sources Non SAP Sources (*)

MSFT SQL Server Enterprise Edition OKOK

Oracle Enterprise Edition OK OK

IBM DB2 LUW/ UDB (DB6) OK OK

IBM DB/2 zSeries OK OK

IBM DB2 iSeries (former AS/400) OK Not yet supported

IBM Informix Planned for HANA SPS4 Not supported

SAP MaxDB OK OK

Sybase ASE Available until End of January 2012 Planned for HANA SPS4

For non-SAP source systems, the customer database license needs to cover a

permanent database connection with 3rd party products like SAP LT Replication

Server.

(*) Since a DB connection from SAP LT replication server to a non-SAP system is required, the OS/DB restrictions of SAP

NetWeaver 7.02 apply (see at http://service.sap.com/pam)

97




SAP LT Replication Server - Roadmap at A Glance

Several conceptual enhancements in alignment with

SAP HANA development

Replication of tables into multiple HANA systems

User experience and usability

More integrated monitoring capabilities, e.g. status

and replication logs in SAP HANA and SAP Solution

Manager

Improved operations aspects

Replication repository

Transactional integrity

98

Summary





• Understand the positioning of SAP LT Replication Server

• Describe the key concepts and features

• Know the prerequisites and how to set up the SAP LT ReplicationServer

• Name the benefits of the trigger-based replication approach

SummaryPositioning and Key Concepts

99



Landscape Strategy and Sizing Aspects

100

Objectives





ObjectivesLandscape Strategy and Sizing Aspects

• Describe landscape strategy of SAP LT Replication Server

• Explain the general sizing recommendations

• Describe important LT replication jobs

101

Concept: SAP LT Replication Server Installation options




Concept: SAP LT Replication Server Installation optionsLandscape Strategy and Sizing Aspects

SAP sourcesystem

Non-SAP sourcesystem

SAP LT ReplicationServer

SAP sourcesystem

SAP HANA

SAP LT Replication Server runningon the respective SAP source system

SAP sourcesystem

Non-SAP sourcesystem

SAP LT ReplicationServer

SAP sourcesystem

SAP HANA

SAP HANA

Dedicated SAP LT Replication Serveras central replication system

SAP sourcesystem

SAP HANASAP source

system

102

Concept: PROs and CONs - Installation Options




Concept: PROs and CONs Installation OptionsLandscape Strategy and Sizing Aspects

Recommended only for sandbox purposes, in

pure prototyping projects or as DEV / QAS

environment - if technical prerequisites

allow installation

Source system Solution Manager Dedicated system

PRO • Simplified landscape

and administration

• Re-use of existing NW

instance

• No patching dependency

• Central LT Replication Instance

for all replication scenarios

CONS • Performance impact

• Patching dependency

• Performance impact

• Patching dependency

• Investment and maintenance

effort for separate server / NW

instance

Recommended as productive

SLT instance

Finally - it is the customer’s choice!!!

103

Concept: Technical Requirements and System Set-Up

I f ti S t f li ti f SAP t




Information- Setup for replication from SAP systemsLandscape Strategy and Sizing Aspects

SAP HANA systemSAP LT Replication Server SAP source system

System Requirements:

-SAP Basis: NetWeaver 7.02 with Kernel 7.20EXT

(64BIT Unicode) PL110 - see SAP note 1597627

- Filesystem: 100 GB

- RAM: 16-32 GB

- CPU: 2-4 cores

- Recommended number of background jobs: 10

DB

Connection

RFC

Connection


- SAP Basis 4.6C and higher

- All data bases

Installation:

- respective DMIS 2010 version- Minimum support pack level: latest

available recommended!

Installation:

- Addon DMIS 2010_1_700- Minimum support pack level: SP05

Basic Configuration:

- Define RFC connection to source system

- Define DB connection to HANA system

- Define no. jobs for data replication


- Optional: define separate table space

for logging tables

- Define RFC user with appropriate authorization

(With SP05 - a streamlined user role

SAP_IUUC_REPL_REMOTE is available)


- Create / define DB user with appropriate

authorization

104

Concept: Supported Software Combinations




Co cept Suppo ted So t a e Co b at o sLandscape Strategy and Sizing Aspects

Source System LT Replication Server SAP HANA

DMIS 2010 SP3/4 DMIS 2010 SP4

HDB DBSL Patch Level = 100

SAP HANA 1.0 SPS2

DMIS 2010 SP3/4/5 DMIS 2010 SP5

HDB DBSL Patch Level >= 110

SAP HANA 1.0 SPS3

It is recommended to install the same DMIS support package level on all

involved systems

Due to incompatible changes in the SAP HANA SQL syntax within the HANA 1.0SP3 delivery, a HANA SP2 and SP3 system cannot be addressed by the same SAP


105

Concept: General Sizing Recommendations




p gLandscape Strategy and Sizing Aspects

LT Replication Server: see below

Network Connection: 1-2 GBit/sec

Source system: no specific considerations

except size of SLT specific logging tables


Installation:

- Addon DMIS 2010_1_700

- Minimum support pack level: SP05


- Define RFC connection to source system

- Define DB connection to HANA system

- Define no. jobs for data replication


-SAP Basis: NetWeaver 7.02 with Kernel 7.20EXT

(64BIT Unicode) PL110 - see SAP note 1597627

- Filesystem: 100 GB- RAM: 16-32 GB

- CPU: 2-4 cores

- Recommended number of background jobs: 10

Processing on SLT system needs mainly

RAM and BGD jobs

For the productive use and depending on

expected performance, the sizing

requirements may by higher

106

Concept: Important LT Replication Jobs




p p pLandscape Strategy and Sizing Aspects

Monitoring Job – IUUC_MONITOR_<Mass Transfer ID>

Every 5 seconds, the monitoring job checks in the HANA system whether there are new

tasks and triggers the master control jobs. It also deletes the processed entries (tasks) from

table RS_ORDER (in the corresponding HANA schema) and write statistics entries into

table RS_STATUS.

Master controller Job – IUUC_REPLIC_CNTR_<Mass Transfer ID>_<4digits>

This job is started on demand by the monitor job and is responsible for:

• creating DB triggers and logging table in source system• creating tables and synonyms in HANA system

• Generate load / replication object

Data load Job – DTL_MT_DATA_LOAD_<Mass Transfer ID>_<2digits>

This job is responsible for:

• loading data (load)

– replicating data (replication)

107

Concept: Sizing of LT Replication Server - Number of

BGD jobs




BGD jobsLandscape Strategy and Sizing Aspects

Number of schemas parallel in use

• Each configuration schema needs one master background job

plus one for each defined load/replication job

Number of tables to be replicated / in replication

• As a standard value, one replication job should be defined for

each 20 tables to be in real-time replication

• Depending on the change rate, the standard value needs to be

increased to ensure real-time replication

• During initial data load, additional jobs may be added to shorten

the initial load time.

Replication controller jobs

• If new tables are added for load or replication, a controller job is

started to execute the required steps (e.g. trigger creation,

generation of runtime objects)

108

Summary





yLandscape Strategy and Sizing Aspects

• Describe landscape strategy of SAP LT Replication Server

• explain the general sizing recommendations

• describe important LT replication jobs

109



Installation Procedure

110

Objectives






• Describe the installation procedure of SAP LT

Replication Server

111

Procedure: Add-On DMIS2010 and Relevant SPs in

Source system and SAP LT Replication Server




Source system and SAP LT Replication Server Installation Procedure

1. Install DMIS add-on on the SAP source system and SAP LT Replication

Server system

Make sure basis requirements are met as per Note 1468391

Install DMIS add-on as per Note 1468391

Apply required support packages (according to the HANA SP level)

Apply additional corrections (SAP Notes) as references in central SLT Note 1605140

SAP Notes

1605140 - SAP HANA 1.0: Central Note - SAP LT

Replication Server

1468391 - Installation and delta upgrade of DMIS

2010_1

112

Procedure: SAP Kernel and DBSL Installation in SAP





LT Replication Server Installation Procedure

1. Install required SAP kernel and DBSL on SAP LT Replication Server

2. Upgrade kernel as per Note 1597627

• 7.20 or 7.20_EXT Kernel with PL >= 82

• 7.20 DBSL with PL >= 110 is needed

3. Install HANA DB-Client SW on SLT system

as per Note 1597627

• #./hdbinst -a client -p /usr/sap/TF1/hdbclient -s TF1

• Add hdb client libraries to library path, e.g. by adding the following line to .sapenv_<host>.cshsetenv LD_LIBRARY_PATH ${LD_LIBRARY_PATH}:/usr/sap/<SID>/hdbclient

SAP Notes

1597627 - HANA connection

1603660 - Individual release 7.20 kernel on

MaxDB for Hana LT

19466 - Downloading SAP kernel patches

>= 82>= 110

113

Procedure: Activation of Web Services in SAP LT

Replication Server




Replication Server Installation Procedure

1. Activate WebDynpro as per Installation Guide

• Make sure to enable the services that are listed at (link is also included in Installation

Guide)http://help.sap.com/saphelp_nw70ehp1/helpdata/en/46/d28dfa34bb12bee10000000a1553f7/content.h

tm

• Activate all services listed in the Installation Guide

• Start WebDynpro with transaction LTR to verify if all services are active

114

Procedure: Create RFC User in SAP source system





If the SAP LT Replication Server is installed on a separate System, an RFC User has to be

created on the source system. The user can be created as communication user.

To have the required authorization, role SAP_IUUC_REPL_REMOTE must be assigned to

this user.

User role SAP_IUUC_REPL_REMOTE includes much less authorizations than therecommended user roles with HANA SPS02 (but old roles can still be used)

Note: The streamlined user role is included with SP05 - therefore is required to apply

DMIS_2010 SP05 on the source system first!

115

Procedure: User Role Assignment in SAP Source

System (1/2)




System (1/2)Installation Procedure

After the installation of the DMIS add-on, the role SAP_IUUC_REPL_REMOTE is

available in the system but not generated yet. To generate a role proceed as follows:

a)Call transaction PFCG, enter role name and switch to change the mode

b)Go to the Authorization tab page and define

the profile name for this role using

button Propose Profile Names

c)After the profile name is generated,save the data and switch to the

authorization data screen using button

Change Authorization Data

d)Generate the profile authorities using

button Generate. The status will

switch to generated. Afterwards youcan return to the previous screen

116

Procedure: User Role Assignment in SAP Source

System (2/2)




System (2/2)Installation Procedure

e) The status on the tab header Authorizations should be green now. Check the status of the

tab header User and proceed with the following steps if it is not showing a green light.

f) Go to the User tab page and press

button User comparison

g) In the pop-up window press button

Complete comparison

Both Authorization and User tab pages should have a green light now.

117

Procedure: Create RFC Connection in SAP LT

Replication Server




Replication Server Installation Procedure

If the SAP LT Replication Server is installed on

a separate system, a RFC connection to eachrelevant source system has to be created on

the SAP LT Replication Server.

It is recommended to use a system identifier in

the RFC destination name to easier find the

right RFC destination afterwards.

Call transaction SM59 and create a new RFC

destination with Connection Type = 3 (ABAP

Connection). Define the connection parameters(target host and system number) in the

Technical Settings tab page.

Switch to the Logon & Security tab page and

enter the User and Password created in the

source system before. Set the corresponding

Client in which the user is created.

In case of replication from a single codepage

source system, the corresponding Languagehas been set (not relevant for replication from a

Unicode system)

118

Procedure: Create Database Connection (non-SAP

source) in SAP LT Replication Server




source) in SAP LT Replication Server Installation Procedure

Install appropriate DBSL client on the SAP LT Replication Server

Establish a secondary database connection via transactionSM30 (table DBCON) to the non-SAP source system

The user defined in the database connection needs the following authorizations:•Selecting from the tables

•Creating tables in the given schema (for creating the logging table)

•Selecting from the logging tables

•Deleting the logging tables

•Creating database triggers for tables

•Deleting the triggers•Creating synonyms for specific tables

•Deleting the synonyms

Add DB connection to DBA cockpit (T-Code: DBACOCKPIT) and test connection

119

Procedure: Create Database Connection to Non-SAP

Source System - Oracle




Source System OracleInstallation Procedure

DBMS – ORA

User name & DB password

User name and password on the source database

Conn. Info

<database_host>: <port> / <DB_ID>

<database_host> = host name of the database server

<port> = TCP port of the database listener

<DB_ID> = database ID of the database that has to be connected

Flag permanent should usually not be set for a secondary connection.

120

SummaryI t ll ti P d






• Describe the installation procedure of SAP LT

Replication Server

121



Configuration Aspects

122

ObjectivesC fi ti A t






• Know how to define a configuration of SAP LT

replication Server

123

Concept: Define Configuration / SchemaConfiguration Aspects





SAP HANA systemSAP source system SAP LT Replication Server

Trigger-baseddelta recording

Replicationengine

RFCConnection

Replication Configuration

A new configuration can be created in the LT Configuration and Monitoring Dashboard. In

that step, the connection between the source and the HANA system is established and thetarget schema will be created (if it doesn’t exist already). Also replication control tables are

created and table lists are replicated from the source system. In addition, the required roles

and GRANT / REVOKE procedures are generated.

Schema 1

DBConnection

124

Concept: Call SAP LT Replication Server - DashboardConfiguration Aspects





Start WebDynpro with transaction LTR to verify after all services are activated

To create a new

configuration, press thebutton New

125

Procedure: Creating a New ConfigurationConfiguration Aspects





General Data

• Define the replication target Schema Name in the HANAsystem (if schema does not exist, it will be created

automatically)

• Define the Number of Replay Jobs used for data load

and replication

Connection to the source system

• SAP Source System: Use previously defined RFC

destination to source system

• Non SAP Source System: Select the source databasesystem and set the required fields (see also next slides)

Connection to HANA system

•Define the User Name and Password which can be used to connect to the HANA system (see also next slide)

•Define the Host Name and Instance Number of the target HANA system

Table space assignment

• Optional: define table space for logging tables. If no table space is defined, logging table will be created in the same table

space as the original table. Own table space is recommended for easier monitoring of the table sizes of the logging tables

Replication Mode

• Replication can be executed in Real-time mode or in Scheduled mode

126

Procedure: Creating a New Configuration- Non-SAP

source system




yConfiguration Aspects

To replicate from non-SAP source

system select Legacy and the

affected database system.

Depending on the database system,

additional required information needs

to be specified (e.g. for DB2 specify

the DB connection and the tablespace name).

Start with transaction LTR

127

Procedure: User for Connection to SAP HANA System

SAP HANA System




yConfiguration Aspects

To connect to the HANA system and to create the

relevant objects, an user with the required privilegesneeds to be defined in the connection details for the

HANA system.

You can use user SYSTEM or any other HANA user

with the required system privileges:

See also SAP Note 1635735

128

Procedure: Change Password of HANA Schema Owner Configuration Aspects





It might be necessary to change the password of the schema owner of a target schema

handled by LT Replication Server. As the password is also stored in the in the databaseconnection in the SLT system, the password needs to be changed on both sides:

1.Stop replication jobs (that no jobs try to connect while password is changed.

2.Change the password in the HANA system.

3.Logon with the user. The initial password needs

to be changed again.

4.Change the password in the SLT

database connection.

The naming convention for the

database connection is:<MT ID>:R:R, e.g. 125:R:R

Naming convention for DB connection with user entered when creating the configuration: <MT ID>:R:C, e.g. 125:R:C

129

Procedure: Use of Advanced Role and Security ConceptConfiguration Aspects





Name Role Purpose

Data Provisioning <SCHEMA>_DATA_PROV Data provisioning - deploy replication orders

Power User <SCHEMA>_POWER_USER Power user - allow modif ication within the repl icat ion schema

User Admin <SCHEMA>_USER_ADMIN Can cal l the RS_GRANT_* and RS_REVOKE_* procedures

For each target schema, three roles are generated which can assigned to a user:

To assign or revoke individual authorities, there are also two respective procedures generated for each

target schema. To execute these procedures the user admin role must be assigned.

REPLICATION SCHEMA is the schema where the table is located that is subject to altering access rights.TABLE NAME is the name of the table in the schema. USER OR ROLE NAME is the name of the user or

role that shall be granted or revoked access. Use 'X' to grant / revoke a specific right, use ' ' to leave the

rights unchanged.

Granting Access Rights

SET SCHEMA <REPLICATION SCHEMA>;

CALL RS_GRANT_ACCESS('TABLE NAME','USER OR ROLE NAME','X', -- to grant SELECT'X', -- to grant INSERT

'X', -- to grant UPDATE'X') -- to grant DELETE

Revoking Access Rights

SET SCHEMA <REPLICATION SCHEMA>;

CALL RS_REVOKE_ACCESS('TABLE NAME','USER OR ROLE NAME','X', -- to revoke SELECT'X', -- to revoke INSERT

'X', -- to revoke UPDATE'X') -- to revoke DELETE

130

SummaryConfiguration Aspects






• Describe the definition of a configuration of SAP

LT replication Server

131



Monitoring of Replication

132

ObjectivesMonitoring of Replication






• Describe the monitoring dashboard

• understand the concept of Mass Transfer IDs

• Know how to use the IUUC Synchronization

Cockpit

133

Concept: Different Monitoring CapabilitiesMonitoring of Replication





Configuration & Monitoring Dashboard(Transaction: LTR)

• Issue with monitoring job

• Alert - trigger failures

• Basic statistics on replication time

Expert Functions

(Transaction: MWBMON, IUUC_SYNC_MON)• Check correct creation logging tables / triggers

• Review details on runtime and data throughput

• Analyze and identify replication errors using Application

log

•These are expert functions and should be used carefully!

It is planned to integrate LT monitoring features with the

monitoring for HANA that is part of SAP Solution

Manager, and the HANA Studio in the near future

134

Procedure: Status Monitoring – Configuration and

Monitoring Dashboard- SAP LT Replication Server





The status can be monitored in the Configuration and Monitoring Dashboard in the LT

Replication Server. The detailed monitor can be started by selecting an existingconfiguration in the Available Configurations overview. The status displayed in the overview

section is the most severe status derived from the detailed status information.

135

Procedure: Configuration and Monitoring Dashboard -

Details (1/4) - SAP LT Replication Server M i i f R li i





On the Jobs and Connections tab page, you get details about the status of the master job, the load jobs and

the connection details of all the involved systems.If the Master Job aborts (for example due to a restart of the LT Replication server), you can restart the

master job by choosing the relevant pushbutton.

The Load Jobs status shows the total number of available batch tasks in the LT Replication Server and also

the number of planned and currently running replication jobs for the current configuration. If there are no

tables to be processed, the status might be green even though no replication jobs are running.

In the Jobs Connections tab page,

you can view the current connection

status to the remote systems (sourcesystem and HANA System).

136


Details (2/4) - SAP LT Replication Server M it i f R li ti





On the Triggers tab page, you can view all tables for which a trigger issue might exist. A trigger issue

occurs if a trigger is dropped not using the LT Replication Server. Therefore LT replication server expectsthat a trigger is still active even though it was dropped.

When a new table is scheduled for replication there will be a warning message that the trigger is not yet

created. Note that this message should disappear after a few seconds when the trigger is active.

The Incomplete Tables section in the Trigger s tab page is empty if no trigger issues exist. This does not

mean that no triggers are active, as it only displays tables for which trigger issues exist.

137







On the Statistics tab page, you can view the current status of all relevant tables of the selected

configuration. You can view the Current Action and the Current Status.For all tables started in replication mode, and the initial replication of all data is completed, a latency is

calculated and also displayed here. The latency is the time difference between the change timestamp on

the source system and the commit timestamp in the HANA system. There are different latency figures

calculated for each replicated table:

Ensure that times are synchronizedbetween source system and the LT

replication server to get a correct latency

• Latency Med (all): Median of

all latency figures

• Latency Med (24h): Median ofthe latency figures from the last

24 hours

• Latency Min (24h): Minimum

latency within last 24 hours

• Latency Max (24h): Maximum

latency within last 24 hours

• Last Replication: Laps of time

since last replication

138







On the Properties tab page, the data entered when creating the configuration is displayed. If you switch to

the Edit mode some properties can be changed.The Number of Replay Jobs can be increased or decreased. In the properties tab also the maximum

number of jobs used for the Initial Load can be defined. The number of Initial Load Jobs defines how many

replication jobs can be used for initial load. Therefore this number cannot be higher than the total number of

replay jobs. It’s recommended to choose the number of Initial Load Jobs 1 number less then the number of

total jobs, so that there is at least one job reserved for delta replication.

The Tablespace Assignment can also

be changed but will only affect newly

created logging tables.

You can also switch the replication

mode between Real Time replication

and Scheduled replication.

In edit mode, the pushbutton Copy DB

Connection is active. This pushbutton

can be used to copy the database

connection to the HANA target system

into the source system (for examplefor a Suite Accelerator scenario).

139

Concept: Mass Transfer IDsMonitoring of Replication




g p

As the LT Replication Server

bases on existing LT basisfunctionalities, all technical expert

functions, monitor capabilities and

job names use a so called Mass

Transfer ID for selecting the

relevant configuration.

When creating a new

configuration schema in the LT

Replication Server, a Mass

Transfer ID (MT_ID) is created

and assigned to this configuration.

The numbering of mass transfer

ID will continuously increase on

the LT Replication server when

new configuration schemas are

defined.

The mass transfer ID of a

configuration schema is displayedas follows:

140

Concept: IUUC Synchronization CockpitMonitoring of Replication




g p

Internal monitoring tool called with transaction IUUC_SYNC_MON

• Administration -> General information

• Relevant Tables -> Information about replicated tables, log tables, and so on

• Processing Steps -> Obsolete, do not execute any function here

• MT Overview -> Information about runtime objects

• Application Logs -> Log information

• Runtime Information -> Not valid in LT Replication Scenario (-> MBWMON)

• Expert Functions -> Collection of Expert Functions

Enter mass transfer ID

to see the table details

141

Procedure: IUUC Synchronization Cockpit- Relevant

Tables (1/2)Monitoring of Replication





Double click on

a cell to define

the table filter

Name of loaded

or replicated

tables

Name of the

corresponding

logging table

Table Category

(Transparent,

Pool, Cluster)

Process Flag

for object

definition

Failed Flag

for object

definition

Replication forbidden = ‘X’

-> Load without replication

Trigger stateLogging

table

created

Only important columns are displayed here.

Other columns are hidden

Screen displays all processed

tables and their definition status

Process Option:

Complete = Initial Load

Delta = Delta Replication

Record Only = Delta Recording without Replication

142

Procedure: IUUC Synchronization Cockpit- Relevant

Tables (2/2)Monitoring of Replication





Double click on

a cell to define

the table filter

Name of loaded

or replicated

tables

Name of the

corresponding

logging table

Table Category

(Transparent,

Pool, Cluster)

Process Option:

Complete = Initial Load

Delta = Delta Replication

Record Only = Delta Recording without Replication

Process Flag

for object

definition

Failed Flag

for object

definition

Replication forbidden = ‘X’

-> Load without replication

Trigger stateLogging

table

created

Only important columns are displayed here.

Other columns are hidden

Screen displays all processed

tables and their definition status

Double click on

a cell to define

the table filter

Name of loaded

or replicated

tables

Table load

status. Tables in

replication mode

will permanentlyswitch from

loaded to not

loaded

Table Category

(Transparent,

Pool, Cluster)

Table State:

Err – Error occurred

Proc – Table currently in process

Def – Load / Replication Object defined

Gen – Load / Replication Runtime Objects generated

Calc – Access Plan calculated (for data load an table access plan is calculated)

Physical

Pool or

Cluster table

Process

Order for

Load / Repl.

Settings for

parallelization

of initial Load

Access Plan Type

Space = Standard

CAP = Parallel Proc.

Screen displays all processed tables

and their data load / replication status

143

Procedure: IUUC Synchronization Cockpit- Application

LogMonitoring of Replication





On the Application Logs tab page, you can view the logs of the executed definition and

replication tasks. You have to define a filter to view the logs.

We recommend that you only display the logs that contain

error messages. To do this, select the Only Important Ones

radio button in the filter definition dialog box.

144

Concept: Data Transfer Monitor Monitoring of Replication




Internal load / replication monitor called with transaction MWBMON

• Administration -> General information

• Relevant Tables -> Information about runtime objects

(same as MT Overview in IUUC_SYNC_MON)

• Steps -> Obsolete, do not execute any function here

• Application Logs -> Log information

• Runtime Information -> Runtime statistic of initial data load

• Activities -> Not relevant

• Expert Functions -> Collection of expert functions

Enter mass transfer ID

and execute

145

Procedure: Data Transfer Monitor- Runtime Information

for LoadMonitoring of Replication





Set Access Plan / Precalculation ID = 1

Name of loaded

or replicated

tables

Runtime information is initialized

for tables in delta replication

Portions: Total # of portions

Run: # of running portions

End: # of finished portionsErr: # of failed portions

Total number will increase

depending on the load type

Number of Calc. Records: Calculated

records to be transferred. Final number

only for reading type 1,4 & 5.For 3 number will increase

Number Records Read: Records read from

the source DB. After commit on HANA DB,

number match to the loaded records

Total Runtime

and detail runtime

for individualsteps

Calculated Size

of transferred

data (# of recordsx table width).

Does not reflect

the real DB size

146

Procedure: Data Transfer Monitor- Runtime Information

for Load - DetailsMonitoring of Replication





You can enter the detail view by double click on a table name

In this screen, the individual status for each load portion is displayed. Also the total runtime

and also the runtime for each individual step (for example to read the data) is displayed here

and gives a first indication about potential bottlenecks during the data transfer.

147

SummaryMonitoring of Replication





• Describe the monitoring dashboard

• understand the concept of Mass Transfer IDs

• Know how to use the IUUC Synchronization

Cockpit

148



Accelerated Load Procedures

149

Objectives Accelerated Load Procedures





• Describe the different reading types to accelerate

laod procedures

• know how to change default reading type of a

table

150

Concept: Different Options for Initial Load available Accelerated Load Procedures




There are different options available for the initial load. Each option is assigned to

a reading type. The reading types differ in the way the access the source table:

Reading Type 1: Access Plan Calculation – Range calculation based on a

selective field

Reading Type 2: Not relevant

Reading Type 3: DB_SETGET – Data transfer ordered by primary key

(default reading type) Reading Type 4: Index Cluster – Extracting data in a cluster like table

Reading Type 5: Index Cluster with full table scan – Same as reading type 4

using a full tablespace hint

151

Concept: Reading Type 1 – Access Plan Calculation-

ExampleAccelerated Load Procedures




Accelerated Load Procedures

When using the Access Plan Calculation reading type, the source table is divided into ranges

using a single key field. Every range represents a data portion and will be processed in theinitial load.

In this example we use key field KEY_3 for the range calculation:

KEY_1 KEY_2 KEY_3 DATA

100 2500 1000000120 Document 1

100 3750 1000000127 Document 8

100 8000 1000000123 Document 4100 8000 1000000125 Document 6

200 2500 1000000122 Document 3

200 2500 1000000124 Document 5

200 8000 1000000121 Document 2

200 8000 1000000126 Document 7

Portion Range

1 KEY_3 <= 1000000121

2 KEY_3 > 1000000121KEY_3 <= 1000000123

3KEY_3 > 1000000123

KEY_3 <= 1000000125

4 KEY_3 > 1000000125

Range

Calculation

If the first key field cannot be used for range calculation, a separate index on the respective key field isrequired. The index must contain the key field only used for the range calculation.

In case of a cross client load (the default setting) most times a separate index is required. In a client-

specific load, the second key field can be used without creating a separate index for the table.

152

Concept: Type 3 – DB_SETGET- Example Accelerated Load Procedures




The reading type DB_SETGET uses a basis function to read the records of the source table

ordered by the primary key. Therefore no additional index is required as primary index is used.The function returns a bunch of records (default 10.000 records). In this example , two records

are returned in one portion:


100 2500 1000000120 Document 1

100 3750 1000000127 Document 8

100 8000 1000000123 Document 4

100 8000 1000000125 Document 6

200 2500 1000000122 Document 3

200 2500 1000000124 Document 5

200 8000 1000000121 Document 2

200 8000 1000000126 Document 7

As no range calculation is required for this reading type, data load can start immediately. But datacannot be processed in parallel jobs.

If at least DMIS 2010 SP6 (or DMIS 2011 SP1) is installed on all systems, this reading also starts a

range calculation based on the primary key to enable parallel load.

Portion 1

Portion 2

Portion 3

Portion 4

153

Concept: Reading Type 4 & 5 – Index Cluster - Example Accelerated Load Procedures




The reading type index cluster reads the data from the source table and stores it in a

cluster like table (DMC_INDXCL) on the source system. All rows are read from thesource table, divided into portions and compressed in a raw format


100 2500 1000000120 Document 1

100 3750 1000000127 Document 8

100 8000 1000000123 Document 4

100 8000 1000000125 Document 6

200 2500 1000000122 Document 3

200 2500 1000000124 Document 5

200 8000 1000000121 Document 2

200 8000 1000000126 Document 7

As data is extracted in a separate table on the source system, additional table space is required for table

DMC_INDXCL. The tables can be compressed by a factor of 10 (less for cluster tables).

Both reading types read the data without any sort order (good for cluster tables where in case of a sort orderall data needs to be extracted and sorted before). Reading type 5 adds a full table scan hint to enforce the

data base to extract the data with a full table scan. Reading type 4 should be used for cluster tables and

GUID key tables. For all other table reading type 5 should be used

CLUSTER ID DATA

000001 0372DC93A1713B5F1AE50DAB…

000002 278D476A02E4EB60F527DD763…

000003 BDB52E893A9C0C27B5A277C3…

000004 5C8649E8822E5495D01B4A9A7…

154

Concept: Reading Types- Advantages and

Disadvantages Accelerated Load Procedures




cce e a ed oad ocedu es

Reading Type Advantages Disadvantages

1 – Access Plan

Calculation

Fast data load if index exists

Parallel data load possible

Additional index may be required

Requires key field which is

sufficiently selective

Calculation required before load

3 – DB_SETGET No separate index required No parallelization possible

(until DMIS 2010 SP6 / DMIS

2011 SP1)

Additional consumption of database

buffer

4 & 5 – Index Cluster Very fast data load after data

is extracted to table

DMC_INDXCL

Minimal usage of DB buffer

Additional table space temporarily

required on the source system

155

Procedure: Change default reading type Accelerated Load Procedures




The default reading type 3 can be changed for each table individually. A corresponding entry

in table IUUC_PERF_OPTION needs to be entered before the load or replication is started.

Enter Mass Transfer ID

and table name

Number of parallel jobsused for load

Define Reading Type

Key field used range

calculation (only relevant

for reading type 1)

Table can be maintained

in transaction SM30

156

Procedure: Reading Type 1 -Search for selective field Accelerated Load Procedures




To identify which field can be used for range calculation, transaction DB05 can

be used to analyze the distinct values of a table.

For huge tables the analyze should be started in a background task. The result is

stored in the spool of background job TABLE_ANALYSIS_<table name>.

157

Summary Accelerated Load Procedures





• Describe the different reading types to accelerate

laod procedures

• know how to change default reading type of a

table

158



Other Operations Aspects

159

ObjectivesOther Operations Aspects





• Know how to manager structural changes on

replicated tables

• Understand the Backup and Recovery Strategy

• Describe the concept of data volumemanagement

160

Concept: Software Maintenance Activities in Source

System - General ConsiderationsOther Operations Aspects




Software maintenance in the source system can affect tables in replication and care must be

taken to ensure that replication can continue after maintenance events.

Maintenance events that affect structures of tables (key fields or non-key fields) in

replication need to be identified prior to the maintenance event to ensure that replication can

continue after the maintenance. These structure changes must be identified (in the transport

requests) manually, as there are no predictive or comparison tools between the source

system and HANA database for this purpose.

General Procedure• Request transport owner to identify any dictionary change of replicated tables

• Apply software maintenance or import transports in the test system first to identify the

impact of replicated tables

• Take any necessary actions depending on the dictionary changes of replicated tables (see

following sections)

• Resume the replication after the maintenance event or transports

161

Concept: Structural Changes on a replicated TableOther Operations Aspects




When the replication process begins for a table, a database trigger is activated for that

table. As soon as the database trigger is active, the data dictionary blocks any structuralchanges for that table. Therefore the table activation is cancelled if a trigger is active and

table structure was changed:

Also a transport containing structural changes for a table where a trigger is active will end

with an error in the ABAP Dictionary Activation step.

162

Procedure: Delete DB triggers Using Data Provisioning

UIOther Operations Aspects




To be able to activate the structural changes, database triggers have to be deactivated for the

relevant tables. We recommend that you delete the triggers by stopping the replication in theHANA system.

If for any reason deletion of the trigger via HANA Studio is not possible, triggers can be

deleted via transaction IUUC_REMOTE in the source system or directly on the database(see note 1620618). If triggers are dropped in the source system without using data

provisioning UI, replication should be stop via HANA studio afterwards to get a consistent

table status (and be able to start it again).

163

Procedure: Structural Changes on A Replicated Table -

Repeat activationOther Operations Aspects




Once the triggers are removed, the structure change for the relevant table can be activated in

the data dictionary.

In case of a transport, the import can continue now.

164

Procedure: Restart Replication - Recommended processOther Operations Aspects




To adapt the structure change in the HANA database and to setup the replication for the

affected tables again, we recommend that you start the replication again. The LT replicationserver will drop the table in the HANA system, creates it again with the new structure and

loads the data again from the source system.

Reloading the table again ensures data consistency but may be critical if huge tables are

adjusted. There is an alternative expert function to avoid the reload if some prerequisites are

fulfilled (see next slide).

165

Procedure: Restart Replication - Expert modeOther Operations Aspects




As action M and Q are not supported by

the Data Provisioning UI, you will get

an error in the UI as long as the last

action in status table is either M or Q.

1. If the table changes are executed during system downtime, and it is ensured that no user or

program will change any data while triggers are not active, the replication can be resumed withoutrepeating the initial load.

2. To resume the replication of a stopped table without repeating the initial load, the action M (activate

delta recording) and Q (start replication without initial load) can be used. As both actions are not

available via the Data Provisioning UI, the action have to be trigger via an insert in table

RS_ORDER in the respective HANA schema:

3. 1. Activate delta recording (trigger) on source table – Action M:

4.

5. 2. Continue with Replication (without Load) – Action Q:

6. Check the status of action M and Q in table “RS_STATUS”:

Activate delta recording (Action M):

Status: O (Scheduled) -> P (in Process) -> X (Executed)

Continue Recording (Action Q):

Status: O (Scheduled) -> P (in Process) -> X (Executed)

Replication in Process

(switches automatically if first record is replicated)

166

Concept: Backup and Recovery Strategy (1/2)- General

RecommendationsOther Operations Aspects




Backup your system landscape regularly to ensure that you can

restore and recover it in case of system outages or other failures.

The backup and restore strategy for SLT system consists of two parts:

• Back-p and restore coverage for each component (see details on

next slide)

• Cross-system data dependencies and handling

The backup and recovery strategy for your system landscape should

not only consider SAP systems but should also be embedded in overall

business requirements and incorporate your company’s entire process

flow.

In addition, the backup and recovery strategy must cover disaster

recovery processes. It is important that you ensure that backup

devices are not lost together with normal data storage (separation of

storage locations).

167

Concept: Backup and Recovery Strategy (2/2)-

Different Failure ScenariosOther Operations Aspects




Situation Consequences Action

Source system goes down Replication is stopped

SLT waits for source system to

be available again

Restart source system

SLT will continue

automatically where it

stopped

SLT system goes down

(or source + SLT system if

in the same stack)

Replication is stopped Restart SLT system

Restart master job (via

transaction LTR) to

continue replication

SAP HANA system goes

down

Replication is stopped

SLT waits for HANA system to

be available again

Restart HANA system

SLT will continue

automatically where it

stopped

If the source system or HANA system cannot be recovered, tables have to be dropped and

loaded into the HANA system to ensure that both systems are in synch again. Thereforereplication needs to be stopped and restarted for all tables.

168

Concept: Data Volume Management (1/2)Other Operations Aspects




1. Source system(s):

• SLT related logging tables: The size of logging tables may increase in size, in case the replication is

suspended for a longer time and/or there is a system outage of the system of the SLT system or the

SAP HANA system. You should monitor the table space size (assuming logging table have been

assigned to separate tablespace) carefully and take appropriate action early enough.

• RFC logging: Since data replication from SAP sources is management by RFC connection, related size

of log files should be reviewed. Especially, if performance improvements are implemented that will

increase the number of jobs for initial load / replication, check if RFC related logging is critical.

2. SLT system:

• Since the data transfer – managed in dedicated portions of data records - during the replication process

is handled by the memory of the SLT system, there are no specific data volume issues to be

considered.

• In case of system (source and/or SAP HANA system) or network outages, the replication process will

generate logging information for related failures.

• To avoid that unnecessary logging information are stored, you can pause the replication by stopping theschema-related jobs.

Data Volume Management should not be a critical topic, however the

following considerations apply:

169

Concept: Data Volume Management (2/2)Other Operations Aspects




3. SAP HANA system: Depending on the number of tables that have the status In Replication

(or initially loaded only) and the growth rate of tables in the source system, the size of theHANA database will increase accordingly.

Note:

Consider that the SAP HANA database is supports compression rates – therefore the table size in the SAP

HANA database may be different to source system.

If the table size (in the SAP HANA database) exceeds 2 billion records, you must split the table by using the

available partitioning features.

170

SummaryOther Operations Aspects





• Know how to manager structural changes on

replicated tables

• Understand the Backup and Recovery Strategy

• Describe the concept of data volumemanagement

171



Configuring Data Replication with SAP

BusinessObjects Data Services

172

Configuring Data Replication with SAP BusinessObjects

Data Services





• Configure SAP BusinessObjects Data Services for Metadata

Import

• Configure SAP HANA Studio for Metadata Import

• Import Metadata via Data Services into SAP HANA

• Load Data via Data Services into SAP HANA

At the end of this lesson you should be able to:

173

Configure SAP BusinessObjects Data Services






• Start Central Management Console on server wdflbmt2287:6400

• Log on with user train-00/train-00

• Select “Applications” in the manage area

• Select “Data Services Application” from application list

• Check if the Encryption Passphrase is set, if not set one.

• Select “Server” from navigation drop-down list• Navigate to view Server Status = Running

• Check if the Enterprise Information Management Adaptive Processing

Server is running, then restart this server

174






Create SAP HANA Datastore in Data Services

•Start Data Services Designer •Log on using server wdflbmt2287:6400 with user train-00/train-00

•Use local Repository DSREPO00

•Go to Datastore tab in Local Object Repository

•Open context menu (right mouse click) and choose “New”

•Create new Datastore using the following properties:

•Datastore name: DS_HANA00•Datastore type: Database

•Database type: HANA

•Database version: HANA 1.x

•Data Source: HANA_H00

•User Name: STUDENT00

•Password: Training1•Click on button “OK”

175

Create SAP ERP Datastore in Data Services





Create SAP ERP Datastore in Data Services

The Solution Manager system RWS is used as the source system instead of anERP system.•Start Data Services Designer

•Log on using server wdflbmt2287:6400 with user train-00/train-00


•Go to Datastore tab in Local Object Repository

•Open context menu (right mouse click) and choose “New”

•Create new Datastore using the following properties:Datastore name: DS_ERP

Datastore type: SAP Applications

Application server: WDFLBMT2263

User/password: prep-user/welcome

•Click on button “Advanced”

•Edit the following properties:Client number: 200

System number: 14Number of connection retries: 1

•Click on button “OK”

176

Configure SAP HANA Studio






•Start SAP HANA Studio•Navigate to Information Modeler Perspective

•Open Quick Launch View

•Select ”Configure Import Server”

•Type in the following properties for Import Server:Server Address: wdflbmt2287.wdf.sap.corp

Repository Name: DSREPO00

ODBC Data Source: DS_HANA00

177

Import Metadata 1/2





Import Metadata

•Start SAP HANA Studio•Navigate to Information Modeler Perspective

•Open Quick Launch View

•Select “Import“

•Select as Import Source: Modeler Source Objects

•Click “Next”

•Select as target: HANA H00(STUDENT00)

Assumption: SAP HANA H00(STUDENT00) have been configured before•Click “Next”

•Select as Source Connection: DS_ERP

•Select as object for import: Tables

•Click “Next”

•Search for table “T005”

•Select table “T005” and click button “Add”

178

Import Metadata 2/2





Import Metadata

•Select as target schema: STUDENT00•Click “Next”

•Click on button “Validate”

•Click “Next”

•Click “Finish”

•Go to Navigator pane in SAP HANA Studio

•Navigate to schema H00 Catalog STUDENT00 Tables

•Check if table “T005” was imported•Open Definition for table “T005” via context menu

•Open Data Preview for table “T005” via context menu

179

Load Data 1/3





Load Data

•Start Data Services Designer •Log on using server wdflbmt2287:6400 with user train-00/train-00


•Create new project “TZHANA” via menu Project New Project

•Go to Project Area Pane and select Project “TZHANA”

•Create new Batch Job “Job_ERP2HANA_T005” via context menu

•Open Batch Job “Job_ERP2HANA_T005” in workspace via double-click

•Create new Data Flow “DF_ERP2HANA_T005” by selecting the Data Flow Iconin the left toolbar (one click) and clicking in the empty workspace.

•Open Data Flow “DF_ERP2HANA_T005” in workspace via double-click

•Go to Datastore tab in Local Object Library

•Expand Datastore “DS_ERP”

•Open context menu for node “Tables” and choose commend “Import by name”

•Type in “T005” and click on button “Import”

• Add the imported ERP-Table “T005” as source table via drag-and-drop to theworkspace

180

Load Data 2/3





Load Data

•Go to Datastore tab in Local Object Library•Expand Datastore “DS_HANA00”

•Open context menu for node “Tables” and choose commend “Import by name”

•Type in “T005” and click on button “Import”

• Add the imported HANA-Table “T005” as target via drag-and-drop to the

workspace

• Add a Query-Transform by selecting the Query Icon in the left toolbar (one click)

and clicking in the workspace.•Connect the Source Table – the ERP-Table “T005” – with the Query-Transform

and then the Query-Transform with the target table – the HANA-Table “T005”

•Open the Query-Transform via double-click

•Map source fields with target fields by mark one source field and pull it via drag-

and-drop over the corresponding target field – repeat that for all fields.

•Close Query-Transform

•Validate Data Flow via menu Validation Validate All Objects in View

181

Load Data 3/3





Load Data

•Go to Project Area Pane and select Batch Job “Job_ERP2HANA_T005”•Open context menu for Batch Job “Job_ERP2HANA_T005” and choose

“Execute”

•Start Batch Job by clicking on button “OK”

•Follow the Job Log which opens automatically and change view between Trace

Log, Monitor Log and if necessary Error Log

• After successful job execution go to SAP HANA Studio and open the Data

Preview for Table “T005” again.

182

Configuring Data Replication with SAP BusinessObjects Data

Services





• Configure SAP BusinessObjects Data Services for Metadata

Import




183



Appendix

184



APPENDIX A

Software Download

185

Procedure: Software Download for Add-on DMIS 2010Software Download




Download DMIS_2010 from the following path:

http://service.sap.com/swdc Installations and Upgrades A-Z SAP HANA Enterprise SAP

HANA Enterprise Installation DMIS 2010 for SAP HANA ENTERPRISE 1.0

Apply on SAP source and

SLT system. Follow the

DMIS_2010 installation

procedure as described in

SAP Note 1468391

186

Procedure: Support packages for Add-on DMIS 2010Software Download




Download latest available support packages from the following path:

http://service.sap.com/swdc Support Packages and Patches A-Z SAP HANA Enterprise

Comprised Software Component Versions relevant DMIS Add-on Support Packages

Apply on top of DMIS2010 in

SAP source and SLT

system

187

Procedure: Software Download for SAP Kernel 7.20EXTSoftware Download




The system hosting the SAP LT Replication Server must be an SAP system with SAP NetWeaver 7.02 ABAP

stack using SAP Kernel 7.20EXT (64BIT Unicode).

Note: The patch level for the secondary database connections (HDB DBSL) to the SAP HANA system needs

to be at least patch level 110 - see SAP Note 1597627.

Download the kernel version from the following path:

http://service.sap.com/swdc Support Packages and Patches A-Z SAP HANA Enterprise

Comprised Software Component Versions SAP KERNEL 7.20 EXT 64-BIT UC

Apply appropriate SAP kernel

version and patch level 110 for

secondary database

connection to SAP HANA as

described in SAP Note

1597627.

188



Appendix B

Trouble Shooting

189

Concept: Create New Configuration- Possible Issues (1/2)Trouble Shooting




SymptomWhen creating a new schema in SLT system, you get the error message “Error when connecting to Source

system” in the WebDynpro.

Possible reasons1. Missing add-on DMIS_2010 in your source system.

Ensure that you have installed the required add-on DMIS_2010 in your source system . See SAP Note

1468391 for further information.

2. Missing proper roles for the RFC user

In the system log (SM21) and ABAP dump (ST22), both indicated that “RFC_NO_AUTHORIZATION” erroroccurred. Logon to the source system and check if role SAP_IUUC_REPL_REMOTE assigned to the RFC

user. Assign the role if it is not assigned yet.

3. Roles are not generated properly

If the roles are assigned correctly to the RFC user, but still get the error, you might have not generated the

roles properly. The role should have a green traffic light on the tab pages Authorization and User . In case of

yellow light on those tabs, generate the roles and / or execute the user comparison.

4. DDIC user is used for RFC communication

You cannot use user DDIC for RFC connection between source system and SLT.

190

Concept: Create New Configuration- Possible Issues (2/2)Trouble Shooting




SymptomWhen creating a new schema in SLT system, you get the error message “Error when creating SYS_REPL

schema” or “Error while connecting to HANA system” in the WebDynpro.

Possible reasons1. HANA DBSL is not installed or DB client software path not specified in OS environment

If you get this error, check the work process log if following error is displayed:

Refer to Note 1597627 to install the HANA DBSL in your system.

2. DB client software is outdated

If you get this error, check the work process log if following error is displayed:

Update DB client software. See SAP Note 1603671 for further information.

3. Logon credential for HANA system is not correct

If the logon information is not set correctly, you will also get this error. Check the logon information when you

create a new schema.

191





(SBO DS)

192

Objectives




Configuring Data Replication with SAP BusinessObjects Data Services


Describe the cooperation of SAP HANA and SAP BusinessObjects Data

Services

Configure SAP BusinessObjects Data Services for Metadata Import

Configure SAP HANA Studio for Metadata Import

Import Metadata via Data Services into SAP HANA Load Data via Data Services into SAP HANA

193

Agenda




SAP BusinessObjects Data Services 4 and SAP HANA

SAP BusinessObjects Data Services 4 Architecture

Configure SAP BusinessObjects Data Services 4


Import Metadata into SAP HANA

Load Data into SAP HANA

Exercise

194


Metadata




SAP

ERP

Any Source

BW

Data Load

Metadata

Repository Server

Open Hub

SAP BusinessObjects

Data Services 4.0HANA

Designer and

Management

Console

Data Services is the engine to load data into HANA DB

Modeler will use Data Services to browse and ‘import’ external metadata

Modeler can generate initial data flows load data into NewDB tables Further modifications to data flows have to be done via Data Services Designer

Jobs for loading data into SAP HANA have to be created via Designer as well

195

Agenda





SAP BusinessObjects Data Services 4 Architecture


Configure SAP HANA



Exercise

196

SAP BusinessObjects Data Services 4

Architecture




Designer (Windows) Administrator (Web)

Job Server and EngineHeterogeneousData Sources

Heterogeneous

Data Targets

Web Applications

LocalRepository

CentralRepository

Dictionaries

+ Directories

ProfilerRepository

Request-Response

Access Server

Real-time

Services

Required only for

Data Quality

Management

Repositories can be stored

on supported database platforms

197

SAP BusinessObjects Data Services 4

Architecture / Components




CMSDatabase Server

(DB2 Community Edition,MS SQL Server Express

or Other)

Application

Server (Tomcat or other)

CMC

CMS Repository

APS AJS

File InputRepo

File OutputRepo

SAP BusinessObjects

Information Platform Services

or Business IntelligencePlatform

SAP

BusinessObjects

Data Services

DS ManagementConsole

DS local repo

Job Server

Access Server

Designer

Message ClientLib

EIM APS

RFCServer

View DataMetadataBrowse

AdminService

DS InfoObjects

SAP Business Objects

Data Services uses SAP

Business ObjectsEnterprise Platform

198

Agenda





SAP BusinessObjects Data Services 4 Architecture Configure SAP BusinessObjects Data Services 4

Configure SAP HANA



Exercise

199





Required steps for configuring SAP BusinessObjects Data Services Meta

Data and View Data Services to be used by SAP HANA Studio


Logon to the SAP Business Objects Enterprise CMC (Central Management Console) with

an user having “Administrator” privileges

Set the “Encryption passphrase” to allow to be used for encryption purposes by Metadata

Browsing and View Data Services

Restart the EIM Adaptive Processing Server containing the Metadata Browsing and View

Data Services so that the encryption passphrase becomes effective

Logon to Data Services Management Console with an user having having “Administrator”

privileges

Adjust Session Security setting for Web Service “Import_Repo_Object”

Install SAP HANA ODBC driver on Data Services server component – and if needed on

Data Services clients Configure SAP HANA ODBC Connection

200


Logon to Central Management Console




Logon to the BOE CentralManagement Console with an user

having “Administrator” privileges

201


Adjust application settings for “Data Services” 1/3




Enter the application management area

via the quick link on the CMC Home

page or via the drop-down menu

202






Enter the Data Services Application

Management area

203






Setting the encryption passphrase for using Metadata

Browsing and View Data Services not only affects the

SAP In-Memory Computing Studio also all other

applications using this service

204


Enter the server management area




Enter the Server management area be

one of the quick links or via the drop

down menu

205


Restart the EIMAdaptiveProcessingServer




Restart the

EIMAdaptiveProcessingServer (right

mouse Restart Server

1.

2.

3.

4.

206


Status monitoring of the server process




Status transition of the server process

until the status “running” is reached

2.

1.

207


Logon to Data Services Management Console




Logon to the Data Services

Management Console with an user

having “Administrator” privileges

208


Start Administrator




Choose Administrator

209


Adjust Web Services settings




Choose Web Services

210






Choose Web Services Configuration

211






1. Select Web Service “Import_Repo_Object”

2. Select “Disable Session Security” from

drop-down menu and choose “Apply”

212


Install the SAP HANA ODBC driver

The server / host on which SAP BusinessObjects Data Services 4 0 is




The server / host on which SAP BusinessObjects Data Services 4.0 is

installed requires the SAP HANA ODBC drivers in order to be able toconnect. The subsequent steps are required:

Install HANA 1.0 ODBC driver (64bit version required for Windows or Linux server

platform)

Execute “hdbinst –a client” via command line from the HANA installation directory

Add an ODBC DataSource via the respective administration tool

– Use “odbcad32.exe” on Windows 64bit platform to add a ODBC DataSource (User orSystem DataSource)

– Use unixODBC on Linux platform to add a ODBC DataSource

Logon via the Data Services Designer, create a new Datastore of type HANA, test the

connectivity and add it to the respective repository

213

Configure an SAP HANA ODBC Connection on Windows

Create a new HANA Datastore in Data Services




214

Configure an SAP HANA ODBC Connection on Windows

Add an ODBC Data Source via the Administration tool




<host>:3<Instance#>15

1.2.

3.

215

Agenda










Exercise

216







Data and View Data Services to be used by SAP HANA Studio


Enter the Information Modeler perspective and configure the Import Server to

communicate with SAP Data Services’ Metadata Browsing and View Data Services

capabilities

217

Configure an SAP HANA Studio

Configure Import Server




Configure Import Server to

communicate with Data Services

218

Configure an SAP HANA Studio

Configure Import Server

Required parameters




Required parameters

Server Address – Address of the host having

IPS or BOE installed together with

Data Services’ Metadata Browsing

and View Data services

Repository Name

– Name of the local Data Services

repository wherein connectivityinformation is stored and

where job should be created

ODBC Data Source

– If maintained with the target Datastore,

Information Modeler builds Data Services

dataflows when importing an extractor

within the respective repository

219

Agenda







ConfigureSAP HANA Studio



Exercise

220


Required steps for importing Metadata via SAP BusinessObjects Data




Required steps for importing Metadata via SAP BusinessObjects Data

Services Meta Data and View Data Services to be used by SAP HANA Studio

SAP BusinessObjects Data Services

Source Datastore should be configured first in the linked Data Services Repository

SAP HANA Studio

Enter the Information Modeler perspective and start the Import wizard

Additional Information

Currently the Import Wizard only supports SAP ERP Systems as source systems for

Metadata Import

221


Start Import Wizard




Click “Import” to import meta data via DataServices or use the menu

222


Importing Metadata from an ERP System

Select the import of “Source Objects”




Select the import of “Source Objects”

into a connected target system

1.

2.

223


Choose one of the maintained connections

Connections of Datastore type “SAP




Connections of Datastore type SAP

Applications” are imported from thespecified DataServices repository

Relation to

Data Services Designer

224


Select Objects for import - Search vs. hierarchy drill-down

There are two possibilities to select objects for import




p j p

Search for objects via the direct input field Use applications hierarchy to drill down to a certain table

225


Select target schema for the metadata import




“RKT” catalog in

In-Memory

Computing

Engine empty

226


Validate the target structure




Validate the target

structure

1.

2.

227


View the newly created target structure




Table creation status in

the deployment log

Refresh the Tables sectionin the “RKT” catalog and

double click the table to

see the structure

1.

2.

3.

228


Import the created table structure into Data Services

For modeling of jobs and data flows within SAP Business Objects Data Services the created




table structure needs to be imported. The subsequent steps are necessary:

229

Agenda






Configure SAP HANA



Exercise

230


For creating and executing a simple Data Services job with a 1:1 transfer from a




source SAP ERP system to the target SAP HANA system, the following steps arerequired:

Create a new batch job within Data Services (this is the high-level executable to be started

on the fly in Data Services or to be scheduled on a regular basis)

Create a new data flow, containing the source table from the SAP ERP system, a query

object realizing a basic 1:1 mapping and the target table which already exists within the

HANA system

Execute the created Data Services job and preview the records with the in SAP HANAStudio

231


Create new DS Job and data flow with simple 1:1 mapping

Create a simple job and dataflow with a 1:1




Create a simple job and dataflow with a 1:1

mapping from the SAP EPR source table tothe HANA target

Simple 1:1 query object

ABAP dataflow recommended for large data sets

232


Execute the job and monitor the load




Monitor load progress

233


View the uploaded data within the SAP HANA Studio




234


SAP HANA as target in Data Services

Additional Information on content enhancements in

SAP B i Obj t D t S i 4 0 SP02




SAP BusinessObjects Data Services 4.0 SP02

Support of specific SAP HANA table types

When using Template Tables in Data Services the table type column store and row store

can be chosen.

Bulk loading in SAP HANA

Bulk loading performance and flexibility was improved, but can only be used in all

combinations of product versions

The following combinations of product versions should be used:

– SAP HANA SP02 with SAP BusinessObjects Data Services 4.0 SP01

– SAP HANA SP03 with SAP BusinessObjects Data Services 4.0 SP02 up to 10x faster

235

Agenda






Configure SAP HANA



Exercise

236

Exercise


B i Obj t D t S i





237

Summary





• Describe the cooperation of SAP HANA and SAP BusinessObjects Data

Services

• Configure SAP BusinessObjects Data Services for Metadata Import




238




239


L 1 St ti d St i SAP HANA





Lesson 1: Starting and Stopping SAP HANA

Lesson 2: Configuring SAP HANA DB

Lesson 3: Backup and Recovery SAP HANA

Lesson 4: Maintaining Users and Authorizations

240

Unit Objectives

After completing this unit, you will be able to understand:

HANAAdministration Starting & Stopping HANA




HANA Administration: Starting & Stopping HANA

HANA Backup and Recovery

HANA Security

241



Starting and Stopping SAP HANA

242

Objectives





p g , y

Start & Stop SAP HANA

243

Stop and Starting SAP HANA Database

Stopping SAP HANA database




• Using sapcontrol as root/usr/sap/hostctrl/exe/sapcontrol -nr <Instance_Number> –function Stop

• Using HDB as <sapsid>adm/usr/sap/<SAPSID>/<Instance_Name>/HDB stop

Starting SAP HANA database

• Using sapcontrol as root/usr/sap/hostctrl/exe/sapcontrol -nr <Instance_Number> –function Start

• Using HDB as <sapsid>adm/usr/sap/<SAPSID>/<Instance_Name>/HDB start

244

Displaying the Process List

Displaying process list at command line




• Log on to Linux command line as root/usr/sap/hostctrl/exe/sapcontrol -nr <instancenr> -functionGetProcessList

Displaying Process list in GUI

• You can also use SAP Microsoft Management console (SAP MMC) from

Windows PC to display SAP HANA process list

245

Logging on to the SAP HANA System

Logging on to the SAP HANA system using SAP HANA Studio




Launch SAP HANA Studio on your PC Open the “Administration Console perspective”

On the right hand Navigator pane right-click and select “Add System”

Enter required parameters, hostname, instance number and SAP system ID

Choose Authentication by database user” and enter SYSTEM for “User Name”

Enter the master password your set during installation

You see your newly installed SAP HANA system in the “Navigator” view

246


The SUM uses a key pair for HTTPS connections to host agent, and another

key pair for accepting connection from user PC (to update Uses’ Studio)




key pair for accepting connection from user PC (to update Uses Studio)

The following diagram shows the key pair usage

247


The following steps need to be done on each SAP HANA Studio installation

where the SAP HANA Update UI will be used




where the SAP HANA Update UI will be used

• Copy the server certificate sumforhana.cer from

/usr/sap/<SID>/SUM/config/sumforhana.cer to the host where the

SAPHANA Studio is installed.

• Run the following command from the directory where you have copiedsumforhana.cer:

keytool -importcert -keystore"<JRE_DIR>\lib\security\cacerts" -alias

sumforhana_$<hostname>_$<SAPSID> -file sumforhana.cer

• Restart the SAP HANA Studio

248


Prerequisite




You have configured SUM for SAP HANA as previous step.

Procedure

Log on to SAP HANA system using SAP HANA Studio

Use the “Lifecycle Management Perspective” in the SAP HANA studio to update your

system.

249


By default the SAP HANA database is configured that it is not started

automatically when the SAP HANA host is rebooted, to enable auto start




automatically when the SAP HANA host is rebooted, to enable auto start

• Log on to the SAP HANA host as a user with root equivalent authorization

• Change to the system profile directory //usr usr/sap/<SAPSID>/SYS/profile/sap/<SAPSID>/SYS/profile

• Edit the <SAPSID>_HDB<<SAPSID>_HDB<Instance_NoInstance_No>_<>_<host_namehost_name>> profile

• Change the parameter setting Autostart Autostart = 0= 0 to Autostart Autostart = 1= 1

• Save the profile <SAPSID>_HDB<<SAPSID>_HDB<Instance_NoInstance_No>_<>_<host_namehost_name>>

The SAP HANA database will start automatically next time SAP HANA host

is rebooted

250

Monitoring the SAP HANA System landscape

Perform regular system monitoring task




Check the system status on the Overview tab page of the Administration screen in the“Administrative Perspective”, for important system information

Overall system state

General system information (software version, etc)

Warnings (generated by statistics server which is a monitoring tool for the db)

System resources on the bar view (available memory, CPU and storage space)

Services (preprocessor, name server, index server for each host; the statistic server runson each host but only the one on master server is actually running)

Diagnosis Files shows server side logs

251

Summary




You should now be able to: Start and stop SAP HANA system

Display the process list

Logon to the SAP HANA system

Configure the SUM for SAP HANA

Apply updates and support packages

Enable automatic start of the SAP HANA database

Monitor the SAP HANA system landscape

252



Configuring SAP HANA DB

253

Objectives

After completing this lesson, you will be able to configure SAP HANA




database using: SAP HANA Studio

254

Configure SAP HANA DatabaseUsing SAP HANA Studio

You administrate the SAP HANA database using the administration console of the

SAP HANA studio.




The administration console of the SAP HANA studio allows technical users to

manage the SAP HANA database as well as to create and manage user

authorizations.

Details of configuration can be found in SAP HANA Database Administration Guide.

255

Configure SAP HANA DatabaseExample of Parameters

Configuring Automatic Updates




Configuring the Administration Console

Organizing System Landscapes

Configuring Security Logging and Tracing

User Management

System Configuration

Periodic Administration Tasks

DBA Cockpit

256

Configure SAP HANA DatabaseExample: System Configuration Parameters

Setting the global allocation limit parameter




The global_allocation_limit is used to limit the amount of memory which can be used by the database. Thevalue is the maximum allocation limit in MB. A missing entry or a value of 0 results in the system using the

default settings (that is, 90% of the physical memory or physical memory minus 1GB in case of small

physical memory). This limit is only displayed on the Configuration tab.

Procedure

1. Open the Administration Editor by choosing in the navigator toolbar.

2. Open the Configuration tab page.

3. Open the global.ini parameter group.4. Open the memorymanager section.

5. Choose Change in the context menu for global_allocation_limit . Change Configuration Value dialog box

for global_allocation_limit is displayed. There are two parts to the dialog box which enable you to set this

parameter for the entire SYSTEM and for an individual HOST. If it is set for SYSTEM, the value is used

for each host. For example, if you have 5 hosts and set the limit to 5 GB, the database can to use up to 5

GB on each host (25 GB in total). You can additionally set the value for a specific HOST. For that host

the specific value is used and the SYSTEM-value is used for all other hosts.

6. Enter the values in the New Value fields (for the SYSTEM and HOST, if required) and choose Save.

257

Configure SAP HANA DatabaseExample: Monitoring the System State Parameters

Monitoring the System State




The Administration Editor provides several tabs that display the most important systeminformation.

To open the Administration Editor, choose in the toolbar of the navigator.

The header of the Administration Editor contains the following information:

• System Name, which is defined during system installation.

• The comment in parentheses () is defined when the system is added to the navigator.

• The hostname of the system host.

• The system instance number.

• The time when the tab you are viewing was last refreshed.

• The manual refresh button which enables you to manually refresh the tab you are viewing.

• The start/pause button which is used for the automatic refresh function.

• The interval between automatic refresh (in seconds). You can change this by clicking on the

down arrow and selecting a different number of seconds.

258

Summary




You should now be able to understand the many aspects ofconfiguration of SAP HANA DB which can be accessed via SAP

HANA Studio.

259



Backup and Recovery SAP HANA

260

Objectives





• Understand the backup & recovery of SAP HANA

261

SAP HANA Backup and Recovery

In-memory computing is secure

•




The SAP HANA database holds the bulk of its data in memory for maximumperformance, but still uses persistent storage to provide a fallback in case of

failure. The log is capturing all changes by database transactions

• Data and log are automatically saved to disk at regular savepoints, the log is also

saved to disk after each COMMIT of a database transaction

• After a power failure, the database can be restarted like a disk-based database:

• System is normally restarted („lazy“ reloading of tables to keep the restart time short)

• System returns to its last consistent state (by replaying the log since the last savepoint)

Time

Data savepoint

to persistent storage

1 Log written

to persistent storage

(committed transactions)

2Power failure

3

262

Backup and RecoveryWhy are backups necessary?

• While save points and log writing protect your data against power failures, this

does not help when the persistent storage itself is damaged.




To protect against data loss due to disk failures, backups are required

• Backups save the contents of the data and log area to different destinations.

Currently only backups to the file system are supported.

• Backup types:

– Data backup

– Log backup

• Backups are carried out while the database is running and users can continue to

work normally. Impact of backups on the system performance are negligible.

263

Backup and RecoveryData backups

• Data backups save the content of the data area to a different location in the file system.

Depending on the usage scenario, this includes the replicated business data from ERP and




all the modeling data.• Data backups can be carried out manually:

– SAP HANA studio

– DBA Cockpit

– SQL commands (command line)

• Scheduling is also possible:

– Using scripts (via the SQL interface) – Planning calendar in DBA Cockpit

• Backup frequency

– Regular data backups required, but no general guidelines available

(depends on the usage scenario)

• Space requirements

– Only occupied space is backed up

264

Backup and RecoveryLog backup (automatic)

• Prerequisites:

– global.ini: log_mode=normal, enable_auto_log_backup=yes,

( 900 )




log_backup_timeout_s > 0 (e.g. 900 s)• System restart required after log mode change

– Log backups save the log area to a different location in the file system. The default location isspecified in the global.ini configuration file (basepath_logbackup).

• The system carries out automatic log backups

– When a log segment in the log area is full

– After a specified time (log_backup_timeout_s)

– After a database restart

• Log backup files need to be archived regularly to an external destination. Otherwise there

is a risk of the file system filling up.

265

Backup and RecoveryBackups during normal operation of the database: Summary




Data backups

(external backup

destination)

1

Log backups

(external backup

destination)

2

Hardware failure

4

Most recent

log entries

from log area

3

Time

266

Backup and RecoveryRecovery options

ABC




(A) Until the latest point in time

Uses the latest available data backup + all log backups since the latest data backup+ all log entries that are still available in the log area (if it was not destroyed by the failure)

(B) Until a specified point in time in the past Uses the last data backup before the specified point in time + the log entries from the log

backups between that data backup and the specified point in time

(C) Using a specified data backup (without using log information)

Uses the specified data backup, but no log backups. All log entries that still exist in the logarea are deleted, no log will be replayed

For support purposes only: Until a specified log position

Uses the last data backup before the specified log position + the log entries from the logbackups between that data backup and the specified log position

Time

267

Recovery scenarios

SAP HANA Backup and Recovery

S t d i SAP HANA GA SPS02




There is an option for clearing the log during recovery. With this option, older data

backups can be restored (without running into problems with a gap between the

older data backup and the log that is still available in the system).

Supported in SAP HANA GA, SPS02

Recovery to last data backup

Recovery to older data backup *

Recovery to last state before crash ()**

Point-in-time recovery

*requires clearing of the log during recovery **limited, requires undamaged log

268

Backup and RecoveryChanges SAP HANA SPS 2 SPS 3

Automatic log backups

– After a log segment is full

Aft t i ti h l d




– After a certain time has elapsed – Customizable using configuration file

parameters

– Prerequisite for point-in-time recovery

Point-in-time recovery

– To the latest point in time (using the latest data

and log backups and remaining log in the log

volumes)

– To a specified point in time in the past (using

suitable data and log backups)

– To a specified data backup (without using any

log information Clear log)

– To a specified log position (expert option,

needed in case other recovery strategies fail)

Backup catalog

– Contains backup history, including informationabout successful execution of backups

269

SAP HANA Backup and RecoveryBackup to External Backup Destinations




270

SAP HANA Backup and RecoveryRecovery Scenarios: Power Failure




271

SAP HANA Backup and RecoveryRecovery Scenarios: Disk Failure




272

SAP HANA Backup and RecoveryRecovery Scenarios: Disk Failure




273

SAP HANA Backup and RecoveryDistributed Landscape




274

SAP HANA Backup and RecoveryHigh Availability




275

SAP HANA Backup and RecoveryFeature Overview




276

SAP HANA Backup and RecoveryRoadmap HANA 1.0




277

SAP HANA Backup and RecoveryRoadmap HANA > 1.5




278

SAP HANA Backup and RecoveryRoadmap HANA > 1.5 on High Availability




279

SAP HANA Backup and RecoveryRoadmap HANA > 1.5 on High Availability




280

High Availability Features

Scenarios

One data center fails (due to fire, power outage, earthquake, etc.)






Concept

Redundant data center (including redundant HANA system) – Hot Standby

– Synchronous mirroring

Standby system within one SAP HANA landscape – Cold Standby

– Failover is triggered automatically

281

Data Center 2Data Center 1

SAP HANA Post SPS03 High Availability — Disaster ToleranceCluster Across Data Centers Incl. Mount Management

Clients Application Servers




Data Center 2Data Center 1

OS: Mounts

DataVolumes

LogVolume

OS: DNS, hostnames

Primary

Name

Server

Indexserver

Name

Server

Indexserver

Name

Server

Index

server

Secondary

Name

Server

Index

server

Name

Server

Index

server

Name

Server

Index

server

H A S o l u

t i o n P a r t n e r

S

t o r a g e

M

i r r o r i n g

H A S o l u

t i o n P a r t n e r

DataVolumes

LogVolume

DataVolumes

LogVolume

DataVolumes

LogVolume

282

Scale OutHigh Availability

Server 1

Server 2

High Availability configuration

• N active servers in one cluster

• M standby server(s) in one cluster




Server 3

Server 4

Server 5

Server 6

Cold Standby Server

S h a r e d S t o r a g e

M standby server(s) in one cluster

• Shared file system for all servers

Services

• Name and index server on all nodes

• Statistics server (only on active servers)

Failover

• Server X fails

• Server N+1 reads indexes from shared storage and

connects to logical connection of server X

283

SAP HANA Backup and RecoveryBackup Recommendations

The main backup recommendations are:

• Data backups should be performed regularly to allow the system to overwrite log

information in the log area.




information in the log area.

• It is preferable to perform a backup (data + .ini files) before the database software is

upgraded to a new version. This allows for restoration of the system in case the software

upgrade fails.

• After the initial load has successfully completed, a data backup is strongly recommended.

284

SAP HANA OperationsRecommendations

Backup and Recovery recommendations:

• Perform a full backup after initial load

• Never delete database log files on the filesystem




Never delete database log files on the filesystem

• Perform a regular data backup to allow logs to be overwritten

• Estimate backup size to avoid ‘disk full’ before executing the backup

• Review available recovery options as documented in the ‘Backup and Recovery Guide’

For information about backup and recovery for the Sybase Replication,

observe the following:

• Supported: Recovery to the last committed state

• Not supported: point-in-time recovery of either the SAP ERP system or SAP HANA

• Sybase Administration Guide: Volume 2

• Replication System Recovery

285

For information about backup and recovery for the SAP Landscape

Transformation Replicator (SLT Replicator), observe the following:

• The SAP Landscape Transformation Replicator (SLT Replicator) creates a schema in the





p p ( p )SAP In-Memory Database called SYS_REPL where the replication control tables are stored

(RS_* tables, to store replication status for example).

• These tables are part of the normal database backup/recovery.

Recovery scenarios:

• If the database is recovered to the latest consistent state, no further action is necessary, thereplication automatically resumes (as the jobs are not running on the SAP HANA hardware).

• If the database is recovered to an earlier point in time (recovery of data backup with clear

log option), initial load and replication have to be started again.

286

For information about backup and recovery for SAP BusinessObjects Data

Services, observe the following:

• Data Services stores its own metadata in a relational database (currently not the SAP In-





( yMemory Database). This metadata is the definition of the source and target connections,

the mappings and transformations, the workflows with load order etc. backup this database

regularly.

• If the SAP In-Memory Database needs to be recovered, can replication resume without any

further user interaction? Data Services provides batch loading for SAP in-memory

database, so no further user interaction would be needed. The next time a batch load is

started, it will be loaded into the database again.

287

For performance and security:

• Single server SAP HANA instances -> data files on SSA disk

– Recommended mount point /hana/data





• Distributed SAP HANA instances -> data files on shared storage

– Recommended mount point /hana/data

• SAP HANA database log files on SSD disk

– Recommended mount point /hana/log

Configure SAP Support connection (SAP Note 1058533)

Consider dedicated private network to data acquisition systems

Ensure that the SAP HANA database, client, and server are the same revision

level

288

SAP HANA is supported on certified hardware only

Sync time between all HANA nodes and related components (consider NTP)





Plan for close cooperation between operations team and data architect

At project start:

• Verify SAP HANA appliance / installation Checks

– At least 1Gbps network, full duplex, 10Gbps preferred

– Verify disks SSA/SSD and mount points – Verify /etc/hosts does not contain 127.0.0.2

• Align SAP HANA database password policy with corporate policy

• Decide on authentication mechanism for SAP HANA database

289


Summary




• Understand the backup & recovery of SAP HANA

290



Maintaining Users and Authorizations

291

Objectives


• Manage users and roles




g – Create users and roles

– Edit users and roles

• Understand the Security Concept of SAP HANA Appliance

292

Agenda

User Management

Security Details




y

293

User Management and Security in SAP HANA

Create Users

Assign Initial Passwords

Important UserP t




Manage Users

Lock UsersReset Passwords

Check User Privileges

Integration with BI

Assign Security

Control Access to Objects

Row-Level Security

Restrict allowed actions

Parameters

294

Creating named users

Creating user accounts

Named accounts in the database Creation via SAP HANA Studio




Creation via SAP HANA Studio

or via SQL syntax

or via SAP NetWeaver IdentityManagement (version 7.2 SP 3)

No replication of existing authorizationsfrom source systems

AuthenticationName / password

Password management via SAP HANAStudio or via SQL

Kerberos Authentication

Based on certificates

Enables SSO authentication

295

Integration HANA, IDM, LDAP and BOE

Connector SAP IDM <-> SAP HANA

As of SAP IDM 7.2 SP 3U i SQL I t f i HANA

Central repository for

user accounts




Using SQL Interface in HANA

Create / delete users

Create / delete roles

Grant / revoke roles

Change passwords

Authentication BOE <-> HANA

Up to recently: name / password

Using “Credential Mapping”

Duplicate maintenance of user accounts

As of BI 4.0 FP 3: Kerberos integration

Active

Directory /

LDAP

SAP HANA

Database

SAP IDM

BOE Server

User Store User Store

Push

Import

Kerberos

(BI 4.0

FP 3)

296

Authentication via Kerberos

SAP HANA Server

Kerberos

Domain Controller




End user

Users starts application

(e.g. Analysis for Office);

Authentication via domain

controller

User logs on and

receives ticket

297

User ProvisioningHow to get Users into the System

Creating Named Users in HANA

Actual Database Users

Create via SAP HANA Studio




Or using standard SQL statements

Authentication Methods

User / Password

Set up and manage passwords using

SAP HANA Studio or SQL

Kerberos Authentication

Certificate-based

Requires Named User in HANA DB

298

User ManagementUser and Role Concept

Roles allow grouping privileges

Create roles for specific tasks, e.g.

– Create data models (on a given subset of thedata)

User




data)

– Activate data models

– Consume models

All types of privileges can be granted to a role

– Individual privileges

– Roles ( create a hierarchy of roles)

Roles / privileges can be assigned to users

User / Role management are closely related

– Reflected in almost identical editor

Role:

edit model

Role:

activate model

Role:

edit + activate

Package:

create / edit

models

SQL:

select

Package:

activate

SQL:

write

runtime

object

299

User ManagementUser and Role Concept

User and Role Concept

• Allows for a fine granularity of access control, based on the users‘ tasks

– Business end users (consume reports using client tools, e.g. Excel)




– Modelers (create models and reports using SAP in-memory computing studio)

– Engine administrators (operate and maintain the engine and users, using studio),

SYSTEM administrator created during installation

– Replication users (carry out data replication on ERP source system and target system)

• Free definition of roles

• Roles are assigned to users, and roles can also be assigned to roles (role hierarchy)

• User provisioning is carried out using the SAP in-memory computing studio

300

User ManagementUser Creation

SAP In-Memory Computing studio is used for user provisioning

• Creation of users

• Creation of roles and role hierarchy

A i t f t l




• Assignment of users to roles

• Authentication: To check if users really are who they say they are

• The SAP in-memory computing engine provides the following options for authentication, also

– Direct logon to SAP In-Memory Computing Engine with user name and password

o SAP In-Memory Computing Engine authenticates users

– Authentication using third-party authentication providers: Kerberos -> Active Directory,can be integrated into single-sign-on landscape

o External services Authenticates users (eg. Active Directory Server)

o External services then passes logon token to SAP In-Memory Computing Engine

301

Process Flow




302

Assign Privileges to RolesGeneric background information

Two generally different cases:

Object / Privilege combinations. E.g.

• grant SELECT (privilege) on <TABLE> (object)




• grant EXECUTE (privilege) on <PROCEDURE> (object)

• Direct Privilege Assignment. E.g.

• grant USER ADMIN (system privilege)

• grant EXAMPLE_ROLE (Role)

Concept of Grant Option

Allows granting a privilege to

other users/roles

• Not available for all types

of privileges

303

User ManagementRole Creation




304

IMCE AuthorizationsPrivileges




305

IMCE AuthorizationsSQL Privileges




306

User ManagementRole Creation – Assigning Privileges




307

IMCE AuthorizationsSYSTEM Privileges




308

User ManagementRole Creation – Assigning Privileges




309

IMCE Authorizations Analytic Privileges




310

User Management Analytic Privileges Creation




311

User Management Analytic Privileges Creation – Specifying Attributes




312

User Management Analytic Privileges Creation – Specifying Restrictions




313

User Management Analytic Privileges Creation – Save and Activate




314

User Management Analytic Privileges Assignment – Repeat from Role




315





316





317

User ManagementRole Creation – Save and Deploy




318

User ManagementRole Creation – Confirm Role Deploy




319

User ManagementUser Creation Steps




320

User ManagementUser Creation Steps - User




321

User ManagementUser Creation Steps – Assigning Role




322

User ManagementUser Creation Steps – Assigning Role




323

User ManagementUser Creation Steps – Confirm User Deploy




324

Reporting and PrivilegesRequired Privileges for Reporting

What privileges do I need in order to read from a given view?

• One always needs SQL SELECT for the column view

• For Attribute Views:

– No Analytic privilege required / possible




y p g q p

o (can create them, but they are not evaluated)

– Need SQL SELECT on the Column View for the Attribute View

• For Analytic Views:

– At least one analytic privilege is needed

o Defined on Analytic View itself, or on Attribute View used within Analytic View

– Without analytic privilege for the view, no data is returned

– There is a „See everything system wide“ privilege: „_SYS_BI_CP_ALL“

– Need SQL SELECT for the Column View for the Analytic View

• For Calculation views:

– No analytic privilege required for the Calculation View itself

– If Analytic View used in Calculation View: need Analytic Privilege for that Analytic View

– Need SQL SELECT for all views and tables explicitly used in the Calculation View – Need SQL SELECT for the Column View for the Calculation View

325

Creating Analytic PrivilegesRequired Privileges

What privileges do I need in order to create Analytic Privilege?

• The user only needs the ‚ALTER SYSTEM„ system privilege

– No SQL SELECT or other SQL privilege needed

• As Modelers require ALTER SYSTEM, too




As Modelers require ALTER SYSTEM, too

– Any Modeler is allowed to create and activate analytic privileges

• Privileges are implicitly assigned to user who activates them

326

ModelingRequired Privileges

What privileges do I need in order to do Modeling?

• SQL Privileges needed:

– CREATE ANY, INSERT, UPDATE, DELETE, SELECT on _SYS_BIC

o the modeler creates column views in that schema

– SELECT on the tables used in the view




SELECT on the tables used in the view

o in RKT system: you have SELECT for the entire SYSTEM schema

• System privileges:

– ALTER SYSTEM, DATA ADMIN

• Analytic Privileges

– Strictly, none required

– For being able to preview/test views: some analytic privilege

o In RKT system: you have „_SYS_BI_CP_ALL“

• Consequences of these facts

– Any Modeler can create their own analytic privileges, since they have „ALTER

SYSTEM“

– Any Modeler can see all data in the tables they use in the model

– Any Modeler can see all data in the views (because they can authorize themselves)

o Modeling on confidential data hardly possible in a production systemo need two-system landscape, model on randomized data, then import

327


• Manage users and roles

Summary




– Create users and roles

– Edit users and roles

• Understand the Security Concept of SAP HANA Appliance

328

Unit 4: Monitor and Troubleshoot



Unit 4: Monitor and Troubleshoot

SAP HANA

329



Lesson 1: Configuring Remote Support

Lesson 2: Setting Up Monitoring Lesson 3: Monitoring




Lesson 4: Analyzing Logs and Traces

Lesson 5: Analyzing Performance

Lesson 6: Auditing SAP HANA

330

Unit Objectives

After completing this unit, you will be able to:

Understand the overview of “things to monitor” in the SAP HANA Studio

Perform general troubleshooting and analyzing logs & traces




331

Configuring Remote Support



Configuring Remote Support

332

Objectives


Establish a remote connection




333

Solution Manager Integration and Remote ServiceConnection

In addition to run the on-site configuration tool, SAP recommends to

establish SAP Solution Manager connectivity and configuration of a Remote

Service Connection (via SAP Router) as part of initial setup.

As of Solution Manager 7 1 SP04




As of Solution Manager 7.1 SP04

the SAP HANA databases can be integrated into Solution Manager

o Performance Warehouse

o Alerting Infrastructure

o DBA Cockpit (also available in BW systems as of BW 7.30 SP05)

Remote service connection can be established through the SAP Router

o New connection type allows SAP support to access customer databases via local HANA studio

installation

334

Safe Remote Access via Solution Manager




335

Supportability for Business ObjectsOverview

Remote Access

SAP Router Line Opener Program




Remote Debugging

Root Cause Analysis

Remote SupportComponent SAP Solution Manager

336

Remote Access: SAP Router and Line Opener Program

SAProuter Client + TCP ProxySAP Logon

Web ApplicationSAProuter

https




Line Opener

Program

(LOP)

Backend

Services

SAP BusinessObjects

components

Other components

337

Remote Connection:To Solution Manager

Remote Connection to Solutionmanager

HANA can be connected to Solution Manager 7.1 >= SP02 Level 3

Standard SAPGUI and HTTP connection to Solution Manager has tobe established (see note 962516)




338

Remote Connection:via SAP Router to HANA DB Studio

What is needed to connect from SAP

Network to customer network:

Connection via sapstartsrv on theHANA Server to the Master Index

Server

SAP

Network




SAP HANA

Server

SAP Router

Customer

Network

339

Remote Connection:via SAP Router to HANA DB Studio

• Saprouter installation required at customer side

see also http://service.sap.com/serviceconnection

Connection to customer HANA DB possible from SAP local HANA DB Studio New connection type „SAP HANA database“ in customer system data and STFK

See note 1592925 (SAP HANA database service connections)




See note 1592925 (SAP HANA database service connections)

Port of sapstartsrv for HANA

(by default: 5<instno>13)

Port of HANA master indexserver

(by default: 3<instno>15)

340

Remote Connection:further components in HANA Scenarios

Business Objects Enterprise / BI Platform 4.0 can be connected to

Solution Manager 7.1

remote connection to Solution Manager 7.1 to be established (note 962516)

Business Objects Central Management Console (CMC) to be connected via

HTTP connect – URL access (note 592085)




SAP Backend system and SLT system can be connected to

Solution Manager 7.1 and shall also be remotely connected to SAP via

R/3 support (see notes 812732) and HTTP Connect

341

Remote Access to OS Level

In very hard support cases it might be necessary to have OS level access.

For the HANA linux systems a SSH or Telnet remote connection should be

set up (notes 1275351 + 1327257)

For Windows based systems (potentially used for Business Objects components) we

therefore recommend to setup a Netviewer connection (note 1036616) Netviewer requires




the customer to active accept a connection request.

For unattended access a Windows Terminal Server connection can be setup

(note 605795)

342


Establish a remote connection

Summary




343

Setting Up Monitoring



Setting Up Monitoring

344

Objectives


Setup the EarlyWatch Alert for SAP HANA

Setup Availability Monitoring in SAP Solution Manager of SAP HANA

Database




345

Agenda

Technical Operations

SAP EarlyWatch Alert

Overview and Setup of the EarlyWatch Alert for SAP HANA

Availability Monitoring in SAP Solution Manager of SAP HANA Database




y g g

Availability Monitoring of the HANA Processes

346





347

Technical Operations in SAP Solution Manager 7.1Part of Application Lifecycle Management

Solution Implementation

Solution Documentation Enhanced Solution Documentation Assistant

Reverse Business Process Documentation and IBIS Content

integration

Upload interface to build an initia l Business Blueprint structureMaintenance Management

Enhanced Maintenance Optimizer

System Recommendations

Upgrade Management Integration of Upgrade Dependency Analyzer

Enhanced Custom Code Lifecycle Management




Template Management Comparison & Adjustment for Template

Roll-in changes from projects

Change Control Management Enhanced Quality Gate Management for various activities

Enhanced process flexibility for Change Request Management

Improved mechanism for the change and transport backend Configuration Validation and Change Analysis

Application Incident Management IT Service Management Processes

Highly configurable web-client user interface

Additional Service document functions

p Enhanced Business Blueprint

Implementing Business Functions

Integration with the service messages

Business Process Operations Enhanced BPO Dashboards with Alert Inbox

Cross Database Comparison

Job Control and Schedule Management

Test Management Enhancement to manage test phases efficiently

Test Automation Framework with 3rd party tools

Test Scope Identification & Optimization with BPCA

Technical Operations New Infrastructure for Technical Monitoring

and Alerting

Technical Administration

Technical Analytics

Enhanced Root Cause Analysis

Data Volume Management

Configuration Validation

348

The process behind technical operations…

Monitor

Proactive real-time

monitoring

Optimize

Optimize excellence of

technical operations

Analyze

Lower mean time to

problem resolution

Notify

Reactive handling of

critical events




ReportProve value to business

349

Agenda


• SAP EarlyWatch Alert

– Overview and Setup of the EarlyWatch Alert for SAP HANA

• Availability Monitoring in SAP Solution Manager of SAP HANA Database




Availability Monitoring in SAP Solution Manager of SAP HANA Database – Availability Monitoring of the HANA Processes

350

EWA for HANA (SPS02): Overview

HANA Checks included in the

EWA report of an ABAp Stack

Overview (beginning of EWA):

Rating of area which needs further

investigation:




investigation:

• Overview: All Services are available

• Configuration: Parameters set correctly

• Size and Growth: Host Resource

Utilization (Disk Space, Memory Usage)

• Performance: Workload Statistics fromthe In Memory Database and IO

Statistics

• Alerts and Statistics: Summary of

impotrant Alerts and Aggregated

Statistics of the Statisticserver

351

EWA for HANA (SPS02): Landscape

SolMan 7.0 SAP

„Backend“

System

1. Batchjob triggers data

collection on HANA via Host

Agent

2. Host Agent starts datacollection Skript

3. Information is passed back to




p

background job (XML-Format)

4. Results in background job is

collected in sdcc and send to

SolMan

5. EWA session is executed on

SolMan and EWA report is

created

InMemory

Database

Hana 1.0

Host Agent

Skript

352

EWA for HANA: Setup (HANA Box)

Installation of the Shell scripts

1. Install the attachement of SAPNote 1542651 in a temporary directory of the

HANA Box2. Call the shell script enable_ewa_monitoring_IMCE.sh and choose the correct

HANA installtion according to the Installtion Path:




hana:/tmp/hana_server_tmp_files # ./enable_ewa_monitoring_IMCE.shTrying to find the installation path of IMCE/usr/sap/HCS/HDB00 [Y, N]YInstallation Path used: /usr/sap/HCS/HDB00

copying /usr/sap/hostctrl/exe/operations.d/EwaNewDB.pycopying /usr/sap/hostctrl/exe/operations.d/Tables2XML.py

copying /usr/sap/hostctrl/exe/operations.d/Tables2XML.pycopying /usr/sap/hostctrl/exe/operations.d/config.inicreating /usr/sap/hostctrl/exe/operations.d/newdb_xml.conf

creating /usr/sap/hostctrl/exe/operations.d/newdb_xml.sh

353

EWA for HANA: Setup (HANA Box)

Installation of the Shell scripts

3. In the hostagent directory /usr/sap/hostctrl/exe/operations.d the following

files can be found:

newdb_xml.conf

newdb xml.sh




_

EwaNewDB.py

Tables2XML.pyc

Tables2XML.py

config.ini

4. Test :Change into directory /usr/sap/hostctrl/exe and execute./saphostctrl -function ExecuteOperation -name newdb

“PASSWORD= <Server Name>;DBUser; DBPassword”

The outcome is an XML:<SIMC>

….

<ROW10><COLUMN

354

EWA for HANA (SAP Backend)

Configuration of the ABAP Poxy for Service Oriented calls to the

SAPHostagent of the HANA Box:

1.Call Transaction SOAMANAGER -> Choose TAB ‚Service Administration‘

2. Choose ‚Single Service Configuration‘




355




3.Search for the Hostagent SOA Interface viaSearch by : Consumer Proxy

Search Pattern: *Host*

Field Internal Name




Field: Internal Name

Press

Apply Selection

356




5. Create Logical Port




6. Choose

Logical Port Name: SAPHOST_PORT Description (free): SAPHOST_PORT

Mark Manual Configuration

357



SAPHostagent of the HANA Box: Details:

7. Details:

User / Password of

the Hostagent Operating

System user sapadm




System user sapadm

358




8. Messaging:




359




9. Transport Settings




HANA Box

360


Configuration of the Job Variant

1. Create new Variant of report /SDF/ SHCXSKIPT_SECSTORE

The Configuration Details are:

Name of Operation: newdb

Enter CMS Hostname (hostname o the HANA Box): <Servername of HANA Box>

E t P P t SAPHOST PORT




Enter Proxy Port: SAPHOST_PORT

Enter Username (of the In Memory Database): Database name

Enter Password (of the In Memory Database): Database password

2.Before the report can be executed add the following entry in table RSESACHK

PROGNAME /SDF/SHCXSKRIPT_SECSTORE

CHSUM 0ADD8C932F4ABFEF91C524F10BFC6503

PREFIX /SDF/BOBJ/

361


Configuration of the Background Job

3. Last step: Create Background Job ‘MONITOR_BOBJ_STATUS_HANA’ with Report

/SDF/ SHCXSKRIPT_SECSTORE and the corresponding variant.




362

EWA Content for HANA: Configuration

Configuration:

Overview

Version Landcsape

Service




Configuration

Parameter:

– lock_waittimeout

– Section mergedog: active

363

EWA Content for HANA: Capacity

Size and Growth

Disk Usage

Separated in Data / Anchor / LogFile

Size of Volume Files




Size of Volume files separated by

different services

Table and Indexes

Number of Columnar and Row

Store Tables

Indexes of Row Store tables

Size of Row and Column Store

Tables

364

EWA content for HANA: Performance

Performance

Memory Utilization

– Utlilization by each service

Available Swap Space

Workload

/O f




I/O Performance

Average Volume Statistics

(Read / Write Times

365

EWA content for HANA: Administration

Administration

Number of Log / Trace Files (weekly)

– Should be ensured that these are reorganized regularly




366

EWA availability in Solution Manager

Requirements / Summary:

•Solution Manager 7.01 / ST_SER 2010 SP 6

o Content Update should be scheduled

HANA Box: installation of the script enabling the Host Agent for HANA Specific

Webservice Calls.

SAP N t 1542651




SAP Note 1542651

SAP Backend: SAP_BASIS 7.00. The Support Package >= 18.

SAP Note 1543278

367


• SAP EarlyWatch Alert

– Overview and Setup of the EarlyWatch Alert for SAP HANA

• Availability Monitoring in SAP Solution Manager of HANA DatabaseA il bili M i i f h HANA P

Agenda




– Availability Monitoring of the HANA Processes

368

Availability Monitoring withSolution Manager 7.1 for SAP HANA ( SP 02, SP 03)

HANA host

A g e n t

o n t r o l

CPU

Introscope

EnterpriseManager

IS Server

Browser

SAPCustomer

SolMan Server

SolMan 7.1

E2E Ch A l i




D i a g n o s t i c s

S A P

H o s t c o

Memory

File

system

Browser

access

I n t e r n e

t

DB

E2E Change Analysis

E2E Exception Analysis

E2E Workload Analysis

Introscope WebView

Remote DB Monitoring

File System Browser

logs

Log Viewer

E2E Trace Analysis

Workload Analysis (Perf. Warehouse)

and Trace Analysisplanned with SolMan 7.1 SP05

369

HANA Availability Monitoring in Solution Manager

System Level

inherits worst

case from DB




Availability of all

HANA services

Alert Status of

HANA internal

alerting

(Text not yet final)

Host LevelMonitoring

case from DB

and Host

370

HANA availability monitoring

Requirements:

SAP Solution Manager 7.10 SP 03

SAP Diagnostics Agent has to be installed on the HANA Box

SAP Hostagent 7.20 SP 84

(See SAP Note 1625203)




371

Setup Into Solution Manager

Hostagent & SMDAgent

Setup in Solution Manager

1

2




Setup of Technical Monitoring3

372

Setup of System Monitoring: Overview over landscape

Involved Components are:

Hostagent (Hostagent has to communicate with the HANA Database)

SMDAgent (SMDAgent has to communicate with the Hostagent)

Solution Manager (SMDAgent has to be assigned to a Solution Manager)




Solutionmanager HANA Appliance Server

HANA

Database

Hostagent

Landscape

Managed

Database

(LMDB)

DBACockpit

1

2

34

Performance

Warehouse

Alerting

Framework

373

1. System Monitoring Setup: Hostagent

Hostagent: Configuration of the HDBUserStore

Because of security reasons: Hostagent should not be called with user / password

1. Create a Database user on HANA wich has the role ‚MONITORING‘




374



2. Configuration the hdbuserstore (SAP Note 1625203)

Set the user with password (Databasename is IN1) with the user <SID>adm

R d th t




Read the userstore

Test the settings

375



3. Outside Discovery and Alerting

Outside Discovery: Webmethod GetDatabaseProperties




Status: Webmethod GetDatabaseStatus

376

2. System Moniroting Setup: SMDAgent

Ensure that SMDAgent communicates with Hostagent

SMDAgent needs Permission to execute Hostagent executables

File host_profiles




377




S t f T h i l M it i

1

2





378


Go to Workcenter SAP Solution Manager Configuration -> Managed System

Configuration

The HANA Database should be created via Outside Discovery

Perform the Managed System Setup for Database (HANA) -> ‚Configure database‘




379


Create a Technical System (Necessary to have RCA Change Configuration

Data insight)




380


Define a Technical System of type: ‚Unspecified Cluster‘

Technology Type: Hana Cluster

Assign the previous Database

Add Product Version and Software Component




381


Perform the Setup / enter the directory names in ‚Enter Landscape Parameters‘




382

Setup of Technical Monitoring



Setup of Technical Monitoring

1

2

3





383

Technical System SetUp

Technical Monitoring SetUp:

Configuration Workcenter -> Technical Monitoring




384

Technical System SetUp

Technical Monitoring SetUp:

Configuration Workcenter -> Technical Monitoring (Assign Templates)




385

HANA System Monitoring in Solution Manager

System Level

inherits worst

case from DB

and Host




Availability of all

HANA services

Alert Status of

HANA internal

alerting

(Text not yet final)

Host LevelMonitoring

386

Perform Administration & Monitoring Administrative Tasks in SAP HANA Studio

Initial Administrative Tasks:

After the initial load, perform a database backup (including configuration backup)

Regular (Periodic) Administrative Tasks: Overview tab page of the Administration screen

– System status, Overall system state, General system information

– The latest warnings generated by the statistics server




g g y

Services tab

– Name server, Preprocessor, any services that are actively running on the system

Regularly perform data backups (including configuration backups).

Administrative Tasks on Demand:

Diagnosis Files tab

Navigator

– Restart/Stop/Start SAP HANA DB

Perform data backup

387

Monitoring the SystemStatus Overview




388

Monitoring the SystemServices Overview




389

Monitoring the SystemSystem Load History – Check Alerts




390

Monitoring the SystemDisk Usage Details




391

Monitoring the SystemChecking System Configuration




392

Monitoring the System Alerts Generated by the Statistics Server




393

Monitoring the SystemStatistics Server – Enabling and Checking




394

Monitoring the SystemDisplaying Log Files




395

SAP HANA studio: Administration viewOverview

Provides most important information about one database at a glance

– Database state and general system information

– Alerts

– Memory usage – CPU usage

– Disk usage

Detailed information

il bl i li k




available via links

Database version

history

396

SAP HANA studio: Administration viewForward navigation

Analyze issues in your

landscape

The Overview tab serves also ascentral entry point for various

system analysis tasks.

It allows easy drill-down into




detail problem analysis e.g. by

clicking on a alert notification on

the system overview tab and

navigating to the more detail alertinformation or, starting from the

landscape tab, open the

diagnosis files.

The System Monitor shows even

information for all systems of the

corresponding SAP HANA

landscape.

397

SAP HANA studio: Administration viewLandscape

List of all services (processes), their status and resource consumption

– Name server

– Index server

– Preprocessor – Statistic Server

R t ti i




Restarting services

Display and configuration of hosts and their role (master, standby, …)

Displayed information configurable

398

SAP HANA studio: Administration view Alerts

List of current

or all alerts

– Filter available

Status of all

checks




Configure email notifications

Configure warning level thresholds

Configure check start times

399

SAP HANA studio: Administration viewPerformance

List of threads

Graphical display of

performance KPIs

Displayed information

configurable




400

SAP HANA studio: Administration viewVolumes

Detailed information

about storage size

and usage

– Size of data area – Size of log area

– Size of storage areas

– Usage of storage areas

– Two different views:




– Two different views:

Grouped by service and

grouped by storage

Access Statistics fordifferent volumes

Displayed information

configurable

401

SAP HANA studio: Administration viewConfiguration

List of INI files including the parameters

Editing of parameters

Filter available




402

SAP HANA studio: Administration viewSystem Information

System Information contains list of useful SQL

statements

e.g. to get information about:

– Expensive SQL statements – Memory usage

– SQL locks

– Merge statistics

–




– …

403

SAP HANA studio: Administration viewLog Files / Traces

List and display possibility of all database log and trace files




Activating database traces

404

SAP HANA studio: Administration viewSystem Monitor

Provides most important information about all databases of the system landscape at a

glance

– Database state and general system information

– Alerts – Memory usage

– CPU usage

– Disk usage




Detailed information available via links

Displayed information configurable

405


Understand System Monitoring

Summary




406

Analyzing Logs and Traces



407

Objectives


•Analyze logs and traces as part of routine administrative tasks




408

Analyzing Logs & TracesRegular Administrative Tasks

• In case of problems with the SAP HANA database, log and trace files can be

checked for errors. These log files are available in the SAP HANA studio on the

tab page "Diagnosis Files" of the administration screen. To display a log file,

choose "Open" in the context menu of the list or just double-click the entry of therespective log file.

• In certain situations, you have to restart the system (for example, after a power

failure) In the Navigator of the SAP HANA studio open the context menu on the




failure). In the Navigator of the SAP HANA studio, open the context menu on the

system entry and choose Restart. After confirming the restart, you need to enter

the operating system user and password, before the system is actually restarted.

• If the disk on which the log is located fills up, carry out a data backup. This

ensures that the log space can be reused by the system.

• Before the database software is upgraded to a new version, carry out a data

backup (including configuration backup). This allows for recovery of the system in

case the software upgrade fails.

409

TroubleshootingCommon Scenarios

Disk Full Events

Displaying Log Files in Diagnosis Files

Trace Handling

Additional Trace Files




Merged Trace Files

Resource Usage Information

410

Disk Full Handling

Disk Full Handling

If the storage on which database files

are

stored runs full, the database getssuspended and an event is triggered

This event is displayed on the

Overview tab of the Administration




editor in addition to the bar view

of the disk usage

The disk full situation has to beresolved (additional storage space

has to be provided or unused files

to be deleted) AND the event has

to be marked as handled before

the database can resume its work

Marking the event can be done using

the link on the Overview tab

411

Diagnosis Files

Diagnosis File Display

Diagnosis files can be displayed, even if no SQL connection is available (e.g. if the

database is OFFLINE)

In this case sapstartsrv is used to get the trace file information

Operating user <sid>adm and his password have to be entered for this




412

Additional Trace Options

SQL Trace

SQL Trace can now be filtered by database user,

application user, tables/views and statement type

Performance Trace

Performance Trace can now be filtered by




Performance Trace can now be filtered by

database user and application user

Additional trace options are available:

Tracing of execution plans

Activating function profiler

413

Merged Trace Files

View for merged trace files

Trace files of the different database services and

from all database hosts are merged and sorted by

timestamp, to see easily what happened at aspecific point in time

8000 rows of the merged trace files

are displayed




The slider above the trace file

display allows to change the

displayed rowsErrors and warnings are

highlighted

414

Resource Usage Information

Statistics about column unloads

The nameserver now also collects statistics about column unloads, caused by

memory shortage

These nameserver statistics are displayed in the Administration editor of SAP HANAstudio on tab Performance -> Load .




415


Analyze logs & files to perform routine administrative tasks

Summary




416

Analyzing Performance



417

Objectives


Analyze the SAP HANA performance with E2E diagnostics




418

The process behind technical operations…

Monitor

Proactive real-time

monitoring

Optimize

Optimize excellence of

technical operations

Analyze

Lower mean time to

problem resolution

Notify

Reactive handling of

critical events




Report

Prove value to business

419

Root Cause Analysis: Options for SAP Customers

Remote Support Component

Recommended for SAP Business Objects

landscape only

Limited functionality Upgrade path to SAP Solution Manager in

Q3 2011

SAP Solution Manager

Supports mixed landscapes

(SBOP & other SAP products)

Full blow functionality Complete integration in ALM processes

Single systems / For BO only shops Full blow functionality / For BO and SAP shops




Customer

Landscape

Management

Platform

BusinessObjects

Business

Intelligence

Remote

Support

Component

Upgrade ( Q3 2011)

BusinessObjects

Business

Intelligence

ERP

CRM

420

Root Cause Analysis with Remote Support ComponentOverview

Root Cause Analysis platform

Specifically for SAP customers who do not have a

significant SAP landscape

SAP BusinessObjects Enterprise XI 3.1 SP2 andfuture versions are supported

No additional fee with a valid SAP maintenance

contract

All t t b tt l th i SAP




Allows customers to better analyse their SAP

BusinessObjects Enterprise systems

Reduces time to resolve messages

Less total cost of ownership (TCO) compared to

Solution Manager

421

Root Cause Analysis with Remote Support ComponentArchitecture

Development

system

Web

Application

Server

BusinessObjects

Enterprise

Production

system

Web

Application

Server

EarlyWatch Alert

report in the Service

Marketplace

Monitoring

system

o n

t o

BusinessObjects

Enterprise




CA Wily

IntroscopeAnalysis

Analysis

Root Cause Analysis

by customer or

Managing

Agent

C

o n n e c t i o

Analysis

Operating System Data

Application Specific Data

Managed

Agent

Managed

Agent

Managed

Agent

Managed

Agent

422

End-To-End Change AnalysisStatistical change data cross all technologies based on daily configuration snapshots

Compare configurations between systems and drill down to change reporting for

change history

Root Cause Analysis with SAP Solution Manager Overview

End-To-End Workload AnalysisGeneral performance overview for heterogeneous solution landscape

Review of most important KPI’s cross all technologies and drill down to product specific

KPI’s

End-To-End Exception Analysis




Statistical exception data cross all technologies for exception trend analysis or review

exception

Jump to component specific exception analysis (ST22, NWA,…)

End-To-End Trace AnalysisSingle user request tracing in a complex system landscapes

Identify the problem causing component (performance and functional) and jump-in to detailed

component specific trace analysis (SQL, ABAP, J2EE trace,…)

System, Host & Database AnalysisCentral, safe and remote access to fi le system, OS and DB

Links to read-only monitoring and administration tools like Wily Introscope for performance

analysis and monitoring

423

Root Cause Analysis with SAP Solution ManagerEnd-to-End Change Analysis - Architecture

Extractor Framework

(EFWK)

Hourly

Drilldownnavigation

Detailed Change Reporting

Change Analysis Statistical Overview of Changes


Business Warehouse




Managed Systems

Configuration and Change Database

( CCDB )

ABAP based

installations

Solution Tool

Plugins (ST-A/PI)

Non-ABAP based

installations

Diagnostics

Agents

Extractor Framework

DailyChange History

424

Root Cause Analysis for Business IntelligenceEnd-to-End Change Analysis - Content

BO Web Layer

Web Application Server

specific configuration

data

(e.g. Apache Tomcat,

IBM Web Sphere,

SAP J2EE Engine)

BO Server Layer

Platform SDK




Platform SDK

Configuration

Platform Services

Configuration

WEBI Processing

Configuration

SAP BW Layer

Parameters

Transports

SAP Notes

425

Root Cause Analysis with SAP Solution ManagerE2E Workload Analysis - Architecture

Extractor Framework

(EFWK)

Hourly

C t S ifi W kl d A l i

Cross-Component Workload Analysis


Business Warehouse




Managed Systems

ABAP based

installations

Solution

Tool

Plugins

(ST-A/PI)

Non-ABAP based

installations (Java /

J2EE / .Net / C/C++)

Diagnostics

Agents

Introscope Enterprise Manager

Introscope

ByteCode Agent

Diagnostics

Agents

Component-Specific Workload Analysis

426

Root Cause Analysis for Business IntelligenceE2E Workload Analysis - Content

BO Web Layer

Average Response Time

Number of Requests

Calls to BI Platform

CPU & Memory Util.

BO Server Layer

Average Response Time




g p

Number of Requests

Calls to Data Source

CPU & Memory Util.

SAP BW Layer

Reporting Performance

Process Chains

Performance

Upload Performance

427

Root Cause Analysis with SAP Solution ManagerEnd-to-End Exception Analysis - Architecture

Exception Analysis Statistical overview of Exceptions List of detailed exceptions




Managed Systems

ABAP based

installations

Solution Tool

Plugins (ST-A/PI)

Non-ABAP based

installations

Diagnostics

Agents

Extractor Framework

Hourly

Jump-In to component specific

analysis transactionSAP Solution Manager

Business Warehouse

428

Root Cause Analysis for Business IntelligenceEnd-to-End Exception Analysis - Content

BO Web Layer

Java Application Errors

(from Web Application

Server Log) Event Log Errors

(Windows only)

BO Server Layer

Services errors (from log




written by specific

service)

Event Log Errors(Windows only)

SAP BW Layer

ABAP Syslog Errors

ABAP Dumps

ABAP Update Errors

429

Root Cause Analysis with SAP Solution ManagerEnd-to-End Trace Analysis - Architecture

Record end

user activities

Collect trace data

in Solution Manager




Understandrequest flow

Analyze in detailand find root-cause

430

Root Cause Analysis for Business IntelligenceEnd-to-End Trace Analysis - Layers

BO Web Layer

HTTP Request Analysis

Server Analysis Introscope Transaction

Trace

Log Viewer

BO Server Layer




Server Analysis

Introscope Transaction

Trace Log Viewer

SAP BW Layer

ABAP Trace

ABAP SQL Trace

BI Runtime Statistics

431

Root Cause Analysis for Business IntelligenceEnd-to-End Trace Analysis - Content

HTTP level

client details (Internet Explorer / Office Addin)

client / network / server gross times

Server split upper involved server system




Call tree through

all server components

jump-in to detail logs

432

Root Cause Analysis with SAP Solution ManagerEnd-to-End Host Analysis – Content: CPU, Paging&Swap

Average CPU

Utilization & Load

Average

Data is available in graphical and tabular form. By drilling down it is possible to not

only show very aggregated data like average CPU usage by day, but also get a

table view of the hourly averages for a complete week




433

Root Cause Analysis with SAP Solution ManagerEnd-to-End Host Analysis – Content: Disk & Filesystem

Disk Utilization in %

Available Metrics: Response Time,

Service Time, Wait Time, Queue Length,

KB / s, Operations / s

Data for disk utilization is by default filtered on Top 5 disks by utilization, condition

can be removed to get full list. Data for file systems is by default filtered by Top

10, including metrics on used space, free space. Full information available by disk

or file system




File System Utilization in %

Available Metrics: Used Space, Free

Space

434

Root Cause Analysis with SAP Solution ManagerCA Wily Introscope - Right to view license

Introscope is a performance management solution that enables you to monitorcomplex applications in production environments 24x7.

http://www.wilytech.com (part of CA) Real time (15 s) monitoring using

Dashboards Investigator

Dynamic transaction tracing

Dynamic byte code instrumentation for

J2EE

.Net




Static instrumentation for C/C++ based

products available

Delivered with standard instrumentation andstandard dashboards for SAP & Partner

products, eg:

SAP NetWeaver XI

SAP NetWeaver Portal

SAP NetWeaver MDM

Seeburger XI Adapters

CPS for SAP by Redwood

…

435

Root Cause Analysis for Business IntelligenceCA Wily Introscope for BI Platform

Dashboard entry page

covers Web App Server, BI Platform servers,

Add-on components (Explorer, Data Services)




Drilldown to detail

dashboards per

component / scenario

436

Remote ServicesEarlyWatch Alert report

Sample EWA report (click here)




437

Remote DebuggingArchitecture overview

TCP ProxyJava Debugger

Native Debugger

Java Source Code

C++ Source Code

D e b u g g e r

I n t e r f a c

e

Web ApplicationSAP Logon

Debugger

Interface

SAProuter SAProuter

https




D

Backend

Services

SAP BusinessObjects

components

Other components

Interface

438


Analyze performance using the Root Cause Analysis concept

Summary




439

Auditing SAP HANA



440

Objectives


• Understand the purpose of the Auditing

• Describe the Auditing Infrastructure• Understand the auditing events

• Configure Auditing

• Verify the audit trail




441

MotivationThreats

Internal Threats

• 80-90% of all attacks/security breaches come from inside the intranet

• Examples

– Unauthorized access to data

o Employees looking at salary tables

o External consultants gaining access to sensitive internal information

– Unauthorized data changes




o Employees covering their own mistakes

o Privilege abuse Data Import/Export

• Most security breaches come from company-internal power users (DBAs)o By assigning themselves additional privileges or roles, or

o Log on as different users

External Threats

• Hackers

442

MotivationThreats

Main requirement to audit a system

•Traceability of actions performed in that system

– Who did or tried to do what when?

•Example of actions to be audited

– Changes of a users’ authorization

Creation or deletion of database objects




– Creation or deletion of database objects

– Authentification of users

– Changes of the system configuration

– Changes of the audit configuration

– Access to or alteration of sensitive information

443

Auditing Infrastructure

Extensible auditing infrastructure

• Audit trails

– Currently stored via syslog

– Syslog is a standard mechanism

for logging program messages on

Unix / Linux




444

Events that are Audited

Logging of successful and unsuccessful events

• Access control action list

– GRANT ANY

– REVOKE ANY

– GRANT PRIVILEGE

– REVOKE PRIVILEGE

– GRANT ROLE

– REVOKE ROLE




– GRANT STRUCTURED PRIVILEGE

– REVOKE STRUCTURED PRIVILEGE

•Create/drop principal action list

– CREATE USER

– DROP USER

– CREATE ROLE

– DROP ROLE

445

Configuring AuditingGlobal Audit Configuration -1/3

Maintaining the global audit configuration

• Prerequisite: INIFILE ADMIN system privilege

– Permission to use the following statements to alter the configuration of auditing

system.• Activate or Deactivate Global Auditing

– Activate: alter system inifile('global.ini','SYSTEM') set('auditing configuration','global_auditing_state' ) = 'true'

with reconfigure;

Deactivate: lt t i ifil (' l b l i i' 'SYSTEM') t




– Deactivate: alter system inifile('global.ini','SYSTEM') set('auditing configuration','global_auditing_state' ) = ‘false'

with reconfigure;

446

Configuring AuditingGlobal Audit Configuration - 2/3




447

Configuring AuditingGlobal Audit Configuration - 3/3




448

Configuring AuditingManage Audit Policies - 1/3




449





450





451

Audit EventsFields and Meaning

After completing required

configuration, Audit Events can

be found in Syslog output.




452

Audit Trail

Syslog Example




453


Describe the purpose and functions of Auditing

Summary




454



Lesson 1: Transporting Changes

Lesson 2: Updating SAP HANA




455

Transporting Changes



456

Objectives


Explain how the Enhanced Change and Transport System (CTS+) works

Understand the basic concepts of SAP BOE, SAP HANA and how they are

supported by CTS+

Know best practices for the setup and usage of CTS+ for SAP BOE and SAP

HANA




457

Agenda

CTS+ Overview

CTS+- What‘s new

SAP Business Objects with CTS+ SAP HANA with CTS+




458

Motivation to Extend the Change and Transport System

Change and Transport System (CTS) and Netweaver Development

Infrastructure provide powerful functions to control transports in

ABAP and Non-SAP.

What was missing?

Synchronized import into double stack systems

A solution for the transport of Portal content




A central administration interface for all types of transports and systems

Tracking and management of Non-ABAP objects with Quality Gate Management and

Change Request Management

The open issues are addressed with the Enhanced Change and

Transport System

459

Enhanced Change and Transport System (CTS+)

Connect Non-SAP Systems to standard CTS

Non-SAP applications inherit all properties of the ABAP Change and Transport

System in terms of documentation, tracking and troubleshooting features

Manage transport of ABAP and non-SAP objects centrally

Allows combined transports for mixed objects (ABAP, JAVA, …)

Allows synchronized changes to business processes which run in ABAP and

JAVA




JAVA

100% Compatible with SAP Solution Manager No need for upgrade of Java landscapes

460

Development Environments

Change and Transport System

Developer

Studio and

ExchangeInfrastructure

Integration

Builder

ABAP

Workbench

SE80 Development

Landscape

Quality

Landscape

Production

Landscape

Quality

Component 1

Production

Component 1

. .

Transport Transport

Deploy Deploy

SCA

TPZ




NWDI

Quality

Component n

Production

Component n

.

.

.

.

.

.

SAP BOE

ZIP

…(open Interface for non-

ABAP objects)

461

Enhanced CTS – Supported Object Types

The ABAP Change and Transport System (CTS) has been enhanced with SAP

NetWeaver 7.0 SPS 12 to be capable of transporting non-ABAP objects.

Supported object types (check release notes for details)

Java-based and JEE-based objects

– Software Component Archives (SCAs)

– Software Deployment Archives (SDAs)

– Enterprise Application Archives (EARs)

– DTR-Activities in NWDS (DIPs)

Portal-based objects

– Enterprise Portal Archives (EPAs)

Please check the

system requirements to

see which SP level is

needed to support the

object type




Enterprise Portal Archives (EPAs)

– Portal Archives (PARs)

– KM Documents and Configurations PI/XI-based objects

– Integration Repository design objects, Integration Directory configuration objects, ABAP Mappings

SLD Objects

MDM (specific set of data model objects)

SAP Business Objects Lifecycle Manager

Any Files (.doc, .xls, .xml, …)

462

Transporting Non-ABAP Changes

Legend

logical transport route of non-ABAP objects

physical transport route of non-ABAP objects

check-in/check-out of non-ABAP objects

transport route of ABAP objects

ABAP

Transport

Controller

Non-ABAP

Virtual QAS Virtual PRD

DEV PRDQAS

SAP NetWeaver Application Server CTS+

Non-ABAPNon-ABAP




New System Type:

Virtual Non-ABAP System

Transport parameter

contain deploy options

463

What is CTS+ - Using CTS+ - Systems involved

SAP Solution

Manager

ABAP JAVA

Export Client to

attach Objects to a

Transport Request

execute import e.g.

by deploying via SDM

or Deploy Controller

provide requests to source system,

trigger import services in target system




ABAP

Deploy WS Client

Transport Organizer

(Web UI)

Transport

Directory

JAVA

Deploy WS TargetSystem(s)

Import Service

Source SystemSource System

Export Client

464

Terms

Loose Coupling

No direct integration of CTS+ mechanisms into application

Additional tool needed to create transport requests, attach files and release transport

orders

Manual attachment of files to transport requests via file upload

Close Coupling

CTS+ mechanisms are available via additional buttons, links and input-fields within the

existing export UIs

Automatic attachment of files to transport requests directly within the application (e g EP




Automatic attachment of files to transport requests directly within the application (e.g. EP,

PI, NWDI, SLD etc.)

Get default transport requests

Automatic creation of transport requests possible

Automatic release of transport request possible

Connection from application server

to CTS server

Ex

TR

465

The Transport Organizer Web UI

Is an ABAP Web Dynpro Application

Has to be used to handle Transport Requests for

non-ABAP objects / systems

Don’t use SE09 Is integrated in Applications (PI, NW DI, Portal)

Provides features for Transport Requests

– Create

– Set as default




Set as default

– View attached objects – Attach objects

– Release

– …

466

How to start the Transport Organizer?

Link in STMS

PI – Integration

Builder

Link in

A li ti

Two options




Or create a Browser Favorite Portal

Applications

467

Web UI - Process

4.

2

1.




2010

1 Create Change Request

2 Attach Object

3 Optional: Display Request

4 Release

3.2.

468

Tracking of Changes

Use the Import History to find information on transports in Non-ABAP systems:

Object Lists

Transport Log files

The Import History can be called from any system in the Transport Domain




469

Import History of Non-ABAP System




470

Navigate into the Object List




471

Import / Deployment Protocol

New Step: Deployment

Import of metadata (e.g.

object lists) into the

ABAP stack




SDM protocol is

embedded in here

New Step: Deployment

Done via Deploy Web Serviceand e.g. SDM

472

Navigate through the Transport Logfiles (Java)




473

Agenda

CTS+ Overview

CTS+- What‘s new

SAP Business Objects with CTS+

SAP HANA with CTS+




474

© SAP 2009 / Page 21

CTS+ - what is new?One Transport Tool for Multiple Content Types

Multiple

Development

Workbenches

SAP NetWeaver

AS JavaXI/PI System

SAP NetWeaver

AS ABAP

SAP NetWeaver

AS JavaXI/PI System

SAP NetWeaver

AS ABAP

Portal Systemon SAP NetWeaver

AS Java

NWDIon SAP NetWeaver

AS Java

ESR/PI/XI

Systemon SAP NetWeaver

(D l St k)

SAP NetWeaver

AS ABAP

Multiple

Types of

Backends

...

...

...

...




Enhanced CTS

(Dual Stack)

One central

Transport

Tool

475

CTS Plug-InThree Steps to get the new Functionality of CTS+

1 2 3

Download CTS Plug-In

from ServiceMarketplace

(is part of SL Toolset) Activate CTS Plug-

In




Install CTS Plug-Inon your SAPSolution Manager

476

CTS Plug-InPrerequisites

To be able to use the new functionality of CTS+, some prerequisites apply:

CTS+ System:

SAP Solution Manager has to be the CTS+ System – CTS Plug-In can only be installed

on SAP Solution Manager.

SAP Solution Manager 7.1 with CTS Plug-in of SL Toolset 1.0 SP3

SAP Solution Manager 7.0 EHP1 SP 25 with SP2

.

Applications to be used with CTS+:




pp

CTS+ integration provided by SAP (e.g. for Lifecycle management console for SAP

BusinessObjects BI 4.0):

CTS+ Integration provided by vendor – or done by you

477

CTS Plug-InInitial Installation

Your Company

SAP Solution

Manager

Download

Bootstrapper

Plug-In

Server Plug-In

CTS Plug-In

SPAM /SAINTServices Plug-

In




SAP AG

SAP ServiceMarketplace

Download Area

478

CTS Plug-In Activate new Functionality of CTS+

To activate for the first time

Call transaction SA38 on your SAP Solution

Manager

Run the program

/CTSPLUG/CTS_ACTIVATION .

SAP Solution

Manager

SAP Solution

1.

2.




CTS Bootstrapper Plug-In, CTS Server andServices Plug-in are imported into your SAP

Solution Manager

Manager

No Activation required in case of updates – just install the current

plug-in

Bootstrapper

Plug-In

Server Plug-In

Services Plug-In

479

Agenda

CTS+ Overview

CTS+- What‘s new


SAP HANA with CTS+




480

Using CTS+ with LCMLifecycle management console for SAP BusinessObjects BI (LCM)

Is made for moving content from a

source system to a target system

Database connection, overrides and

mapping

Check dependencies between

BI objects and BW queries

Test the promotion

Auditing

Roll Back

Creating Job Schedules




Creating Job Schedules

Offers integration with version control

481

Using CTS+ with LCMPrerequisites

To be able to use CTS+ with LCM in close coupling mode, some prerequisites

apply:

CTS+ System:

SAP Solution Manager with CTS Plug-In installed

SAP BusinessObjects BI

SAP BusinessObjects BI 4.0

LCM Frontend running on SAP NetWeaver




482

CTS+

Orga-

nizer

CTS System

Landscape

Deploy

WS


Admin

L

C

M

Front-

end

SAP

NetWeaver AS

Java

Deploy

Client

ABAP Java

Using CTS+ with LCMLandscape – What runs where?

1.

2.

5.

4.

3.




BOTarget

L

C

M

Back

-end

SAP Business

Objects BI

BOSource

L

C

M

Back

-end

SAP Business

Objects BI

BOTarget

L

C

M

Back-end

SAP Business

Objects BI

483

Using CTS+ with LCMLandscape - Transporting BOE Content

TMS System-Landscape Configuration – Representation of BOE Systems

TD1

(DEV System)

Promote

via CTS

Job

Transport

Request

Transport

Request

Transport

Request

ZIP

Transport

Request

Transport

Request

Transport

Request

ZIPApplication

Type

BOLM

Application

Type

BOLM

TD2

(Test System)

XYZ

(Prod System)

Transport

Organizer

Web UI

Promotion

of Jobs

Start the import

in TMS to

process the job

Start the import

in TMS to

process the job

2.

4. 5.

3.




BOE Systems

TEST

TD2TD1

TEST

XYZ

Collect

data

of Jobs

TD1 TD2 XYZ1.

484

Agenda

CTS+ Overview

CTS+- What‘s new


SAP HANA with CTS+




485

Using CTS+ with HANAPrerequisites

To be able to use CTS+ with HANA some prerequisites apply:

CTS+ System:

SAP Solution Manager with CTS Plug-In installed

SAP HANA

SAP HANA




486

CTS+

Orga-nizer

CTS System

Landscape

Deploy

WS


DeployClient

ABAP Java

34

2

Using CTS+ with HANALandscape – What runs where?

1




HANASource

HANA

SAP HANA

HANATarget

HANA

SAP HANA

HANATarget

HANA

SAP HANA

487

2.

4.

Using CTS+ with HANALandscape - Transporting HANA Content

TMS System-Landscape Configuration – Representation of HANA Systems

TD1

(DEV System)

Attach Files to

CTS+

Model

Transport

Request

Transport

Request

Transport

Request

Transport

Request

Transport

Request

Transport

Request

Application

Type

FILE

Application

Type

FILE

TD2

(Test System)

TD3

(Prod System)

Transport

Organizer

Web UI

Promotion of

Data Model

Start the import

in TMS to

process the File

Start the import

in TMS to

process the jobSAP HANA Studio

Start the import

3.

5

6.

7




1.

HANA

TEST

TD2TD1

TEST

XYZ

Collect

data

Data Model

TD1 TD2 TD3

Start the import

via SAP HANA

Studio

Start the import

via SAP HANA

Studio

5. 7.

488

Using CTS+ with HANASAP HANA Studio for SAP HANA

Is made for moving Data Model from a source system to a target system

Attribute view

Analytic view

Calculation view

Analytic Privileges

Procedure




489

Agenda

Exporting and Importing with SAP HANA via SAP HANA Studio Client-side export/import: to/from Client PC via SAP HANA Studio

Server-side export/import : to file system of SAP HANA Database server

We will cover only client side export / import of Information Models

Export / import tables as CSV files




490

Exporting and Importing of SAP HANAStart/Import Wizard




491

Client Export of Information ModelsCreation Wizard




492

Client Export of Information ModelsSelect views and Analytic Privileges to export




493

Client Export of Information ModelsSpecify the export location




494

Client Export of Information ModelsVerify the export




495

Client Import of Information ModelsImport Wizard




496

Client Import of Information ModelsSelect source folder




497

Client Import of Information ModelsSelect objects to import




498

Client Import of Information ModelsRun the import




499

Client Import of Information ModelsConsiderations




500

Export / Import of TablesConsiderations




501

CSV Export of TablesChoose export format and export location




502

CSV Export of Tables

Check exported files




503

CSV Import of Tables

Enter export location and table names




504


Run the import




505


Using SQL Statements




506

Further Information

SAP Public Web:

SAP Service Marketplace: http://service.sap.com/changecontrol

SAP Enhanced Change and Transport System:

Central Note: 1003674




507

Summary


Explain how the Enhanced Change and Transport System (CTS+) works

Understand the basic concepts of SAP BOE, SAP HANA and how they are

supported by CTS+ Know best practices for the setup and usage of CTS+ for SAP BOE and SAP

HANA




508

Updating SAP HANA



509

SAP HANA Update & Patching

OS patching

Pre-validated HW/OS stackconfigurations reduce risk ofoperating system SP update

SP Stack Update

Implementation of SAPHANA SP Stack can bedone automated using the

Patching Revisions / SPs

The implementation ofintermediate patches /revisions / SPs, for exampleof the SAP HANA database




while leaving flexibility toimplement importantsecurity patches released bySuSE as soon as they arereleased.

SAP Software UpdateManager for SAP HANA(SUM for SAP HANA),available with SL Toolset 1.0SP02

of the SAP HANA databasecomponent can be doneindividually following thecorrespondingdocumentation available athttps://help.sap.com

510

SAP HANA SP Stack Update

SAP Software UpdateManager (SUM) for SAP HANA

integrates into the look and

feel of SAP HANA monitoring

and administration by being

managed from inside SAP

HANA studio

The Software Update Manager for SAP HANA …

provides automated SP Stack update procedure from within SAP HANA studio.




SUM for SAP HANA supportupdates of all kinds of different

components included in a SAP

HANA support package stack,

while e.g. not relying on other

on-site ABAP infrastructure.

511

The Lifecycle Management perspective within SAP HANA

studio

Update your SAP HANA system from

inside SAP HANA studio

Once installed, SAP HANA systems can be

easily added to SAP HANA studio bychoosing

‘Add System…‘ from the context menu inside

the navigation view.

SAP HANA studio supports multiple SAP

HANA systems to be added and operated

from within one SAP HANA studio

installation




installation.

Within the context menu of any system,

chose

‘Lifecycle Management’ to open the LM

perspective, serving as front-end for the SW

Update Manager

512

Step1: One-click download of SAP HANA SP Stacks

click 1.




513

Step2: One-Click Update of SAP HANA appliance software

click

click 2.




514

SAP HANA SP Stack Update – Process Description

SAP HANA appliance software

SAP HANA database & client

SAP HANA studio repository

SAP HANA load controller

SAP Host

Agent

SUM for SAP

HANA

Maintenance Optimizer

Service Marketplace

Internet




SAP HANA studio(Eclipse)

LM

perspective

All remote connections are done via secure web services.

1. Perform Software Update Manager for SAP HANA self-update

2. Detect components in the SAP HANA landscape

3. Get latest SP stack information from SMP

4. Download required component updates

5. Update components on the SAP HANA system

515

Built-in SAP HANA studio P2 update repository

Allows you to configure

your local studio

installations to use the

SAP HANA system as

central source for

updates

Each time the SAP

HANA system is being

updated, also the

studio installations on

the clients will get

offered to be updated.




516


Summary