Sap Se

Sap Ag

Joerg Schmidt

Karolin Laicher

Thomas Vogt

Andreas Willi Rueegg

Michael Segler

Rainer Leinemann

Peter Eberlein

Volker Driesen

Wulf Kruempelmann

Andrey Engelko

Lars Spielberg

Andres Willi Rueegg

Techniques are described for automatically scheduling and performing upgrades in a hybrid cloud scenario. Advantages to these techniques include revision safe system upgrades and that the process is automated, thus reducing expensive operation costs. Techniques include receiving a landscape model describing changes to a customer landscape, identifying a customer-side system within a customer landscape to upgrade based on the landscape model, and identifying a server-side system within the server landscape that is associated with the customer-side system, and scheduling the customer-side system and the server-side system for upgrade.

Revision safe upgrade in a hybrid cloud landscape

A tenant multiplexer in an administrative tenant of a multi-tenant software architecture can call an administrative agent in the administrative tenant and receive, from the administrative agent, an action framework and a trusted connection protocol for accessing each of the plurality of client tenants. The trusted connection protocol can establish, without tenant-specific authentication information, a trusted system connection to an update agent in each of the plurality of client tenants. An action framework can be simultaneously implemented using the update agent of each of at least a subset of the plurality of client tenants under control of the multiplexer via the trusted system connection to begin execution of the software process for the at least the subset of client tenants.

Multiplexer for multi-tenant architectures

The current subject matter provides a method to upgrade an individual tenant by moving the individual tenant from a source computing system that implements an older software version to a target computing system that implements a newer software version. The movement of the individual tenant incorporates a movement of customer-specific data associated with the moved tenant. Instead of just upgrading a same multi-tenancy computing system implementing the tenant that needs to be upgraded, a new (target) multi-tenancy computing system implementing a newer software version is installed such that this tenant can be moved from the (source) multi-tenancy computing system to the new (target) multi-tenancy computing system. The data associated with the moved tenant is adjusted to new structures associated with the newer software version.

Tenant move upgrade

A multi-tenant system can be switched to a downtime state to implement a transition from a current state to a target state of a core software platform. During a second phase of the transition an error associated with tenant-specific content of a first customer tenant of the plurality of customer tenants of the multi-tenant system can be identified. The second phase can be suspended for the first customer tenant while continuing the second phase for a remainder of the plurality of customer tenants for which an error has not been identified. After a scheduled duration of the downtime state, the multi-tenant system can be reactivated such that the multi-tenant system includes the remainder of the plurality of customer tenants with the transition implemented and the first customer tenant either with the transition implemented if the error has been corrected or without the transition implemented if the error has not been corrected.

Tenant rescue for software change processes in multi-tenant architectures

Growing community of inventors

Sinsheim, Germany

Joerg Schmidt