Schema stack management system for managing extensions through upgrades
AssigneeSap SE
InventorsPeter Eberlein, Volker Driesen
Life of this patent
Estimating the term…
Abstract
Implementations include a schema stack management system that enables zero-downtime during execution of maintenance procedures on application systems having schema stacks including one or more customer-provided schema extensions.
Claims20
A computer-implemented method for executing maintenance procedures on application systems that include one or more extensions, the method being executed by one or more processors and comprising:
- providing, for production use, an application system comprising a schema stack comprising a first cross schema and one or more extension schemas, the first cross schema providing federated data to a first set of applications from data of respective data spaces of a second set of applications;
- initiating a maintenance procedure to the application system;
- during the maintenance procedure:
- maintaining a first set of synonyms between the first cross schema and one or more of the respective data spaces having data stored therein to enable continued production use of the schema stack while the maintenance procedure executes, each synonym connecting a view of the first cross schema to one of a view of an application in the first set of applications and a table in a data space of an application in the second set of applications,
- deploying a second cross schema in the schema stack, the second cross schema being a different version than the first cross schema,
- providing a second set of synonyms between the second cross schema and the one or more data spaces to enable non-production use of the second cross schema while the maintenance procedure executes, and
- in response to determining that the schema stack comprises one or more extension schemas executing one or more of providing at least one connection between a first extension schema and the second cross schema, and deploying a second extension schema;
- and
- after completion of the maintenance procedure:
- selectively transitioning the first cross schema from production use to non-production use and the second cross schema from non-production use to production use for one or more users.
A non-transitory computer-readable storage medium coupled to one or more processors and having instructions stored thereon which, when executed by the one or more processors, cause the one or more processors to perform operations for executing maintenance procedures on application systems that include one or more extensions, the operations comprising:
- providing, for production use, an application system comprising a schema stack comprising a first cross schema and one or more extension schemas, the first cross schema providing federated data to a first set of applications from data of respective data spaces of a second set of applications;
- initiating a maintenance procedure to the application system;
- during the maintenance procedure:
- maintaining a first set of synonyms between the first cross schema and one or more of the respective data spaces having data stored therein to enable continued production use of the schema stack while the maintenance procedure executes, each synonym connecting a view of the first cross schema to one of a view of an application in the first set of applications and a table in a data space of an application in the second set of applications,
- deploying a second cross schema in the schema stack, the second cross schema being a different version than the first cross schema,
- providing a second set of synonyms between the second cross schema and the one or more data spaces to enable non-production use of the second cross schema while the maintenance procedure executes, and
- in response to determining that the schema stack comprises one or more extension schemas executing one or more of providing at least one connection between a first extension schema and the second cross schema, and deploying a second extension schema;
- and
- after completion of the maintenance procedure:
- selectively transitioning the first cross schema from production use to non-production use and the second cross schema from non-production use to production use for one or more users.
A system, comprising:
- a computing device;
- and
- a computer-readable storage device coupled to the computing device and having instructions stored thereon which, when executed by the computing device, cause the computing device to perform operations for executing maintenance procedures on application systems that include one or more extensions, the operations comprising:
- providing, or production use, an application system comprising a schema stack comprising a first cross schema and one or more extension schemas, the first cross schema providing federated data to a first set of applications from data of respective data spaces of a second set of applications;
- initiating a maintenance procedure to the application system;
- during the maintenance procedure:
- maintaining a first set of synonyms between the first cross schema and one or more of the respective data spaces having data stored therein to enable continued production use of the schema stack while the maintenance procedure executes, each synonym connecting a view of the first cross schema to one of a view of an application in the first set of applications and a table in a data space of an application in the second set of applications,
- deploying a second cross schema in the schema stack, the second cross schema being a different version than the first cross schema,
- providing a second set of synonyms between the second cross schema and the one or more data spaces to enable non-production use of the second cross schema while the maintenance procedure executes, and
- in response to determining that the schema stack comprises one or more extension schemas executing one or more of providing at least one connection between a first extension schema and the second cross schema, and deploying a second extension schema;
- and
- after completion of the maintenance procedure:
- selectively transitioning the first cross schema from production use to non-production use and the second cross schema from non-production use to production use for one or more users.
Dependencies are inferred from the claim text.