Oracle International Corporation

Bea Systems, Inc.

David Lee Felts

Vy Nguyen

Steven To

Techniques are disclosed herein for creating and patching software homes using content addressable storage. One or more embodiments comprises storing content for a file that is used to run a particular software deployment. The file is associated with a particular directory that includes a link to a first filename. The first filename is generated as a function of the content for the file, such as by applying a hash function. Responsive to receiving updated content a second filename is generated as a function of the updated content. The second filename is different than the first filename. The link included in the particular directory is modified to point to the second filename. After modifying the link included in the particular directory, the updated content for the file is used to run the particular software deployment.

Creating and patching binary software homes using content addressable storage

Disclosed is an approach for using a declarative model to configure domains, where the declarative model allows definition of applications and services within groups, definition of topology units in groups and a mapping between the application and service groups and topology groups. Processing of this model, embodied in XML, involves automatically changing the application server configuration to reflect the association of applications and services to the topology units, enabling the application server to deploy applications and services to servers, clusters, and other elements upon boot-up of the components.

Method and system for performing application server configuration using configuration groups

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.

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

An installer can use an alias to indicate a combined software program. The combined program can include multiple software products. The software products can each be independently runnable. The alias can be used by the installer system to install the multiple software products automatically.

Use of aliasing in an installer

A computer-based system can comprise a patch management system to a load patch to a software program; and an installer to install components of the software program. The installer can interpret metadata to instruct the patch management system to automatically load the patch to the software program.

Patch attachment facility

Patch management system can be used for maintaining patches downloaded for software. The patch management system can ensure that there are no conflicts between the installed patches.

Patch management system

An XML document can use tags such that scripts can be generated from the documents. The scripts can be start up scripts for different operating systems. For example, the same XML document can be used to produce a UNIX shell script as well as a Windows command file.

Growing community of inventors

Denville, NJ, United States of America

David Lee Felts