Sap Se

Sap Ag

Peter Eberlein

Volker Driesen

Stefan A Baeuerle

Bare Said

Jens Odenheimer

Arne Harren

Markus Schmidt-Karaca

Martijn De Boer

Timm Falter

Martin Hartig

Baré Said

Florian Mueller

Cheng Wang

Juergen Sattler

Rainer Brendle

Oliver Klemenz

Joachim Gaffga

Horst Schaude

Guenter Pecht-Seibert

Hartwig Seifert

Helmut Prestel

Andrey Engelko

Hilmar Demant

Volker Wiechers

Thomas Vogt

Olaf Meincke

Bjoern Mielenhausen

Stefan Rossmanith

Frank Schertel

Klaus Kopecz

Guenter Zachmann

Markus A Peter

Eckhard Farrenkopf

Andreas Poth

Robert Getzner

Wolfgang Janzen

Joerg Schmidt

Johannes Bechtold

Michael Engler

Tobias Brandl

Lars Spielberg

Silke Storch

Jürgen Sattler

Alexander Rieder

Thierry Tung

André Wagner

Shabana Ansari

Ramesh B G

Holger Neu

Hai Anh Pham

Lukas Gross

Heiko Ettelbrueck

Florian Tack

Christoph Lübbe

Martina Galabova

Voker Wiechers

Momchil Atanasov

The disclosure generally describes methods, software, and systems for re-architecting an existing software product provided as a service. A user input specifying current databases used for an old software product version is received. The user input includes a definition of a target persistency layout including databases assigned for storing a new software product version, the old software product version including one or more database tables and the new software product version including an adjustment to the one or more database tables to generate one or more target database tables. Sizes of the one or more database tables are read from a catalog of a database. A migration assessment of the new software product version is generated based on the sizes of the one or more database tables. A migration test of the one or more database tables is executed using the migration assessment to generate migration test results. An updated adjustment to the one or more database tables is provided based on the migration test results.

Refactoring workbench with migration support

Systems and methods include reception of an instruction to initiate an inquiry associated with a first instance of a first object type, querying of a system for object metadata defining a plurality of fields of the first object type, generation of a first user interface presenting one or more of the plurality of fields, reception of user input to the first user interface, the user input specifying a first one or more fields of the presented one or more of the plurality of fields, generation of the inquiry specifying the first one or more fields and the first instance, transmission of the inquiry, reception of a response to the inquiry including data associated with the first one or more fields and the first instance, and instructing of a system to update the data associated with the first instance of the first object type based on the received data associated with the first one or more fields and the first instance.

Low-development system for dynamic information queries

Methods, systems, and computer-readable storage media for receiving, from a first component and by a second component in a cloud platform, a call, a token, and a first client certificate, determining, by the second component, a first client identifier associated with the first component, and determining, by the second component, that the first client identifier is included in a manifest of the token, the manifest defining at least a portion of a communication path between components within the cloud platform, and in response: executing functionality responsive to the call.

Securing identity token forwarding

In an implementation, a request to compute a new machine-learning model for storage in a data lake is received by a role management system (RMS). A role history data is read by the RMS from a role management application and trace history data from a trace application. Metadata read from a plurality of persistencies is stored into the data lake as metadata history. The historic data and metadata history is read by a role recommendation engine (RRE) integrated into the RMS. The RRE, computes the new machine-learning model.

Role management system based on an integrated role recommendation engine

In an implementation, one or more rules associated with a DO from a rules database is read by a rule user interface (UI) plug-in associated with a data object (DO) maintenance UI. The one or more rules for the DO to fields associated with the DO on the DO maintenance UI are related by the rule UI plug-in. The rule UI plug-in, using the related one or more rules, auto-populates and validates received values for the fields associated with the DO on the DO maintenance UI. The rule UI plug-in determines that one or more violations of the one or more rules has occurred and displays an additional UI with mutually exclusive options for mitigating the determined one or more violations of the one or more rules. A new rule is saved into the rules database.

Interactively extending machine-learning-generated rules and recommendations

Methods, systems, and computer-readable storage media for restoring microservice persistencies. A disruptive event potentially affecting a computing system functionality and data synchronization of one or more applications and one or more microservices is determined. Each application and microservice stores respective data records in separate data tables. A restoration of the computing system functionality is determined. A synchronization process is initiated by using a synchronization identification engine. Data record synchronization is verified across a plurality of data tables, by matching record identifiers according to a call mapping between the applications and the microservices. The data record synchronization is restored across the plurality of data tables. An access to the applications and the microservices is reactivated.

Consistent restore across microservice persistencies

Various examples are directed to systems and methods for executing a computer-automated process using trained machine learning (ML) models. A computing system may access first event data describing a first event. The computing system may execute a first ML model to determine an ML characterization of the first event using the first event data. The computing system may also apply a first rule set to the first event data to generate a rule characterization of the first event. The computing system may determine an output characterization of the first event based at least in part on the rule characterization of the first event and determine to deactivate the first rule set based at least in part on the ML characterization of the first event.

Computer-automated processing with rule-supplemented machine learning

A computer-implemented method includes translating into a routing configuration, tenant-specific preferences for primary and secondary datacenter locations. A service mesh is set up for communication between services within and across the primary and secondary datacenter locations. Service persistencies with endpoints in datacenter locations are used to configure replication agents between the service persistencies. Using service endpoints, configuring Virtual Services that implement the service mesh. An Ingress Gateway is configured to route end user requests into the service mesh to a first service instance in the tenant-selected primary datacenter. According to the tenant-specific preferences, data replication is configured to copy data to redundant storage. Using endpoints of persistent storage replication agents for each service persistence in the tenant-selected primary datacenter, configuring persistent storage replication agents for each service persistence in the tenant-selected primary datacenter.

Tenant-specific disaster recovery

In an example embodiment, access to a data set in a data lake can be specified using several approaches, based on the metadata and information attached. The metadata may be replicated from the original data source of the underlying data, and additional metadata may be modeled and stored to construct linkage information between data types. This linkage information may be used to automatically grant access to users to additional objects that are linked to objects that the user has explicit access to.

Deriving and augmenting access control for data lakes

Implementations include a schema stack management system that enables zero-downtime during execution of maintenance procedures on application systems having schema stacks including one or more customer-provided schema extensions.

Schema stack management system for managing extensions through upgrades

Systems and methods include reception of a first service call from a first service at a second service, generation, at the second service, of a response to the first service call, determination, at the second service, of an amount of hardware resources consumed by the second service during generation of the response to the first service call, generation, at the second service, of a first resource consumption token identifying the amount of hardware resources consumed by the second service during generation of the response to the first service call, determination of a first identifier of a type of hardware on which the second service is executing, and return of the response, the first resource consumption token and the first identifier of the type of hardware to the first service.

Holistic measurement of microservice-based application resource consumption

In an example embodiment, a solution is provided that allows a user to submit a document. Information can be obtained from the document using optical character recognition (OCR) or other techniques. This information can then be used to identify one or more workflows that pertain to the document. The one or more workflows may be ranked using machine learning techniques and presented to the user. Once the user selects a desired workflow, the information obtained from the document can then be used to automatically complete at least a portion of the workflow, for example by prefilling one or more fields in a form.

Document initiated intelligent workflow

A request is received to create a graph database from one or more relational databases. For each relational database, data objects in the relational database are identified. For each data object, a graph data object corresponding to the data object is created. The graph data object is linked to the data object. A set of associated data objects in the relational database are determined, and for each associated data object, an associated graph data object is created if a graph data object corresponding to the data object does not exist. For each created graph data object, a graph data relation object is created that represents a relationship between the graph data object and the associated graph data object. Created graph data objects, associated graph data objects, and graph data relation objects are stored in the graph database. The graph database is provided to one or more applications.

Automatic creation and synchronization of graph database objects

In an implementation, a mesh assembler receives a request for a new cloud-computing application tenant, where the request includes an assembly profile. The mesh assembler calls a deployment manager for applications and services that need to be custom deployed according to the assembly profile. The mesh assembler calls a routing configurator, which looks up services with certain attributes and configures services with certain attributes into a service mesh.

User demand-specific service mesh assembly of multi-tenant, single-tenant, and extension services

In an implementation, a shutdown coordinator sends an instruction to a router to no longer assign new sessions to an application instance, where the application instance is to be shut down. The shutdown coordinator sends a request to the application instance to export associated sessions for handover to a new application instance. The shutdown coordinator receives an indication from the application instance that no further requests can be processed by the application instance since all associated sessions have been exported to an external session storage. The shutdown coordinator instructs the router to redirect requests to the application instance to the new application instance. The shutdown coordinator shuts down the application instance. The shutdown coordinator deletes remaining sessions of all associated sessions from the external session storage after a defined timeout period.

Coordinated shutdown of cloud computing applications with session handover

Growing community of inventors

Malsch, Germany

Peter Eberlein