Method and system for distributed control system (dcs) process data cloning and migration through secured file system
US-2016299909-A1 · Oct 13, 2016 · US
US9996330B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9996330-B2 |
| Application number | US-201514949189-A |
| Country | US |
| Kind code | B2 |
| Filing date | Nov 23, 2015 |
| Priority date | Nov 23, 2015 |
| Publication date | Jun 12, 2018 |
| Grant date | Jun 12, 2018 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A system, a method, and a computer program product for deploying objects are disclosed. A file containing a plurality of artifacts for deploying during runtime of an application is defined. At least one dependency for at least one artifact in the plurality of artifacts is determined based on the defined file. A database object for implementation during runtime of the application is created based on the determined dependency. At least one change to the database object during runtime of the application is implemented. The artifact is deployed during runtime of the application based on the implemented change to the database object.
Opening claim text (preview).
What is claimed: 1. A computer-implemented method, comprising: defining a file containing a plurality of artifacts for deploying during runtime of an application; determining, based on the defining, at least one deployment dependency for at least one artifact in the plurality of artifacts, the at least one artifact being included in at least one deployment container having a container schema, the container schema including at least one view object, at least one table object, and at least one synonym object, the at least one synonym object linking to another object in an external schema of a target system and being indicative of the at least one deployment dependency; determining, based on the at least one deployment dependency, an execution order for the plurality of artifacts; creating, by at least one build plugin component of a database system and based on the at least one determined deployment dependency and the execution order, a database object for implementation during runtime of the application; implementing at least one change to the database object during runtime of the application, wherein implementing the at least one change comprises: transmitting, by a second build plugin component of the database system, information associated with the database object to a deployment infrastructure kernel of the database system; performing, by the deployment infrastructure kernel, the at least one change; and transmitting, by the deployment infrastructure kernel, the at least one change to a processor of the database system; performing error checking of the implemented at least one change to the database object subsequent to the implementing; and deploying, based on the at least one implemented change to the database object and the error checking, the at least one artifact during runtime of the application in the target system; wherein at least one of the defining, the determining, the creating, the implementing, the performing, and the deploying is performed using at least one processor of at least one computing system. 2. The method according to claim 1 , wherein at least one build plugin component of the database system performs at least one of the defining, the determining, the implementing, and the deploying. 3. The method according to claim 2 , wherein a separate build plugin component is defined for each type of an artifact in the plurality of artifacts. 4. The method according to claim 3 , wherein the at least one build plugin component accesses at least one deployment container that includes the at least one artifact and a container schema indicative of at least one dependency associated with the at least one artifact, to perform at least one of the defining, the determining, the creating, the implementing, and the deploying. 5. The method according to claim 3 , wherein the at least one build plugin component is sandboxed by accessing an application programming interface of a deployment container. 6. The method according to claim 3 , wherein the at least one build plugin component is packaged with at least one other build plugin component into at least one shared library, wherein the at least one build plugin component and the at least one shared library include a version information and provide information about compatible versions of at least another build plugin component and at least another shared library, respectively. 7. The method according to claim 1 , further comprising performing, by the processor at design-time and at runtime, persistence functions to ensure deployment information associated with the deployed at least one artifact is appropriately persisted. 8. The method according to claim 7 , wherein the at least one build plugin component and the at least one shared library determine at least one other compatible build plugin component and at least another compatible shared library, respectively. 9. The method according to claim 1 , wherein the at least one change to the database object includes at least one of the following: creating the database object, deleting the database object, and modifying the database object. 10. The method according to claim 1 , wherein the at least one artifact includes at least one of the following: a data definition language artifact, a synonym, a table, a view, a role, a privilege, a configuration, a core data service, a function, an index, and any combination thereof. 11. The method according to claim 1 , further comprising preventing deployment of the at least one artifact in response to the error checking indicating a fatal error. 12. The method according to claim 1 , wherein the at least one dependency includes at least one of the following: the at least one artifact being dependent on at least another artifact in the plurality of artifacts and the at least one artifact being independent of any artifact in the plurality of artifacts. 13. 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 a file containing a plurality of artifacts for deploying during runtime of an application; determining, based on the defining, at least one deployment dependency for at least one artifact in the plurality of artifacts, the at least one artifact being included in at least one deployment container having a container schema, the container schema including at least one view object, at least one table object, and at least one synonym object, the at least one synonym object linking to another object in an external schema of a target system and being indicative of the at least one deployment dependency; determining, based on the at least one deployment dependency, an execution order for the plurality of artifacts; creating, by at least one build plugin component of a database system and based on the at least one determined deployment dependency and the execution order, a database object for implementation during runtime of the application; implementing at least one change to the database object during runtime of the application, wherein implementing the at least one change comprises: transmitting, by a second build plugin component of the database system, information associated with the database object to a deployment infrastructure kernel of the database system; performing, by the deployment infrastructure kernel, the at least one change; and transmitting, by the deployment infrastructure kernel, the at least one change to a processor of the database system; performing error checking of the implemented at least one change to the database object subsequent to the implementing; and deploying, based on the at least one implemented change to the database object and the error checking, the at least one artifact during runtime of the application in the target system. 14. The system according to claim 13 , wherein at least one build plugin component of the database system performs at least one of the defining, the determining, the implementing, and the deploying. 15. The system according to claim 14 , wherein a separate build plugin component is defined for each type of an artifact in the plurality of artifacts. 16. The system according to claim 15 , wherein the at least one build plugin component accesses at least one deployment container that includes the at least one artifact and a container schema indicative of at least one dependency associated with the at least one artifact, to perform at least one of the defining, the determining, the c
Software maintenance or management · CPC title
Software deployment · CPC title
Plug-ins; Add-ons · CPC title
Design, administration or maintenance of databases · CPC title
Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.