Sap Se

Sap Ag

Shenol Hulmi Yousouf

Stoyan Zhivkov Boshev

Petar Rusev Rusev

Nikolai Veselinov Neichev

Kaloyan Stefanov Nikov

Georgi Stanev

Antoan Nikolaev Andonov

Henning Blohm

Georgi Enchev

Pavel Genevski

Georgi Gerginov

Michael Herrmann

Radoslav Ivanov

Hristo Ilev

Dimo Stoilov

Georgi Danov

Katya Todorova

The present disclosure relates to computer-implemented methods, software, and systems for an automatic recovery job execution through a scheduling framework in a cloud environment. One or more recovery jobs are scheduled to be performed periodically for one or more registered service components included in a service instance running on a cluster node of a cloud platform. Each recovery job is associated with a corresponding service component of the service instance. A health check operation is invoked at a service component based on executing a recovery job at the scheduling framework corresponding to the service component. In response to determining that the service component needs a recovery measure based on a result from the health check operation, a recovery operation is invoked as part of executing a set of scheduled routines of the recovery job. Implemented logic for the recovery operation is stored and executed at the service component.

Auto-recovery framework

The present disclosure relates to computer-implemented methods, software, and systems for on-demand outage notifications in a cloud environment. Data defining statuses of network calls exchanged between web agents registered at correspondingly different network segments of a cloud platform is evaluated to determine health statuses of the cloud platform. In response to receiving a request to subscribe an application for notifications for a current health status, registering, at the health service, the application to receive the notifications associated with health statuses of network connectivity of the cloud platform. The application is registered to receive the notifications at a subscription network address under a notification regime. A notification for the current health status of network connectivity of the cloud platform is dynamically provided by the health service. The notification is provided to the registered application according to notification rules defined in the notification regime.

On-demand outages notification in a cloud environment

The present disclosure relates to computer-implemented methods, software, and systems for detecting outages in a multiple availability zone cloud environment. Structured data defining network connectivity statuses of network segments is received. Multiple availability zones of the first cloud platform are defined in a multiple availability zone cloud architecture. External structure data defining inbound connectivity statuses of the network segments correspondingly defined for the availability zones of the first cloud platform is iteratively collecting. The inbound connectivity statuses define availability for an entity running at an external cloud platform to the first cloud platform to connect to at least one entity running at the first cloud platform. In response to evaluating the internal and external structured data, determining a health status of the first cloud platform to be provided to platform services provided by the first cloud platform and/or applications running on the first cloud platform to support managing of lifecycle of entities running on the first cloud platform.

Detecting outages in a multiple availability zone cloud environment

The present disclosure relates to computer-implemented methods, software, and systems for detecting outages in a cloud environment. Internal web agents installed at corresponding network segments of a first cloud platform and external web agents installed at an external second cloud platform are configured to perform network calls between themselves and the other web agents. Data from the internal web agents is automatically collected to generate structured data defining network connectivity status corresponding to the network segments of the first cloud platform based on the performed network calls between the internal and external web agents. In response to evaluating the structured data, a health status of network connectivity of the first cloud platform is determined. The health status can be provided to platform services provided by the first cloud platform and/or applications running on the first cloud platform to support managing of lifecycles of entities running on the first cloud platform.

Detecting outages in a cloud environment

Auto-recovery job scheduling framework

The present disclosure relates to computer-implemented methods, software, and systems for detecting isolated zones in a cloud platform. Aggregated data for network connectivity status of web agents at the cloud platform is iteratively collected at a health service. The aggregated data is generated based on network call log data for external accessibility of the web agents. The web agents run at different network segments of the cloud platform. The network call log data is generated based on executed network calls issued from one or more external web agents running outside of the cloud platform and directed to each of the web agents at the cloud platform. A poll request for a network connectivity status for inbound connectivity for an entity running on the cloud platform is received. In response to evaluating the collected aggregated data, the network connectivity status for inbound connectivity for the entity is provided.

Reverse health checks

A client system requests to upload an input data stream to a server system. The input data stream is split to a sequence of chunks. The chunks are transferred in parallel by a number of connections from the client system to the server system. At the server system, the transferred chunks are merged into an output stream according to the sequence. The output stream represents the rebuilt input stream.

Upload operation using multiple connections

Various embodiments of systems and methods to process customized deployment scenarios in a shared computing environment are described. In one aspect, a deployment request is received at the shared computing environment by a client associated with a customized deployment scenario. In a response, a deploy service of the shared computing environment is instantiated. In another aspect, one or more custom deploy processors are identified by the deploy service, where the one or more custom deploy processors correspond to one or more customized deployment scenarios. In yet another aspect, a part of a deployable content passed to the one or more custom deploy processors by the deploy service, is deployed to the shared computing environment by at least one corresponding custom deploy processor.

Performing customized deployment scenarios in shared environments

In one aspect, a transformation of web application archives (WARs) to Open Services Gateway initiative (OSGi&#x2122;) web bundles is performed. WARs are specialized Java&#xae; archives for packaging web applications and the transformation to OSGi&#x2122; web bundles is realized by applying proper entries to the manifest of the WARs thus making them OSGi&#x2122; compliant. In another aspect, the transformed WARs to OSGi&#x2122; web bundles are marked as auto started so that the web application is available for requests after product installation.

Deployment of web application archives as a preprocessing step for provisioning

In one aspect, a metadata of an application is received. The metadata describes a number of artifacts of the computer application. Based on a reference in the application metadata, at least one service that the application is configured to access is determined. In another aspect, additional metadata describing artifacts associated with the at least one service are identified. The artifacts associated with the at least one service and the artifacts of the computer application are selected for installation of the computer application.

Automatic identification of services

In one aspect, a software application with application artifacts is deployed on a cloud computing platform. The cloud computing platform includes a platform product that can provide functionality that is required by the application. Application metadata is created based on analyzing the application artifacts and describes the application artifacts requirement. An application repository stores the application artifacts and the application metadata. A product description defines an application product for the software application and a product reference to the platform product is defined. The product description and the product reference are published in the application repository to update the application metadata. A composite repository refers to the application product and the platform product. The composite repository is transferred to a platform repository provided by the cloud computing platform.

Growing community of inventors

Sofia, Bulgaria

Shenol Hulmi Yousouf