MODELING AND MANAGING HETEROGENEOUS APPLICATIONS

• US 20090113379A1
• Filed: 10/26/2007
• Published: 04/30/2009
• Est. Priority Date: 10/26/2007
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Swartz, Stephen T., Sedukhin, Igor, Eshner, Daniel
• Granted Patent: US 8,181,151 B2
• Time in Patent Office: Days
• US Class Current: 717/104
• CPC Class Codes: G06F 8/10 Requirements analysis; Specification techniques
• CPC Class Codes: G06F 8/35 model driven
• CPC Class Codes: Y10S 707/99948 Application of database or data structure, e.g. distributed, multimedia, or image

Abstract

The present invention extends to methods, systems, and computer program products for modeling and managing heterogeneous applications. Application intent can be described in a relatively straight forward manner that abstracts underlying implementation details. Thus, application developers can develop applications without necessarily having to know extensive details of an underlying implementation environment. In any event, an application can be executed in different implementation environments without requiring changes to the corresponding model.

Claims

1. At a computer system within a computing environment, the computing environment including a plurality of different technologies for implementing distributed applications, a method for implementing a composite distributed application, the method comprising:

an act of describing the components of a composite distributed application in a declarative model, including describing a plurality of different application parts of the composite distributed application;

an act of inserting one or more abstractions into the declarative model, each abstraction describing the intended behavior of a corresponding application part in an implementation independent manner, the abstractions extending the declarative model to make the declarative model executable;

an act of tagging each of the one or more abstractions with a label, each label including implementation specific details that indicate how the plurality of different technologies are to be used to implement the corresponding application part; and

an act of interpreting the declarative model to implement an executable instance of the composite distributed application, the executable instance of the composite distributed application implemented using the plurality of technologies in accordance with the implementation specific details included in the labels.

2. The method as recited in claim 1, further comprising:

an act of setting an implementation attribute on at least one inserted abstraction, the implementation attribute including implementation details expressly indicating how the abstraction is to be tagged to indicate an intended implementation.

3. The method as recited in claim 2, wherein the act of tagging each of the one or more abstractions with a label comprises an act of tagging the at least one inserted abstraction for implementation based on the implementation details in the implementation attribute.

4. The method as recited in claim 1, wherein the act of describing the components of a composite distributed application in a declarative model comprises an act of describing a process application part and a data application part of the composite distributed application.

5. The method as recited in claim 4, wherein the act of describing a process application part and a data application part of the composite distributed application comprises an act of describing a Web Services and Databases.

6. The method as recited in claim 1, wherein the act of describing the components of a composite distributed application in a declarative model comprises:

an act of describing endpoints connecting the plurality of different application parts to one another; and

an act of describing an external provider endpoint for communicating with the composite distributed application.

7. The method as recited in claim 1, wherein the act of tagging each of the one or more abstractions with a label comprises an act of inferring how an abstraction is to be tagged based on one or more of:

available system resources of different technologies, prior system settings, and default system values.

8. The method as recited in claim 1, wherein the act of interpreting the declarative model to implement an executable instance of the composite distributed application comprises an act of implementing different application parts of the composite distributed application in different host environments.

9. The method as recited in claim 1, wherein the computer system further includes one or more drivers, each driver configured to process abstractions for a specified combination of different technologies, the computer system further including one or more translators, each translator configured to process model elements representing objects within a specified technology from among the plurality of different technologies, and wherein the act of interpreting the declarative model to implement an executable instance of the composite distributed application comprises:

for each abstraction;

an act of identifying a driver that is configured to process a described application part corresponding to the combination of technologies indicated for the abstraction;

an act of forwarding the application part to the identified driver; and

an act of the identified driver parsing the application part to identify model elements and their relationship to one another;

for each identified model element;

an act of identifying a translator configured to translate model elements for the specified technology corresponding to the identified model element;

an act of sending the model element to the translator;

an act of receiving a sequence of actions that are to be performed within the specified technology to partially implement the composite distributed application, the sequence of actions being a subset of the total actions that are to be performed to fully implement the composite distributed application; and

an act of assembling the received sequence of actions for the model element into an execution plan, the received sequence of actions assembled into the execution plan in a designated order with respect to sequences of actions received for other model elements based on the model element'"'"'s relationship to other model elements in the received declarative model; and

an act of executing the execution plan to implement the composite distributed application, execution of the execution plan including executing the sequences of actions received for each model element in the designated order.

10. A computer program product for use at a computer system within a computing environment, the computing environment including a plurality of different technologies for implementing distributed applications, the computer program product for implement a method for implementing a composite distributed application, the computer program product comprising one or more physical storage media having stored thereon computer-executable instructions that, when executed at a processor, cause the computer system to perform the method including the following:

describe the components of a composite distributed application in a declarative model, including describing a plurality of different application parts of the composite distributed application;

insert one or more abstractions into the declarative model, each abstraction describing the intended behavior of a corresponding application part in an implementation independent manner, the abstractions extending the declarative model to make the declarative model executable;

tag each of the one or more abstractions with a label, each label including implementation specific details that indicate how the plurality of different technologies are to be used to implement the corresponding application part; and

interpret the declarative model to implement an executable instance of the composite distributed application, the executable instance of the composite distributed application implemented using the plurality of technologies in accordance with the implementation specific details included in the labels.

11. The computer program product as recited in claim 10, further comprising computer-executable instructions that, when executed, cause the computer system to set an implementation attribute on at least one inserted abstraction, the implementation attribute including implementation details expressly indicating how the abstraction is to be tagged to indicate an intended implementation.

12. The computer program product as recited in claim 11, wherein computer-executable instructions that, when executed, cause the computer system to tag each of the one or more abstractions with a label comprises computer-executable instructions that, when executed, cause the computer system to tag the at least one inserted abstraction for implementation based on the implementation details in the implementation attribute.

13. The computer program product as recited in claim 10, wherein computer-executable instructions that, when executed, cause the computer system to describe the components of a composite distributed application in a declarative model comprises comprise computer-executable instructions that, when executed, cause the computer system to describe a process application part and a data application part of the composite distributed application.

14. The computer program product recited in claim 10, wherein computer-executable instructions that, when executed, cause the computer system to describe the components of a composite distributed application in a declarative model comprise computer-executable instructions that, when executed, cause the computer system to:

describe endpoints connecting the plurality of different application parts to one another; and

describe an external provider endpoint for communicating with the composite distributed application.

15. The computer program product as recited in claim 10, wherein computer-executable instructions that, when executed, cause the computer system to tag each of the one or more abstractions with a label comprises computer-executable instructions that, when executed, cause the computer system to infer how an abstraction is to be tagged based on one or more of:

available system resources of different technologies, prior system settings, and default system values.

16. The computer program product as recited in claim 10, wherein computer-executable instructions that, when executed, cause the computer system to interpret the declarative model to implement an executable instance of the composite distributed application comprises computer-executable instructions that, when executed, cause the computer system to implement different application parts of the composite distributed application in different host environments.

17. At a computer system, a method for describing the intended executable behavior of a composite distributed application in an implementation-independent manner, the method comprising:

an act of describing a composite distributed application in a declarative model, the declarative model having a plurality of model elements, each model element representing a portion of the intended executable behavior of the composite distributed application, description of the composite distributed application including at least;

an act of describing a first application part of the composite distributed application, the first application part being a first specified type of application part, including;

an act of declaring a first abstraction for the first application part, the first abstraction describing the intended execution behavior of the first application part; and

an act of describing a second part of the composite distributed application, the second part being a second different specified type of application part, including;

an act of declaring a second abstraction for the second application part, the second abstraction describing the intended execution behavior of the second application part.

18. The method as recited in claim 17, wherein the act of describing a composite distributed application in a declarative model comprises an act of describing a composite distributed application, wherein the first application part is process and the second application part is data.

19. The method as recited in claim 17, wherein the act of describing a first application part of the composite distributed application comprises an act of setting a first implementation attribute on the first abstraction to expressly indicate the technologies that are to be used to implement the first application part.

20. The method as recited in claim 17, further comprising:

an act of describing an external provider endpoint for the composite distributed application, the external provider endpoint configured to;

receive requests from components external to the composite distributed application; and

delegate the requests to the first part provider endpoint for processing.

21. The method as recited in claim 17, wherein the act of describing a first application part of the composite distributed application further includes:

an act of declaring a first application part provider endpoint that provides information processed at the first application part to external components;

an act of declaring a first part consumer endpoint that consumes information from external components; and

wherein an act of describing a second part of the composite distributed application further includes;

an act of declaring a second application part provider endpoint that provides information to external components, the second application part provider endpoint connectable to consumer endpoints including the first application part consumer endpoint; and

an act of declaring a second application part consumer endpoint that consumes information from external components, the second application part consumer endpoint connectable to provider endpoints.