SAP HANA Lightweight Application Server – XS Engine

The screen of S/4 HANA is basically Fiori. Since HANA XS works as a web server, the client-side UI says that static Html / CSS / JS should be arranged as it is. As control flow technology, it was explained that processing can be written by server side JavaScript, and processing can be written by REST based Web protocol called OData. The “Analytical apps” of Fiori described in “S/4 HANA component screen (Fiori)” described above runs on the HANA XS engine.

XS of the engine “XS” is E X Tended Application S stands for services. It refers to the layer that develops and deploys applications on HANA. It becomes like the figure below when it divides the layer of HANA including the XS engine. In the middle is the XS engine, which connects the UI to the data layer. By using a web application on the XS engine, the bottom layer data and UI can be connected to become a self-contained integrated platform with HANA alone.

The HANA XS build app is based on the http protocol and provides the following services:

1. Access the HANA database via http.

2. Support dynamic HTML5 applications, it also has a view layer solution like sap UI5.

3. Powerful search services such as fuzzy search and text analysis.

4. Distributed code management scheme, the client and server have code, the client establishes a repository to share the code to the server.

The development of the HANA app follows this principle: Push the control flow down!

Introduction of Examples of Applications that Make Use of HANA XS

Use statistical processing function in HANA

The following was introduced

  • SAP’s own PAL: In-memory prediction analysis function
  • Integration with statistical language “R”

Geospatial Information Engine

This engine handles the area enclosed by points, lines and polygons.

Graph Engine

There was an introduction on how to handle complex related data such as lot tracking and family tree.

It is data that is expressed by attaching properties to each vertex (vertex) and the edge that connects them (edge).

In addition, it can be expressed simply in comparison with SQL when expressed in SAP’s own language called GEM. 

Text-Based Processing (Text Search, Text Analysis, Text Mining)

In the text analysis demo, it was introduced how to output Japanese morphological analysis.

Contents of XS Engine

The contents of the XS engine are basically two things: OData service and Web resource. Web resources are SAPUI5 and server-side JavaScript.

SAPUI5 is a web application that supports multiple devices and multiple platforms. You can see that the figure below looks very clean on the screen created with SAPUI5. It is almost the same implementation method as SAPUI5 that works with ABAP stack and JAVA stack. Because it is an open world technology on the web, you can use three.js etc.

SAPUI5 is a web application that supports multiple devices and multiple platforms. You can see that the figure below looks very clean on the screen created with SAPUI5. It is almost the same implementation method as SAPUI5 that works with ABAP stack and JAVA stack. Because it is an open world technology on the web, you can use three.js etc.

Question & Answer

Question: Does the application created with SAP HANA XS work other than HANA?

Answer: The server side is only on HANA. Static content may be anywhere.

Question: Can the c4.5 decision tree actually be verified?

Answer: Yes, the c4.5 decision tree actually is verified.

SAP HANA XS Engine Trace File Log Entry Spoofing Vulnerability

The SAP HANA’s XS engine (hdbxsengine) is deficient in the handling of unspecified debug functions, and is therefore disguised as a trace file log entry, resulting in a service disruption (disk consumption and process crash) condition. Vulnerability exists. 

Expected impact A third party can spoof trace file log entries through a specially crafted HTTP request, which could result in a denial of service (disk consumption and process crash) condition.

Leave a Reply

Your email address will not be published. Required fields are marked *