MAPPING APPLICATION DEPENDENCIES AT RUNTIME

• US 20150007197A1
• Filed: 04/27/2012
• Published: 01/01/2015
• Est. Priority Date: 04/27/2012
• Status: Abandoned Application

• Current Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Original Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Inventors: Tripp, Travis S., Vana, Jan, Whisenhunt, Heather L., Colnick, Erik, Spence, Kurt E., Fiedler, Peir, Wilson, Kevin L.
• Application Number:
  US14/375,039
• Publication Number:
  US 20150007197A1
• Time in Patent Office: Days
• US Class Current: 718/106
• CPC Class Codes: G06F 9/445 Program loading or initiating bootstrapping G06F9/4401; security arrangements for program loading or initiating G06F21/57
• CPC Class Codes: G06F 9/46 Multiprogramming arrangements
• CPC Class Codes: G06F 9/5072 Grid computing

Abstract

Systems, methods, and machine-readable and executable instructions are provided for mapping application dependencies. Mapping application dependencies can include defining an application model with a number of application dependencies that enables an application to run and defining a platform model that defines a number of capabilities that are provided by a server. Mapping application dependencies can also include creating a topology model that maps the application model to the platform model at runtime by mapping the number of application dependencies to the number of capabilities while the application remains independent from the server.

Claims

1. A method for mapping application dependencies at runtime comprising:

defining an application model with a number of application dependencies that enables an application to run;

defining a platform model that defines a number of capabilities that are provided by a server; and

creating a topology model that maps the application model to the platform model at runtime by mapping the number of application dependencies to the number of capabilities while the application remains independent from the server.

2. The method of claim 1, wherein creating the topology model that maps the application model to the platform model at runtime includes mapping the application model to a platform model when the application initiates execution.

3. The method of claim 1, wherein the application remains independent from server includes the topology model resolving the application dependencies without requiring the application to communicate with the server.

4. The method of claim 3, wherein topology model resolves the application dependencies by providing a number of values to a number of reference variables that are used by the application to reference the number of capabilities.

5. A non-transitory computer-readable medium storing instructions for mapping application dependencies at runtime executable by a computer to cause the computer to:

define an application model with a number of application dependencies that enable a number of applications to run;

define a platform model with a number of tiers that define a number of capabilities wherein a tier includes a group of servers; and

create a topology model that maps the application model to the platform model at runtime by mapping the number of application dependencies to the number of capabilities while the application model remains independent from the platform model.

6. The medium of claim 5, wherein the number of application dependencies that enable the number of applications to run include application dependencies within the number of applications and application dependencies between the number of applications and a number of servers that define the number of tiers.

7. The medium of claim 5, wherein the topology model that maps the application model to a platform model at runtime resolves the application dependencies using a deployment stack.

8. The medium of claim 7, wherein the deployment stack includes an ordering of the application dependencies wherein the ordering of the application dependencies defines an order in which the number of application dependencies are resolved.

9. The medium of claim 5, wherein the topology model includes a mapping between the number of application dependencies and the number of tiers.

10. The medium of claim 5, wherein the tier that includes the group of servers include a group of servers that have the same operating system (OS) and the same middleware.

11. An system that maps application dependencies at runtime, comprising:

define an application model with a number of requested parameters that enable a number of applications to run;

define a platform model that includes a number of tiers that include a number of server parameters wherein a tier includes a group of servers that provide the same operating system (OS) and the same middleware; and

create a topology model that maps the application model to the platform model at runtime by mapping the number of requested parameters to the number of server parameters through a number of tags while the application model remains independent from the platform model.

12. The system of claim 11, wherein the number of applications define a number of requested parameters by placing a number of dependencies on a platform that supports the platform model through a number of tags.

13. The system of claim 12, wherein the number of tags create a contract between the number of applications and a platform wherein the contract guarantees the number of applications that the number of server parameters that correspond to the requested parameters will be available at deployment.

14. The system of claim, 12 wherein the number of tags allows the number of applications to leverage a number platform specific properties that correspond to the platform through a number of reference variables.

15. The system of claim 11, wherein the reference variables are resolved at run time.