|Publication number||US7797697 B2|
|Application number||US 10/969,089|
|Publication date||Sep 14, 2010|
|Filing date||Oct 20, 2004|
|Priority date||May 5, 2004|
|Also published as||US20050251810, WO2005114392A1|
|Publication number||10969089, 969089, US 7797697 B2, US 7797697B2, US-B2-7797697, US7797697 B2, US7797697B2|
|Inventors||Rob Woollen, Ruslan Bilorusets|
|Original Assignee||Bea Systems, Inc.|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (36), Non-Patent Citations (9), Referenced by (9), Classifications (7), Legal Events (3)|
|External Links: USPTO, USPTO Assignment, Espacenet|
The present application is a nonprovisional of U.S. Patent Application No. 60/568,211, filed on May 5, 2004, entitled FEDERATED APPLICATIONS, Inventors Rob Woolen, et al., the contents of which are incorporated by reference in their entirety.
The present application is related to U.S. Patent Application No. 60/571,106, filed May 15, 2004, entitled SYSTEM AND METHOD FOR WEB APPLICATION EXTENSIBILITY, Inventors Mark Griffith et al., the contents of which are incorporated by reference in their entirety.
A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.
The present invention relates to systems, methods, and computer readable media for structuring and deploying applications.
Since its inception in 1995, the Java™ programming language has become increasingly popular. (Java is a trademark of Sun Microsystems, Inc.) Java, which is an interpreted language, enabled the creation of applications which could be run on a wide variety of platforms. This ability to function across a variety of different client platforms and Java's relatively easy implementation of network applications has resulted in its use in endeavors as basic as personal web pages to endeavors as complex as large business-to-business enterprise systems.
As Java has become more commonplace, a wide variety of tools and development platforms have been created to assist developers in the creation and implementation of Java applications. These development platforms have usually been built around an application server program that provides a common interface for accessing internal data and resources. These development platforms have also included commonly-used modules and components that can be included in newly-created applications, thus sparing the developers the burden of creating these components and having to recreate the efforts of others. One such application platform is WebLogic Platform, by BEA systems of San Jose Calif.
While these platforms enable users to utilize previously developed modules and components, there are some inefficiencies with the current mechanisms by which these modules are included in new applications. Current configurations require that the modules be copied into every application which utilizes the modules or add the modules to a system classpath storing modules that are available to all applications. Thus, if these commonly-used modules are modified, they must be separately modified in every application which utilizes them, greatly complicating the process of maintaining web servers and complicating deployment.
The application 10 also includes a deployment descriptor 38 which stores information necessary for the deployment tool 25 to successfully deploy the application. In one embodiment, the deployment descriptor is an application.xml file. As used herein, files ending with an “xml” filename extension are files in the eXtensible Markup Language (XML) format. The deployment descriptor preferably includes elements indicating each module used in the application, its type, and its path in the EAR file storing the application. If a common module 35 is used in each of the applications 10, 15, 20 it will appear in each of the EAR files, with its existence and location in the EAR referenced in the deployment descriptor 38 for the applications. The deployment descriptor 38 typically lists the location of the file in the EAR relative to a root of the EAR.
The deployment tool 25 is responsible for deploying the applications 10, 15, 20 from the server storage to generate the deployed applications 40, 45, 50. In one embodiment, the deployment tool runs when the server is started and automatically deploys a group of preselected applications. In an alternate embodiment, the deployment tool allows a system administrator to manually select which applications are deployed. The deployment tool checks the deployment descriptors 38 of each of the applications 10, 15, 20 to locate the modules 30, 35 used by the application within that application's EAR file and to deploy the application. The deployed applications are then available for use by remote clients or any party interacting with the web server.
The implementation discussed in
In accordance with one embodiment of the present invention 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.
The server storage 105 also includes library modules 128. The library modules are commonly-used modules that are stored for deployment with created applications. The library modules are preferably stored in Java ARchive (JAR) files. In one embodiment, each JAR file stores a single library module. In an alternate embodiment, multiple library modules are stored in a single JAR file. The library modules typically include a manifest identifying the library module, class files, a deployment descriptor, and additional resources. The structure of the library modules is described in greater detail with respect to
The library modules are typically registered with the server by including a reference to the library in the server's configuration parameters. In one embodiment, the configuration parameters include a config.XML file. When starting, the server detects the reference to the library and generates a configuration bean associated with the library. The reference to the library preferably includes a unique name for the library, a type for the library, a version of the library, and a location of the JAR file storing the library. One embodiment of a config.XML entry for a library file is disclosed below:
The applications 110, 115, 120 include application modules 130 which are modules that have been created for the particular application and are either not commonly utilized or not commonly utilized enough to justify their inclusion with the library modules 125. The applications also include deployment descriptors 155. In one embodiment, the deployment descriptor is an application.xml file. The deployment descriptor preferably includes information necessary for representing the application in different GUI tools, elements indicating each module used in the application, its type, and its path in the EAR file storing the application. Additionally, the application deployment descriptor includes references to the library modules 128 utilized by the application. The reference to the library module includes the library name, which uniquely identifies the library and is compared to the library name included in either the library's manifest or the config.XML file. It also includes the implementation version, which is the minimum implementation version needed by the application. The deployment tool 125 will compare this value with the implementation version stored in the config.XML file to verify that the two match. Finally, the entry includes a module-url which indicates a location on the server 105 where the library module can be located. Below is one example of an application.xml file which references library modules
The deployment tool 125 is responsible for deploying the applications 110, 115, 120 from the server storage to generate the deployed applications 140, 145, 150. In one embodiment, the deployment tool runs when the server is started and automatically deploys a group of preselected applications. In an alternate embodiment, the deployment tool allows a system administrator to manually select which applications are deployed.
The deployment tool, when deploying an application 110, checks the deployment descriptor 155. The deployment tool first checks the library module reference to determine whether there are any library modules referenced by the application 110. If so, the deployment tool uses the identifier for the library module to locate the library module on the server storage 105. The deployment tool 125 then extracts any referenced library modules from the JAR files in which the library file is archived in the order in which the library modules are listed in the deployment descriptor. Alternately the deployment tool 125 can directly deploy the library module from the location where it is stored. If the JAR file contains multiple library modules, all of the library modules in the JAR file are deployed. The deployment tool 125 then deploys any application modules 136 within the application 110.
The library name 330 is the unique identifier used to identify the module. The library name is used by the deployment tool 125 to identify the module when referenced by the application.xml file in the application 120. The implementation title 335 is a string that uniquely identifies the title of the library implementation. The implementation version 340 indicates a version of the implementation of the library module that is stored on the server storage. The web server preferably compares the implementation version 340 and library name 330 of the stored library module to the name and implementation version in the application.xml file of the associated application. In one embodiment, if the library name and implementation version do not match, the deployment tool 125 will not extract the library module.
The library module also includes class files 315. The class files are classes which contain the functionality of the module. The library module also includes additional resources 325. The additional resources include static content files for use by the library module 315. The library module additionally includes a deployment descriptor 320. The deployment descriptor preferably includes information necessary for representing the library module in different GUI tools, elements indicating each module used in the library module and its type and path in the JAR file storing the library module. Alternately, the library module can include a standard web-application deployment descriptor.
If there are library modules referenced in the deployment descriptor, the server then, in step 420, validates the references stored in the deployment descriptor and verifies that they are registered with the server. When the server is first booted (previous to step 405), it performs a registration process where it reads an entry in the config.xml file indicating the location and implementation version of any library modules. Returning to step 420, the server reads the library module name listed in the deployment descriptor for the application and loads the library module located at the location associated with the module name in the server's config.xml file. The server also checks the implementation version of the module registered with the server to make sure that it matches the implementation version listed in the referencing deployment descriptor. If no module is stored at the location listed in the config.xml file, if the module located at the location described in the config.xml file does not have the same name in its manifest as the module listed in the application.xml file, or if the implementation version listed in the config.xml file or module manifest does not match the implementation version stored in the config.xml file, the server determines, in step 425, that the library module has not been validated and halts, in step 428, deployment of the application.
If the references are validated, the server then sequentially extracts and deploys, in step 430, each library module from the JAR file in which it is stored in the order that the library modules appear in the application.xml file. If any JAR files store multiple library modules, all of the library modules in the JAR file are deployed.
The server then deploys, in step 435, the modules listed in the application's application.xml file and then completes, in step 440, deployment of the application.
Other features, aspects and objects of the invention can be obtained from a review of the figures and the claims. It is to be understood that other embodiments of the invention can be developed and fall within the spirit and scope of the invention and claims.
The foregoing description of preferred embodiments of the present invention has been provided for the purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise forms disclosed. Obviously, many modifications and variations will be apparent to the practitioner skilled in the art. The embodiments were chosen and described in order to best explain the principles of the invention and its practical application, thereby enabling others skilled in the art to understand the invention for various embodiments and with various modifications that are suited to the particular use contemplated. It is intended that the scope of the invention be defined by the following claims and their equivalence.
In addition to an embodiment consisting of specifically designed integrated circuits or other electronics, the present invention may be conveniently implemented using a conventional general purpose or a specialized digital computer or microprocessor programmed according to the teachings of the present disclosure, as will be apparent to those skilled in the computer art.
Appropriate software coding can readily be prepared by skilled programmers based on the teachings of the present disclosure, as will be apparent to those skilled in the software art. The invention may also be implemented by the preparation of application specific integrated circuits or by interconnecting an appropriate network of conventional component circuits, as will be readily apparent to those skilled in the art.
The present invention includes a computer program product which is a storage medium (media) having instructions stored thereon/in which can be used to program a computer to perform any of the processes of the present invention. The storage medium can include, but is not limited to, any type of disk including floppy disks, optical discs, DVD, CD-ROMs, microdrive, and magneto-optical disks, ROMs, RAMs, EPROMs, EEPROMs, DRAMs, VRAMs, flash memory devices, magnetic or optical cards, nanosystems (including molecular memory ICs), or any type of media or device suitable for storing instructions and/or data.
Stored on any one of the computer readable medium (media), the present invention includes software for controlling both the hardware of the general purpose/specialized computer or microprocessor, and for enabling the computer or microprocessor to interact with a human user or other mechanism utilizing the results of the present invention. Such software may include, but is not limited to, device drivers, operating systems, and user applications.
Included in the programming (software) of the general/specialized computer or microprocessor are software modules for implementing the teachings of the present invention.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US5835777||Mar 20, 1996||Nov 10, 1998||Hewlett-Packard Company||Method of automatically generating a software installation package|
|US5911071||Sep 13, 1996||Jun 8, 1999||Sun Microsystems, Inc.||Persistent programming system and method for deploying self-containing executable applications|
|US6128647||Apr 4, 1997||Oct 3, 2000||Haury; Harry R.||Self configuring peer to peer inter process messaging system|
|US6529992||Jul 26, 1999||Mar 4, 2003||Iomega Corporation||Self-contained application disk for automatically launching application software or starting devices and peripherals|
|US6721777||May 24, 2000||Apr 13, 2004||Sun Microsystems, Inc.||Modular and portable deployment of a resource adapter in an application server|
|US6751797||Oct 26, 2000||Jun 15, 2004||Bull S.A.||System and method for managing the persistence of EJB components in a directory accessed via LDAP|
|US6766324||Jul 20, 2001||Jul 20, 2004||International Business Machines Corporation||System and method for defining, configuring and using dynamic, persistent Java classes|
|US6829575||Mar 11, 2003||Dec 7, 2004||International Business Machines Corporation||Enterprise javabeans container|
|US6892382 *||May 3, 2000||May 10, 2005||Sun Microsystems, Inc.||Method and apparatus for implementing deployment descriptors in an enterprise environment|
|US6970924||Feb 23, 1999||Nov 29, 2005||Visual Networks, Inc.||Methods and apparatus for monitoring end-user experience in a distributed network|
|US6976061||May 24, 2000||Dec 13, 2005||Sun Microsystems, Inc.||Resource adapter and XML descriptor for use in a client server environment utilizing an enterprise information system|
|US7069553 *||Mar 3, 2003||Jun 27, 2006||Computer Associates Think, Inc.||Universal deployment tool|
|US7086065||Jul 20, 2000||Aug 1, 2006||Telesector Resources Group, Inc.||Functional enterprise bean|
|US7107592||Jul 25, 2002||Sep 12, 2006||Sun Microsystems, Inc.||Method, system, and program for making objects available for access to a client over a network|
|US7127713||Jan 10, 2003||Oct 24, 2006||Akamai Technologies, Inc.||Java application framework for use in a content delivery network (CDN)|
|US7185071||Dec 24, 2002||Feb 27, 2007||International Business Machines Corporation||Self-healing version and configuration model for an application server|
|US7228541||Jan 17, 2003||Jun 5, 2007||National Instruments Corporation||Creation of application system installer|
|US7302609||Mar 12, 2004||Nov 27, 2007||Vladimir Matena||Method and apparatus for executing applications on a distributed computer system|
|US20020049744||Aug 31, 2001||Apr 25, 2002||Dimitris Nakos||Techniques for managing a database system including one or more database servers|
|US20020078132||Nov 14, 2001||Jun 20, 2002||Cullen William M.||Message handling|
|US20030093717||Sep 26, 2001||May 15, 2003||International Business Machines Corporation||Test programs for enterprise web applications|
|US20030101435||Nov 20, 2002||May 29, 2003||Hitachi, Inc.||Method for associating names and device for the same in enterprise applications|
|US20030158919||Feb 20, 2002||Aug 21, 2003||Sun Microsystems, Inc., A Delaware Corporation||Method for deploying version control system server software having remote access capability|
|US20030204784||Apr 29, 2002||Oct 30, 2003||Jorapur Gopal P.||System and method for automatic test case generation|
|US20030212990 *||May 8, 2002||Nov 13, 2003||Thomas Brodkorb||Software delivery manager|
|US20040068537||Mar 11, 2003||Apr 8, 2004||International Business Machines Corporation||Enterprise javabeans container|
|US20040068553 *||Oct 7, 2002||Apr 8, 2004||International Business Machines Corporation||Dynamically selecting a Web service container for hosting remotely instantiated Web services|
|US20040068731||Oct 7, 2002||Apr 8, 2004||International Business Machines Corporation||Remote Web service cloning and instantiation|
|US20040088681||Oct 31, 2002||May 6, 2004||Berg Daniel C.||Method and system for dynamically mapping archive files in an enterprise application|
|US20040172407||Feb 28, 2003||Sep 2, 2004||Arpirez Vega Julio Cesar||Method and system of processing an encapsulated file at a management computer|
|US20040177352 *||Mar 3, 2003||Sep 9, 2004||Narayanaswamy Sreedhara Srinivasulu||Universal deployment tool|
|US20040255294||Feb 12, 2004||Dec 16, 2004||Bea Systems, Inc.||System and method for hierarchical loading of EJB implementations|
|US20050005200||Mar 12, 2004||Jan 6, 2005||Vladimir Matena||Method and apparatus for executing applications on a distributed computer system|
|US20050033767 *||Aug 4, 2003||Feb 10, 2005||Kamentz Joel D.||Computer-implemented system and method for resource caching and execution|
|US20050137856 *||Dec 22, 2003||Jun 23, 2005||Cencini Andrew B.||Full-text index module consistency checking|
|US20050138076||May 4, 2004||Jun 23, 2005||Seo Beom S.||Description and implementation method of threadbean in EJB container|
|1||*||"Microsoft Computer Dictionary," Fifth Edition, Microsoft Press, 2002; p. 115, 176, 542.|
|2||Chappell, et al., "Java Message Service", O'Reilly, Dec. 2000, © 2006, Safari Books Online, 27 pages; http://proquest.safaribooksonline.com/059600685.|
|3||Guo, et al., "Developing a Distributed Scalable Java Component Server", Future Generation Computer Systems, May 24, 2001, vol. 17, Issue 8, pp. 1051-1057, © 2001 Elsevier Science B.V.|
|4||International Search Report for PCT/US05/14430, 8 pages, Mailed Jul. 27, 2005, PCT.|
|5||Mencl, "Enhancing EJB Component Model", Academy of Sciences of the Czech Republic, 2001, 11 pages.|
|6||Popovici, "Spontaneous Container Services ", ECOOP 2003, LNCS 2743, pp. 29-54.|
|7||Taylor, A., J2EE and Beyond: Design, Develop, and Deploy World-Class Java(TM) Software, Prentice-Hall, Dec. 23, 2002, 40 pages.|
|8||Taylor, A., J2EE and Beyond: Design, Develop, and Deploy World-Class Java™ Software, Prentice-Hall, Dec. 23, 2002, 40 pages.|
|9||Vecellio, et al., "Container Services for High Confidence Software", Jun. 10-14, 2002, Seventh International Workshop on Component-Oriented Programming, 13 pages.|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US8225307 *||Nov 15, 2004||Jul 17, 2012||International Business Machines Corporation||On-demand software module deployment|
|US8938735 *||Aug 31, 2007||Jan 20, 2015||Thomson Reuters Global Resources||Bootstrapper and software download manager|
|US9037912 *||Aug 23, 2012||May 19, 2015||Amazon Technologies, Inc.||Validation of asset data for component assemblies|
|US9043781 *||Dec 3, 2004||May 26, 2015||International Business Machines Corporation||Algorithm for automated enterprise deployments|
|US9448790 *||Apr 26, 2011||Sep 20, 2016||Pivotal Software, Inc.||Rapid updating of cloud applications|
|US20050108702 *||Nov 15, 2004||May 19, 2005||International Business Machines Corporation||On-demand software module deployment|
|US20060123040 *||Dec 3, 2004||Jun 8, 2006||International Business Machines Corporation||Algorithm for automated enterprise deployments|
|US20090064135 *||Aug 31, 2007||Mar 5, 2009||Thomson Corporation||Bootstrapper and software download manager|
|US20110265077 *||Apr 26, 2011||Oct 27, 2011||Vmware, Inc.||Rapid updating of cloud applications|
|U.S. Classification||717/170, 717/175, 717/177|
|International Classification||G06F9/445, G06F9/44|
|Mar 7, 2005||AS||Assignment|
Owner name: BEA SYSTEMS, INC., CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:WOOLLEN, ROB;BILORUSETS, RUSLAN;REEL/FRAME:016340/0555;SIGNING DATES FROM 20050204 TO 20050303
Owner name: BEA SYSTEMS, INC., CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:WOOLLEN, ROB;BILORUSETS, RUSLAN;SIGNING DATES FROM 20050204 TO 20050303;REEL/FRAME:016340/0555
|Oct 15, 2010||AS||Assignment|
Owner name: ORACLE INTERNATIONAL CORPORATION, CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BEA SYSTEMS, INC.;REEL/FRAME:025192/0244
Effective date: 20101008
|Feb 12, 2014||FPAY||Fee payment|
Year of fee payment: 4