sap hana sps08 application lifecycle management

Use this title slide only with an image

SAP HANA SPS 08 - What’s New? SAP HANA Application Lifecycle Management

SAP HANA Product Management May, 2014

© 2014 SAP AG or an SAP affiliate company. All rights reserved. 2Public

Agenda

Overview

Model, Develop and Transport an Application

Command Line Tool

Install, Assemble and Configure an Application

Configuration

Prerequisites

Roles & Authorizations

Evolution of HALM

Summary


Agenda

Overview


Command Line Tool


Configuration

Prerequisites


Evolution of HALM

Summary


An Application’s Lifecycle in SAP HANA

Your ContentProducts or delivery units

Based on changes or complete entitiesUsing CTS+ or SAP HANA native

Your ApplicationConfiguration contentEnabled for mass operation and cloud automation

Your ApplicationBundle object changes via automatic recording

Lock objects individually or for teamsRelease changes when ready for transport

Your Product StructureDefine product structure incl. delivery unit and package assignmentView and analyze dependencies for DUs

Your ProductValidate and assemble your product automatically to ensure consistency

and ship efficientlyCreate patches and support packages

for your application

Your ProductDownload from SMPInstall /update /uninstall

New / Labs Preview

Labs Preview

Labs

Preview


SAP HANA Application Lifecycle Management

Is part of XS (SAP HANA Extended Application Services)

Is easy to use

Can be configured based on your preferences

Can be launched immediately after SAP HANA installation:http://<server>:80<instance>/sap/hana/xs/lm

Requires role assignment (details later)


Content lifecycle management in SAP HANAManaging “content” in SAP HANA

SAP HANA content defined: Not part of the core SAP HANA DB installation itself Is delivered by SAP as part of SAP HANA optimized solutions Is created in SAP HANA-based development projects (partner, customer) Sometimes called “objects” or “artifacts”

Content comprises all kinds of objects, for example: Schemas and table definitions defined as HANA Content Attribute views, analytic views and calculation views Procedures and privileges SQLScript, JavaScript and HTML Roles and permissions


Flow of Activities: User Interfaces

Change Recording

(View)

Development, Object Activation and Change Selection

HANA Studio

Web IDE

Change Recording(Browser)

Development, Object Activation and Change Selection

Native & CTS

Transport(Browser)

Modeling(Browser)

Assembly(Command

Line)

HANA Application Lifecycle Management

HANA Application Lifecycle Management

Installation(Command

Line)


Agenda

Overview


Command Line Tool


Configuration

Prerequisites


Evolution of HALM

Summary

ModelProduct

Delivery Unit

Package


Introducing Delivery Units, Packages, and Development Artifacts

1 Product : n Product Instances : m Delivery Units

1 Delivery Unit : n Packages

1 Package : n Objects

___________________________________

1 Object : 1 Package

1 Package : 1 Delivery Unit

1 Delivery Unit : 1 Product Instance : 1 Product

Product Instance Y

Package a

Object 1

Object 2

...

Package b

Object 3

Object 4

...

Delivery Unit I

…

…

…

...

Delivery Unit II

…

Package d

Object 8

Object 9

Package e

Object 10

Object 11

…

…

…

Product Instance Z

Product A

…


Integration into SAP HANA Studio

Easy access to product management capabilities in SAP HANA studio:

Development perspective, repositories view > right mouse click on the workspace >

choose Product Management or Delivery Unit Management


Model ProductProduct View

A product corresponds to an application – which could be an SAP-delivered application, a partner application, or customer application developed on a project basis

The Product View

• Shows installed products (i.e. applications) and their metadata in the system

• Ability to create, modify, and remove SAP HANA products (meta-data only)

• Is used to associate Delivery Units with a product instanceand remove them


Model ProductWhat & Where

What to do to create a product

• Go to PRODUCTS Products

• Define• Name• Version• Description• Instance

New in SPS08

= New for SPS08


List of Products

Actions on

products

Assign and unassign

delivery units

Model ProductProduct View

Product metadata section

Delivery Units assigned to instances

New in SPS08


Model ProductAssign Delivery Unit

What to do to assign a delivery unit to a product

• Go to PRODUCTS Products

• Select your product

• Select an Instance

• Assign the delivery unit

New in SPS08


Model ProductChange Delivery Units assigned

What to do to change a DU assignment

• Unassign• Go to the Product Instance the Delivery

Unit is currently assigned• Choose the DU and unassign it

• Assign• Go to the Product Instance to which you

would like to assign the DU• Click assign to choose the DU


Model Delivery UnitDelivery Unit View

The Delivery Unit view:

• Shows installed Delivery Units and their metadata

• Ability to create, modify, and remove Delivery Units (metadata only)

• Un-deploy (remove) delivery units

• Assign packages to Delivery Units and unassign them

• View Delivery Unit dependencies and object references causing dependencies


Model Delivery UnitWhat and Where

What to do to create a Delivery Unit

• Go to PRODUCTS Delivery Units

• Define• Name• Version• Description• Responsible


List of installed Delivery Units

Search field

Delivery unit dependencies

Actions on delivery units

Assigned packages

Actions on packages

Model Delivery UnitDelivery Units View

Delivery Unit metadata section


Model Delivery UnitAssign Package to Delivery Unit

What to do to assign a package to a delivery unit

• Go to PRODUCTS Delivery Units

• Choose your delivery unit (if not pre-selected)

• Assign the package(s) that you created(include sub-packages if needed)

• You can check for unassigned packages


Model Delivery UnitCheck for “forgotten” packages

Packages not assigned to a Delivery Unit

• Lead to issues during product assembly and installation

• Select Check for Unassigned, and assign them accordingly


Model Delivery UnitUninstalling a Delivery Unit

Delete or uninstall a delivery unit

Deleting means that only the DU metadata will be deleted but all packages and tables remain intact.

Uninstalling means that all DU metadata and all objects, packages, and possible database tables will be removed.


Dependency Viewer

Graphical tool to display dependencies between delivery units: Graphical depiction is interactive –

can be rotated and shifted around to provide different perspectives

Useful for determining which delivery units should be transported together

Useful for detecting unwanted dependencies, in order to clean them up


Model Delivery UnitDependency Viewer – Object References

Move the mouse over a connector to view object references causing the dependency between delivery units.

Dependencies are caused by object references between objects

Example:

• Deliver Unit 1 contains tables

• Delivery Unit 2 contains viewsreferencing the tables of Delivery Unit 1

Delivery Unit 2 depends on Delivery Unit 1


Model Package: Package View

The Package view

• Shows installed packages, their hierarchy and their metadata

• Allows to create, modify, and delete packages


Package concept

Package Every SAP HANA repository object is assigned to a package Groups objects that logically “belong together” Provides a namespace

– Each object is uniquely identified by combination of package name, object name, and object type

Package Hierarchy Establishes a parent-child relationship between packages Used to organize objects

Package Privileges Define access to objects in package; assign to specific user or role Authorizations assigned to a package are implicitly assigned to sub-packages in the hierarchy


Model PackageWhat & Where

What to do to create a Package

• Go to PRODUCTS Packages

• Define• Name• Description• Responsible• Original Language


Package metadata

Hierarchical package

view

Model PackagePackage View

Actions for packages


Model PackageCreate Application

Create an application

• Choose the options that you need Require authentication create a schema developer role create project create index.html overwrite existing objects

• Objects are created automatically, providing a fast start to the application development process.

Develop


Creating ContentWhat & Where

Create Content (i.e. development artifacts) in SAP HANA Developer Studio

Example from Modelling view:

• Refresh the Content folder in your development system

• Choose your package

• Create your content

Alternatively, you can create SAP HANA Content in the Web IDE


Change Recording in SAP HANA

Change recording …is the infrastructure to record changes during development

Change recording provides:• Automatic recording and grouping of object changes• Decoupling of activation and transport• Predecessor calculation of changes

Change Recording…can be enabled as global system setting in your development environment


Change RecordingConcept

Without change recording: Delivery Unit transport contains all active objects in the packages of that particular DU If an object is ready to be transported, its Delivery Unit must be released

– Some objects in the DU may not be ready for transport yet though, but they automatically get transported anyway

With change recording: Automatic recording of object changes to a change list when an object is activated Team Development: Allows a developer (or team) to work on a development artifact and release the

“change” only when the artifact is ready to promote to the test system. For developers not contributing to this change the objects are locked

Release in two steps: contributors have to approve first before a change can be released Transport: Delivery Unit transport contains only objects where their change has been released

D033035

What do you mean by 'released'? You can transport the Du along the defined transport route. I don't know of any additional step to release it


Change RecordingWhat & Where

Changes in HALM

• Select CHANGES

• Filter results if needed (default filter is applied)

• Work with the changes

Changes in SAP HANA Developer Studio

• Open Change Manager view

New in SPS08


Change RecordingEnable Change Recording

Setting the option Enable Change Recording

adds the menu entry CHANGES

Released Changes for all active objects will be

created when Change Recording is first enabled

New in SPS08


Change RecordingChanges in HALM

Details for Change

Actions for changes

List of Changes

List of Contributors

Filter Changes

Changed objects

New in SPS08


Change Recording

Automatic recording of object changes to a change list when doing the object activation

Team Development: Allows a developer (or team) to work on a development artifact and release the “change” only when the artifact is ready to promote to the test system. For developers not contributing to this change the objects are locked.

Release in two steps: contributors have to approve first before a change can be released.


Change RecordingChange Manager View in SAP HANA Studio

Filter for changes

Actions for Changes

List of Contributers

Changes that match your selection

Changed Objects

Transport


SAP HANA content exclusively used by ABAP(ABAP for SAP HANA)

Native SAP HANA content or as part of a solution (BI, Mobile, …)

Native SAP HANAcontent

SAP HANASource

Transport scenarios for SAP HANA content

SAP HANA Application Lifecycle Management SAP HANA stand-alone transport management

No need for ABAP-footprint

Lightweight and easy-to-use transport tool

SAP HANA Target

Use case Transport Management

Enhanced CTS (CTS+) Transported as any other non-ABAP content

Integrated in existing CTS transport landscape

Integrated in SAP process tools (ChaRM, QGM)

HANA Transport Container Transported with standard ABAP transports

Integrated in existing CTS transport landscape

Integrated in SAP process tools (ChaRM, QGM)


Transports: Integration into SAP HANA Studio

Easy access to transport management capabilities in SAP HANA studio:

Development perspective, systems view > right mouse click on the system

select Transport Management from the menu


Native SAP HANA ContentWhat and Where (1/2)

What to do to make a system known

• Log on to the target system

• Go to TRANSPORT System

• Check whether the source system exists

or

• Register the source system

Changed in SPS08


Native SAP HANA ContentWhat and Where (2/2)

What to do to transport content

• Go to TRANSPORT Transports

• Create a route covering your needs

or

• Choose the route you need

Changed in SPS08


Native SAP HANA ContentBasics for Transports

Target Group New SAP customers without ABAP-footprint SAP customers with the need for a lightweight transport management

What to use Content Creation: SAP HANA Studio (source system) Transport: SAP HANA Application Lifecycle Management (target system)

Granularity Full Deliver Unit / Product (without Change Recording) Full Released Delivery Unit / Product (with Change Recording enabled) Change (with Change Recording enabled)

D033035

I changed the 'Granularity' section completely - you are right 'delta DU' is removed. The option for Product-based transport was added


Native SAP HANA ContentTransport Landscape

Test ProductionDevelopment

HND

Content

HNQ

Content

Transport Route

HNP

HALM

Content

Transport Route

HALM1. Request content

Export

Import Activate

Import ActivateExport 2. Content

Provided 2. Content Provided

ApplicationLandscape

1. Request content


Native SAP HANA ContentConfiguration

Configure native SAP HANA Transport

• Go to SETTINGS

• Set Enable Native HANA Transport

This is the default setting

New in SPS08


Native SAP HANA ContentConfiguration

The menu entry TRANSPORT is only available if Native SAP HANA Transport is enabled

New in SPS08


Native SAP HANA ContentCreate Transport Route

The route management is an essential parttransport management.

Route definition for transport on target system:

Source & target system

which Delivery Units (multi-select available)

Select transport all objects (Full Released) or just released changes (Change)

Select DU Transport or Product Transport

The route definition can be specified in a static way or during each transport.

Changed in SPS08


Native SAP HANA ContentTransport based on Changes

Transport based on released changes: only objects which are assigned to a released change are transported

Object transport: Selecting a single change from the list of changes imports only objects involved in this change into the target system –not the full delivery unit.

Dependency calculation: Automatically grabbing depending changes as part of the transport too.


Transport via CTS+Basics for Transports

Target Group SAP customers with ABAP-footprint and existing CTS transport landscape SAP HANA content is handled like any other non-ABAP content

What to use Content Creation: SAP HANA Studio (source system) Export: SAP HANA Studio (source system) Transport: Transport Organizer Web UI (for source system) / STMS (for target system)

Granularity Delivery Unit Change


SAP HANA Studio

TestDevelopment

Transport via Change and Transport System (CTS+)Transport Landscape

HNQ HNP

ApplicationLandscape

CTS System

Transport Transport

ImportImport

Transport Request

Transport Request

Transport Request

HND HNQ HNP

Production

HND

Repository

Objects

HALM

Attach

Repository

Objects

Repository

Objects

New in SPS08


Transport via CTS+Configuration

Go to SETTINGS

Select Enable CTS Transport

Enter Data of your CTS System

(Additional Configuration on CTS System is required)

New in SPS08


Transport via Change and Transport System (CTS+)Configuration

• Menu entry CTS EXPORT is only shown if CTS Transport is enabled

• (Menu entry TRANSPORT is removed)

• Transports can be done on DU or Change level

New in SPS08


Transport via Change and Transport System (CTS+)What & Where

What to do to transport content

• Log on to the source system

• Go to CTS Export

• Transport Delivery Units

or

• Transport Released Changes

New in SPS08


Transport via Change and Transport System (CTS+)Export Process in SAP HANA Studio

Choose transport via Delivery Units or Released Changes

SelectAttach to Transport Request

Check Transport Request Details

Click on Next and then Finish

File Export Change and Transport System (CTS) or Modeler Export

Click on Next

Choose System

Changed in SPS08


Transport via CTS+Transport Organizer for non-ABAP

Click icon to add picture

Transport Organizer for non-ABAP is used to:• Create Transport Requests

• Preselect requests

• Release requests

• Monitor or change content of requests

• Maintain attributes

• Monitor status

• View logs


Transport via CTS+Import Process in TMS

Choose queue of your target system

Import the request(s) and check the result


Agenda

Overview


Command Line Tool


Configuration

Prerequisites


Evolution of HALM

Summary


SAP HANA Database Client Installation

Command Line Tool

• can be installed locally

• Can run on Server

New in SPS08


Open the Command Line Tool

hdbalm

Commands: product admin update dependencies install du Transport log help

New in SPS08


Command Line Support for Delivery Units

All operations available from the delivery unit view are available through the command line

In addition a full dependency report is available to show all relevant dependencies between delivery units.

C:\halm>halm.py help dependenciesView and analyze delivery unit dependencies.usage: halm [<args>] dependencies [<command args>] [<source du>] [<source du vendor>] [<target du>] [<target du vendor>]command args: -f, --full show full dependency view and analysis -r, --references shows object references between delivery units -n, --nirvana shows nirvana references for a delivery unit

notes:The references command requires source and target du name as well as theDU vendor.

The nirvana command displays object references for objects that are part ofa delivery unit to objects which are not part of a delivery unit. Whenexported it will not be possible to import and activate these deliveryunits into another system. Those reference therefore pose a serious problem.

With no arguments a list of delivery unit dependencies will be displayed.Each line of the output lists a delivery unit followed by a colon and acommand separated list of referenced delivery units. In the following examplethe delivery unit HANA_XS_LM has references to SAPUI5_1 and HANA_XS_BASE:

HANA_XS_LM(sap.com): SAPUI5_1(sap.com), HANA_XS_BASE(sap.com)

New in SPS08


hdbalm transport

list

start

New in SPS08


hdbalm product

list

get

create

delete

New in SPS08


hdbalm dependencies New in SPS08


Agenda

Overview


Command Line Tool


Configuration

Prerequisites


Evolution of HALM

Summary

Assemble


AssembleWhat You Should Know

Currently only available for SAP-internal usage

Planned for Customers and partners for a future release

Planned to support you in creating a file out of your product that can be delivered to your (internal or external) customers

Labs Preview

Install


Install an Application

Use Command Line Tool; Install one or several product instances

Checks that all pre-requisites are met for installing the product (correct SAP HANA version, other products as a pre-requisite)

Possibility to select single product instances for installation

Installs all delivery units and creates product metadata

Command line based installation

New in SPS08


Installation Transcript

C:\dev\test>hdbalm install SAP_HANA_EXPLORER_WEB.zip

SYSTEM INFORMATION___________________________________________________________________________HOST : ld2020PORT : 8045USER : dirkINSTANCE : 045___________________________________________________________________________

PRODUCT INFORMATION___________________________________________________________________________| NAME : SAP HANA EXPLORER WEB| VERSION : 1.0| VENDOR : sap.com___________________________________________________________________________

PRODUCT INSTANCES FOR INSTALL___________________________________________________________________________| No.| Instance Id | Product Instance___________________________________________________________________________| 1 | 1 | SAP Lumira Server (EA) 1.0___________________________________________________________________________

Validating Product Descriptor.Validation successful.

SAP HANA EXPLORER WEB___________________________________________________________________________| | INSTALLED | TO BE INSTALLED___________________________________________________________________________|PRODUCT VERSION| NOT YET INSTALLED |1.0|SP VERSION | NOT YET INSTALLED |Initial Shipment Stack___________________________________________________________________________

SAP Lumira Server (EA) 1.0___________________________________________________________________________INSTALLED VERSION | TO BE INSTALLED | IMPORT | DELIVERY UNIT___________________________________________________________________________|NOT YET INSTALLED | 1.0.000.0 | YES | HANA_EXP_WEB___________________________________________________________________________

Do you wish to continue with the installation for the specified product?[yes/no]-->yes

Installing Delivery Units.

[…]

Updating Repository Tables.Update successful.

Installation process is complete.

New in SPS08


Product Installation

Install and uninstall products via Command Line tool

Functionality moved from SAP HANA Platform Lifecycle Management to HALM

No <SID>adm required any more

New in SPS08


hdbalm install

Command:

install

Optional parameters to

Display product instance information

Install specified Product instance(s)

Required parameter to

Specify installation file location

New in SPS08

Configure Planned for future releases


Technical Configuration Today

Application Configuration (specific)

Hana Live Configuration Configuration is documented in

installation guide

Manual description of SQL statements to configure application

SCENARIO PROCESS

Application Configuration (general) Typically found on service

market place/instguides

Configuration Process

Administrator reads documentation

Administrator performs tasks

1 1 NN

Steps

SERVICE

Tasks

https://websmp110.sap-ag.de/~sapdownload/011000358700000476572013E/HBA_Jan_27_2014.pdf

https://websmp110.sap-ag.de/instguides

https://websmp110.sap-ag.de/instguides


Technical Configuration (planned)

Application Developer

Understanding scenarios and their content contribution requirements

Providing content for configuration automation

Lifecycle Experts

(Cloud Infrastructure Experts)

Defining scenarios

Documentingscenarios

Administrators or

Orchestration Tools Executing configuration

services

Orchestrating end2end and/or cloud processes

SCENARIO PROCESS1 1 NN

Steps

SERVICE

Tasks

Labs Preview


Agenda

Overview


Command Line Tool


Configuration

Prerequisites


Evolution of HALM

Summary


Set vendor

Vendor must be set before you start creating SAP HANA Content

You can change the vendor later on


Agenda

Overview


Command Line Tool


Configuration

Prerequisites


Evolution of HALM

Summary


System requirements

For SAP HANA Application Lifecycle Management – Part of each SAP HANA shipment as of SAP HANA appliance SP06

For Transporting SAP HANA content with enhanced CTS (CTS+)– CTS+ Domain Controller: SAP Solution Manager 7.1 SP05 and higher support package levels

or SAP NetWeaver 7.31 with SL Toolset 1.0 SP07 and higher support package levelsor SAP NetWeaver 7.4 with SL Toolset 1.0 SP07 and higher support package levels

– SAP HANA systems: SAP HANA Appliance SP05 and higher support package levels

For Transporting SAP HANA content with HANA Transport Container– SAP NetWeaver 7.40 SP0 and higher support package levels– SAP NetWeaver 7.31 SP5 and higher support package levels


Agenda

Overview


Command Line Tool


Configuration

Prerequisites


Evolution of HALM

Summary


Roles

The following roles exist for the SAP HANA Application Lifecycle Management:

• Administrator

• Developer

• DevelopmentExpert

• Display

• Execute Transport

• Transport

Additional roles for SAP HANA Repository are required

New in SPS08


Agenda

Overview


Command Line Tool


Configuration

Prerequisites


Evolution of HALM

Summary


Availability of features in SAP HANA

+ Ship configuration + Allow configuration dev

+ DU/Products via HALM & CTS+ in Studio

+ Change Transport (HANA native)

+ Change Transport (via CTS+)

+ CTS+ without AS JAVA

+Basics in HALM + Dependency Viewer + Improved UIs

+ Via CLT + via Web UI

+ For customers and Partners

+ Change Recording via HANA Studio

+ Change Recording via WebIDE & HALM

CLT: Command Line Tool

HALM: SAP HANA Application Lifecycle Management

Model

Develop

Transport

Install

Assemble

Configure

SP7 SP8 FutureSP6

Labs Preview


Agenda

Overview


Command Line Tool


Configuration

Prerequisites


Evolution of HALM

Summary


Key Takeaways for SAP HANA Application Lifecycle Management

What do we provide?HALM as tool to manage the Lifecycle of SAP HANA XS Applications

When?Available since SAP HANA 1.0 SPS06

For whom?• Easy to use, lightweight application with native SAP HANA transport for customers with none or

little ABAP footprint, or who simply prefer it’s streamlined approach• Comprehensive transport handling with CTS+ for customers who prefer to integrate SAP HANA

transports into existing promote-to-production processes


Further information

SAP Public Web

http://www.saphana.com/docs/DOC-4268 > What´s new in SAP HANA 1.0 SPS07 for Extended Application Services (XS)

and Content Lifecycle Management

http://scn.sap.com/community/hana-in-memory >

http://scn.sap.com/docs/DOC-46119 > SAP HANA Lifecycle Management

http://scn.sap.com/docs/DOC-49327 > Overview of SAP HANA Content Transport Management

http://scn.sap.com/docs/DOC-8576#HANA > How to Configure SAP HANA for CTS+

http://www.saphana.com/community/about-hana/features#administration/application-lifecycle-management > HALM@ saphana.com

SAP Internalhttps://wiki.wdf.sap.corp/wiki/display/SDT/HANA+Application+Lifecycle+Management

SAP Notes1920406 - Release Note SAP HANA Application Lifecycle Management SP7

1998966 – Release Note for SAP HANA Application Lifecycle Management SP8

http://www.saphana.com/docs/DOC-4268

http://scn.sap.com/community/hana-in-memory

http://scn.sap.com/docs/DOC-46119



http://www.saphana.com/community/about-hana/features

https://wiki.wdf.sap.corp/wiki/display/SDT/HANA+Application+Lifecycle+Management

http://service.sap.com/sap/support/notes/1920406







Further information

SAP Public Web

SAP HANA Master Guide: http://help.sap.com/hana/SAP_HANA_Master_Guide_en.pdf SAP HDB Client Installation Guide: http://help.sap.com/hana/SAP_HANA_Client_Installation_Update_Guide_en.pdf SAP HANA Studio Installation Guide: http://help.sap.com/hana/SAP_HANA_Studio_Installation_Update_Guide_en.pdf SAP HANA Developer Guide: http://help.sap.com/hana/SAP_HANA_Developer_Guide_en.pdf SAP HANA Server Installation guide: http://help.sap.com/hana/SAP_HANA_Server_Installation_Guide_en.pdf SAP HANA LCM Tools Reference Guidehttp://help.sap.com/hana/SAP_HANA_LCM_Tools_Reference_Guide_en.pdf

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

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

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

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

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

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


Disclaimer

This presentation outlines our general product direction and should not be relied on in making a purchase decision. This presentation is not subject to your license agreement or any other agreement with SAP.

SAP has no obligation to pursue any course of business outlined in this presentation or to develop or release any functionality mentioned in this presentation. This presentation and SAP’s strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice.

This document is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP assumes no responsibility for errors or omissions in this document, except if such damages were caused by SAP intentionally or grossly negligent.


How to find SAP HANA documentation on this topic?

SAP HANA Platform SPS What’s New – Release Notes

Installation– SAP HANA Server InstallationGuide

Security

Administration– SAP HANA Administration Guide

Development– SAP HANA Developer Guide

References – SAP HANA SQL Reference

• In addition to this learning material, you find SAP HANA documentation on SAP Help Portal knowledge center at http://help.sap.com/hana_platform.

• The knowledge center is structured according to the product lifecycle: installation, security, administration, development. So you can find e.g. the SAP HANA Server Installation Guide in the Installation section and so forth …

http://help.sap.com/hana_platform



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



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


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


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


© 2014 SAP AG or an SAP affiliate company. All rights reserved.

Thank youContact information

Ron SilbersteinSAP HANA Product [email protected]

To get the best overview of what’s new in SAP HANA SPS 08, read this blog.

mailto:[email protected]

http://www.saphana.com/community/blogs/blog/2014/05/28/what-s-new-in-sap-hana-sps-08


© 2014 SAP AG or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG or an SAP affiliate company.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG (or an SAP affiliate company) in Germany and other countries. Please see http://global12.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

National product specifications may vary.

These materials are provided by SAP AG or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP AG or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP AG or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

In particular, SAP AG or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP AG’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP AG or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

http://global12.sap.com/corporate-en/legal/copyright/index.epx