Tenant Move Upgrade

• US 20120174085A1
• Filed: 12/30/2010
• Published: 07/05/2012
• Est. Priority Date: 12/30/2010
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP SE
• Inventors: Driesen, Volker, Spielberg, Lars, Eberlein, Peter, Engelko, Andrey, Schmidt, Joerg, Vogt, Thomas
• Granted Patent: US 8,875,122 B2
• Time in Patent Office: Days
• US Class Current: 717/168
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57

Abstract

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.

Claims

1. A computer-implemented method to individually upgrade a tenant in a multi-tenancy computing environment to a new version of a software, the method comprising:

starting, using one or more processors, a tenant at a source computing system that implements a version of the software;

receiving, using the one or more processors, in response to a change of the version of the software, a request for the upgrade of the tenant;

stopping, using the one or more processors and in response to the received request, the tenant at the source computing system;

moving, using the one or more processors, the tenant from the source computing system to a target computing system that implements a newer version of the software; and

starting, using the one or more processors, the moved tenant at the target computing system.

2. The method in accordance with claim 1, wherein the starting of the tenant at the source computing system includes accessing a same instance of a software application as being accessed by other tenants at the source computing system.

3. The method in accordance with claim 1, wherein the stopping of the tenant at the source computing system disables the tenant from accessing a software application as being accessed by other tenants at the source computing system.

4. The method in accordance with claim 1, wherein the moving of the tenant includes a separate movement of customer-specific data associated with the tenant.

5. The method in accordance with claim 4, wherein the customer-specific data associated with each tenant is stored separately in a database persistency layer that is accessed by an application server at the source computing system.

6. The method in accordance with claim 4, wherein the customer-specific data associated with each tenant is stored separately in a database persistency layer that is accessed by an application server at the target computing system.

7. The method in accordance with claim 1, wherein the moving of the tenant includes a separate movement of separated tenant data associated with the tenant, the movement of separated tenant data being enabled by application exits that are software routines implemented at pre-defined phases of the moving of the tenant.

11. The computer program product in accordance with claim 1, wherein the move of the tenant includes a separate movement of customer-specific data associated with the tenant.

12. The computer program product in accordance with claim 11, wherein the customer-specific data associated with each tenant is stored separately in a database persistency layer that is accessed by an application server at the source computing system.

13. The computer program product in accordance with claim 11, wherein the customer-specific data associated with each tenant is stored separately in a database persistency layer that is accessed by an application server at the target computing system.

8. A computer program product comprising a machine-readable medium storing instructions that, when executed by at least one programmable processor, cause the at least one programmable processor to perform operations comprising:

start a tenant at a source computing system that implements a version of the software;

receive, in response to a change of the version of the software, a request for the upgrade of the tenant;

stop, in response to the received request, the tenant at the source computing system;

move the tenant from the source computing system to a target computing system that implements a newer version of the software; and

start the moved tenant at the target computing system.

9. A computer program product in accordance with claim 8, wherein the start of the tenant at the source computing system includes accessing a same instance of a software application as being accessed by other tenants at the source computing system.

10. The computer program product in accordance with claim 8, wherein the stop of the tenant at the source computing system disables the tenant from accessing a software application as being accessed by other tenants at the source computing system.

14. The computer program product in accordance with claim 8, wherein the move of the tenant includes a separate movement of separated tenant data associated with the tenant, the movement of separated tenant data being enabled by application exits that are software routines implemented at pre-defined phases of the moving of the tenant.

15. A system comprising:

at least one programmable processor; and

a machine-readable medium storing instructions that, when executed by the at least one processor, cause the at least one programmable processor to perform operations comprising;

starting a tenant at a source computing system that implements a version of the software;

receiving, in response to a change of the version of the software, a request for the upgrade of the tenant;

stopping, in response to the received request, the tenant at the source computing system;

moving the tenant from the source computing system to a target computing system that implements a newer version of the software; and

starting the moved tenant at the target computing system.