A method is described that inserts first and second deployment descriptors into an application archive file. The first deployment descriptor conforms to a first document type definition that is defined by a standard specification. The second deployment descriptor conforms to a second document type definition that is not defined by the standard specification. The second deployment descriptor has an element that is directed to a service that is an extension to the services offered by an environment described by the standard specification. The first and second deployment descriptors provide configuration information selected from the group consisting of: a) configuration information that pertains to the application as a whole; and, b) configuration information that pertains to a web application portion of the application.
Legal claims defining the scope of protection. Each claim is shown in both the original legal language and a plain English translation.
1. A method of deploying an application, the method comprising: in an application archive associated with said application, said application archive including a first deployment descriptor and a second deployment descriptor, said first deployment descriptor associated with an application-level of a hierarchy of deployment descriptors associated with said application and said second deployment descriptor associated with a module-level of said hierarchy, each of said first and second deployment descriptors conforming to a first document type definition that is defined by a standard specification, inserting a third deployment descriptor and a fourth deployment descriptor, each of said third and fourth deployment descriptors conforming to a second document type definition that is not defined by said standard specification, each of said third and fourth deployment descriptors having an element directed to a service that is an extension to said services offered by an environment described by said standard specification, each of said first and third deployment descriptors providing configuration information that pertains to said application as a whole; and each of said second and fourth deployment descriptors providing configuration information that pertains to a module of said application, said third deployment descriptor associated with said application-level of said hierarchy, said fourth deployment descriptor associated with said module-level of said hierarchy, each of said first deployment descriptor, second deployment descriptor, third deployment descriptor, and fourth deployment descriptor to be used at deployment time; and deploying said application consistently with said configuration information provided in said first and third deployment descriptors and said configuration provided in said second and fourth deployment descriptors.
A method for deploying applications involves inserting extra deployment descriptors into an application archive (like a WAR or EAR file). This archive already contains standard deployment files (descriptors) for both the application level and module level that conform to a standard specification. The method adds two more deployment descriptors, one for the application level and one for the module level, that *don't* conform to the standard. These non-standard descriptors include elements that configure services extending the standard environment's capabilities. The standard and non-standard descriptors for the application level contain configuration that applies to the whole application, and the descriptors for the module level configure individual modules. All four descriptors are used when the application is deployed, ensuring the application runs with the configurations specified in both the standard and custom descriptors.
2. The method of claim 1 wherein said standard specification is a J2EE standard specification.
The application deployment method previously described utilizes the J2EE (Java 2 Enterprise Edition) standard specification as the "standard specification" for the initial deployment descriptors, which are extended by the insertion of non-standard descriptors providing extended services configuration.
3. The method of claim 1 wherein said first and third deployment descriptors are both application deployment descriptors.
In the application deployment method, the first and third deployment descriptors – the standard and non-standard ones associated with the application level – are both application deployment descriptors. This means they both describe configuration information relevant to the entire application, rather than specific modules within it.
4. The method of claim 3 , further comprising interpreting said information from both of said deployment descriptors as application deployment descriptor information for said application.
The application deployment method where both the first and third deployment descriptors are application deployment descriptors, further involves interpreting information from both descriptors as being directed to the application level configuration. This ensures the deployment process treats the configuration details provided in both the standard and non-standard application-level descriptors as pertaining to the overall application's setup and behavior.
5. The method of claim 1 , wherein said second document type definition comprises an element for a named reference to an item of software outside said application and selected from the group consisting of: another application; a library; a service; and, an interface.
The application deployment method's non-standard deployment descriptors (third and fourth) contain an element that acts as a named reference to external software. This software can be another application, a library, a service, or an interface. This element allows the application to depend on and interact with resources located outside its own archive, extending its functionality.
6. The method of claim 1 , wherein said second document type definition comprises an element to identify a classpath to a resource outside said application that said application is designed to use.
The application deployment method's non-standard deployment descriptors (third and fourth) include an element that specifies the classpath to a resource external to the application. This allows the application to locate and use external resources (e.g., JAR files, configuration files) by defining the path where they can be found during runtime, enabling it to leverage external dependencies.
7. The method of claim 1 , wherein said second document type definition comprises an element to identify said application's provider.
The application deployment method's non-standard deployment descriptors (third and fourth) include an element to identify the application's provider. This could be the company or organization that developed and is distributing the application. This allows the deployment environment to track the origin of the application.
8. The method of claim 1 , wherein said second document type definition comprises an element to identify one or more modules of said application that are to be distributed to one or more containers that are not standard J2EE containers.
The application deployment method's non-standard deployment descriptors (third and fourth) contain an element that identifies modules within the application intended for deployment to non-standard J2EE containers. This accommodates deployment scenarios where certain application components are designed to operate in environments outside the standard J2EE ecosystem.
9. The method of claim 1 , wherein said second document type definition comprises an element to indicate whether or not a failover service is enabled, said failover service being said extension.
The application deployment method's non-standard deployment descriptors (third and fourth) contain an element that indicates whether a failover service (the extension service) is enabled. This allows configuration of high availability features, where the application can automatically switch to a backup server in case of failure.
10. The method of claim 1 , wherein said second document type definition comprises an element that indicates a start time for said application, said ability to specify said start time being said extension.
The application deployment method's non-standard deployment descriptors (third and fourth) contain an element to specify a start time for the application. The ability to customize the application's startup schedule represents an extension to the standard deployment environment's features.
11. The method of claim 1 wherein said second and fourth deployment descriptors are both web application deployment descriptors, said application being a web application.
In the application deployment method, the second and fourth deployment descriptors, corresponding to module-level descriptors, are both web application deployment descriptors. This focuses the custom configuration specifically on a web application module.
12. The method of claim 11 wherein said second document type definition comprises an element for a reference to a resource external to said web application, said reference being a JNDI name.
In the application deployment method concerning web applications, the non-standard web application deployment descriptor includes an element for referencing external resources using JNDI (Java Naming and Directory Interface) names. This allows the web application to look up and utilize resources managed by the application server, like database connections or message queues.
13. The method of claim 11 wherein said second document type definition comprises an element for a reference to an object in an environment of said web application, said reference being a JNDI name.
In the application deployment method concerning web applications, the non-standard web application deployment descriptor includes an element referencing objects in the web application's environment via JNDI (Java Naming and Directory Interface) names. This allows configuration to access server-managed objects.
14. The method of claim 11 wherein said second document type definition comprises an element to define a login module for said web application.
In the application deployment method concerning web applications, the non-standard web application deployment descriptor defines a login module for authenticating users. This customizes the web application's security by integrating specific authentication mechanisms beyond the standard options.
15. The method of claim 11 wherein said second document type definition comprises an element to define a password changing setting for said web application.
In the application deployment method concerning web applications, the non-standard web application deployment descriptor includes an element to define password changing settings. This customizes how users can reset or change their passwords within the web application.
16. The method of claim 1 , wherein said second document type definition comprises an element for a reference to an enterprise java bean, said reference being a JNDI name.
The application deployment method's non-standard deployment descriptors (third and fourth) contain an element that references an Enterprise Java Bean (EJB) using a JNDI (Java Naming and Directory Interface) name. This facilitates access and utilization of EJBs within the application.
17. The method of claim 1 , wherein said second document type definition comprises an element to identify security roles that are available on a server upon which said application is to be deployed.
The application deployment method's non-standard deployment descriptors (third and fourth) contain an element to identify security roles available on the deployment server. This enables the application to leverage existing server-level security configurations.
18. The method of claim 1 , wherein said second document type definition comprises an element having information to construct an HTTP response.
The application deployment method's non-standard deployment descriptors (third and fourth) contain an element holding information to construct an HTTP response. This permits customization of the application's output and interaction with clients using HTTP protocol.
19. The method of claim 1 , wherein said second document type definition comprises an element to invoke a fail alert service in which an alert message warning is sent to a client of said application to alert said client that a server on which said application is running will be shut down, said fail alert service being said extension.
The application deployment method's non-standard deployment descriptors (third and fourth) contain an element to invoke a fail alert service. This service sends a warning message to the application's client, notifying them of an impending server shutdown.
20. The method of claim 1 , wherein said second document type definition comprises an element to specify if user sessions will be tracked by a URL or by a cookie.
The application deployment method's non-standard deployment descriptors (third and fourth) contain an element that specifies whether user sessions are tracked using URLs or cookies. This allows the application to configure its session management strategy based on client capabilities and security considerations.
21. The method of claim 1 , wherein said second document type definition comprises an element to specify a security policy domain for said application.
The application deployment method's non-standard deployment descriptors (third and fourth) contain an element to specify a security policy domain for the application. This allows administrators to enforce specific security policies tailored to the application's needs.
22. The method of claim 1 , wherein said second document type definition comprises elements to describe a cookie, said cookie being an application cookie or a session cookie.
The application deployment method's non-standard deployment descriptors (third and fourth) contain elements describing cookies, which can be application cookies or session cookies. This permits granular control over cookie attributes like name, value, domain, path, and expiration.
23. The method of claim 1 wherein said inserting is performed by a deploy tool.
In the application deployment method, the insertion of the custom deployment descriptors (third and fourth) is performed by a deployment tool. This automates the process of adding the descriptors to the application archive.
24. The method of claim 1 wherein said inserting is performed upon a server targeted for deployment of said application.
In the application deployment method, the insertion of the custom deployment descriptors (third and fourth) is performed on the server where the application is targeted for deployment. This streamlines the configuration process by directly modifying the deployment package on the target environment.
25. An article of manufacture including program code which, when executed by a machine, causes the machine to perform operations for deploying an application, the operations comprising: in an application archive associated with said application, said application archive including a first deployment descriptor and a second deployment descriptor, said first deployment descriptor associated with an application-level of a hierarchy of deployment descriptors associated with said application and said second deployment descriptor associated with a module-level of said hierarchy, each of said first deployment descriptor and said second deployment descriptor conforming to a first document type definition that is defined by a standard specification, inserting a third deployment descriptor and a fourth deployment descriptor, each of said third and fourth deployment descriptors conforming to a second document type definition that is not defined by said standard specification, each of said third and fourth deployment descriptors having an element directed to a service that is an extension to said services offered by an environment described by said standard specification, said first and third deployment descriptors providing configuration information that pertains to said application as a whole, said second and fourth deployment descriptors providing configuration information that pertains to a module of said application, said third deployment descriptor associated with said application-level of said hierarchy, said fourth deployment descriptor associated with said module-level of said hierarchy, each of said first deployment descriptor, second deployment descriptor, third deployment descriptor, and fourth deployment descriptor to be used at deployment time; and deploying said application consistently with said configuration information provided in said first and third deployment descriptors and said configuration provided in said second and fourth deployment descriptors.
A program (article of manufacture) enables application deployment by inserting additional deployment descriptors into an application archive. The archive includes standard descriptors at the application and module levels, adhering to a standard specification. The program adds two non-standard descriptors, one for each level, containing elements configuring extended services. Standard and non-standard application-level descriptors contain application-wide configuration, while module-level descriptors configure individual modules. All four descriptors are used during deployment, applying configurations from both standard and custom descriptors.
26. The article of manufacture of claim 25 wherein said standard specification is a J2EE standard specification.
The program for application deployment utilizes the J2EE standard specification for the initial deployment descriptors, extended by the insertion of non-standard descriptors that provide configuration for extended services.
27. The article of manufacture of claim 25 wherein said first and third deployment descriptors are both application deployment descriptors.
A software product (e.g., executable code) for deploying applications operates by processing an application archive. This archive initially includes two deployment descriptors: a standard application-level descriptor and a standard module-level descriptor, both conforming to a defined standard specification. The product then inserts two *additional* deployment descriptors: a non-standard application-level descriptor and a non-standard module-level descriptor. These non-standard descriptors conform to a specification that is *not* standard and contain elements for services extending the standard environment. All four descriptors (standard and non-standard, application and module level) are used at deployment time. The application is deployed using the combined configuration from all four. Crucially, both the initial standard application-level descriptor and the inserted non-standard application-level descriptor function as application deployment descriptors, providing configuration for the entire application.
28. The article of manufacture of claim 27 , wherein said second and fourth deployment descriptors are both web application deployment descriptors.
The program for application deployment, where first and third descriptors are application deployment descriptors, specifies the second and fourth descriptors (module-level) as web application deployment descriptors.
29. The article of manufacture of claim 28 wherein said second document type definition comprises an element for a reference to a resource external to said application, said application being a web application, said reference being a JNDI name.
The program for application deployment with web application descriptors (as above) includes, in the non-standard web application descriptor, an element referencing external resources via JNDI names.
30. The article of manufacture of claim 28 wherein said second document type definition comprises an element for a reference to an object in an environment of said web application, said reference being a JNDI name.
The program for application deployment with web application descriptors, includes, in the non-standard descriptor, an element referencing objects in the environment via JNDI names.
31. The article of manufacture of claim 28 wherein said second document type definition comprises an element to define a login module for said web application.
The program for application deployment concerning web applications, the non-standard web application descriptor defines a login module.
32. The article of manufacture of claim 28 wherein said second document type definition comprises an element to define a password changing setting for said web application.
The program for application deployment of web applications, the non-standard web application descriptor defines password change settings.
33. The article of manufacture of claim 25 , wherein said second document type definition further comprises an element for a named reference to an item of software outside said application and selected from the group consisting of: another application; a library; a service; and, interface.
The program for application deployment includes, in the non-standard descriptor, an element that references external software like another app, library, service or interface.
34. The article of manufacture of claim 25 , wherein said second document type definition comprises an element to identify a classpath to a resource outside said application that said application is designed to use.
The program for application deployment includes, in the non-standard descriptor, an element that specifies the classpath to an external resource.
35. The article of manufacture of claim 25 , wherein said second document type definition comprises an element to identify said application's provider.
The program for application deployment includes, in the non-standard descriptor, an element that identifies the app's provider.
36. The article of manufacture of claim 25 , wherein said second document type definition comprises an element to identify one or more modules of said application that are to be distributed to one or more containers that are not standard J2EE containers.
The program for application deployment includes, in the non-standard descriptor, an element that identifies application modules for non-standard J2EE containers.
37. The article of manufacture of claim 25 , wherein said second document type definition comprises an element to indicate whether or not a failover service is enabled, said failover service being said extension.
The program for application deployment includes, in the non-standard descriptor, an element indicating whether the failover service is enabled.
38. The article of manufacture of claim 25 , wherein said second document type definition comprises an element that indicates a start time for said application, said ability to specify said start time being said extension.
The program for application deployment includes, in the non-standard descriptor, an element indicating a start time for the application.
39. The article of manufacture of claim 25 , wherein said second document type definition comprises an element for a reference to an enterprise java bean, said reference being a JNDI name.
The program for application deployment includes, in the non-standard descriptor, an element that references an Enterprise Java Bean using JNDI.
40. The article of manufacture of claim 25 , wherein said second document type definition comprises an element to identify security roles that are available on a server upon which said application is to be deployed.
The program for application deployment includes, in the non-standard descriptor, an element that identifies available security roles on the server.
41. The article of manufacture of claim 25 , wherein said second document type definition comprises an element having information to construct an HTTP response.
The program for application deployment includes, in the non-standard descriptor, an element holding information to construct an HTTP response.
42. The article of manufacture of claim 25 , wherein said second document type definition comprises an element to invoke a fail alert service in which an alert message warning is sent to a client of said application to alert said client that a server on which said application is running will be shut down, said fail alert service being said extension.
The program for application deployment includes, in the non-standard descriptor, an element to invoke a fail alert service that warns clients of server shutdown.
43. The article of manufacture of claim 25 , wherein said second document type definition comprises an element to specify if user sessions will be tracked by a URL or by a cookie.
The program for application deployment includes, in the non-standard descriptor, an element specifying if user sessions are tracked via URL or cookies.
44. The article of manufacture of claim 25 , wherein said second document type definition comprises an element to specify a security policy domain for said application.
The program for application deployment includes, in the non-standard descriptor, an element to specify a security policy domain for the application.
45. The article of manufacture of claim 25 , wherein said second document type definition comprises elements to describe a cookie, said cookie being an application cookie or a session cookie.
The program for application deployment includes, in the non-standard descriptor, elements to describe application or session cookies.
46. The article of manufacture of claim 25 wherein said inserting of said deployment descriptors is performed by a deploy tool.
In the program for application deployment, the insertion of custom descriptors is performed by a deployment tool.
47. The article of manufacture of claim 25 wherein said inserting of said deployment descriptors is performed upon a server targeted for deployment of said application.
In the program for application deployment, the insertion of custom descriptors is performed on the target deployment server.
48. A computing system comprising instructions disposed on a computer readable medium, said instructions capable of being executed by said computing system to cause the computer system to perform operations comprising: in an application archive associated with said application, said application archive including a first deployment descriptor and a second deployment descriptor, said first deployment descriptor associated with an application-level of a hierarchy of deployment descriptors associated with said application and said second deployment descriptor associated with a module-level of said hierarchy, each of said first deployment descriptor and said second deployment descriptor conforming to a first document type definition that is defined by a standard specification, inserting a third deployment descriptor and a fourth deployment descriptor, each of said third and fourth deployment descriptors conforming to a second document type definition that is not defined by said standard specification, each of said third and fourth deployment descriptors having an element directed to a service that is an extension to said services offered by an environment described by said standard specification, said first and third deployment descriptors providing configuration information that pertains to said application as a whole, said second and fourth deployment descriptors providing configuration information that pertains to a module of said application, said third deployment descriptor associated with said application-level of said hierarchy, said fourth deployment descriptor associated with said module-level of said hierarchy, each of said first deployment descriptor, second deployment descriptor, third deployment descriptor, and fourth deployment descriptor to be used at deployment time; and deploying said application consistently with said configuration information provided in said first and third deployment descriptors and said configuration provided in said second and fourth deployment descriptors.
A computing system executes instructions to deploy an application. These instructions insert additional deployment descriptors into an application archive. This archive contains standard descriptors for the app and its modules, following a defined standard. The instructions add two more descriptors, not compliant with the standard, which configure extended services. The standard and custom application-level descriptors configure the whole application. The module-level descriptors configure specific modules. All four are used at deploy time for consistent configuration.
49. An apparatus comprising: means for, in an application archive associated with said application, said application archive including a first deployment descriptor and a second deployment descriptor, said first deployment descriptor associated with an application-level of a hierarchy of deployment descriptors associated with said application and said second deployment descriptor associated with a module-level of said hierarchy, each of said first deployment descriptor conforming to a first document type definition that is defined by a standard specification, inserting a third deployment descriptor and a fourth deployment descriptor, each of said third and fourth deployment descriptors conforming to a second document type definition that is not defined by said standard specification, each of said third and fourth deployment descriptors having an element directed to a service that is an extension to the services offered by an environment described by said standard specification, said first and third deployment descriptors providing configuration information that pertains to said application as a whole, said second and fourth deployment descriptors providing configuration information that pertains to a module of said application, said third deployment descriptor associated with said application-level of said hierarchy, said fourth deployment descriptor associated with said module-level of said hierarchy, each of said first deployment descriptor, second deployment descriptor, third deployment descriptor, and fourth deployment descriptor to be used at deployment time; and means for deploying said application consistently with said configuration information provided in said first and third deployment descriptors and said configuration provided in said second and fourth deployment descriptors.
An apparatus deploys applications by adding custom deployment descriptors. It has means to insert two non-standard deployment descriptors into an application archive, which already includes standard descriptors. These custom descriptors contain configuration elements to extend environment services beyond the standard specification. The descriptors include application-level (standard and custom) configuration and module-level (standard and custom) configuration. The apparatus then uses means to deploy the app, using both the standard and custom configurations.
50. A method comprising: for a first instance of an application that is targeted to an environment that includes additional services that complement a set of services specified by a standard specification: in an application archive associated with said first instance of said application, said application archive including a first deployment descriptor and a second deployment descriptor, said first deployment descriptor associated with an application-level of a hierarchy of deployment descriptors associated with said application and said second deployment descriptor associated with a module-level of said hierarchy, each of said first and second deployment descriptors conforming to a first document type definition that is defined by said standard specification, inserting a third deployment descriptor and a fourth deployment descriptor, each of said third and fourth deployment descriptors conforming to a second document type definition that is not defined by said standard specification, each of said third and fourth deployment descriptors having an element directed to a service that is an extension to said services offered by an environment described by said standard specification, said third deployment descriptor associated with said application-level of said hierarchy, said fourth deployment descriptor associated with said module-level of said hierarchy, each of said first deployment descriptor, second deployment descriptor, third deployment descriptor, and fourth deployment descriptor to be used at deployment time; recognizing an existence of said third and fourth deployment descriptors and deploying said first instance of said application consistently with information found in said third and fourth deployment descriptors; and, for a second instance of an application that is targeted to an environment that does not include said additional services that complement said set of services specified by said standard specification, in said application archive, not inserting said third and fourth deployment descriptors.
A method selectively deploys an application based on the target environment's capabilities. If the environment supports extended services, the method inserts two non-standard deployment descriptors with elements for configuring those extensions into the archive (which also has standard descriptors). If these are present, the application is deployed using the extended configurations. For environments lacking extended services, the non-standard descriptors *aren't* inserted, thus the application will deploy using only standard configurations. This allows deployment in environments with/without extended services, all from the same application archive.
Cooperative Patent Classification codes for this invention. Click any code to explore related patents in that topic.
June 8, 2004
April 18, 2017
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.