Repository system and method
AssigneeHewlett-Packard Development Company, L.P.
InventorsRadek Pospisil, Tomas Vocetka, Albert Regner
Life of this patent
Estimating the term…
Abstract
A repository has a database containing a number of artifacts storing data and a system device model defining various entities, including the artifacts and properties used in the artifacts. To update a system device model in database an extension package is passed to the repository. Update software identifies differences introduced by the extension package that are only permitted if the data in the artifacts is compatible and updates the database if and only if the data and extension package are compatible.
Claims18
A method, comprising:
- generating an extension package comprising information representing at least one change between a current object definition file and an updated object definition file;
- identifying each change represented in the extension package for which allowability depends on content of a database (“non-compatible change”);
- checking each non-compatible change for allowability against objects in the database before modification via the extension package;
- and
- updating the current object definition file with the extension package to create a merged model file based on each non-compatible change being allowable.
A repository, comprising:
- a database storing a plurality of artifacts, including a current object definition file;
- and
- update software for receiving an extension package containing changes to the artifacts in the current object definition file, checking the extension package against the artifacts in the database before modification via the extension package, and updating the object definition model based on the changes being allowable,
- wherein the update software merges the extension package with the current object definition file, so as to create a merged model file.
A method comprising:
- receiving an extension package comprising information representing at least one change between a current object definition file and an updated object definition file;
- merging the current object definition file with the extension package to create a merged model file;
- identifying each change represented in the extension package for which allowability depends on content of a database (“non-compatible change”);
- checking each non-compatible change for allowability against the artifacts in the database before modification via the extension package;
- and
- updating the current object definition file using an updated system device model based on each non-compatible change being allowable.
A database update computer program product recorded on a computer readable medium, the computer program product including:
- code for generating an extension package comprising information representing at least one change between a current object definition file and an updated object definition file;
- code for identifying each change represented in the extension package for which allowability depends on content of a database (“non-compatible change”);
- code for checking each non-compatible change for allowability against the objects in the database before modification via the extension package;
- and
- code for updating the current object definition file with the extension package to create a merged model file based on each non-compatible change being allowable.
Dependencies are inferred from the claim text.