Lifecycle Management: Week 5 Unit 1

Week 5 Unit 1:
Lifecycle Management
Managing 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
Calculation views
Procedures and privileges
JavaScript, Java, and HTML
Roles and permissions
2016 SAP SE or an SAP affiliate company. All rights reserved.
Public
Changes to the SAP HANA repository
Version control will be done in an external version
control system (e.g. Git/Gerrit repository)
The SAP HANA Deployment Infrastructure only deploys
design-time artifacts but does not manage their lifecycle
Pre SPS 11 repository will remain part of the shipment
for some SPSs
Enables custom XS applications to adopt new runtime at
own pace
Public
Vision
XSA runtime
LM
Lifecycle Management in XSA plans:

Enable the installation and update of products
Provide modeling functionality for products and software component versions (SCV)
Provide SAP Fiori-based user interfaces for installation, update, and modelling processes
Provide a component registration service
Enable a dependency check during installation and update
Fully support Git as external repository
Provide a CTS+ interface for transporting XS advanced content based on multi-target applications
(MTAs)
Public
Status as of SPS 12
XSA runtime
LM
Application lifecycle management for SAP HANA XS, advanced model provides functions for installing
and updating individual software components of SAP HANA XS advanced.
To install and update software components in SAP HANA XS advanced, the xs install command is
available in the XS advanced command-line interface (CLI).
The installation logs can be checked with the command display-installation-logs.
Restriction: With SAP HANA SPS 11/12 the tool to assemble software components for XS advanced
is only available SAP-internally. Therefore, customers can only install XS advanced software
components delivered by SAP.
Customers can use the xs deploy command to install archives built within the SAP Web IDE for SAP
HANA.
Public
Multi-target application
A multi-target application (MTA) is comprised of multiple software pieces (modules) which all share a
common lifecycle for development and deployment. These modules can be written in different
technologies and deployed to different targets on the same platform respectively but they all serve
(different aspects of) a particular purpose for the application users.
Development environment
Project
Versioning system
Version x,y
Runtime environment
Version x,y
Runtime dependency
Public
MTA creation
MTA sources
MTA archive
Source
module 1
type X
Builder
Module 1
type X
Source
module 2
type Y
Builder
Module 2
type Y
Source
module 3
type Z
Builder
Module 3
type Z
MTA
source
descriptor
Module 1
type X
MTA
Builder
Module 2
type Y
Module 3
type Z
MTA
deployment
descriptor
Public
File parts
manifest.yml: Used for command-line push testing
mta.yaml: Used by SAP Web IDE for SAP HANA
mtad.yaml: Built automatically into the MTAR archive
and used by the Deploy/Install command. SAP Web IDE
for SAP HANA builds this file from your mta.yaml during
the project build step
SL_MANIFEST.XML: SAP-internal only for now used
for the additional packaging and software component
definition needed by the Install command
pom.xml and assembly if you have a Java module and/or
build with Maven
Public
MTA creation from SAP Web IDE for SAP HANA (1/2)
1. Create MTA project
3. Synchronize with Git
2. Create modules within project
Public
MTA creation from SAP Web IDE for SAP HANA (1/2)
4. Build and test modules
6. Export MTA archive
5. Build multi-target application (MTA)

7. Deploy MTA archive to target system
Public
10
Support for cross-MTA dependencies
Provisioning of config data to outside of an MTA
Consumption of config data from outside an MTA
Provider mta.yaml:
Consumer mta.yaml
_schema-version: "2.0.0
ID: com.sap.sample.mta.providerversion: 2.3.0
modules:
- name: provider
type: nodejs
provides:
- name: message
public: true # default = true
properties:
message: "Hello! This is a message provided by application
\"${app-name}\", deployed in org \"${org}\" and space \"${space}\"!"
_schema-version: "2.0.0
ID: com.sap.sample.mta.consumerversion: 0.1.0
modules:
- name: consumer
type: nodejs
path: node
requires:
- name: message
properties:
message: ~{message}
resources:
- name: message
type: configuration
parameters:
ID: com.sap.sample.mta.provider:message
version: ">=1.0.0"
target:
org: myorg
space: test
Public
11
Support for service creation and binding parameters
Override or add top-level config entries in mta.yaml:
Public
12
MTA miscellaneous features
Register service URIs:
Create service tags:

via special managed-service parameter: service-tags: [my-custom-tag]
Public
13
Thank you
Contact information:
open@sap.com

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate
company) in Germany and other countries. Please see http://global12.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.
Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its
affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE 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 SE 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 SEs 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 SE 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 forwardlooking 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.
Public
15
Week 5 Unit 2: Git
Git
Changes to the SAP HANA repository
Version control will be done in an external
version control system (e.g. Git/Gerrit
repository)
The SAP HANA Deployment Infrastructure only
deploys design-time artifacts but does not manage
their lifecycle
Pre SPS 11 repository will remain part of the
shipment for some SPSs
Enables custom XS applications to adopt new
runtime at own pace
Public
Git
Goal: To provide Git server for XSA
Gerrit server (Open Source project led by Google)
Git server based on JGit
Access control
Code review workflow
OAuth authentication against UAA service
User provided service
Git service broker

Integrates Gerrit with XSA
Enable XSA services/apps to bind to Git service

Create/delete repository
Bind to repository
Public
Git
SAP Web IDE for SAP HANA
Designed to use Git/GitHub as
the primary source code
repository
Clone repository
Create repository
Load from local file system
Public
Git
Gerrit and Git service broker for XSA
XS Runtime
SAP HANA
Public
Git
Outlook Planned for beyond SPS 12
REST API for runtime authoring
Require developer OAuth scope
Support OAuth authentication against multiple SAP HANA systems

Support versioning large binary files via large file extension (git-lfs)
SAP Web IDE
OAuth SSO
Bind to Git service
Support code review workflow
Deployment service and SL
Integrate with Git service
Public
Thank you
open@sap.com

Public
Week 5 Unit 3: Migration
Migration
Migration of applications Overview
Motivation
Why migration?
New SAP HANA applications and development features
will only be delivered for SAP HANA XS, advanced model
Existing XS Classic applications will be adapted to benefit

from new XS Advanced capabilities
Different application format DU vs. multi-target application
(.mtar)
To be able to run on the advanced runtime, applications

need to be reviewed and migrated
Public
Migration
Migration of applications User management
User Management
User store outside of SAP HANA
Generic SAML2 provider
SAP HANA as a user store
Access to database artifacts with technical user

Assigning database privileges to each business user to
protect database access will no longer work
Business users are no longer bound to the .hdbrole role

definition file
It is possible to pass business user information to the
HDI container (SESSION_CONTEXT)
Public
Migration
Migration of applications Security concepts
Security Concept of XSA
Scopes
Attributes
Scopes are introduced in the application layer
User name, region, cost center are made

available to application via attributes
Application checks, if user has certain scope
Scopes are assigned to users via roles
Attributes are used for instance-based

authorizations
Role Template
Instance-based authorizations only available

through CDS views
A certain set of scopes defines a role
Role templates are a blueprint of a role
Role Collection
Roles are assigned to role collections
Role collections are assigned to users
Public
Migration
Migration of applications Database artifacts
Database Artifacts
Storage
Defined outside of SAP HANA database
Created in SAP HANA via HDI
Container Isolation
Each app gets its isolated container
Synonyms
Method to break container isolation
Definition on table level
Public
Migration
More than just a repository change
Migration is a multi-step process
Convert modeled views to calculation views within the current repository
Migrate all design-time artifacts from the SAP HANA repository to Git
Convert database artifacts to new HDI syntax and file extensions
Deploy database artifacts via HDI into containers
Adjust security for HDI container concepts
Adjust consumption for HDI container concept
Convert XS layer artifacts to XSA (Node.js and XSJS compatibility adjustments)
Deploy XS artifacts as microservices
Data migration
Public
Migration
Process flow
Preparation
Migration
Adjustments
Prep of Source DU
Transfer DU into XSA

Application Format
Manual Adjustments in
Target Application Format
Manual migration of
Analytic views
Attribute views
Scripted calculation views
Migration assistant creates:

XSA application format
Application analysis report
Security concept adjustments

$repo accesses
Not yet supported features
Public
Migration
Migration Assistant
Migration Assistant
Public
Migration
Migration Assistant Scope
Convert modeled views to calculation views within the current repository
Migrate all design-time artifacts from the SAP HANA repository to Git
Convert database artifacts to new HDI syntax and file extensions
Deploy database artifacts via HDI into containers
Adjust security for HDI container concepts
Adjust consumption for HDI container concept
Convert XS layer artifacts to XSA (Node.js and XSJS compatibility adjustments)
Deploy XS artifacts as microservices
Data migration
Public
Migration
Migration Assistant Migration process
Phase 1: Done by
app dev team
Phase 2: Done by Migration Assistant

Command-line tool
App DU1
App DU2
.
:
Migrate to calculation views

in SAP HANA studio:
Scripted calculation views
Analytic views
Attribute views
run
1
Make manual adjustments
based on generated files
and analysis results
App DUn
SAP HANA XSC System
2
generate
SAP HANA XSA Application Structure
As defined in the
XSA documentation
xs2app
db
svc
web
resources
xsjs
lib
Phase 3: Done by
app dev team
Report (html)
Application Analysis Report

Shows number of files per object type
Shows number of files per object successfully
converted/copied/migrated for XS Adv.
Shows number of files per object type not (yet)
migrated to XS Adv.
Due to XS Classic XS Adv. incompatibility
Due to missing functionality
Shows issues that need to be fixed manually
E.g. usage of $.repo functionality
Public
10
Migration
Migration Assistant Tool report
Shows number of files per object type
Shows number of files per object successfully converted/copied/migrated
for XS Advanced
Show number of files per object type not (yet) migrated to XS Advanced
Due to missing functionality
Due to XS Classic XS Advanced incompatibility
Shows issues that need to be fixed manually

E.g. usage of $.repo functionality
Public
11
Migration
Example Migration Report Summary
Public
12
Migration
Example Migration Report File Statistics
Public
13
Migration
Example Migration Report Security Concept
Public
14
Migration
Example Migration Report Database Artifacts
Public
15
Migration
Example Migration Report XSJS
Public
16
Migration
Example Migration Report Unknown File Types or File Content
Public
17
Migration
Example Migration Report Objects Which Have Not Been Migrated
Public
18
Migration
Data migration: NOT covered!
App vers. XS Classic
App vers. XS Adv.
Current tool scope

only covers app
migration
Data migration is not
included in current tool
scope
Applications need their own logic

to cover data migration aspects
Public
19
Migration
Detailed status (1/2)
Calculation/Attributes/Analytic Views
Critical for the migration of almost all XS applications
Manual step to first convert to calculation views (see phase 1)
OData
Schema references removed
XSJS
Identifies code snippets that are not supported in the new XSJS runtime
Development effort for migration of some applications might be high due to security and conceptual changes
Database Artifacts (HDI)

Most objects can be migrated automatically
Some issues possible for migration of .procedure and .hdbdd files
Public
20
Migration
Detailed status (2/2)
Translation
There are different i18n approaches that are hard to migrate automatically
Security
Significant manual effort might be required for application migration as the new XS infrastructure provides a
different security concept
Tool will support migration by providing an XS security report
Cross-Schema Access
Schema prefix removed wherever possible (exception: xsjs and xsjslib files)
Synonyms and synonym configuration generated
Public
21
Thank you
open@sap.com

Public
23
Week 5 Unit 4:
Look Ahead/Roadmap
Look Ahead/Roadmap
Disclaimer
The information in this presentation is confidential and proprietary to SAP and may not be disclosed without the permission of
SAP. Except for your obligation to protect confidential information, this presentation is not subject to your license agreement or
any other service or subscription agreement with SAP. SAP has no obligation to pursue any course of business outlined in this
presentation or any related document, or to develop or release any functionality mentioned therein.
This presentation, or any related document and SAP's strategy and possible future developments, products and or platforms
directions and functionality are all subject to change and may be changed by SAP at any time for any reason without notice.
The information in this presentation is not a commitment, promise or legal obligation to deliver any material, code or functionality.
This presentation 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. This presentation is for informational
purposes and may not be incorporated into a contract. SAP assumes no responsibility for errors or omissions in this
presentation, except if such damages were caused by SAPs intentional or gross negligence.
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.
Public
Look Ahead/Roadmap
A Comprehensive Portfolio for the Developer Persona
Business Needs
Create custom
applications
Extend SAP
applications
Manage the lifecycle of

SAP and custom
applications
Business Benefit
Build applications that reflect the unique business processes and key innovations of your business
Customize user interfaces to your business process and terminology, thereby increasing end-user efficiency
Gain competitive advantage by focusing applications on the key value providers of your business
Fill gaps in standard applications that are specific to your business
Build custom analytics that give specific insights into your business
Database: SQL, SQLScript, CDS, HDI

Application Server: XSA, JavaScript/Node.js, Java
Development Tools
Customize user interfaces to your business process and terminology, thereby increasing end-user efficiency
Gain competitive advantage by focusing applications on the key value providers of your business
Fill gaps in standard applications that are specific to your business
Add customer-specific fields to database, services, and user interfaces extended to your key business needs
Reduce training and cost of ownership by adjusting applications to reflect your industry or business-specific terminology
and processes

Development Tools
Ease the adoption of new releases and product upgrades

Deliver application fixes and new functionality to your business with less downtime and disruption
Manage your design-time assets more efficiently, reducing the cost of ownership for your SAP HANA-based
applications
Integrate SAP HANA application lifecycle management with other SAP solution lifecycles for better overall visibility and
lower complexity
Application Lifecycle Management
Support development tools and debugging that work with the developer to reduce the time to deliver custom
development
Tools that support continuous integration and agile development reduce defects and increase the time to delivery
Code scanners and automated unit testing reduce the number of development bugs that reach productive systems
Developer tool optimization reduces the cost of development

Development Tools
XSA offers the all-in-one-box application server and database server by default, thereby providing a low cost of
ownership and making start of use easy
XSA scales independent of the SAP HANA database. It can run on lower-cost hardware and can scale to Internet scale
loads without directly increasing the cost of your SAP HANA-specific hardware
XSA can be installed in a DMZ or with a firewall between it and SAP HANA, providing multiple security options
Developer productivity
Architecture scalability
and security
Key Capabilities
Public
Look Ahead/Roadmap
Developer Persona Roadmap key themes and capabilities
Today (Recent SPS12)
Application Server
Planned Q3/2016
Planned 2017
Application Server
Application Server
Node.js 6.x support
OData V4 / SAP Fiori Smart Extensions support
Migration Assistant to help with the move from XS

classic to XS advanced
Java 9
Developments Tools
Bring Your Own Language/Runtime support
Work toward feature parity with SAP Web IDE and

existing studio/Web workbench tool
SAP Fiori launchpad
Security: Additional authentication (SPNEGO, X.509

and SAP logon tickets)
App2App SSO
Developments Tools
Developments Tools
SAPUI5 View WYSIWYG editor
Full support for graphical data models
SAP Fiori project templates and wizards
Integration of HRTT in SAP Web IDE
Java tooling and debugging
New tools for text analysis, remote sources, virtual

tables, flowgraph, and replication
Database
Node.js 4.x support, optimize deployment and

service start-up time, disaster recovery and scaleout options
No SAP HANA platform shipment in Q3 2016
Planned Q4/2016
Ongoing
3rd
party and IaaS certifications
Streaming Module
Database
Simpler language and improved security
HDI: Public synonyms, schema-local structured
privileges, text analysis and mining artifacts
CDS: Index Enhancements and Extensibility Model
Git/Gerrit delivery
Software component and product installation and
update for XSA content via command line
Uninstall of SCVs and products via command line
Database
Initial XML and JSON document store support
Performance optimizations and enhancements
HDI: Consumption libraries, parallelization
enhancements, container groups
CDS: Automated exposure of CDS models for

OData (Java Runtime only)
SAP Fiori-based user interfaces as alternative to
command line
CTS+ transport for MTAs
This is the current state of planning and may be changed by SAP at any time.
Deployment of MTA from Git
JavaScript: debugging on the fly
SQL: Integration with Vora, further XML support,

enhanced dynamic cached views
SQLScript: Continue optimization of scalable &
massively-parallel business logic processor for best
performance on OLTP and OLAP; native XML/JSON
support; testing framework; user exits
HDI: Support for new database artifacts
CDS: Automated exposure of CDS model via OData
for both Java and JavaScript
Change management and transport tooling on top of
Git
Application configuration service
Public
Look Ahead/Roadmap
Developer Persona Roadmap Application Server (1/2)
SAP Web IDE for SAP HANA will be technically
implemented as an XS Advanced application and
was delivered post SPS11
Planned Q3/2016
Ongoing
3rd
Planned Q4/2016
General
Migration Assistant to help with the move from XS

Classic to XS Advanced
Planned 2017
OData Version 4 / SAP Fiori Smart Extensions
support
Java 9
The XS Advanced runtime and HDI will not support

full feature compatibility with XS Classic in the
SPS11 delivery. Feature compatibility will continue
to be enhanced in SPS 12 and beyond
Bring Your Own Language/Runtime support
Web Admin
SAP Fiori launchpad
Blob Store Admin
Node.js 6.x support
Buildpack Admin
Node.js 4.x support
Full multi-DB support
Services Admin
Advanced Git/Gerrit lifecycle management scenarios
Web Admin
Domain Admin
Additional deployment and scaling options as well as

startup and recovery optimization
Application monitoring (workload statistics, stop,

start, restage, etc.)
CDS Integration with OData
Certificate handling
Debugging on the fly
Routes and Runtimes administration
Buildpack caching
OData V2
Job Scheduling: Job Chaining
Feature parity to XSC XSODATA
Security
Java
XSJS
Authentication flow in Java Security client library for

support of Java applications without an app router in
front of them
Feature parity to XSC
Additional security APIs for FLP
JavaScript runtime
SPNEGO authentication
Audit Logging service
X.509 authentication
Footprint reduction and protocol optimizations
SAP logon tickets authentication
Audit service and end-to-end trace
JavaScript runtime
Git/Gerrit APIs for runtime generation of artifacts
Public
Look Ahead/Roadmap
Developer Persona Roadmap Application Server (2/2)
Planned Q3/2016
Planned Q4/2016
Planned 2017
Approuter
New authentication methods

Multi-tenancy support
Job Scheduling
Token-based authentication to execute jobs as the
business user
Polling URI for async jobs
Security
UAA version 3.x
Issue JWTs with certain scopes to services or apps

for authentication without a business user
App2App SSO
User settings
Runtime
Secure debugging
Extended monitoring for Node.js and Java
Linux PPC / Little Endian support
System replication
SLD registration for applications
Public
Look Ahead/Roadmap
Developer Persona Roadmap Development Tools
Installation via HDBLCM
Work toward feature parity with SAP HANA

studio/Web-based Development Workbench
Planned Q3/2016
Ongoing
3rd
Streaming
Planned Q4/2016
Planned 2017
Multi-space/org support
SAP Fiori project template and wizards
Advanced Git capabilities
SAPUI5 view WYSIWYG editor
Full support for graphical data models
Java tooling
Text analysis
Java debugger
SAP Fiori launchpad
OData Explorer
Create remote source
Plan Viz
Remote source browsing
JavaScript: Debug running applications
Create virtual tables

Flowgraph editor
CDS - code completion for catalog objects, data

preview, OData annotations in CDS
Replication editor
SAP HANA runtime tools - MDX console
JavaScript tools - build: browse build results, debug:

harmonize with SQLScript, debug: edit variables,
expressions, break on exception
CDS - Editor templates/wizards
Problems view
Integration of HRTT in SAP Web IDE
Public
Look Ahead/Roadmap
Developer Persona Roadmap Application Lifecycle Management
update for XSA application content via command
line, including dependency check and component
registration service
Planned Q3/2016
Ongoing
3rd
MTA deployment via command line ((near) Zero

Downtime deployment)
Uninstall of SCVs and products via command line
Planned Q4/2016
Planned 2017

update for XSA content via SAP Fiori-based user
interfaces
Application configuration service
CTS+ transport for MTAs
Upload of SCVs and product archives to Git
Zero Downtime Maintenance for XSA: initial version
Installation of SCVs and products from Git
Parallel deployment of applications/MTA modules
Runtime authoring
Support for new service type for HDI synonym
Runtime authoring support by installation of SCVs

and products
Consistency check for installed MTAs

Git
Deployment of MTAs from Git
Change management and transport tooling on

top of Git
Installation/update of hybrid products by central

product installer (outside of XSA)
Support for multiple databases assigned to one

space, including a default database
Support versioning large binary files via large file
extension proposed by GitHub
REST API can be used for runtime authoring
Developer OAuth scope
Support OAuth authentication against multiple SAP
HANA systems
Public
Look Ahead/Roadmap
Developer Persona Roadmap Database; SQL
Check Constraints for Insert / Update
Planned Q3/2016
Planned 2017
Multi-Store Tables
Cloud Scalability
Plans to support multi-store tables (single table with

partitions on different storages)
Plans to improve scalability of SQL execution to

support Big Data
Security Innovations
Dynamic Cached Views
Integration with SAP HANA Vora
Supported functions include HASH_MD5
Incremental maintenance of view cache to include

cached data as well as delta data (only single table
aggregates, only column store)
Plans to improve integration between SAP HANA

and SAP HANA Vora
JSON Document Store

Seamless integration with document database
More functionality such as row store support, scaleout optimization, etc.
XML Support
Further XML Support
Functions similar to XPATH() and XMLEXTRACT()
More functions similar to XMLTABLE(), XML data

type
Adds functionality to check constraints on columns

when creating tables
Planned Q4/2016
Ongoing
3rd
Partition Restriction for UPDATE

Limit update to certain partition
MONTHSBETWEEN / YEARSBETWEEN
Easily calculate time between date arguments
SQL Hint Table Extension

Option to include statements in table to execute
automatically with hint
Gap Closing for DBMS Features
Continuous improvements to close gaps to other
DBs
Enhancements for Dynamic Cached Views
Further Internal Optimizations

Continuous improvements with regard to
performance and execution
Gap Closing for DBMS Features
Continuous improvements to close gaps to other
DBs
Public
Look Ahead/Roadmap
Developer Persona Roadmap Database; SQLScript
Support global session variables
Signatures for anonymous blocks
Planned Q3/2016
Planned Q4/2016
Performance Optimization
Default Empty for table UDF
Enablement of the lightweight execution path to

reduce the overhead
Results of implicit Select in nested calls
Smart SQL inlining
System view extension e.g. in-place table type

definition and security mode
Scalar UDF result caching
Query export
Lazy revalidation of SQLScript artifacts
Move from repository to Git
Extend Core Feature Set
Move to SAP HANA Deployment Infrastructure (HDI)
FOR EACH
Move to SAP Web IDE for SAP HANA for

development of database artifacts such as
procedures and user-defined functions
Synonyms on HEADER ONLY artifacts
Ongoing
3rd
SQLScript debugger
Function debugging
Break on error
Watchpoints
Table function compilation optimization
Enhancement of Table Variable Operations
Planned 2017
Continue Optimization of Our Scalable &
Massively-Parallel Business Logic Processor for
Best Performance on OLTP and OLAP
Workloads Likewise
Scale-out optimization (e.g. dynamic plan re-routing)
Performance optimizations for scalar UDFs
Improved multi-statement optimizations
Extend Core Feature Set
Additional data structure (e.g. maps, matrices)
Native XML/JSON support
Print functionality in SQLScript artifacts
SIZE operator
Extend table variable operations (e.g. insert, sort

and search operation, ...)
Initialization of empty result set
Support of holdable cursor
Improve Supportability
EXPLAIN PLAN FOR CALL
Better support of (3rd party) legacy code, i.e. library

support
Code scanner
Testing Framework
SQLScript Debugger
User Exits Within SQLScript
Anonymous block debugging
Improve Supportability
Offset/Length for scalar values
Easier root cause analysis of scenarios
Access content of global temporary tables while

debugging
Simpler application coding
Public
10
Look Ahead/Roadmap
Developer Persona Roadmap Database; HANA Deployment Infrastructure (HDI)
Deployment Process
Simulation mode
Planned Q3/2016
Ongoing
3rd
Async Make improvements (client handling,

cancelation)
Planned Q4/2016
Deployment Process
Artifact Enhancements
Deploy & redeploy optimizations and performance

improvements
Support for new database artifacts
Parallelization enhancements
Supportability
Supportability
Container Export / Import (for Support use cases)
Enhancements to Export/Import container

functionality
Container-level trace extensions, trace

improvements
Planned 2017
Security
Security
Additional security alerts
Auditing via standard SAP HANA features (How-To

documentation)
Introduction of container groups & group-level SQL

Admin APIs
Public synonyms
Synonyms: _SYS_BIC, Smart-BI
Text analysis & text mining artifacts
Export Table Data enhancements
Extended calculation view features
Table Data Key Reservation flag
Schema-local structured privileges
Force Delete flag
Expose DB-level associations & WITH COMMENTS

clause
Misc
Misc
Table structure migration optimizations
Multi-DB support
HDI Node.js, XSJS, and Java libraries
Provide SQL APIs for retrieving cross-references
Public
11
Look Ahead/Roadmap
Developer Persona Roadmap Database; Core Data Services (CDS)
Index Enhancements
ASC/DESC per column
Planned Q3/2016
Ongoing
3rd
Planned Q4/2016
Planned 2017
Entities
General Enhancements
GENERATED ALWAYS AS <expression>
Automated exposure of CDS model via OData for

analytical features & write scenarios (Java Runtime)
Index on nested elements
GENERATED BY DEFAULT AS IDENTITY
Extensibility Model
Views
Adding elements to entities and structured types
TOP/LIMIT/OFFSET

read/write & analytical features scenarios
(JavaScript runtimes)
Adding select items to views
Views with parameters
Multiple top-level artifacts in a CDS source
Adding annotations to artifacts and elements

Adding clauses to technical configuration
Associations in views
Subqueries

simple read scenarios (Java Runtime only)
Explicit type specification for view elements

AUTO MERGE option
Public
12
Thank you
open@sap.com

Public
14
Week 5 Unit 5:
Closing/Summary
Closing/Summary
Course Content
Course week 1: Introduction
Course week 2: Database Development
Course week 3: Application Server and UI Development
Course week 4: Node.js
Course week 5: Wrap-Up
Public
Thank you
open@sap.com

Public

Lifecycle Management: Week 5 Unit 1

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Lifecycle Management: Week 5 Unit 1

Uploaded by

Copyright:

Available Formats

Week 5 Unit 1:

2016 SAP SE or an SAP affiliate company. All rights reserved.

Lifecycle Management in XSA plans:

2016 SAP SE or an SAP affiliate company. All rights reserved.

2016 SAP SE or an SAP affiliate company. All rights reserved.

2016 SAP SE or an SAP affiliate company. All rights reserved.

2016 SAP SE or an SAP affiliate company. All rights reserved.

3. Synchronize with Git

2. Create modules within project

2016 SAP SE or an SAP affiliate company. All rights reserved.

6. Export MTA archive

5. Build multi-target application (MTA)

2016 SAP SE or an SAP affiliate company. All rights reserved.

Consumption of config data from outside an MTA

2016 SAP SE or an SAP affiliate company. All rights reserved.

2016 SAP SE or an SAP affiliate company. All rights reserved.

Create service tags:

2016 SAP SE or an SAP affiliate company. All rights reserved.

2016 SAP SE or an SAP affiliate company. All rights reserved.

2016 SAP SE or an SAP affiliate company. All rights reserved.

Week 5 Unit 2: Git

2016 SAP SE or an SAP affiliate company. All rights reserved.

User provided service

Git service broker

Enable XSA services/apps to bind to Git service

2016 SAP SE or an SAP affiliate company. All rights reserved.

2016 SAP SE or an SAP affiliate company. All rights reserved.

2016 SAP SE or an SAP affiliate company. All rights reserved.

Support OAuth authentication against multiple SAP HANA systems

2016 SAP SE or an SAP affiliate company. All rights reserved.

2016 SAP SE or an SAP affiliate company. All rights reserved.

2016 SAP SE or an SAP affiliate company. All rights reserved.

Week 5 Unit 3: Migration

Existing XS Classic applications will be adapted to benefit

To be able to run on the advanced runtime, applications

2016 SAP SE or an SAP affiliate company. All rights reserved.

Access to database artifacts with technical user

Business users are no longer bound to the .hdbrole role

2016 SAP SE or an SAP affiliate company. All rights reserved.

Scopes are introduced in the application layer

User name, region, cost center are made

Application checks, if user has certain scope

Scopes are assigned to users via roles

Attributes are used for instance-based

Instance-based authorizations only available

A certain set of scopes defines a role

Role templates are a blueprint of a role

2016 SAP SE or an SAP affiliate company. All rights reserved.

2016 SAP SE or an SAP affiliate company. All rights reserved.

2016 SAP SE or an SAP affiliate company. All rights reserved.

Transfer DU into XSA

Migration assistant creates:

Security concept adjustments

2016 SAP SE or an SAP affiliate company. All rights reserved.

2016 SAP SE or an SAP affiliate company. All rights reserved.

2016 SAP SE or an SAP affiliate company. All rights reserved.

Phase 2: Done by Migration Assistant

Migrate to calculation views

SAP HANA XSA Application Structure

2016 SAP SE or an SAP affiliate company. All rights reserved.

Application Analysis Report

Shows issues that need to be fixed manually

2016 SAP SE or an SAP affiliate company. All rights reserved.