Model for system-wide application extension

• US 8,707,294 B2
• Filed: 04/07/2009
• Issued: 04/22/2014
• Est. Priority Date: 04/07/2009
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Bajaj, Aseem, Pallamreddy, Prasanth
• Primary Examiner(s): Zhen, Wei
• Assistant Examiner(s): HUDA, MOHAMMED NURUL
• Application Number:
  US12/419,685
• Publication Number:
  US 20100257508A1
• Time in Patent Office: 1,841 Days
• Field of Search: 717/175
• US Class Current: 717/175
• CPC Class Codes: G06F 9/44563 Sharing

Abstract

A model for extending application server functionality includes two types of libraries: an automatically-referenced (auto-ref) library and a superseding library. The auto-ref library includes a special tag that identifies it as the auto-ref library and a pattern that restricts the application types that can refer to it. Once the auto-ref library is deployed, it is automatically referred to by all applications as long as they are not excluded by the restricting pattern. The code contained in the auto-ref library is merged into the application code and the configuration of the library is merged into the application configuration at deployment time. The superseding library also includes an identifying tag and a restriction pattern. At deployment, however, the code and configuration data in the superseding library overrides the corresponding application configuration and code. The remaining code of the application that is not overridden by the superseding library is used without any modification.

Claims

1. A system for providing a model for system-wide application extension, said system comprising:

an application server that executes on one or more microprocessors, wherein the application server includes a plurality of applications , wherein each application is associated with an application type, and includes application code and application configuration data;

a first shared library that contains fragment code, fragment configuration data, and a first tag, wherein the first shared library is identified by the application server as an auto-ref library using the first tag;

wherein when a particular application of said plurality of applications is deployed as a particular deployed application on the application server, the application server causes the particular deployed application to automatically reference the auto-ref library unless the application type associated with the particular application is excluded by the auto-ref library;

wherein when referencing the auto-ref library, the fragment code and the fragment configuration data of the auto-ref library are automatically merged into the application code and application configuration data of the particular application at deployment time without replacing any conflicting application code, and wherein conflicting application code and application configuration data of the particular application are used without modification in the particular deployed application;

a second shared library that contains superseding code, superseding configuration data, and a second tag, different than the first tag, wherein the second shared library is identified by the application server as a superseding library using the second tag;

wherein when the particular application is deployed on the application server as the particular deployed application, the application server causes the particular deployed application to automatically reference the superseding library unless the application type associated with the particular application is excluded by the superseding library; and

wherein when referencing the superseding library, the superseding code and the superseding configuration data override the application code of the particular application, such that conflicting application code and configuration data of the particular application is replaced by the superseding code and superseding configuration data in the particular deployed application, and wherein application code and application configuration data of the particular application that is not replaced by the superseding library is used without modification in the particular deployed application.

2. The system of claim 1, wherein the superseding library further includes a restriction pattern that excludes a set of application types from referring to the superseding library, such that applications having any of the set of application types are not automatically referenced by the application server.

3. The system of claim 1, wherein the auto-ref library further includes a restriction pattern that excludes a set of application types from referring to the auto-ref library, such that applications having any of the set of application types are not automatically referenced by the application server.

4. The system of claim 3, wherein the restriction pattern is configured in a manifest file as a name value pair.

5. The system of claim 3, wherein the restriction pattern is configured using a graphical user interface.

6. The system of claim 1, wherein the application server is repackaged as a middleware product by deploying a set of extensions as one or more auto-ref libraries and superseding libraries.

7. The system of claim 1, wherein a container of the application server merges the fragment code and the fragment configuration data into the application code and the application configuration data at the time of deploying the plurality of applications.

8. The system of claim 1, wherein a system filter is deployed as a shared library on the application server, such that said system filter intercepts requests flowing to the plurality of applications and performs monitoring or security functionality on the requests.

9. A method for providing a model for system-wide application extension, said method comprising:

repackaging an application server that executes on one or more microprocessor by deploying one or more application extensions as at least a first shared library and a second shared library on said application server,

wherein the first shared library includes fragment code and fragment configuration data to implement the one or more application extensions, and a first tag which identifies the first shared library as an auto-ref library, and

wherein the second shared library contains superseding code and superseding configuration data and a second tag, different than the first tag, which identifies the second shared library as a superseding library;

deploying a plurality of applications on the application server, wherein each application is associated with an application type, and includes application code and application configuration data;

wherein when a particular application of said plurality of applications is deployed on the application server as a particular deployed application, the application server causes the particular deployed application to automatically reference the auto-ref library unless the application type associated with the particular application is excluded by the auto-ref library; and

automatically merging the fragment code and the fragment configuration data of the auto-ref library with the application code and the application configuration data of the particular application upon deployment;

wherein when referencing the auto-ref library, the fragment code and the fragment configuration data of the auto-ref library are merged into application code and application configuration data of the particular deployed application without replacing conflicting application code and configuration data, and wherein conflicting application code and application configuration data of the particular application are used without modification in the particular deployed application;

wherein when the particular application is deployed on the application server, the application server also causes the particular deployed application to automatically reference the superseding library unless the application type associated with the particular application is excluded by the superseding library; and

automatically merging the application code and configuration data of the particular application with the superseding code and the superseding configuration information, wherein when referencing the superseding library, the superseding code and the superseding configuration data override the application code of the particular application, such that conflicting application code and application configuration data is replaced by the superseding code and superseding configuration data in the particular deployed application, and application code and application configuration data or the particular application that is not replaced by the superseding library is used without modification in the particular deployed application.

10. The method of claim 9, wherein the superseding library further includes a restriction pattern that excludes a set of application types from referring to the superseding library, such that applications having any of the set of application types are not automatically referenced by the application server.

11. The method of claim 9, wherein the auto-ref library further includes a restriction pattern that excludes a set of application types from referring to the auto-ref library, such that applications having any of the set of application types are not automatically referenced by the application server.

12. The method of claim 11, wherein the restriction pattern is configured in a manifest file as a name value pair.

13. The method of claim 11, wherein the restriction pattern is configured using a graphical user interface.

14. The method of claim 9, wherein the application server is repackaged as a middleware product by deploying a set of extensions as one or more auto-ref libraries and superseding libraries.

15. The method of claim 9, wherein a container of the application server merges the application fragment code and configuration data into the application code and configuration data at the time of deploying the particular deployed application.

16. The method of claim 9, further comprising:

deploying a system filter as a shared library on the application server, such that said system filter intercepts requests flowing to the application and performs monitoring or security functionality on the requests.

17. A non-transitory computer-readable storage medium carrying one or more sequences of instructions for providing a model for system-wide application extension, which instructions, when executed by one or more processors, cause the one or more processors to carry out the steps of:

repackaging an application server by deploying one or more application extensions as at least a first shared library and a second shared library on said application server,

wherein the first shared library includes fragment code and fragment configuration data to implement the one or more application extensions, and a first tag which identifies the first shared library as an auto-ref library, and

wherein the second shared library contains superseding code and superseding configuration data and a second tag, different than the first tag, which identifies the second shared library as a superseding library;

deploying a plurality of applications on the application server, wherein each application is associated with an application type, and includes application code and application configuration data;

wherein when a particular application of said plurality of applications is deployed on the application server as a particular deployed application, the application server causes the particular deployed application to automatically reference the auto-ref library unless the application type associated with the particular application is excluded by the auto-ref library; and

automatically merging the fragment code and the fragment configuration data of the auto-ref library with the application code and the application configuration data of the particular application upon deployment, wherein when referencing the auto-ref library, the fragment code and the fragment configuration data of the auto-ref library are merged into the application code and application configuration data of the particular application without replacing conflicting application code and application configuration data, and conflicting application code and application configuration data of the particular application are used without modification in the particular deployed application;

wherein when the particular application is deployed on the application server, the application server also causes the particular deployed application to automatically reference the superseding library unless the application type associated with the particular application is excluded by the superseding library; and

automatically merging the application code and configuration data of the particular application with the superseding code and the superseding configuration information, wherein when referencing the superseding library, the superseding code and the superseding configuration data override the application code and application configuration data of the particular application, such that conflicting application code and application configuration data is replaced by the superseding code and superseding configuration data in the particular deployed application, and wherein application code and application configuration data of the particular application that is not replaced by the superseding library is used without modification in the particular deployed application.

18. The non-transitory computer-readable storage medium of claim 17, wherein the superseding library includes a restriction pattern that excludes a set of application types from referring to the superseding library, such that applications having any of the set of application types are not automatically referenced by the application server.

19. The non-transitory computer-readable storage medium of claim 18, wherein the restriction pattern is configured in a manifest file as a name value pair.

20. The non-transitory computer-readable storage medium of claim 17, wherein a container of the application server merges the application fragment code and configuration data into the application code and configuration data at the time of deploying the particular deployed application.