System and method for deploying applications with library modules

• US 7,797,697 B2
• Filed: 10/20/2004
• Issued: 09/14/2010
• Est. Priority Date: 05/05/2004
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: BEA Systems Incorporated (Oracle Corporation)
• Inventors: Bilorusets, Ruslan, Woollen, Rob
• Primary Examiner(s): Zhen; Li B
• Application Number:
  US10/969,089
• Publication Number:
  US 20050251810A1
• Time in Patent Office: 2,155 Days
• Field of Search: 719/331, 717/170, 717/175, 717/177
• US Class Current: 717/170
• CPC Class Codes: G06F 8/61 Installation

Abstract

Federated applications are configured to use both modules created for the applications as well as library modules which perform commonly used functions. The library modules are stored separately for deployment when utilized by applications. A deployment descriptor is configured with descriptions of internal modules and references to library modules. A deployment tool reads the deployment descriptor, extracts the library modules according to the information stored in the deployment descriptor, and loads the modules specific to the application.

Claims

1. A method for deploying a plurality of applications, the method comprising:

providing at least one library module in a server storage, wherein the at least one library module performs commonly used functions shared by the plurality of applications and the at least one library module includes a manifest that stores information uniquely identifying the library module to a web server, and wherein the library module can be implemented in different implementation versions, and wherein the manifest includes an implementation version that indicates a version of an implementation of the library module stored in the server storage;

identifying the at least one library module using a key that includes a name of the at least one library module, an implementation version, and a specification version, wherein the specification version indicates a minimum extension specification version that is needed for extensions to the at least one library module;

providing a plurality of deployment descriptors, wherein each said deployment descriptor is associated with one of the plurality of applications stored in the server storage, wherein each said deployment descriptor includes a reference to the at least one library module, wherein the reference includes a minimum implementation version of the at least one library module required by a said application that is associated with the said deployment descriptor;

comparing the minimum implementation version in a first deployment descriptor of the plurality of deployment descriptors with the implementation version in the at least one library module, wherein the first deployment descriptor is associated with a first application of the plurality of applications in the server storage;

deploying the first application to a first web server, if the implementation version in the at least one library module satisfies the minimum implementation version in the first deployment descriptor, and generating a first deployed application based on the at least one library module and the first application, such that the first application has access to the commonly used functions provided by the at least one library module;

comparing the minimum implementation version in a second deployment descriptor of the plurality of deployment descriptors with the implementation version in the at least one library module, wherein the second deployment descriptor is associated with a second application of the plurality of applications in the server storage; and

deploying the second application to a second web server, if the implementation version in the at least one library module satisfies the minimum implementation version in the second deployment descriptor, and generating a second deployed application based on the at least one library module and the second application, such that the second application has access to the commonly used functions provided by the at least one library module.

2. The method of claim 1, wherein each said deployment descriptor is in a markup language.

3. The method of claim 1, wherein the at least one library module is stored in an archive file.

4. The method of claim 1, wherein the at least one library module is stored externally to the plurality of applications.

5. The method of claim 1, further comprising:

halting a deployment of the first application when the implementation version in the at least one library module does not satisfy the minimum implementation version required by the first application.

6. The method of claim 1, further comprising:

halting a deployment of the second application when the implementation version in the at least one library module does not satisfy the minimum implementation version required by the second application.

7. The method of claim 1, further comprising:

allowing the minimum implementation version in the first said deployment descriptor to be different from the minimum implementation version in the second deployment descriptor.

8. A computer program product, stored on a computer readable storage medium, and including computer executable instructions for deploying a plurality of applications, the instructions comprising instructions for:

providing at least one library module in a server storage, wherein the at least one library module performs commonly used functions shared by the plurality of applications and the at least one library module includes a manifest that stores information uniquely identifying the library module to a web server, and wherein the library module can be implemented in different implementation versions, and wherein the manifest includes an implementation version that indicates a version of a implementation of the library module stored in the server storage;

identifying the at least one library module using a key that includes a name of the at least one library module, an implementation version, and a specification version, wherein the specification version indicates a minimum extension specification version that is needed for extensions to the at least one library module;

providing a plurality of deployment descriptors, wherein each said deployment descriptor is associated with one of the plurality of applications stored in the server storage, wherein each said deployment descriptor includes a reference to the at least one library module, wherein the reference includes a minimum implementation version of the at least one library module required by a said application that is associated with the said deployment descriptor;

comparing the minimum implementation version in a first deployment descriptor of the plurality of deployment descriptors with the implementation version in the at least one library module, wherein the first deployment descriptor is associated with a first application of the plurality of applications in the server storage;

deploying the first application to a first web server, if the implementation version in the at least one library module satisfies the minimum implementation version in the first deployment descriptor, and generating a first deployed application based on the at least one library module and the first application, such that the first application has access to the commonly used functions provided by the at least one library module;

comparing the minimum implementation version in a second deployment descriptor of the plurality of deployment descriptors with the implementation version in the at least one library module, wherein the second deployment descriptor is associated with a second application of the plurality of applications in the server storage; and

deploying the second application to a second web server, if the implementation version in the at least one library module satisfies the minimum implementation version in the second deployment descriptor, and generating a second deployed application based on the at least one library module and the second application, such that the second application has access to the commonly used functions provided by the at least one library module.

9. The computer program product of claim 8, wherein the deployment descriptor is in a markup language.

10. The computer program product of claim 8, wherein the at least one library module is stored in an archive file.

11. The computer program product of claim 8, wherein the at least one library module is stored externally to the plurality of applications.

12. A system for deploying a plurality of applications, the system comprising:

at least one library module in a server storage, wherein the at least one library module performs commonly used functions shared by the plurality of applications and the at least one library module includes a manifest that stores information uniquely identifying the library module to a web server, and wherein the library module can be implemented in different implementation versions, and wherein the manifest includes an implementation version that indicates a version of a implementation of the library module stored in the server storage;

a plurality of deployment descriptors, wherein each said deployment descriptor is associated with one of the plurality of applications stored in the server storage, wherein each said deployment descriptor includes a reference to the at least one library module, wherein the reference includes a minimum implementation version of the at least one library module required by a said application that is associated with the said deployment descriptor; and

a deployment tool, running on one or more processors, configured to;

compare the minimum implementation version in a first deployment descriptor of the plurality of deployment descriptors with the implementation version in the at least one library module, wherein the first deployment descriptor is associated with a first application of the plurality of applications in the server storage;

deploy the first application to a first web server, if the implementation version in the at least one library module satisfies the minimum implementation version in the first deployment descriptor, and generate a first deployed application based on the at least one library module and the first application, such that the first application has access to the commonly used functions provided by the at least one library module;

identify the at least one library module using a key that includes a name of the at least one library module, an implementation version, and a specification version, wherein the specification version indicates a minimum extension specification version that is needed for extensions to the at least one library module;

compare the minimum implementation version in a second deployment descriptor of the plurality of deployment descriptors with the implementation version in the at least one library module, wherein the second deployment descriptor is associated with a second application of the plurality of applications in the server storage; and

deploy the second application to a second web server, if the implementation version in the at least one library module satisfies the minimum implementation version in the second deployment descriptor, and generate a second deployed application based on the at least one library module and the second application, such that the second application has access to the commonly used functions provided by the at least one library module.

13. The system of claim 12, wherein the deployment descriptor is in a markup language.

14. The system of claim 12, wherein the at least one library module is stored in an archive file.

15. The system of claim 12, wherein the at least one library module is stored externally to the plurality of applications.