# US 2017/0286100 A1 · User-configurable database artifacts > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2017/0286100 A1 - Document ID: US20170286100A1 - Status: Published application - Kind: A1 - Application number: 15/622,873 - Filed: 2017-06-14 - Published: 2017-10-05 - Earliest claimed: 2015-11-23 - Assignees: Sap SE - Applicants: Sap SE - Inventors: Jonathan Bregler; Alexander Bunte; Arne Harren; Andreas Kellner; Daniel Kuntze; Vladislav Leonkev; Simon Lueders; Volker Sauermann; Michael Schnaubelt; Le-Huan Stefan Tran; Michael Wintergerst; Cornelia Kinder; Christopher Schildt - Web page: https://patentgrep.com/patent/US20170286100A1 ## CPC - G06F 8/71: Version control (security arrangements therefor G06F21/57); Configuration management - G06F 8/60: Software deployment - G06F 9/44521: {Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading} - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract A system, a method, and a computer program product for deployment of objects are disclosed. At least one configuration for deploying of at least one artifact during runtime of an application is defined. The configuration includes at least one dependency for the artifact. The configuration is applied to the artifact. The artifact is deployed based on the applied configuration during runtime of the application. The configuration can include at least one of the following: a default configuration for the artifact and an explicit configuration for the artifact. ## Claims ### Claim at position 1 1-20. (canceled) ### Claim 21 A computer-implemented method, comprising: defining, using a container generation component, a container deployment schema and, using, a container deployment component, a design time container metadata, for deploying of at least one artifact during runtime of an application; generating, using the container generation component, a container including the at least one artifact based on the defined container deployment schema; and deploying, using the container deployment component, the at least one artifact within the generated container based on the defined design time container metadata. ### Claim 22 (depends on 21) The method according to claim 21, wherein the generating includes at least one of the following: creating the container, modifying the container, deleting the container, granting a privilege to the container to a user, revoking a privilege to the container from a user, granting a privilege to an application programming interface of the container to a user, revoking a privilege from an application programming interface of the container from a user, and any combination thereof. ### Claim 23 (depends on 21) The method according to claim 21, wherein the container deployment schema includes at least one of the following: a view object, a table object, and a synonym object, wherein the view object is associated with a view plugin for transforming a design-time view resource into a view database object, the table object is associated with a table plugin for transforming a design-time table resource into a table database object, and the synonym object links the at least one artifact and at least another artifact. ### Claim 24 (depends on 21) The method according to claim 21, wherein the design time container metadata includes at least one of the following: a design time artifact, a data dependency, a build plugin metadata, and any combination thereof. ### Claim 25 (depends on 21) The method according to claim 21, wherein the deploying further comprises at least one of the following: writing a design-time artifact, reading a design-time artifact, triggering deployment of the at least one artifact, triggering undeployment of the at least one artifact, and any combination thereof. ### Claim 26 (depends on 21) The method according to claim 21, further comprising executing a zero-downtime maintenance of the application. ### Claim 27 (depends on 26) The method according to claim 26, wherein the executing comprises revoking at least one privilege to modify the at least one artifact in the container at runtime; and allowing modifying the at least one artifact in the container at design time; wherein the modifying includes at least one of the following: deleting the at least one artifact in the container, creating the at least one artifact in the container, changing the at least one artifact in the container, and any combination thereof. ### Claim 28 A system comprising: at least one programmable processor; and a machine-readable medium storing instructions that, when executed by the at least one programmable processor, cause the at least one programmable processor to perform operations comprising: defining, using a container generation component, a container deployment schema and, using, a container deployment component, a design time container metadata, for deploying of at least one artifact during runtime of an application; generating, using the container generation component, a container including the at least one artifact based on the defined container deployment schema; and deploying, using the container deployment component, the at least one artifact within the generated container based on the defined design time container metadata. ### Claim 29 (depends on 28) The system according to claim 28, wherein the generating includes at least one of the following: creating the container, modifying the container, deleting the container, granting a privilege to the container to a user, revoking a privilege to the container from a user, granting a privilege to an application programming interface of the container to a user, revoking a privilege from an application programming interface of the container from a user, and any combination thereof. ### Claim 30 (depends on 28) The system according to claim 28, wherein the container deployment schema includes at least one of the following: a view object, a table object, and a synonym object, wherein the view object is associated with a view plugin for transforming a design-time view resource into a view database object, the table object is associated with a table plugin for transforming a design-time table resource into a table database object, and the synonym object links the at least one artifact and at least another artifact. ### Claim 31 (depends on 28) The system according to claim 28, wherein the design time container metadata includes at least one of the following: a design time artifact, a data dependency, a build plugin metadata, and any combination thereof. ### Claim 32 (depends on 28) The system according to claim 28, wherein the deploying further comprises at least one of the following: writing a design-time artifact, reading a design-time artifact, triggering deployment of the at least one artifact, triggering undeployment of the at least one artifact, and any combination thereof. ### Claim 33 (depends on 28) The system according to claim 28, further comprising executing a zero-downtime maintenance of the application. ### Claim 34 (depends on 33) The system according to claim 33, wherein the executing comprises revoking at least one privilege to modify the at least one artifact in the container at runtime; and allowing modifying the at least one artifact in the container at design time; wherein the modifying includes at least one of the following: deleting the at least one artifact in the container, creating the at least one artifact in the container, changing the at least one artifact in the container, and any combination thereof. ### Claim 35 A computer program product comprising a non-transitory 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: defining, using a container generation component, a container deployment schema and, using, a container deployment component, a design time container metadata, for deploying of at least one artifact during runtime of an application; generating, using the container generation component, a container including the at least one artifact based on the defined container deployment schema; and deploying, using the container deployment component, the at least one artifact within the generated container based on the defined design time container metadata. ### Claim 36 (depends on 35) The computer program product according to claim 35, wherein the generating includes at least one of the following: creating the container, modifying the container, deleting the container, granting a privilege to the container to a user, revoking a privilege to the container from a user, granting a privilege to an application programming interface of the container to a user, revoking a privilege from an application programming interface of the container from a user, and any combination thereof. ### Claim 37 (depends on 35) The computer program product according to claim 35, wherein the container deployment schema includes at least one of the following: a view object, a table object, and a synonym object, wherein the view object is associated with a view plugin for transforming a design-time view resource into a view database object, the table object is associated with a table plugin for transforming a design-time table resource into a table database object, and the synonym object links the at least one artifact and at least another artifact. ### Claim 38 (depends on 35) The computer program product according to claim 35, wherein the design time container metadata includes at least one of the following: a design time artifact, a data dependency, a build plugin metadata, and any combination thereof. ### Claim 39 (depends on 35) The computer program product according to claim 35, wherein the deploying further comprises at least one of the following: writing a design-time artifact, reading a design-time artifact, triggering deployment of the at least one artifact, triggering undeployment of the at least one artifact, and any combination thereof. ### Claim 40 (depends on 35) The computer program product according to claim 35, further comprising executing a zero-downtime maintenance of the application; wherein the executing comprises revoking at least one privilege to modify the at least one artifact in the container at runtime; and allowing modifying the at least one artifact in the container at design time; wherein the modifying includes at least one of the following: deleting the at least one artifact in the container, creating the at least one artifact in the container, changing the at least one artifact in the container, and any combination thereof.