Systems and methods for delivering software upgrades in a provider-tenant environment

• US 20070156849A1
• Filed: 12/30/2005
• Published: 07/05/2007
• Est. Priority Date: 12/30/2005
• Status: Abandoned Application

• Current Assignee: SAP AG (SAP SE)
• Original Assignee: SAP AG (SAP SE)
• Inventors: Becker, Wolfgang
• Application Number:
  US11/320,953
• Publication Number:
  US 20070156849A1
• Time in Patent Office: Days
• US Class Current: 709/219
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling

Abstract

Exemplary methods and systems consistent with the present invention allow for upgrading a first tenant of a plurality of tenants. By receiving a patch including a data structure not shared by the plurality of tenants, and informing an administrator associated with the provider that a patch is available, a provider may receive an authorization to upgrade the first tenant. The upgrade may be applied to systems of the first tenant based on the data structure included in the patch.

Claims

1. A method for upgrading a first tenant of a plurality of tenants, comprising:

receiving, at a provider, a patch including a data structure not shared by the plurality of tenants;

informing an administrator associated with the provider that a patch is available;

receiving an authorization to upgrade the first tenant; and

upgrading the first tenant based on the data structure included in the patch.

2. The method of claim 1, wherein upgrading the tenant further comprises:

upgrading a tenant database associated with the first tenant.

3. The method of claim 2, wherein upgrading the tenant database comprises:

associating a plurality of data structures determined to be dependent upon the first tenant with a first tenant template;

applying a patch to a provider database, wherein the patch includes a new plurality of data structures shared by the plurality of tenants;

determining, based on the patched provider database, which of the new plurality of data structures are specific to the first tenant and which of the new plurality of data structures are shared by the plurality of tenants;

associating each data structure determined to be dependent upon the first tenant with a second tenant template; and

determining a difference between the first and second tenant templates.

4. The method of claim 3, wherein determining a difference comprises:

comparing the data structures of the first tenant template to the data structures of the second tenant template.

5. The method of claim 3, further comprising:

linking the upgraded tenant database to the provider database.

6. The method of claim 3, wherein the patch identifies differences between the first plurality of data structures and the new plurality of data structures.

7. The method of claim 1, wherein the patch includes a priority tag.

8. The method of claim 1, wherein the authorization further includes a scheduled time for upgrading the tenant.

9. The method of claim 1, further comprising:

upgrading a provider database based on the patch.

10. The method of claim 1, further comprising:

upgrading a tenant application based on the patch.

11. The method of claim 1, wherein upgrading the first tenant further includes:

generating a tenant template reflecting data structures of a tenant database associated with the first tenant, wherein the data structures include the data structure included in the patch; and

upgrading the first tenant based on the generated tenant template.

12. A system for upgrading a first tenant of a plurality of tenants, comprising:

means for receiving, at a provider, a patch including a data structure not shared by the plurality of tenants;

means for informing an administrator associated with the provider that a patch is available;

means for receiving an authorization to upgrade the first tenant; and

means for upgrading the first tenant based on the data structure included in the patch.

13. The system of claim 12, wherein the means for upgrading the tenant further comprises:

means for upgrading a tenant database associated with the first tenant.

14. The system of claim 13, wherein the means for upgrading the tenant database comprises:

means for associating a plurality of data structures determined to be dependent upon the first tenant with a first tenant template;

means for applying a patch to a provider database, wherein the patch includes a new plurality of data structures shared by the plurality of tenants;

means for determining, based on the patched provider database, which of the new plurality of data structures are specific to the first tenant and which of the new plurality of data structures are shared by the plurality of tenants;

means for associating each data structure determined to be dependent upon the first tenant with a second tenant template; and

means for determining a difference between the first and second tenant templates.

15. The system of claim 13, wherein the means for determining a difference comprises:

means for comparing the data structures of the first tenant template to the data structures of the second tenant template.

16. The system of claim 13, further comprising:

means for linking the upgraded tenant database to the provider database.

17. The system of claim 13, wherein the patch identifies differences between the first plurality of data structures and the new plurality of data structures.

18. The system of claim 12, wherein the patch includes a priority tag.

19. The system of claim 12, wherein the authorization further includes a scheduled time for upgrading the tenant.

20. The system of claim 12, further comprising:

means for upgrading a provider database based on the patch.