SAP HANA SPS09 - XS Programming Model

1
©2014 SAP AG or an SAP affiliate company. All rights reserved.
SAP HANA SPS 09 - What’s New? XS Programming Model
SAP HANA Product Management November, 2014
(Delta from SPS 08 to SPS 09)

©2014 SAP SE or an SAP affiliate company. All rights reserved.
2
Public
Agenda
Miscellaneous Improvements
Security
User Handling
Outbound HTTP
New Database Interface
Core XSJS APIs
SMTP
ZIP
Job Scheduling
OData
Web Dispatcher
XS Admin
Self Service
Logon Screen
HANA Test Tools
CDS
Lifecycle Management
XSDS
Managed
Unmanaged
Procedures
Repository REST APIs

4
Public
HANA XS SPS9: Miscellaneous Improvements
New Mozilla VM (currently 28)
Relaxed strict mode settings of the JS VM
New Thread Model
OData execution tracking (SP9: GET only)
Usage Statistics

6
Public
HANA XS SPS9: Misc. Security Features
Full CORS support (Cross-Origin Resource Sharing)
Secure http session cookies
Support for Client Certificates from F5’s BigIP
Custom Headers/X-Frame
SAML Single Logout (SLO)
SAML Authentication in Authorization header
Support of Virus Scan Interface (VSI) for applications

7
Public
HANA XS SPS9: Misc. Security Features – CORS Support
Full CORS support (Cross-Origin Resource Sharing)
•Filtering by origins, headers, and methods

8
Public
HANA XS SPS9: Misc. Security Features – Custom Headers/X-Frame
Custom Headers/X-Frame
•Controls if the browser should allow a page to be rendered in a frame, iframe, or object.
•Avoids clickjacking attacks by keeping content from being embedded in a malicious site

10
Public
HANA XS SPS9: Recommended User Handling
Recommended default pattern: no SQL privileges for end-users!
Named DB users are used for logon and assignment of XS application privileges
Default connection is used to switch to technical user for all DB access
Access to name/ID of logged-on user still possible
Instance filtering is still done for the logged-on user
Improved Support for Close Cooperation with ABAP Applications
Logon via SAML or SAP Logon Tickets is possible even without named DB User!
Programmatic alternative (SqlScript) to XS application privileges

11
Public
User handling in XS Plain DB user
•The logon maps to the personal DB user, who is used for checking XS application privileges
•SQL connections are opened for the personal DB user, who is thus also used for checking SQL privileges
•Instance-filtering is also done with personal DB user
•Personal DB user needs SQL privileges which he can abuse via SQL Console/Studio

12
Public
User handling in XS SQLCC scenario (best practice for stand-alone XS Apps)
•The logon maps to the personal DB user
•XS privilege checks are done with this user
•Package without configured default connection
•OData services and plain DB access from XSJS are not recommended, to avoid granting SQL privileges to personal DB users
•Controlled navigation to non-exposed packages which have a configured default connection
•Packages with configured default connection
•All SQL connections (xsjs and OData) are opened for the configured default connection, which is thus used for checking all SQL privilges
•Instance-filtering is not possible (planned for SPS09) Personal DB user needs only XS Privileges

13
Public
User handling in XS Anonymous section scenario
•No logon is enforced
•XS privilege checks will fail
•OData services and plain DB access from XSJS are not possible
•navigation to packages with XS privilege check is not possible
•All SQL connections (xsjs and OData) are opened for the configured default connection, which is thus used for checking all SQL privileges
•Instance-filtering is not possible

14
Public
User handling in XS Technical user scenario
•The logon is successful without mapping to a personal DB user
•XS privilege checks will fail
•DB access not possible
•All SQL connections (xsjs and OData) are opened for the configured sqlcc user, which is thus used for checking all SQL privileges
•Instance-filtering is done with logon user

16
Public
HANA XS SPS9: Additional features for Outbound Connectivity
Anonymous Outbound SSL supported
Act as SAML 2.0 ID Provider
OAuth 2.0 client
Option to Enforce Proxy for all outgoing communication

18
Public
New database interface
Performance gain
•Achieves higher throughput
•Better scale out support
•Minimal remote traffic
Usability improvements
•Simple and easy to use JavaScript interface
•Code reduction
•No boilerplate code
Light-weight architecture
•Based upon thin C++ client library
•No SQL Processing in XS layer
•Uses internal HANA communication protocol

19
Public
New database interface Examples – old $.db interface
var conn = $.db.getConnection(); var query = 'SELECT * FROM "sap.hana.democontent.epmNext.data::EPM.Purchase.Item" ‘ + ' WHERE "PRODUCT.PRODUCTID" = ? '; var pstmt = conn.prepareStatement(query); pstmt.setString(1, productId); var rs = pstmt.executeQuery(); var body = ''; while (rs.next()) { var gross = rs.getDecimal(6); if(gross >= 500){ body += rs.getNString(1) + "t" + rs.getNString(2) + "t" + rs.getNString(3) + "t" + rs.getDecimal(6) + "n"; } } rs.close(); pstmt.close();

20
Public
Parameters set via separate command – type specific

21
Public
Returned Record Set – no random access, one loop sequential

22
Public
Each cell must be read with another type specific function call

23
Public
New database interface Examples – new $.hdb interface
var conn = $.hdb.getConnection();
var query = 'SELECT * FROM "sap.hana.democontent.epmNext.data::EPM.Purchase.Item"' +
' WHERE "PRODUCT.PRODUCTID" = ?';
var rs = conn.executeQuery(query,productId);
var body = '';
for(var i = 0; i < rs.length; i++){
if(rs[i]["GROSSAMOUNT"] >= 500){
body += rs[i]["HEADER.PURCHASEORDERID"] + "t" + rs[i]["PURCHASEORDERITEM"] + "t" + rs[i]["PRODUCT.PRODUCTID"] + "t" + rs[i]["GROSSAMOUNT"] + "n";
}
}

24
Public
var conn = $.hdb.getConnection(); var query = 'SELECT * FROM "sap.hana.democontent.epmNext.data::EPM.Purchase.Item"' + ' WHERE "PRODUCT.PRODUCTID" = ?'; var rs = conn.executeQuery(query,productId); var body = ''; for(var i = 0; i < rs.length; i++){ if(rs[i]["GROSSAMOUNT"] >= 500){ body += rs[i]["HEADER.PURCHASEORDERID"] + "t" + rs[i]["PURCHASEORDERITEM"] + "t" + rs[i]["PRODUCT.PRODUCTID"] + "t" + rs[i]["GROSSAMOUNT"] + "n"; } }
Parameters are sent into the execute function directly – not type specific

25
Public
var body = '';
}
}
Returned Record Set is a JSON object – direct index access or easy looping

26
Public
var body = '';
}
}
Record Set object doesn’t materialize the data into JavaScript VM

27
Public
var body = '';
}
}
Individual Cells accessible by name / not type specific

28
Public
New database interface Debugging
New interface makes debugging easier as the result set is JSON and fully accessible in the debugger

29
Public
New database interface Examples – new $.hdb interface, JSON RecordSet
var connection = $.hdb.getConnection();
var results = connection.executeQuery(
'SELECT * FROM "sap.hana.democontent.epmNext.data::EPM.MasterData.Employees" ' +
'WHERE LOGINNAME <> ?', 'EPM_USER');
$.response.setBody(JSON.stringify(results));
Result Record Set is JSON; ready for output

30
Public
New database interface Examples – new $.hdb interface, Stored Procedures
var partnerRole = $.request.parameters.get("PartnerRole");
partnerRole = typeof partnerRole !== 'undefined' ? partnerRole : '01';
var getBpAddressesByRole = connection.loadProcedure("SAP_HANA_EPM_NEXT",
"sap.hana.democontent.epmNext.procedures::get_bp_addresses_by_role");
var results = getBpAddressesByRole(partnerRole);
//Pass output to response
$.response.status = $.net.http.OK;
$.response.contentType = "application/json";
Procedure has a JavaScript function “proxy”

31
Public
JavaScript input parameters / Table parameters as JSON

32
Public
Result Record Set is also JSON

34
Public
HANA XS SPS9: New XSJS-APIs
SMTP (sending mails from xsjs application code)
ZIP and GZIP support (read and write)
XML parsing support
Secure Store for applications
Better Multipart Support
Asynchronous request completion
Text Access
Text Mining
Management of Scheduled Jobs
Various utility functions (hash, encrypt)
AntiVirus for applications

35
Public
New XSJS-APIs Examples – SMTP
var mail = new $.net.Mail({
sender: {address: "demo@sap.com"},
to: [{ address: "user@sap.com"}],
subject: "XSJS Email Test",
parts: [ new $.net.Mail.Part({
type: $.net.Mail.Part.TYPE_TEXT,
text: "The body of the mail.",
contentType: "text/plain"
})]
});
var returnValue = mail.send();
var response = "MessageId = " + returnValue.messageId +
", final reply = " + returnValue.finalReply;

36
Public
New XSJS-APIs Examples – SMTP with attachment
var mail = new $.net.Mail({
sender: {address: "demo@sap.com"},
to: [{ address: "user@sap.com"}],
subject: "XSJS Email Test",
parts: [ new $.net.Mail.Part({
type: $.net.Mail.Part.TYPE_TEXT,
text: "Atachement Test",
contentType: "text/plain"
})]
});
mail.parts.push(new $.net.Mail.Part({
type: $.net.Mail.Part.TYPE_ATTACHMENT,
data: getImage(),
contentType: "image/jpg",
fileName: "myPicture.jpg"}));
var returnValue = mail.send();

37
Public
New XSJS-APIs Examples – SMTP Configuration

38
Public
New XSJS-APIs Examples – ZIP
var zip = new $.util.Zip();
zip["folder1/demo1.txt"] = "This is the new ZIP Processing in XSJS";
zip["demo2.txt"] = "This is also the new ZIP Processing in XSJS";
$.response.contentType = "application/zip";
$.response.headers.set('Content-Disposition', "attachment; filename = 'ZipExample.zip'");
$.response.setBody(zip.asArrayBuffer());

39
Public
New XSJS-APIs Examples – ZIP
var zip = new $.util.Zip();
zip["folder1/demo1.txt"] = "This is the new ZIP Processing in XSJS";
zip["demo2.txt"] = "This is also the new ZIP Processing in XSJS";
$.response.contentType = "application/zip";
$.response.headers.set('Content-Disposition', "attachment; filename = 'ZipExample.zip'");
$.response.setBody(zip.asArrayBuffer());
Folder structure in ZIP simply by specify the full path as you create the content

40
Public
New XSJS-APIs Examples – ZIP Continued
Load Zip directly from web request object – avoid moving content into JavaScript variable
var zip = new $.util.Zip($.request.body);
Similar direct access for Record Set result object of a database query
statement = conn.prepareStatement("select data from EXAMPLETABLE where id=1");
var rs = statement.executeQuery();
if (rs) {
while (rs.next()) {
//Load Zip From ResultSet
var loadedZip = new $.util.Zip(rs, 1);
}
}

41
Public
New XSJS-APIs Examples – XML
var parser = new $.util.SAXParser();
//parse XML from String
var parser = new $.util.SAXParser();
var xml = '<?xml version="1.0" encoding="UTF-8" standalone="yes"?>n' +
'n'+'<note noteName="NoteName">'+
'<to>To</to>'+'<from>From</from>'+'<heading>Note heading</heading>'+
'<body>Note body</body>'+'</note>';
var startElementHandlerConcat = "";
parser.startElementHandler = function(name, atts) {
startElementHandlerConcat += name;
if (name === "note") {
startElementHandlerConcat += " noteName = '" + atts.noteName + "'";
}
startElementHandlerConcat += "n";
};
parser.parse(xml);

42
Public
New XSJS-APIs Examples – Improved Multi-Part
var i;
var n = $.request.entities.length;
var client = new $.net.http.Client();
for (i = 0; i < n; ++i) {
var childRequest = $.request.entities[i].body.asWebRequest();
client.request(childRequest, childRequest.headers.get("Host") + childRequest.path);
var childResponse = client.getResponse();
var responseEntity = $.response.entities.create();
responseEntity.setBody(childResponse);
}

43
Public
New XSJS-APIs Examples – Response Callback
$.response.followUp({
uri : "playground.sp9.followUp:other.xsjs",
functionName : "doSomething",
parameter : {
a : "b"
}
});

44
Public
New XSJS-APIs Examples – Text Access
var textAccess = $.import("sap.hana.xs.i18n","text");
var bundle = textAccess.loadBundle("playground.sp9.textAccess","demo1");
var singleText = bundle.getText("demo");
var replaceText = bundle.getText("demo2",['1001']);
var oAllTexts = bundle.getTexts();

45
Public
New XSJS-APIs Examples – AntiVirus
try {
//create a new $.security.AntiVirus object using the default profile
var av = new $.security.AntiVirus();
av.scan($.request.body);
} catch (e) {
$.response.setBody(e.toString());
}
•The scan needs a Virus Scan Adapter (VSA) to be installed on the host
•The setup and configuration is available with SAP note 2081108
•This class uses the SAP certified interface NW-VSI 2.00 (see SAP note 1883424)
•For a list of the AV products supported, see SAP note 1494278

46
Public
New XSJS-APIs Examples – Secure Store
function store() {
var config = {
name: "foo",
value: "bar"
};
var aStore = new $.security.Store("localStore.xssecurestore");
aStore.store(config);
}
function read() {
var config = {
name: "foo"
};
try {
var store = new $.security.Store("localStore.xssecurestore");
var value = store.read(config);
}
catch(ex) {
//do some error handling
}
}

48
Public
HANA XS SPS9: Scheduled Jobs
Robustness
Active jobs will not block DU import anymore
No hick-up of scheduling, even in case of process crashes
Enhanced xsjs API for Job Management
Enumerate schedules of a job object (access as e.g. myjob.schedules[19])
Modify schedules via properties (xscron, description, parameter like myjob.schedules[19].xscron = “* * * * * * *”;)
Expose job_log entries of a schedule as a property (like myjob.schedules[19].logs.jobLog)
Enhanced support for SqlScript parameters
Scalar parameters
References to tables
Creating local tables by type
New Management UI (XS Job Dashboard)

49
Public
HANA XS SPS9: Scheduled Jobs – New Management UI
URL: /sap/hana/xs/admin/jobs/

50
Public
HANA XS SPS9: Scheduled Jobs – New Management UI Continued
Drill into details of a single job definition from Job Dashboard or from the XS Admin tool

52
Public
HANA XS SPS9: OData
Configurable Cache-settings for Metadata-Document
E-Tag support
Automatic parallelization for GET batch requests
INA Search capabilities integrated into OData

53
Public
OData Explorer
SAP River application explorer rebuilt as SAP OData Explorer in SPS09
•General OData test and data generation tool which supports XSODATA services
•Launches from the SAP Web- based Development Workbench or via URL
•/sap/hana/ide/editor/plugin/testtools/odataexplorer/index.html?appName=<xsodata service path>

55
Public
HANA XS SPS9: Local Web Dispatcher
Full Integration into HANA Process Management
Monitoring
Configuration
Administration

56
Public
Monitoring

57
Public
Configuration

58
Public
Administration
–URL: /sap/hana/xs/wdisp/admin/public/

60
Public
HANA XS SPS9: HANA XS Admin Tool
Much improved usability
User Self Service
UI of Logon Screen is Customizable

61
Public
HANA XS SPS9: HANA XS Admin Tool – new visual design

62
Public
HANA XS SPS9: HANA XS Admin Tool: Scheduled Jobs – New Management UI
URL: /sap/hana/xs/admin/jobs/

63
Public
HANA XS SPS9: HANA XS Admin Tool: Scheduled Jobs – New Management UI Continued
Drill into details of a single job definition from Job Dashboard or from the XS Admin tool

64
Public
HANA XS SPS9: Customize Login Screen
Custom background image set via xsengine.ini -> httpserver parameter

65
Public
HANA XS SPS9: User Self Service
/sap/hana/xs/selfService/user/resetPassword.html

66
Public
HANA XS SPS9: User Self Service
/sap/hana/xs/selfService/user/requestAccount.html

67
Public
HANA XS SPS9: User Self Service – Admin
/sap/hana/xs/selfService/admin/

68
Public
HANA XS SPS9: User Self Service – User Profile
/sap/hana/xs/formLogin/profile/

70
Public
HANA XS SPS9: Test Framework
Unit Test Framework
Mock Framework
(shipped with HANA, but not pre-installed)

71
Public
Contents of HANA_TEST_TOOLS Delivery Unit
•XS Unit Test Framework and Test Runner (unit.jsaminexs)
•XSUnit Test Coverage for XS JavaScript (unit.codecoverage)
•Test Isolation Framework (mockstar)
•Test Helper (unit.util)
•Developer Documentation (doc)
•Demos (demo)

72
Public
How to create an XSUnit Test
•One common tool for testing XS JavaScript, database content: SQLScript, Views
•Based on open-source library, extended by custom assertions, test utilities
•Test code and test data are developed beside your productive code, in the same HANA instance
•Tests are implemented in XS JavaScript in HANA Studio or the Web-based Development Workbench

73
Public
Execute XSUnit Test in the browser
•URL: /sap/hana/testtools/unit/jasminexs/TestRunner.xsjs?package=<>
•package = the repository package your tests are located

74
Public
Parameter
Required
Description
Example
tags
no
Comma-separated list of tags to restrict the tests to be executed.
tags=integration,long_running
reporter
no
Complete path to module providing an implementation of the Jasmine reporter interface. With this parameter a custom reporter can be passed to publish the test results in an application specific format
reporter=sap.hana.testtools.unit.jasminexs.reporter. db.dbReporter has the same effect like format=db
profile
no
Name of a "profile" defined in the test which filters the tests to be executed on the basis of tags.
profile=end2end
Execute XSUnit Test in the browser: URL Parameters

75
Public
Parameter
Required
Description
Example
pattern
no
Naming pattern that identifies the .xsjslib files that contain the tests. If not specified, the pattern “*Test” is applied. You can use wildcards “?” and “*” to match a single and multiple arbitrary characters respectively.
pattern=Test* would match all xsjslib files beginning with “Test”; In these files you may then manually import other test files.
package
yes
Package that acts as starting point for discovering the tests. If not otherwise specified by parameter “pattern” all .xsjslib files in this package and its sub-packages conforming to the naming pattern “*Test” will be assumed to contain tests and will be executed.
package=sap.hana.testtools.demo
Execute XSUnit Test in the browser: URL Parameters (Continued)

76
Public
Parameter
Required
Description
Example
format
no
Specifies the output format the test runner uses to report test results. By default, the results will be reported as HTML document. This parameter has no effect if a custom reporter is provided via parameter “reporter”.
format=html shows results in HTML; format=junit or format=xml outputs XML conforming to schema used by Jenkins; format=json outputs results in JSON format; format=db writes test results to database tables
Execute XSUnit Test in the browser: URL Parameters (Continued)

77
Public
Execute XSUnit from SAP Web-based Development Workbench

78
Public
Analyze Test Coverage

79
Public
View XSUnit Test Results

80
Public
Mocking Framework

82
Public
HANA XS SPS9: CDS
Mission Statement
CDS provides an enriched data model
CDS allows for graceful life-cycle management
CDS allows for extending the meta-model
Features coming with SP9
Multi-File
Table Lifecycle
Associations
DCL (Instance filtering)
Much improved editing support in Studio and Web-based Development Workbench

83
Public
CDS new features
•Support for view complex features such as sub-selects
•Multi-file support
•Calc-view support
•Unmanaged Associations
•Annotation (enums, array, etc)
•Lifecycle management support for data migration
•GIS-Types
•Core HANA data types
•Currency Conversion
•Enterprise search via full text index

84
Public
CDS Lifecycle Management Example
SQL:
CREATE TABLE PARTNER(NAME char(30), TYPE char(1));
Adding new field:
ALTER TABLE PARTNER ADD(GROSS int);

85
Public
CDS:
entity PARTNER { NAME: String(30); TYPE: String(1); GROSS: Integer; };
Simply add the field. The necessary SQL is generated

86
Public
CDS:
entity PARTNER { NAME: String(30); TYPE: String(1); GROSS: Integer Integer64; };
This Lifecycle Management supports a wide variety of scenarios
•Conversion from same named HDBTABLE
•Change of key / data type
•Removal of columns
Upon activation data is migrated automatically

87
Public
CDS Multi-file: File 1
namespace playground.sp9.cds; @Schema: 'SP9DEMO‘ context ContextA { type T1 : Integer; context ContextAI { type T2 : String(20); type T3 { a : Integer; b : String(88); }; }; };

88
Public
CDS Multi-file: File 2
namespace playground.sp9.cds; using playground.sp9.cds::ContextA.T1; using playground.sp9.cds::ContextA.ContextAI as ic; using playground.sp9.cds::ContextA.ContextAI.T3 as ict3; @Schema: 'SP9DEMO‘ context ContextB { type T10 { a : T1; // Integer b : ic.T2; // String(20) c : ic.T3; // structured d : type of ic.T3.b; // String(88) e : ict3; // structured }; context ContextBI { type T1 : String(7); // hides the T1 coming from the first using declaration type T2 : T1; // String(7) };};

89
Public
CDS Enumerations
namespace playground.sp9.cds; @Schema: 'SP9DEMO‘ context enumerations {
type Color : String(10) enum { red = 'FF0000'; g = '00FF00'; b = '0000FF'; };
annotation MyAnnotation { a : Integer; b : String(20); c : Color; d : Boolean; };};

90
Public
CDS New Types
entity SomeTypes { a : hana.ALPHANUM(10); b : hana.SMALLINT; c : hana.TINYINT; d : hana.SMALLDECIMAL; e : hana.REAL; h : hana.VARCHAR(10); i : hana.CLOB; j : hana.BINARY(10); k : hana.ST_POINT; l : hana.ST_GEOMETRY; };

91
Public
CDS Views – OrderBy
view EmployeesView as select from Employee { orgUnit, salary } order by salary desc;

92
Public
CDS Views – Case
entity MyEntity { key id : Integer; a : Integer; color : String(1); }; view MyView as select from MyEntity { id, case color when 'R' then 'red‘ when 'G' then 'green‘ when 'B' then 'blue‘ else 'black‘ end as color, case when a < 10 then 'small‘ when 10 <= a and a < 100 then 'medium‘ else 'large‘ end as size };

93
Public
CDS Unmanaged Associations
entity Employee { key id : String(256); officeId : Integer; }; entity Room { key id : Integer; inhabitants : Association[*] to Employee on inhabitants.officeId = id; };
entity Thing { key id : Integer; parentId : Integer; parent : Association[1] to Thing on parent.id = parentId; children : Association[*] to Thing on children.parentId = id; };

94
Public
CDS Backlink workaround via Unmanaged Associations
entity Header { key id : Integer; items : Association[*] to Item on items.headerId = id; description : String(120); };
entity Item { key headerId : Integer; key id : Integer; header : Association[1] to Header on header.id = headerId; description : String(120); };

95
Public
CDS Many to Many relationships
entity Employee { key id : Integer; name : String(80); projectLinks : Association[*] to E2P on projectLinks.e_id = id; };
entity Project { key id : Integer; name : String(80); employeeLinks : Association[*] to E2P on employeeLinks.p_id = id; };
entity E2P { key e_id : Integer; key p_id : Integer; projects : Association[*] to Project on projects.id = p_id; employees : Association[*] to Employee on employees.id = e_id; };

96
Public
CDS Many to Many relationships (continued)
view EmployeesWithProjects as select from Employee { name as EmployeeName, projectLinks.projects.id as projectId, projectLinks.projects.name as projectName };
view ProjectsWithEmployees as select from Project { name as projectName, employeeLinks.employees.id as EmployeeId, employeeLinks.employees.name as EmployeeName };

97
Public
CDS Full Text Index Annotation
entity Header { key id : Integer; @SearchIndex.text: { enabled: true } @SearchIndex.fuzzy: { enabled: true } description : String(120); };

Extended Programming Model XSDS

100
Public
Goals of seamless HDB consumption in XSJS
General HANA consumption
Native JavaScript embedding of HANA database artifacts
Structured API calls instead of low-level SQL interface (ODBC)
Less boilerplate coding, e.g., result set conversion
XSDS: Native CDS consumption
Import CDS entities as native JavaScript objects
Understand CDS metadata for working with JavaScript objects

101
Public
XS Data Services (XSDS)
XSDS as Native CDS Client and Query Builder for XSJS
Succeeds three HANA Consumption projects by Platform Research
XS ORM
XS Query Builder
CDS
XS Data Services
XS Relations
+

Extended Programming Model XSDS – Data Models

103
Public
Core Data Services
CDS is central HANA functionality provided via SQL interface
Core Data Services (CDS) are a cross-platform set of concepts and tools to define semantically rich data models for SAP HANA applications. A central part of CDS is the object-relational mapping that links semantically meaningful entities to their technical representation as records in the HANA database.

© 2014 SAP SE or an SAP affiliate company. All rights reserved. Public 104
CDS and XSDS
XSDS is the native CDS embedding for JavaScript in the XS Engine
CDS
XSDS
HANA
XS

105
Public
Sample CDS data model
namespace sap.hana.xsopen.dbutils.xsds.examples.data;
context bboard {
entity user {
key uid: Integer not null;
Name: String(63) not null;
Email: String(63);
Created: UTCDateTime; };
type text {
Text: String(255);
Lang: String(2); };
entity post {
key pid: Integer not null;
Title: String(63) not null;
Text: text;
Author: association [1] to user;
Parent: association [0..1] to post;
Rating: Integer;
// Comments: association [0..*] to comment via backlink Parent;
// Tags: association [0..*] to tag via entity tags_by_post;
Created: UTCDateTime; };
};

106
Public
Consume CDS model data in XS
Import and extend CDS entity definitions
Reads available metadata on types, keys, associations
Supports extension, projection, renaming of entity definitions
Already supports CDS via backlink, via entity associations
Pre-generation of imports moves metadata processing overhead to dev time
var User = XSDS.$importEntity("demo.bboard", "bboard.user");
var Post = XSDS.$importEntity("demo.bboard", "bboard.post", { Comments: { $association: { $entity: Comment, $viaBacklink: "Post" } } });

107
Public
Import pre-generation
CDS import costly operation
XS Engine has no session state
 (Re-)Import of CDS metadata for every single requests
Pregeneration of imports improves performance
Serialize result of imports into single library file
var UserLib = $.import("demo.bboard", "User"); var User = UserLib.demo.bboard.User.entity;

108
Public
Main XSDS features
XS Data Services
Entity instances and unmanaged values
Query Builder
Ad-hoc queries
Based on CDS QL (WIP)
Manual consistency
Full HANA support
CDS Entities and Types
HANA
Entity Manager
Lightweight ORM
Navigation to associations
Data consistency
Limited query functionality
+

Extended Programming Model XSDS – Managed Mode

110
Public
XSDS managed entities
Create, retrieve, update, and delete instances of entities
Result is plain JavaScript object
Optional lazy retrieval of associated instances to avoid "n+1 problem"
Optimized JOIN strategy to minimize DB queries (WIP) Write changes to database explicitly
Manager tracks local changes for minimal updates
var post = Post.$get({ pid: 101 });
if (post.Author.Name === "Alice") post.Rating++;
post.$save();

111
Public
Reference: instance manipulation
Retrieve by key
Update instance
Create new instance
Delete instance
var post = Post.$get({ pid: 101 });
post.Author.Name = "Alice";
post.$save();
var user = new User({ Name: "Alice", Created: new Date() }); user.$save();
post.$discard();

112
Public
Instance management
Entity instances are managed
Instances are singleton objects with "personality"
Associated instances are stored by reference
Upside: Runtime guarantees on consistency
Single consistent view on every instance (enforced by $persist)
Automatic association management (1:1, 1:n, m:n)
Downside: Entity cache
Additional overhead for instance management
Only limited subset of database functionality for instance retrieval

113
Public
Consistent instance view
HANA
XSJS
{ uid: 1, Email: "alice@sap.se" }
{ pid: 103, Title: "Third", Author: }
{ uid: 2, Email: "bob@sap.ag" }
pid
Title
Author.uid
101
First
1
103
Third
1
uid
Email
1
alice@sap.ag
2
bob@sap.ag
{ pid: 101, Title: "First", Author: }

114
Public
Database and transaction handling
Transparent database and transaction handling
Minimal XSDS runtime (metadata processing, entity cache, type conversion)
Exposes/reuses DB functionality as much as possible (e.g., constraints checks)
XSDS uses single DB connection and single transaction
Suited for single-threaded, per-request execution model of XS Engine
Supports auto commit, explicit commits, and rollbacks
Supports connection configurations (.xssqlcc)
post1.$save();
post2.$save();
XSDS.Transaction.$commit();

Extended Programming Model XSDS – Unmanaged Mode

116
Public
XS Code
CDS Metadata Definition
CDS queries from XSJS: motivation
„Get the names of authors which commented on their own posts and the text of that comment“
var rs = conn.prepareStatement(‘
SELECT a."Name", c."Text.Text"
FROM "bboard.post" p
JOIN "bboard.user" a ON p."Author.uid"=a."uid"
JOIN "bboard.comment" c ON p."pid"=c."Post.pid"
JOIN "bboard.user" ca ON c."Author.uid"=ca."uid"
WHERE a."uid"=ca."uid“').execute();
while (rs.next()) {
rs.getInt(1); rs.getString(2);
}
entity post {
key pid: Integer not null;
Author: association [1] to user;
};
entity user {
key uid: Integer not null;
Name: String(63) not null;
};
entity comment {
key cid: Integer not null;
Text: text;
Author: association[1] to user;
Post: association[1] to post; //via backlink
};
Leaking Abstraction:
Column name can only be derived from table definition
Convenience:
„String-based“ query interface
& manual result set processing
Redundant Code:
JOINs could be derived from metadata

117
Public
XSDS queries
Ad-hoc queries
Construct general queries in a JavaScript-like way
Yields plain JavaScript object as unmanaged value, not instance
Query Language
Incremental query building
Operators $project, $where, $matching, ...
Full support for CDS path navigation
Expression language based on CDS Query Language using fluent API
Alternative, more concise JSON-like selection notation for restricted subset
var query = Post.$query().$where(Post.Author.Name.$eq("Alice"));
var results = query.$execute();

118
Public
Demo: XSDS queries - $project
Projections with CDS navigation expressions
Result:
var res = Post.$query().$project({ Author: {Name: true},
Comments: {Author: {Name: true}}, Title: "TitleOfPost"})
.$execute();
[{ Author: {
Name: "Alice"
},
Comments: {
Author: {
Name: "Bob"
}
},
TitleOfPost: "First Post!"
}, ...]

119
Public
Demo: XSDS queries - $where
Complex where conditions:
Predefined operators of expression language:
$eq, $ne, $gt, $lt, $ge, $le, $like, $unlike
Escape to any SQL operator:
var selfCommentingPosts = Post.$query().$where(Post.Comments.Author.pid.$eq(Post.Author.pid))
.$execute();
var somePost = Post.$query() .$where(Post.Rating.$prefixOp('SQRT').$gt(2)).$execute();
translated to:
WHERE SQRT ("t0"."Rating") > 2

120
Public
Demo: XSDS queries - $matching
Selection using “template” for the result
Unmanaged version of $find, $findAll, uses same template language
More concise Less expressive
var interestingPosts = Post.$query().$matching({
Rating: {
$gt: 2
},
Tags: {
Name: "+1"
}
}).execute();
+
–

121
Public
Demo: incremental query construction
Incremental construction with immutable query objects
Explicit trigger
// build query without DB call
var qBadPosts = Post.$query().$where(Post.Author.pid) .$eq(Post.Comments.Author.pid)));
// refine query
var qStarBadPosts = qBadPosts.$where(Post.Rating.$gt(4));
// trigger actual DB calls
var badTitles = qBadPosts.$project(
{ Title: true, Author: {Name : true}}).$execute();
var recentBadTitles = qStarBadPosts.$project({ Title: true }) .$execute();

122
Public
Reference: JSON expressions
Simple expressions
Complex expressions
JSON Expression Language Operators
$eq $ne $lt $le $gt $ge $like $unlike $null
Post.$find({ mandt: "001", pid: 101 });
Post.$find({ Title: { $like: "First%" },
Rating: { $gt: 1, $lt: 3 }, Created: { $lt: Date.now() – 3600 } });

123
Public
Query builder
Optimized query construction
Allows for incremental query construction without database roundtrips
Immutable query objects support sharing of subqueries
Just-in-time translation into plain SQL, using needed joins
SELECT "t0.Author"."Name" AS "t0.Author.Name",
"t0.Author"."Email" AS "t0.Author.Email",
"t0"."Title" AS "t0.Title"
FROM "sap.hana.xsopen.xsds.examples::bboard.post" "t0"
JOIN "sap.hana.xsopen.xsds.examples::bboard.user" "t0.Author"
ON "t0"."Author.uid"="t0.Author"."uid"
WHERE ("t0"."Rating" > 2) AND ("t0.Author"."Name" = 'Alice')

Extended Programming Model XSDS - Procedures

125
Public
XS Procedures Library
A standard reusable library shipped by SAP to simplify Stored Procedure calls from XSJS and make they “feel” like JavaScript functions

Extended Programming Model Repository REST API

127
Public
SAP HANA REST API
•An implementation of the Orion Server API within HANA
•Designed to allow development tools access to HANA capabilities, especially the Repository.

128
Public
SAP HANA REST API – server API parts
•File API
•Workspace API
•Transfer API
•Metadata API
•Change Tracking API
•OData Services
•Info API

129
Public
SAP HANA REST API – File API
•File API
•Workspace API
•Transfer API
•Metadata API
•OData Services
•Info API
•Enables you to browse and manipulate files and directories via HTTP
•Basic HTTP methods GET, PUT, and POST to send requests
•JSON is used as the default representation format
•Can also retrieve metadata and previous versions of the content

130
Public
SAP HANA REST API – Workspace API
•File API
•Workspace API
•Transfer API
•Metadata API
•OData Services
•Info API
•Enables you to create and manipulate workspaces and projects via HTTP
•Workspace and project concepts taken over from Eclipse
•Both ORION concepts are technically mapped to the SAP HANA XS package concept
•When you create a project, it is an SAP HANA XS sub package in the specified workspace package

131
Public
SAP HANA REST API – Transfer API
•File API
•Workspace API
•Transfer API
•Metadata API
•OData Services
•Info API
•Is used to import and export packages and files
•Resumable, chunked uploads of file content
•Export not yet implemented. Use the File API for export.

132
Public
SAP HANA REST API – Metadata API
•File API
•Workspace API
•Transfer API
•Metadata API
•OData Services
•Info API
•Provides services to support search and auto completion scenarios
•it is possible to retrieve metadata for tables, views, procedures, functions, sequences, and schemas as well as CDS metadata

133
Public
SAP HANA REST API – Change Tracking API
•File API
•Workspace API
•Transfer API
•Metadata API
•OData Services
•Info API
•Enables you to make use of specific lifecycle-management features included with the SAP HANA Repository via HTTP
•For example: you can ensure that an export operation includes only the latest approved versions of repository objects

134
Public
SAP HANA REST API – OData Services
•File API
•Workspace API
•Transfer API
•Metadata API
•OData Services
•Info API
•A set of OData services that enable access to configuration data stored in the SAP HANA environment
•Includes details on the following:
•Delivery Units
•INI Configuration files
•M_FEATURES

135
Public
SAP HANA REST API – Info API
•File API
•Workspace API
•Transfer API
•Metadata API
•OData Services
•Info API
•Can be used to display information about the current version of the REST API.
•Includes a description of the current version of the delivery unit and the number of commands (API entry points) that are currently supported by the REST API

136
Public
SAP HANA REST API - SapBackPack
•SAP specific functionality (like activation) added via the additional parameter - SapBackPack

138
Public
SAP River – What’s New in SPS 09?
The benefits of the SAP River language (RDL) application development environment were validated by partners and early adaptors. However, based on feedback we received, and consistent with our strategic direction of building open and standard environments, SAP has decided to abandon a proprietary language approach, and to reapply and integrate the SAP River assets and principles within a cloud based development environment as part of the HANA Cloud Platform.
The SAP River language will therefore no longer be available as a stand-alone development environment in SAP HANA.

139
Public
SAP River assets reused
SAP River application explorer rebuilt as SAP OData Explorer in SPS09
General OData test and data generation tool which supports XSODATA services

140
Public
SAP River concepts realized in alternative ways
Integrated one-click debugging
Step from the application server layer logic directly in database layer logic within one debug session

141
Public
SAP River concepts realized in alternative ways - XSDS
XSDS: Native CDS consumption
Import CDS entities as native JavaScript objects
Understand CDS metadata for working with JavaScript objects
Import and extend CDS entity definitions
Reads available metadata on types, keys, associations
Supports extension, projection, renaming of entity definitions
Already supports CDS via backlink, via entity associations
var Post = XSDS.$importEntity("demo.bboard", "bboard.post", { Comments: { $association: { $entity: Comment, $viaBacklink: "Post" }}});

142
Public
SAP River concepts realized in alternative ways – XSDS (continued)
XS Data Services
Entity instances and unmanaged values
Query Builder
Ad-hoc queries
Based on CDS QL (WIP)
Manual consistency
Full HANA support
CDS
Entities and Types
HANA
Entity Manager
Lightweight ORM
Navigation to associations
Data consistency
Limited query functionality
+

143
Public
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.

144
Public
How to find SAP HANA documentation on this topic?
•In addition to this learning material, you can find SAP HANA platform documentation on SAP Help Portal knowledge center at http://help.sap.com/hana_platform.
•The knowledge centers are structured according to the product lifecycle: installation, security, administration, development:
SAP HANA Options
SAP HANA Advanced Data Processing
SAP HANA Dynamic Tiering
SAP HANA Enterprise Information Management
SAP HANA Predictive
SAP HANA Real-Time Replication
SAP HANA Smart Data Streaming
SAP HANA Spatial
•Documentation sets for SAP HANA options can be found at http://help.sap.com/hana_options:
SAP HANA Platform SPS
What’s New – Release Notes
Installation
Administration
Development
References
•

Thank you
Contact information
Thomas Jung
SAP HANA Product Management
AskSAPHANA@sap.com

146
Public
© 2014 SAP SE 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 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 SE’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 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 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.

SAP HANA SPS09 - XS Programming Model

More Related Content

Viewers also liked (9)

Similar to SAP HANA SPS09 - XS Programming Model (20)

More from SAP Technology (20)

Recently uploaded (20)

SAP HANA SPS09 - XS Programming Model