Automatic upgrade of pluggable components
First Claim
Patent Images
1. A method of using a processor for automatically upgrading pluggable objects, comprising:
- receiving an input package comprising a dataset specifying steps in a data transformation process for an application implemented as an object model, the input comprising a metadata for an object, the metadata having a first version number;
querying a property of the object in the object model to check a value that is set to one of two alternative states for indicating that the object can or cannot be upgraded irrespective of version number;
comparing the first version number with a stored version number of the object, the stored version number contained in a registry of objects of the object model;
in response to determining from the stored version number that the object in the object model is a newer version and said value of property is set for indicating that the object can be upgraded, automatically, without user intervention, modifying the first version number contained in the metadata in the input to be compatible with the stored version number contained in the registry of objects; and
the object is a communications manager object or a log provider object, and the first version number contained in the metadata is metadata associated with said communications manager object or said log provider object, respectively.
4 Assignments
0 Petitions
Accused Products
Abstract
When a component is to be loaded or executed, the version of the component to be loaded may be compared with available versions of the component. If an upgraded version of the component is available, the upgraded version of the component may be enabled to dynamically and deterministically update itself. The component may be an object in an object model. The upgraded version of the component may update itself by calling an update method. The component may be upgraded with minimum user intervention, dynamically as the object is loaded.
47 Citations
18 Claims
-
1. A method of using a processor for automatically upgrading pluggable objects, comprising:
-
receiving an input package comprising a dataset specifying steps in a data transformation process for an application implemented as an object model, the input comprising a metadata for an object, the metadata having a first version number; querying a property of the object in the object model to check a value that is set to one of two alternative states for indicating that the object can or cannot be upgraded irrespective of version number; comparing the first version number with a stored version number of the object, the stored version number contained in a registry of objects of the object model; in response to determining from the stored version number that the object in the object model is a newer version and said value of property is set for indicating that the object can be upgraded, automatically, without user intervention, modifying the first version number contained in the metadata in the input to be compatible with the stored version number contained in the registry of objects; and the object is a communications manager object or a log provider object, and the first version number contained in the metadata is metadata associated with said communications manager object or said log provider object, respectively. - View Dependent Claims (2, 3, 4)
-
-
5. A system comprising a computer configured for automatically upgrading pluggable objects, comprising:
-
a property value of a pluggable object, the property value operable to be set true or false for indicating that the pluggable object is upgradeable or not upgradeable respectively; and a persistence engine configured for receiving an input package from a source located external to the computer, the input package containing metadata pertaining to one or more pluggable objects of an object model resident at least in part, in the computer, the persistence engine further configured to dynamically compare a first version number contained in the metadata of the input package against a stored version number of a first pluggable object, and in response to determining that the stored version number corresponds to a newer version and the first version number corresponds to an outdated version, automatically updating the metadata in the input package by replacing the first version number contained in the metadata with the stored version number of the first pluggable object, the replacing being carried out subject to verifying that the property value has been set to true; and the first pluggable object is resident in the computer and is a communications manager object or a log provider object, and the outdated version of metadata contained in the input package is metadata associated with said communications manager object or said log provider object, respectively. - View Dependent Claims (6, 7, 8, 9, 10, 11, 12, 13, 14)
-
-
15. A computer-readable storage medium comprising computer-executable instructions for:
-
receiving input to an application implemented as an object model, the input comprising a metadata for an object, the metadata having a first version number; querying a property of the object in the object model to check a value that is set to one of two alternative states irrespective of version number, for indicating that the object can or cannot be upgraded; comparing the first version number with a stored version number of the object, the stored version number contained in a registry of objects of the object model; and in response to determining from the stored version number that the object in the object model is a newer version and said value of property is not set thereby indicating that the object can be upgraded, automatically, without user intervention, modifying the first version number contained in the metadata in the input to be compatible with the stored version number contained in the registry of objects; and the object is a communications manager object or a log provider object, and the first version number contained in the metadata is metadata associated with said communications manager object or said log provider object, respectively. - View Dependent Claims (16, 17, 18)
-
Specification