Sap Se

Tatjana Pfeifer

Raphael Dibbern

Jens Roessler

Silvana Straus

Jonas Braun

Arne Rantzen

Andreas Hoffner

Matthias Tebbe

Olaf Tennie

Andre Pany

Martin Mueller

Roland Trapp

Roman Belosludtsev

Thomas Ehret

Nadine Baumgaertel

Vanessa Rau

Ihlas Basha

Jes Sie Cheah

In an example embodiment, multiple different categories of events from an Enterprise application are separated and processed by different daemons. This allows events of a first category, such as business events, to be processed separately from events of a second category, such as configuration events. This provides the benefits of stable event processing, additional monitoring functionality, and specialized error handling.

Manage daemon for event reconciliation in a computer system

Embodiments may facilitate event processing for an ABAP platform. A business object data store may include a RAP model, including a behavior definition, for a business object. A framework may automatically transform the behavior definition of the RAP model into a producer event via an event binding and a cloud event standardized format. Information about the producer event may then be passed to an ABAP application associated with a pre-configured destination at an enterprise business technology platform. In some embodiments, a standalone API enterprise hub data store may contain an event specification. An ABAP development tenant of a business technology platform may automatically parse the event specification and translate the parsed information into high-level programming language structures that reflect an event type at runtime. An event consumption model may then be generated based on the event type.

Event consumption for high-level programing language platform

Event provisioning for high-level programing language platform

Embodiments may facilitate event processing for an ABAP platform. A business object data store may include a RAP model, including a behavior definition, for a business object. A framework may automatically transform the behavior definition of the RAP model into a producer event vian event binding and a cloud event standardized format. Information about the producer event may then be passed to an ABAP application associated with a pre-configured destination at an enterprise business technology platform. In some embodiments, a standalone API enterprise hub data store may contain an event specification. An ABAP development tenant of a business technology platform may automatically parse the event specification and translate the parsed information into high-level programming language structures that reflect an event type at runtime. An event consumption model may then be generated based on the event type.

The present disclosure involves systems, software, and computer implemented methods for providing an asynchronous transport channel for OData data using web sockets. One example method includes upgrading a HTTP connection to a web socket connection in response to an upgrade request. The web socket connection is maintained, after the upgrading, for receipt of subsequent web socket requests. An OData request is received, from a consuming application, over the web socket connection. The OData request is translated to a format used by an OData runtime environment and sent to the OData runtime environment. A response to the OData request is received from the OData runtime environment. The response is incorporated into a web socket message. The web socket message is sent to the consuming application, over the web socket connection, in response to the OData request, with the web socket connection remaining open after the web socket message is sent.

Transport channel via web socket for OData

Embodiments described herein relate to an improved technique for preemptive client application request processing based on observed use access patterns and/or models. The system includes a framework engine operable to trace sequences of requests to one or more service provider applications, including which particular client requests are likely to be followed by other particular client requests for each service. Based on the resulting traces, the framework can determine the probability of a particular request B following another particular request A. When request A is retrieved from the service provider application, and when the probability is high enough (e.g. &#x3e;50%) that request B will follow request A in the sequence of requests, the framework is operable to simulate request B in a background process and provide a response to request B from a local memory storage.

System and method for preemptive request processing

The present disclosure involves methods and devices, including computer programs encoded on a computer storage medium, for providing a foldable computing device that provides multiple operating modes and is especially adaptable in size to particular functions of the operating modes. In one aspect, a foldable mobile computing device for establishing a connection with a network or for displaying an electronic document, comprising: a processor; a foldable display including a bendable material configured to emit light and including a folding axis, wherein the bendable material extends across the folding axis and the foldable display is configured to be folded with respect to the folding axis. In an aspect, the foldable device provides access to a first function of the device and to a second function different from the first function upon folding or unfolding a portion of the display with respect to the folding axis, wherein the folding or unfolding of the portion of the display with respect to the folding axis activates the second function.

Foldable computing device capable of behaving as different types of devices

Growing community of inventors

Altrip, Germany

Tatjana Pfeifer