sap-archive/com.sap.opensap.hana5.example

openSAP HANA5/HANA6 Course: Example Completed Implementation

Important Notice

This public repository is read-only and no longer maintained.

com.sap.openSAP.hana5.example

openSAP HANA5 Course: Example Completed Implementation

In this course, we will focus on the new and improved features that were introduced in SAP HANA SPS 11 and 12. Developers taking this course should be able to get up to speed quickly and begin leveraging these new features to enhance their own productivity, as well as tap into powerful new features of SAP HANA itself. Students will learn to use SAP Web IDE for SAP HANA to develop both HDI (SAP HANA Deployment Infrastructure) and XSA (SAP HANA extended application services, advanced model) based applications.

Course Summary

With the delivery of SAP HANA SPS 11, we see a large number of new features in both the underlying SAP HANA infrastructure and in particular in the custom development aspects of SAP HANA native development.

Requirements change over time, and so too has XS within SAP HANA. SAP HANA extended application services in SPS 11 represents an evolution of the application server architecture, building upon the previous strengths while expanding the technical scope. This course will offer an overview of the new architecture and the various expanded capabilities it makes possible.

All of the architectural changes described in this course can be summarized in one key point: Choice. SAP HANA SPS 11 and higher offers customers and partners the freedom of choice of technologies, tools, and deployment options for high-scale development and operation of native SAP HANA applications.

It is also easier to choose between on-premise and cloud deployment. Because of the shared architecture being delivered going forward, it will soon be easy to develop an application that can be deployed on-premise, in the cloud, or in both scenarios without any coding changes.

In this course, we’ll assume that you have baseline knowledge of SAP HANA development and will instead focus on the new and improved features that were introduced in SAP HANA SPS 11 and 12. Developers taking this course should be able to get up to speed quickly and begin leveraging these new features to enhance their own productivity, as well as tap into powerful new features of SAP HANA itself. Students will learn to use SAP Web IDE for SAP HANA to develop both HDI (SAP HANA Deployment Infrastructure) and XSA (SAP HANA extended application services, advanced model) based applications.

Course Characteristics

Starting from: November 2, 2016, 09:00 UTC. (What does this mean?) Duration: 5 weeks (3 - 4 hours per week) Final exam: December 7-15, 2016 Course language: English How is an openSAP course structured?

Course Content

Week 1: Introduction Week 2: Database Development Week 3: Application Server and UI Development Week 4: Node.js Week 5: Wrap-Up Week 6: Final Exam

Target Audience

Application developers SAP HANA developers HCP developers Course Requirements Basic programming knowledge including HTML, JavaScript, and SQL Baseline SAP HANA development knowledge from one of the previous openSAP HANA courses would be helpful

How to import code to SAP Web IDE for SAP HANA?

The code can be imported to SAP Web IDE for SAP HANA version SP12 and up.

• Launch SAP Web IDE for SAP HANA

• Navigate to File->Git->Clone repository

• Enter the URL of the repository https://github.com/SAP/com.sap.openSAP.hana5.example

• Click Ok button

##Getting Help If you need addition help resources beyond this document, we would suggest the following content: • The Online Help at http://help.sap.com/hana/SAP_HANA_Developer_Guide_for_SAP_HANA_XS_Advanced_Model_en.pdf

Exercise Summary

EXERCISE 1 - HELLO WORLD

Objective

In this first exercise, we will connect to the remote system, run the new project wizard, and then create an HTML5 module to serve as the application endpoint and proxy all of our services and client-side content. At the end of this exercise you will be able to connect to your server via web browser and see a Hello World message.

EXERCISE 2 –DATABASE ARTIFACT DEVELOPMENT

Objective

In this exercise, we will continue to develop our overall application. Applications in the HANA/XS Advanced world, are often made up of multiple modules at design time which deploy to separate micro-services or database container content. We created client side UI application content in the first exercise using the HTML5 module. In this exercise we will create database artifacts, such as database table, stored procedures and user defined functions, using the HDB (HANA Database) module. We will then see how we build these database artifacts using the new container-based, schema-less HDI (HANA Deployment Infrastructure) concepts.

Exercise Description

• Database Tables via HDBCDS • Stored Procedures via HDBPROCEDURE • User Defined Functions via HDBFUNCTION • Initial table data load via CSV • Deploy to HANA via HDI

EXERCISE 3 –XSJS AND XSODATA SERVICES

Objective

For this exercise we will now build the XSJS and XSODATA services used to expose our data model to the user interface. Although XS Advanced runs on node.js, SAP has added modules to node.js to provide XSJS and XSODATA backward compatibility. Therefore you can use the same programming model and much of the same APIs from XS, classic even within this new environment. .

Exercise Description

• Node.js XSJS Bootstap • XSJS Services • XSODATA Services

EXERCISE 4 – SAPUI5 USER INTERFACE

Objective

For this exercise we will build a proper SAPUI5 user interface that consumes both the XSJS and XSODATA services from our Node.js module.

Exercise Description

• SAPUI5 Entry Point • SAPUI5 Component • SAPUI5 Views • SAPUI5 Controllers

EXERCISE 5 – NODE.JS

Objective

In exercise 3 we created a Node.js module, but didn’t really do much Node.js specific programming. We only were using Node.js to run XSJS and XSODATA services. The support for XSJS and XSODATA is an important feature for XS Advanced. It not only allows backward compatible support for much of your existing development; but it provides a simplified programming model as an alternative to the non-block I/O event driven programming model normally used by Node.js.

But we certainly aren’t limited to only the functionality provided by XSJS and XSODATA. We have access to the full programming model of Node.js as well. In this exercise we will learn how to extend our existing Node.js module in the SAP Web IDE for SAP HANA.

You will learn about how to create and use reusable code in the form of node.js modules. You will use packages.json to define dependencies to these modules which make the installation of them quite easy. You will use one of the most popular modules – express; which helps with the setup the handling of the request and response object. You will use express to handle multiple HTTP handlers in the same service by using routes.

You will learn about the fundamentals of the asynchronous nature of nodel.js. We will so see how this asynchronous capability allows for non-blocking input and output. This technique is one of the basic things that makes Node.js development different from other JavaScript development and also creates one of the reasons for its growing popularity. We will see how these techniques are applied to common operations like HTTP web service calls or even SAP HANA database access. We will also see how to create language translatable text strings and HANA database queries from Node.js.

Our final part of this exercise will demonstrate the ease at which you can tap into the powerful web sockets capabilities of Node.js. We will use web sockets to build a simple chat application. Any message sent from the SAPUI5 client side application will be propagated by the server to all listening clients.

Exercise Description

• Modules • Express Module and package.json • Local Modules • SAP HANA database access from node.js • Basic asynchronous processing • Non-blocking I/O • Non-blocking HTTP requests • Non-blocking database requests • Text bundles • Web Sockets chat application

EXERCISE 6 – PACKAGING FOR TRANSPORT

Objective

Now that we have a completed application we can package it for transport

Exercise Description

• Build all modules • Build project to create MTAR • Download MTAR

com.sap.opensap.hana5.example's Issues

static port of module

Good morning!
I faced with problem - when you redeploy XSA application, for different module XSA assigns random ports. I need to assign static port to module. I saw documentation and I found there that in mta.yaml there is parameter port in scope of module, which I can use. As I understood It could help to solve issue.

I put those parameter in mta.yaml in Parameters of module:

But When I run It - It fails with message in log:
"Unexpected type Double for option "port" of app "qs1svgEnowhBkHra-testPort-uiPort", expected Integer!"

Do you know, is it possible to fix port in application?
And may be I make It wrong?

Moving file cause "xs deploy" to fail

Hi,
I am using HANA Express 2.0 with web ide version 4.2.18.
I moved a file from one folder to another and while deploying to test space (xs deploy <mtar>) I got an error:

Merging... ok
3/9/18 6:49:23.421 AM [APP/2-1/deploy] OUT Error: "calc.scenario://requestStatus": the object cannot be provided more than once [8212002]
3/9/18 6:49:23.421 AM [APP/2-1/deploy] OUT "src/modelling/requestStatus.hdbcalculationview": the file would provide it
3/9/18 6:49:23.421 AM [APP/2-1/deploy] OUT "src/requestStatus.hdbcalculationview": the deployed file already provides it
3/9/18 6:49:23.421 AM [APP/2-1/deploy] OUT Error: "db://requestStatus": the object cannot be provided more than once [8212002]
3/9/18 6:49:23.421 AM [APP/2-1/deploy] OUT "src/modelling/requestStatus.hdbcalculationview": the file would provide it
3/9/18 6:49:23.421 AM [APP/2-1/deploy] OUT "src/requestStatus.hdbcalculationview": the deployed file already provides it
3/9/18 6:49:23.421 AM [APP/2-1/deploy] OUT Error: "db://requestStatus/hier/requestStatus": the object cannot be provided more than once [8212002]
3/9/18 6:49:23.421 AM [APP/2-1/deploy] OUT "src/modelling/requestStatus.hdbcalculationview": the file would provide it
3/9/18 6:49:23.421 AM [APP/2-1/deploy] OUT "src/requestStatus.hdbcalculationview": the deployed file already provides it
3/9/18 6:49:23.421 AM [APP/2-1/deploy] OUT Error: Calculating dependencies... failed [8212108]
3/9/18 6:49:23.421 AM [APP/2-1/deploy] OUT Error: Could not compose a consistent make graph [8212012]

But the build in development space using web-ide is fine.
Is there any way to deploy it, other than moving the file back to its original position?
Is it a possible bug which got fixed in later patches?

Regards,
Himanshu

The predefined session variable cannot be set via SET command: XS_APPLICATIONUSER

Hello,

I am having the following issue, "

Error: the predefined session variable cannot be set via SET command: XS_APPLICATIONUSER"

When accessing an .xsodata endpoint in my nodeJS app hosted on CF, this is the server.js I am using:

`/eslint no-console: 0, no-unused-vars: 0/
"use strict";
/*
var xsjs = require("@sap/xsjs");
var xsenv = require("@sap/xsenv");
var xsHDBConn = require("@sap/hdbext");
const express = require('express');
const passport = require('passport');
const JWTStrategy = require('@sap/xssec').JWTStrategy;
var port = process.env.PORT || 3000;
var hanaconfig = xsenv.getServices({ hana: {tag: "hana"} }).hana;

const app = express();

const services = xsenv.getServices({ uaa:'my-xsuaa' });
xsHDBConn.middleware(hanaconfig);

passport.use(new JWTStrategy(services.uaa));

app.use(passport.initialize());

app.use(passport.authenticate('JWT', { session: false }));

var options = {
//anonymous : false, // remove to authenticate calls
redirectUrl : "/index.xsjs"
};

// configure HANA
try {
options = Object.assign(options, xsenv.getServices({ hana: {tag: "hana"} }));
} catch (err) {
console.log("[WARN]", err.message);
}

// configure UAA
try {
options = Object.assign(options, xsenv.getServices({ uaa: {tag: "xsuaa"} }));
} catch (err) {
console.log("[WARN]", err.message);
}

// start server
xsjs(options).listen(port);

console.log("Server listening on port %d", port);
*/

"use strict";
var https = require("https");
var xsenv = require("@sap/xsenv");
var port = process.env.PORT || 3000;
var server = require("http").createServer();
https.globalAgent.options.ca = xsenv.loadCertificates();
global.__base = __dirname + "/";

//Initialize Express App for XSA UAA and HDBEXT Middleware
var xsenv = require("@sap/xsenv");
var passport = require("passport");
var xssec = require("@sap/xssec");
var xsHDBConn = require("@sap/hdbext");
var express = require("express");

//logging
var logging = require("@sap/logging");
var appContext = logging.createAppContext();
var logger = appContext.getLogger("/Application");
var tracer = appContext.getTracer(__filename);

//Initialize Express App for XS UAA and HDBEXT Middleware
var app = express();

passport.use("JWT", new xssec.JWTStrategy(xsenv.getServices({
uaa: {
tag: "xsuaa"
}
}).uaa));
app.use(logging.expressMiddleware(appContext));
app.use(passport.initialize());
var hanaOptions = xsenv.getServices({
hana: {
tag: "hana"
}
});
//hanaOptions.hana.rowsWithMetadata = true;
app.use(
passport.authenticate("JWT", {
session: false
}),
xsHDBConn.middleware(hanaOptions.hana)
);

//Setup Routes
//var router = require("/lib")(app, server);

//Start the Server
server.on("request", app);
server.listen(port, function() {
console.info(Logger Level: ${logger.getLevel().toString()});
console.info(Logger Error Enabled: ${logger.isEnabled("error")});
console.info(Tracer Level: ${tracer.getLevel().toString()});
console.info(Tracer Error Enabled: ${tracer.isEnabled("error")});
logger.error(HTTP Server: ${server.address().port});
tracer.info(HTTP Server: ${server.address().port});
console.info(HTTP Server: ${server.address().port});
});`

This is my package.json

{ "dependencies": { "@sap/approuter": "^5.6.4", "@sap/xsenv": "1.2.9", "@sap/xsjs": "3.3.7", "@sap/xssec": "^2.1.15", "@sap/hdbext": "4.7.2", "@sap/hana-client": "~2.3", "express": "^4.16.3", "passport": "^0.4.0" }, "devDependencies": { "@sap/xsjs-test": "2.0.16" }, "files": [], "main": "server.js", "name": "NODE_JS_MODULE", "scripts": { "start": "node server.js", "test": "node testrun.js" }, "engines": { "node": "8.x" }, "version": "1.0.0" }
Anything I am missing? This only fails when I setup the authentication, without it it's possible to call the odata service without issues. I am also able to retrive user authentication scopes from simple JS endpoint s (with authentication on), only with .xsodata (and possible any DB accesses it fails)

Regards,

no such package available : accept-language-parser

Hi, I'm having an issue on exercise: Exercise 5.1: Modules and Express. The moment i start running the core_js module, i get the error below. which is mainly about accept-language-parser, in which by right it should be able to see in the central repository. Is this an issue on xsa runtime or something else? I'm on hana2_sps2. Thanks!

[INFO] Injecting source code into builder...
[INFO] Source code injection finished
[INFO] ------------------------------------------------------------------------
npm ERR! Linux 3.12.67-60.64.24-default
npm ERR! argv "/hana/shared/H03/xs/app_working/appsrv13/executionroot/cbddfdb3-afc8-4d00-9b53-83bcd25188d3/app/META-INF/resources/nodejs/vendor/node6.11/bin/node" "/hana/shared/H03/xs/app_working/appsrv13/executionroot/cbddfdb3-afc8-4d00-9b53-83bcd25188d3/app/META-INF/resources/nodejs/vendor/node6.11/lib/node_modules/npm/bin/npm-cli.js" "install" "--registry" "https://hostname.com:51040"
npm ERR! node v6.11.1
npm ERR! npm v3.10.10
npm ERR! code E404

npm ERR! 404 no such package available : accept-language-parser
npm ERR! 404
npm ERR! 404 'accept-language-parser' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404 It was specified as a dependency of 'core-js'
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

npm ERR! Please include the following file with any support request:
npm ERR! /hana/shared/H03/xs/app_working/appsrv13/executionroot/cbddfdb3-afc8-4d00-9b53-83bcd25188d3/app/META-INF/.sap_java_buildpack/tomcat/temp/builder/sap.nodejs/builds/build-6176383983240492414/core_js/npm-debug.log

Internal SAP reference in settings files

The file httpclient.js contains a reference to an internal SAP server:

{path: "http://www.loc.gov/pictures/search/?fo=json&q=SAP&",
--
20 | host: "proxy.wdf.sap.corp",
21 | port: "8080",
22 | headers: {

Specifically, the server:

proxy.wdf.sap.corp

This artifact won't work outside the SAP firewall.

SAP Open Source runs regular scans looking for artifacts in the code which might indicate our internal code has accidentally released in to the Open Source stream. This file continues to show up in our scans. Can you please fix it, or remove it, so that it no longer shows up as an error?

Thank you.

Error: "db://gm2t" is required but not provided by any file

Hi Thomas,

great class, but i'm still struggling with exposing any data in views.

the full error console error dump:

12:17:03 PM (Builder) Build of /gm2p/gm2m started.
12:17:05 PM (DIBuild) Build of /gm2p/gm2m in progress
12:17:12 PM (DIBuild) ********** Printing /gm2p/gm2m Build Log **********
[INFO] Injecting source code into builder...
[INFO] Source code injection finished
[INFO] ------------------------------------------------------------------------
[email protected] node_modules/sap-hdi-deploy
├── [email protected]
├── [email protected] ([email protected], [email protected])
└── [email protected]

deploy@ start /hana/shared/HXE/xs/ea_data/vhcalhxedb/executionroot/194a7474-491c-4f94-948c-f4c3103f7ce5/app/tomcat/temp/builder/hdi-builder/builds/build-4577747085478011748/gm2m
node node_modules/sap-hdi-deploy/deploy.js

sap-hdi-deploy, version 2.0.0
Collecting files...
Collecting files... ok (0s 2ms)
Processing grants files...
Processing grants files... ok (0s 0ms)
Preprocessing files...
Preprocessing files... ok (0s 2ms)
Synchronizing files with the container "7QZP9UHWGMOQPQBN_GM2P_HDI_CONTAINER"...
4 modified or added files are scheduled for deploy
0 deleted files are scheduled for undeploy
Synchronizing files with the container "7QZP9UHWGMOQPQBN_GM2P_HDI_CONTAINER"... ok (0s 983ms)
Deploying to the container "7QZP9UHWGMOQPQBN_GM2P_HDI_CONTAINER"...
Starting make in the container "7QZP9UHWGMOQPQBN_GM2P_HDI_CONTAINER" with 4 files to deploy, 0 files to undeploy...
Migrating libraries...
Making...
No make necessary
Making... ok
Migrating libraries... ok
Making...
Preparing...
Preparing the make transaction...
Adding "src/admin.hdbrole" for deploy...
Adding "src/admin.hdbrole" for deploy... ok
Adding "src/gm2ap.hdbanalyticprivilege" for deploy...
Adding "src/gm2ap.hdbanalyticprivilege" for deploy... ok
Adding "src/gm2sp.hdbstructuredprivilege" for deploy...
Adding "src/gm2sp.hdbstructuredprivilege" for deploy... ok
Adding "src/gm2v.hdbcalculationview" for deploy...
Adding "src/gm2v.hdbcalculationview" for deploy... ok
Preparing... ok
Preparing the make transaction... ok
Checking the uniqueness of the catalog objects in the schema "7QZP9UHWGMOQPQBN_GM2P_HDI_CONTAINER"...
Checking the uniqueness of the catalog objects in the schema "7QZP9UHWGMOQPQBN_GM2P_HDI_CONTAINER"... ok
Calculating dependencies...
Expanding...
Expanding... ok
Precompiling...
Precompiling "src/admin.hdbrole"...
Precompiling "src/gm2ap.hdbanalyticprivilege"...
Precompiling "src/gm2sp.hdbstructuredprivilege"...
Precompiling "src/admin.hdbrole"... ok
Precompiling "src/gm2v.hdbcalculationview"...
Precompiling "src/gm2v.hdbcalculationview"... ok
Precompiling "src/gm2ap.hdbanalyticprivilege"... ok
Precompiling "src/gm2sp.hdbstructuredprivilege"... ok
Precompiling... ok
Merging...
Merging... ok
Error: Calculating dependencies... failed
Error: Make failed (1 errors, 0 warnings): tried to deploy 4 files (effective 4), undeploy 0 files (effective 0), redeploy 0 dependent files
Error: "db://gm2t" is required but not provided by any file
Error: Making... failed
Error: Starting make in the container "7QZP9UHWGMOQPQBN_GM2P_HDI_CONTAINER" with 4 files to deploy, 0 files to undeploy... failed
Error: Could not run make
Error: "db://gm2t" is required but not provided by any file
Deployment to container 7QZP9UHWGMOQPQBN_GM2P_HDI_CONTAINER failed - error Error executing: CALL "7QZP9UHWGMOQPQBN_GM2P_HDI_CONTAINER#DI".MAKE(#DEPLOY, #UNDEPLOY, #FOLDERPRMS, #PRMS, ?, ?, ?); (nested message: HDI call failed) [Deployment ID: none].
Error: Error: Error executing: CALL "7QZP9UHWGMOQPQBN_GM2P_HDI_CONTAINER#DI".MAKE(#DEPLOY, #UNDEPLOY, #FOLDERPRMS, #PRMS, ?, ?, ?);
(nested message: HDI call failed)
(2s 822ms)

npm ERR! Linux 3.0.101-71-default
npm ERR! argv "/hana/shared/HXE/xs/ea_data/vhcalhxedb/executionroot/194a7474-491c-4f94-948c-f4c3103f7ce5/app/resources/nodejs/vendor/node4.4/bin/node" "/hana/shared/HXE/xs/ea_data/vhcalhxedb/executionroot/194a7474-491c-4f94-948c-f4c3103f7ce5/app/resources/nodejs/vendor/node4.4/lib/node_modules/npm/bin/npm-cli.js" "start"
npm ERR! node v4.4.6
npm ERR! npm v2.15.5
npm ERR! code ELIFECYCLE
npm ERR! deploy@ start: node node_modules/sap-hdi-deploy/deploy.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the deploy@ start script 'node node_modules/sap-hdi-deploy/deploy.js'.
npm ERR! This is most likely a problem with the deploy package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node node_modules/sap-hdi-deploy/deploy.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs deploy
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!
npm ERR! npm owner ls deploy
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR! /hana/shared/HXE/xs/ea_data/vhcalhxedb/executionroot/194a7474-491c-4f94-948c-f4c3103f7ce5/app/tomcat/temp/builder/hdi-builder/builds/build-4577747085478011748/gm2m/npm-debug.log

********** End of /gm2p/gm2m Build Log **********
12:17:12 PM (Builder) Check console logs for details
12:17:12 PM (Builder) Build of /gm2p/gm2m failed.

the gm2 zip file is attached:
gm2p.zip

if you cannot support it, who can?

thx, greg

$.hdb.getConnection() undefined

Hello everyone,

Im facing several issues trying to follow some of tutorial instructions, the first one im facing is this:
1.- Create a template.
2.- Add a new NodeJS Module.
3.- In file called: server.js there're this lines:

try{
  options = Object.assing(options, xsenv.getServices({hana : {tag: "hana"}});
}catch(error){
 console.log("[WARN] : " + error.message);
}

I always got this: "[WARN] : No service matches hana"

Also, i have created this "CreateCountry" function (as tutorial said) in country.xsjs file:

function createCountry(country){
 var conn = $.hdb.getConnection();
 //.... truncated ....
}

And i got this error running Node Application (tinyjs):

"500 Cannot read property 'getConnection' of undefined"

Can someone please, give me a tip ?

WebIDE Debugger disconnected due to WebSocket Error

I'm doing the XSJS debugging exercise and inspecting the variables after an xsjs file operation is suspended by a debugger breakpoint. However, when I try to inspect the variables in the WebIDE console, the debugger will soon disconnect. Repeating the debugging process again and again consistently result in the debugger being disconnected. Checking on the chrome developer tools console, I can see some websocket error. Is this an issue on webide or on-premise hana?

system: HANA 2.0 SPS02

see screenshot below for reference:

outbound api return 500 response

Hi,
I use the demo to exploy outbound restful api by creating xsjs ,

but it return 500, any other configuration should be set

Regarts,
June