Sap Se

Sap Ag

Joachim Fitzer

Simon Seif

Felipe Musse

Juergen Sattler

Pietro Francesco Menna

Ioannis Grammatikakis

Hilmar Demant

Markus Viol

Jan Heiler

Frank Schertel

Sebastian Droll

Thorsten Weber

Reinhold Kautzleben

Eduardo Carvalho

Eduardo Berlitz

Alexandre Faltz

Willian Mendes

Boris Gruschko

Klaus-Peter Lang

Frank Brunswig

Udo Peter Klein

Juergen Specht

Daniel Hutzel

Thomas Gauweiler

Jan Teichmann

Steffen Tatzel

Daniel Goldmann

Frank Wagner

Jens Weiler

Dirk A Giebel

Heiko Steffen

Pietro Francesco Menna Ruiz Diaz

Stefan A Baeuerle

Rainer Brendle

Jens Freund

Marcel Hermanns

Rolf Krane

Joachim Kenntner

Alexander Rauh

Stephan Lange

Ye Jin

David Kernert

Thomas Reiss

Martin Tewes

Klaus Eschenroeder

Tugba Bodrumlu Asena

Ecem Unal

Hasan Turken

Daniel Johannsen

Christian Krause

Hendrik Radke

Anton Niadzelka

Pietro Francisco Menna

A file is created in a standardized format that defines a type of a containerized application and includes information for deployment of the containerized application. A single parser of the standardized format is thus enabled to deploy different types of containerized applications. The standardized file format includes an application definition. The application definition includes a service, a port list, a container list, a volume mount list, an access mode list, a resource usage list, or any suitable combination thereof. A client device presents a user interface that allows a user to select a containerized application to execute. An application server parses an application template file for the selected containerized application and, based on the information in the application template file, causes one or more servers (e.g., one or more Kubernetes cluster nodes) to execute the containerized application.

Standardized format for containerized applications

A user requests installation of a software package on a server. The server identifies an artifact for the software package installed on a first layer of an overlay file system. Based on dependency information for the artifact, the server identifies one or more additional artifacts that the artifact depends on, installed on additional layers of the overlay file system. Instead of duplicating the software package and its dependencies in storage for the user, the server updates a layer strategy for the user. A layer strategy indicates a set of layers to be used by an overlay file system in generating a logical file system. The updated layer strategy for the user includes both the layer for the artifact of the requested software package and the layers for the additional artifacts that the software package depends on.

Software installation through an overlay file system

Example methods and systems are directed to a multitenant application server using a union file system. Each tenant has one or more users and a tenant layer in the union file system. Each user has a user layer in the union file system. The union file system provides a logical file system to each user based on the user layer, the tenant layer, and a base layer comprising a set of application layers. A first user shares an application template file with other users of the same tenant by moving the file from the first user's user layer to the tenant layer. After the file is moved, all users of the tenant have access to the application defined by the application template file. The moving of the file is achieved by modifying metadata for the file.

Multitenant application server using a union file system

A client device sends a connection request to a virtual system in a Kubernetes cluster. The connection request identifies the client device and the application to which the request pertains. Based on a tenant associated with the client device, the virtual system connects the client device to an instance of the application. The instance of the application has access to data for the tenant but not for other tenants. Another client device of the tenant sends another connection request to the virtual system for a connection to another application. Because the tenant is the same, the instance of the other application may access the same data as the instance of the first application. In this way, applications for a single tenant may share data while maintaining the security of the data from other tenants.

Kubernetes as a distributed operating system for multitenancy/multiuser

A method for generating a data processing pipeline is provided. The method may include generating a user interface for displaying, at a client, a first operator node and a second operator node. The first operator node and the second operator node may each correspond to a data processing operation. In response to one or more inputs received from the client via the user interface, the first operator node and/or the second operator node may be added to a graph displayed in the user interface. The graph may be representative of a data processing pipeline. The first operator node and the second operator node may further be interconnected with an directed edge. The data processing pipeline may be generated based on the graph. Related systems and articles of manufacture, including computer program products, are also provided.

Data processing pipeline engine

Disclosed herein are system, method, and computer program product embodiments for driving multiple user interfaces using a backend view controller. A view interface system that is capable of displaying multiple user interfaces of different view formats may receive a data set request to display a data set in a particular view format. The view interface system may then transmit, to the backend view controller, the data set request and receive an indication that the data set is exposed by the backend view controller. Based on the indication, the view interface system may perform data binding of the data set to interface objects associated with the view format to form a user interface based on the view format and display the user interface.

Driving different types of user interfaces with a single backend view controller

Disclosed herein are system, method, and computer program product embodiments for providing access to changed states in a data source to front-ends and back-ends in a data orchestration system. When displaying a scene including transformed data, a data orchestration system may receive a change to the data source from the data repository or a client viewing the data. The data orchestration system may transform data based on configured data pipelines and propagate the changed state to all viewing clients and to the backend data repository. By managing the connections, pipelines, operators, data sources, clients, backends, and other components, the data orchestration system may provide intelligent data solutions and advanced analytic capabilities across the entirety of an organization's data landscape.

Providing changing data-source states to front ends viewing a scene in a data orchestration system

Disclosed herein are system, method, and computer program product embodiments for providing a collaborative web application and data system. An embodiment operates by receiving a changed value to data presented in a first web interface with a first set of interface components. A data source is updated based on the changed value to include the changed value. A second web interface associated including a second set of interface components at least one of which is different from the first set of interface components is identified. An update to the second web interface is provided based on the changed value.

Collaborative web application and data system

Example methods and systems are directed to multitenancy using an overlay file system. Each tenant has one or more users and a tenant layer in the overlay file system. Each user has a user layer in the overlay file system. The overlay file system provides a logical file system to each user based on the user layer, the tenant layer, and a strategy comprising a set of application layers. A first user shares a file with other users of the same tenant by moving the file from the first user's user layer to the tenant layer. After the file is moved, all users of the tenant have access to the file. The moving of the file is achieved by modifying metadata for the file.

Multitenancy using an overlay file system

Disclosed herein are system, method, and computer program product embodiments for providing extension points to alter a data source in a data pipeline. By providing a before-state-change extension point, a data orchestration system may allow connected clients to aggregate delta from a changed state source, allowing the data orchestration system to include only changed or added data in a transferred data state. By providing an after-state-change extension point, a data orchestration system may harness additional customizations, for example, effectively and efficiently handle changes to the state made by a viewing client following the transmission of a delta of changes.

Creating custom code on back-end and front-end using extension points

Disclosed herein are system, method, and computer program product embodiments for providing a dashboard user interface design and integration system. An embodiment operates by receiving a request to generate an interface associated with a data source and establishing a connection with the data source to receive data from the data source. An indication of a component to be displayed on the interface is received and the interface is generated. The interface includes the component and is coupled to the data source.

Dashboard user interface for data driven applications

Growing community of inventors

Schriesheim, Germany

Joachim Fitzer