Sap Se

Sap Ag

Ulrich Bestfleisch

Oliver Klemenz

Sebastian Schroetel

Gerrit Simon Kazmaier

Nadine Sachs

Sergey Smirnov

Tim Philipp Trabold

Veit Spaegele

Udo Peter Klein

Joachim Gaffga

Gregor Karl Frey

Thomas Vogt

Karl-Peter Nos

Dirk Baumgaertel

Markus Wolf

Mario Andy Mueller

Johannes Bechtold

Paul P Tanzer

Eduard Stelle

Herbert Boche

Leif Albers

Jan Brink

Andre Von Rekowski

A system and method providing database level migration of an application and associated data. In one embodiment, the method may include deploying a new data structure, a first database trigger to capture data written to an old data structure and to write the captured data to the new data structure, and a bulk migration stored procedure to a database instance; deploying, in response to a conclusion of an execution of the bulk migration stored procedure, a second database trigger to the database instance to capture data written to the new data structure and to write the captured data to the old data structure; deploying a second version of the application; routing validation data to the second version of the application to validate an expected operation thereof; and routing, in response to a completion of the validation, production data for the database instance to the second version of the application.

Database-driven zero downtime data migration

Provided is a system and method for providing a single entry point for integrating software extensions across different software application. In one example, the method may include receiving, via a unified extensibility entry point, an indication that a first software artifact of a first software application is being locally extended, identifying one or more other software artifacts in one or more other software applications that are capable of being cross-extended based on the local extension of the first software artifact in the first software application, and displaying, via a user interface, information about the one or more other software artifacts that are capable of being cross-extended.

Federated extensibility workbench

Some embodiments provide a non-transitory machine-readable medium that stores a program. The program receives a data model definition defined using a human-readable syntax. The data model definition includes a set of annotated entity definitions. The program further generates a machine-readable representation of the data model definition. Based on the data model definition, the program also generates, for each annotated entity definition in the set of annotated entity definitions, an interface and an implementation class from the machine-readable representation of the data model definition. The program further provides the set of interfaces and the set of implementation classes to an integrated development environment (IDE) application for design-time implementation of the set of interfaces and the set of implementation classes.

Generating interfaces from annotated entity definitions for developing applications

Some embodiments provide a non-transitory machine-readable medium that stores a program. The program receives a data model definition defined using a human-readable syntax. The program further generates a machine-readable representation of the data model definition. Based on the data model definition, the program also generates a set of interfaces from the machine-readable representation of the data model definition. Each interface in the set of interfaces includes code specified in a programming language. The program further provides the set of interfaces to an integrated development environment (IDE) application for design-time implementation of the set of interfaces.

Generating interfaces from data and service definitions for developing applications

A system and method providing a single entry point for implementing software extensions across multiple different software applications. In one embodiment, the method may include retrieving an indication of an extension point offered by a cloud application, the extension point being defined by a signature including a name and one or more parameters; generating one or more extension point implementations of the extension point by configuring custom code that fulfills the signature of the extension point; and sending, to the cloud application, an indication the extension point is active for requesting an execution of the one or more extension point implementations to be executed apart from the cloud application.

Synchronous side-by-side extensibility

Technologies described herein can be used to support modification to data by a client computing device without a concurrency check. An update to a data document can be received from a client computing device. Contents of the update can be analyzed to determine whether a concurrency check is required before applying the update to the data document. In at least some embodiments, at least part of the contents of the data document can be organized in such a way that multiple, independent modifications can be made to the contents of the data document without concurrency checks. A server computer can be configured to identify updates to these contents of the data document, and to apply the updates to the data document without performing concurrency checks. In at least some embodiments, a list of concurrency-safe data document properties can be accessed when determining whether to omit the concurrency check.

Optimistic concurrency for collaborative applications

A persistent library bundle (PLB) is added as a library of an application. The PLB is automatically downloaded from a central registry and installed in an application directory. The PLB provides an out-of-the-box functionality to the application. The PLB includes a PLB persistence description. The PLB persistence description specifies how runtime data of the PLB has to be persisted. Upon installation of the PLB to the application, the PLB persistence description is copied to an application database directory. The application database directory stores application persistence description and the PLB persistence description. The application persistence description and the PLB persistence description are assigned to a certain database schema.

Consuming persistent library bundles

A computing device hosts a graphical user interface (GUI) of a computer application, the computer application being run on a backend computing platform accessible to the computing device via a network. The GUI includes multiple models in a Model-View-Controller (MVC) pattern, an eventing mechanism, and a model synchronizer. Each model in the GUI represents one or more application objects of the computer application. The eventing mechanism generates an application object change event when an application object of one of the multiple models in the GUI is changed to a new state. The model synchronizer listens to the generated application object change event, retrieves the new state of the application object, and locally updates other models of the multiple models in the GUI that also represent the application object with the new state of the application object.

Graphical user interface with consistent redundant models

Some embodiments provide a non-transitory machine-readable medium that stores a program. In response to receiving a first query for a set of data, the program generates a first query execution plan based on the first query. The program further executes the first query execution plan in order to generate a first result set comprising the set of data. The program also stores the first query execution plan in a cache. The program further replaces the first query execution plan in the cache with a second query execution plan. The second query execution plan includes a query hint applied to the first query execution plan. In response to receiving a second query for the set of data, the program also retrieves the second query execution plan from the cache. The program further executes the second query execution plan in order to generate a second result set comprising the set of data.

Automated application of query hints

An event bus is instantiated for subscribing applications for notifications in relation to cached results. The cached results may be associated with executed requests sent by the applications to services. It is determining whether a result value associated with a request from a first application to a remote service is cached. When the result value is blank, the first application is subscribed for an event associated with request parameters, defined with the request from the first application. A result event associated with caching the result value is published, e.g. at the event bus. The result value is determined based on executing a request sent by a second application, which defines the request parameters and is sent to the remote service prior to the request from the first application. A notification is provided to the first application with regards to the result event.

Concurrent services caching

A method for internationalization of a computer application being designed and developed as cloud application in a platform-as-a-service (PaaS) environment includes disposing a translatable texts table in a data layer of the computer application as a common source of translatable texts for all layers of the computer application. The method further includes disposing a text string translation service in a logic layer of the computer application. to expose the translatable texts table disposed in the data layer to a presentation layer of the computer application.

Translatable texts in cloud applications

Techniques are described for providing a non-blocking application object framework allowing parallelization of operation and function calls throughout an application executing within the framework. In one example, a dependency model associated with an application in a non-blocking application object framework is identified, where the application is associated with a plurality of operations and the dependency model defines at least one dependency between at least two of the operations. At runtime of the non-blocking application object framework, the identified dependency model is interpreted. An optimized execution plan of the application is automatically generated in the non-blocking application object framework based on the interpreted dependency model, wherein at least a first portion of the operations of the application are optimized in a sequential execution order based on dependencies defined in the dependency model. The application is then executed in the non-blocking application object framework based on the optimized execution plan.

Non-blocking application object framework and dependency model management

A system, a method, and a computer program product for providing a layered business configuration are disclosed. A configuration information for configuring an application object of a software application is obtained. The configuration information is arranged in at least one configuration staging table. The configuration staging table contains at least one configuration object. The configuration object contained in the configuration staging table is activated. Based on the activated configuration object, at least one configuration runtime table for configuring the application object is generated.

Layered business configuration

A system, a method, and a computer program product for providing an application object framework are disclosed. In response to a request, an application object of a software application is obtained from an application object framework. The application object framework loads a metadata corresponding to the requested application object. The metadata contains at least one metadata schema definition. The application object framework generates a runtime interface for execution of the requested application object based on the loaded metadata.

Application object framework

According to one aspect of systems and methods for dynamic recreation of multidimensional analytical data, lost sets of calculation scenarios that provide multidimensional analytical data results after aggregations and transformations of the multidimensional analytical data are recreated in the volatile storage of an in-memory computing engine. A multidimensional analytical data view (MDAV) compiler is triggered to read the MDAV metadata stored in an intermediate buffer in the MDAV compiler. The read MDAV metadata is compiled into a calculation scenario including calculation view metadata. The calculation view metadata is stored in the intermediate buffer. The recreated set of calculation scenarios is deployed on the in-memory computing engine.

Growing community of inventors

Schwetzingen, Germany

Ulrich Bestfleisch