System and method for software product versioning packaging, distribution, and patching

• US 9,477,462 B2
• Filed: 01/16/2009
• Issued: 10/25/2016
• Est. Priority Date: 01/16/2008
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Felts, David
• Primary Examiner(s): APONTE, FRANCISCO JAVIER
• Application Number:
  US12/355,681
• Publication Number:
  US 20090183150A1
• Time in Patent Office: 2,839 Days
• Field of Search: 717168-178
• US Class Current: 1/1
• CPC Class Codes: G06F 8/60 Software deployment
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: G06F 9/44505 Configuring for program initiating, e.g. using registry, configuration files

Abstract

A system and method for software product versioning, packaging, distribution, and patching. The system provides for convergence of registry models, adding critical information to a home registry and simplifying processing algorithms in the install framework. In accordance with an embodiment, a product alias element is added to a Product Provisioning model, referencing one or more products. This provides a loose coupling between the external market-oriented product name and version, and the internal product names and versions. The internal product names and versions are captured in the registry and used for all code-based decisions during installation and other provisioning related activities. In accordance with an embodiment, a Feature Model is also added to the Product Provisioning model, and modules are grouped under features.

Claims

1. A system for software product packaging, distribution, and patching, comprising:

a computer including a microprocessor and a storage medium;

a product registry for use in storing and distributing information about a plurality of different software products or versions thereof, wherein the product registry includes an install metadata, that defines

a product model, including a plurality of software components for use by the software products or versions thereof, including, for each of the plurality of different software products or versions thereof, an indication of those software components that form said each of the plurality of different software products or versions thereof,

a product alias element used to reference the plurality of different software products or versions thereof to provide a coupling between an external market-oriented product name and version and a plurality of internal product names associated with the plurality of different software products or versions thereof,

a feature model, including feature reference data, including, for each of the software components, an indication of one or more features of that software component, wherein each feature has a version associated therewith,

a runtime metadata, that defines a plurality of modules that can be provisioned at runtime including, for each version of a feature, an indication of those modules that provide that version of the feature,

wherein the information in the product registry can be updated to include information about a new software product or version thereof, and used, by joining features defined by the feature model to components defined by the product model via the feature reference data, to provision the new software product or version thereof for a customer according to the information in the product registry; and

a patch management system which generates a random unique patch identifier (ID) for each of a plurality of patches, whereby the patch management system is configured to support either a one-off or a rolling patch model to enable patching of the plurality of modules that can be provisioned at runtime;

wherein, where one or more of the plurality of modules have been patched using the patch management system to generate one or more patched modules, the runtime metadata is modified to reference the one or more patched modules.

2. The system of claim 1, wherein the plurality of internal product names associated with the plurality of different software products or versions thereof are captured in the product registry and used for all code-based decisions during installation and provisioning.

3. The system of claim 1, wherein each of the features has a version information associated therewith, and wherein the version information specifies one or a plurality of versions of the modules that are defined to be compatible with one another.

4. The system of claim 1, wherein each of the one or more different versions of a software product of the plurality of different software products or version thereof is defined by a feature definition file that is used by an installer process in creating a build of the software product to populate a JAR or other archive with information about modules in the feature definition file.

5. The system of claim 4, wherein the feature definition file further defines feature dependencies, including any requirement that other modules be present in the build.

6. The system of claim 1, wherein each of the modules is one or more of an OSGi-compliant module, OSGi bundle, Java archive (JAR), shared library, or other archive that can be directly loaded and used by the system.

7. The system of claim 1, wherein the product registry is provided as a schema that can be parsed to determine the configuration of the new version of the software product.

8. The system of claim 1, wherein products are defined in the product registry, and wherein the product registry contains a separate section for each version of a given product, including service/maintenance pack versions, and patches installed or available for that version.

9. The system of claim 1, wherein the product registry includes semantic definitions that define component dependencies on other components, and relationships between groups of software executables and artifacts.

10. A method for software product packaging, distribution, and patching, comprising the steps of:

providing a product registry for use in storing and distributing information about a plurality of different software products or versions thereof, wherein the product registry includes an install metadata, that defines

a product model, including a plurality of software components for use by the software products or versions thereof, including, for each of the plurality of different software products or versions thereof, an indication of those software components that form said each of the plurality of different software products or versions thereof,

a product alias element used to reference the plurality of different software products or versions thereof to provide a coupling between an external market-oriented product name and version and a plurality of internal product names associated with the plurality of different software products or versions thereof,

a feature model, including feature reference data, including, for each of the software components, an indication of one or more features of that software component, wherein each feature has a version associated therewith, and

a runtime metadata, that defines a plurality of modules that can be provisioned at runtime including, for each version of a feature, an indication of those modules that provide that version of the feature;

updating the information in the product registry to include information about a new software product or version;

providing a patch management system which generates a random unique patch identifier (ID) for each of a plurality of patches, whereby the patch management system is configured to support either a one-off or a rolling patch model to enable patching of the plurality of modules that can be provisioned at runtime;

modifying said runtime metadata to reference one or more patched modules, where one or more of the plurality of modules have been patched using the patch management system to generate said one or more patched modules; and

provisioning the new software product or version thereof for a customer according to the information in the product registry by joining features defined by the feature model to components defined by the product model via the feature reference data.

11. The method of claim 10, wherein the plurality of internal product names associated with the plurality of different software products or versions thereof are captured in the product registry and used for all code-based decisions during installation and provisioning.

12. The method of claim 10, wherein each of the features has a version information associated therewith, and wherein the version information specifies one or a plurality of versions of the modules that are defined to be compatible with one another.

13. The method of claim 10, wherein each of the one or more different versions of a software product of the plurality of different products or version thereof is defined by a feature definition file that is used by an installer process in creating a build of the software product to populate a JAR or other archive with information about modules in the feature definition file.

14. The method of claim 13, wherein the feature definition file further defines feature dependencies, including any requirement that other modules be present in the build.

15. The method of claim 10, wherein each of the modules is one or more of an OSGi-compliant module, OSGi bundle, Java archive (JAR), shared library, or other archive that can be directly loaded and used.

16. The method of claim 10, wherein the product registry is provided as a schema that can be parsed to determine the configuration of the new version of the software product.

17. The method of claim 10, wherein products are defined in the product registry, and wherein the product registry contains a separate section for each version of a given product, including service/maintenance pack versions, and patches installed or available for that version.

18. A non-transitory computer readable storage medium including instructions stored thereon for supporting software product packaging, distribution, and patching, which instructions, when read and executed by a computer, cause the computer to perform steps comprising:

providing a product registry for use in storing and distributing information about a plurality of different software products or versions thereof, wherein the product registry includes an install metadata, that defines

a product model, including a plurality of software components for use by the software products or versions thereof, including, for each of the plurality of different software products or versions thereof, an indication of those software components that form said each of the plurality of different software products or versions thereof,

a product alias element used to reference the plurality of different software products or versions thereof to provide a coupling between an external market-oriented product name and version and a plurality of internal product names associated with the plurality of different software products or versions thereof,

a feature model, including feature reference data, including, for each of the software components, an indication of one or more features of that software component, wherein each feature has a version associated therewith, and

a runtime metadata, that defines a plurality of modules that can be provisioned at runtime including, for each version of a feature, an indication of those modules that provide that version of the feature;

updating the information in the product registry to include information about a new software product or version thereof;

providing a patch management system which generates a random unique patch identifier (ID) for each of a plurality of patches, whereby the patch management system is configured to support either a one-off or a rolling patch model to enable patching of the plurality of modules that can be provisioned at runtime;

modifying said runtime metadata to reference one or more patched modules, where one or more of the plurality of modules have been patched using the patch management system to generate said one or more patched modules; and

provisioning the new software product or version for a customer according to the information in the product registry by joining features defined by the feature model to components defined by the product model via the feature reference data.

19. The non-transitory computer readable storage medium of claim 18, wherein the plurality of internal product names associated with the plurality of different software products or versions thereof are captured in the product registry and used for all code-based decisions during installation and provisioning.