Sap Se

Rick Weigel

Markus Viol

Marcel Kassner

Benjamin Klehr

Christian Boehrer

Antonia Gross-Tarakji

Markus Reetz-Lamour

Pramod Sidlaghatta Jaiprakash

Thomas Salvador

Christine Hoerner

Rashmi Nagendra

Eugen Resch

Aditya Bhatia

Harald Kopf

An application executing on a pod may generate a content request for a particular version of content. The application sends a request including an identifier of the version of the content to a repository in a cluster of pods. The repository determines, using the identifier, whether the version of the content is stored in the cluster or stored at a database in a different cluster. The application receives a response from the repository that may indicate that the version of the content is stored in the cluster and the response may include an identifier of a content pod storing the version of the content. The application sends the content request to the content pod storing the version of the content and may receive the version of the content without querying the database for the version of the content.

Image scaling cloud database

Techniques and solutions are described for retrieving metadata artefacts from a repository that includes multiple instances of a metadata artefact. The instances can have at least some different content. Metadata artefacts are associated with metadata describing group, searching, or selection criteria, such as one or more of a particular solution, tenant, layer, or version. A request for a metadata artefact can include at least one value for one or more of the criteria, which in turn can be used to identify one or more relevant metadata artefacts. Identifiers for, or content of, relevant metadata artefacts can be returned in response to the request. Fallback logic can be used to determine at least in part what metadata artefacts are relevant to a request, or how to return or process request results.

System and method for selective retrieval of metadata artefact versions

A notification job is executed as a background job in a recurrent notification framework. The registered scenario along with the recurrent notification information is retrieved from a central notification scenario registration table. The user information along with an application context is retrieved from a notification scenario BADI. The user information along with a notification preference is retrieved from a user registration table. The mapping information of the user identifier and the device identifier is retrieved from the device registration table. Based on the retrieved information, the notification channel is identified from the recurrent notification information. A recurrent notification is sent through the notification channel to a device.

Recurrent notification framework

Growing community of inventors

Rheinstetten, Germany

Rick Weigel