ALLOCATING OPTIMIZED RESOURCES FOR COMPONENTS BASED ON DERIVED COMPONENT PROFILES

• US 20130275990A1
• Filed: 04/13/2012
• Published: 10/17/2013
• Est. Priority Date: 04/13/2012
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: Andrey Hoursanov
• Inventors: Koutyrine, Oleg, Hoursanov, Andrey
• Granted Patent: US 9,323,510 B2
• Time in Patent Office: Days
• US Class Current: 718/104
• CPC Class Codes: G06F 2209/501 Performance criteria
• CPC Class Codes: G06F 8/40 Transformation of program code
• CPC Class Codes: G06F 8/41 Compilation
• CPC Class Codes: G06F 8/433 Dependency analysis; Data or control flow analysis
• CPC Class Codes: G06F 8/51 Source to source
• CPC Class Codes: G06F 9/44505 Configuring for program initiating, e.g. using registry, configuration files
• CPC Class Codes: G06F 9/50 Allocation of resources, e.g. of the central processing unit [CPU]

Abstract

Systems, methods and techniques relating to publishing mobile applications are described. A described technique includes identifying, at a second component container contained in a first component container, a first component container profile associated with the first component container, translating at least a portion of the first component container profile to a second component container profile associated with the second component container, and initializing the second component container based, at least in part, on the second component container profile.

Claims

1. A method performed by a component container in a runtime environment, comprising:

identifying, at a second component container contained in a first component container, a first component container profile associated with the first component container;

translating at least a portion of the first component container profile to a second component container profile associated with the second component container; and

initializing a component contained in the second component container based, at least in part, on the second component container profile.

2. The method of claim 1, wherein the first component container profile includes one or more first component container profile attributes, and wherein the one or more first component container profile attributes include at least one of the following:

a property of the first component container or a usage scenario description of the first component container or a property to be consumed by at least one of components directly or indirectly contained in the first container.

3. The method of claim 2, wherein the first component container is a runtime system, and the runtime system is associated with a usage scenario of either a productive system or a development system, wherein identifying the first component container profile includes identifying the usage scenario, and wherein initializing the component includes allocating more system resources to the component when the runtime system is the productive system than when the runtime system is the development system.

4. The method of claim 2, wherein translating the first component container profile to the second component container profile includes:

parsing the one or more first component container profile attributes for at least one attribute associated with the second component container;

translating the at least one first component container profile attribute associated with the second component container to at least one second component container profile attribute interpretable by the second component container; and

compiling the at least one translated second component container profile attribute into the second component container profile for use by the second component container.

5. The method of claim 4, wherein translating the first component container profile to the second component container profile further includes mapping the at least one second component container profile attribute from a first value to a second value based, at least in part, on a modification to the first component container.

6. The method of claim 5, wherein the modification to the first component container includes at least one upgrade of at least a portion of the first component container, an update of at least a portion of the first component container, or a modification to the second component container included in the first component container.

7. The method of claim 1, wherein initializing the component is further based on one or more default attributes associated with the second component container.

8. The method of claim 1, wherein the second component container profile includes information descriptive of at least one of behavioral aspects for initializing the second component container, and wherein the behavioral aspects include at least one of a component initialization strategy, a frequency of backup of the second component container, a logging status of the second component container, or a cache size for an execution of the second component container.

9. The method of claim 1, wherein initializing the component contained in the second component container further includes allocating system resources to the component contained in the second component container.

10. The method of claim 1, wherein initializing the component contained in the second component container further includes providing access to the second component container profile to the component contained in the second component container.

11. The method of claim 1, wherein the second component container is a component nested within the first component container.

12. The method of claim 1, further comprising:

identifying, at a third component container nested within the second component container, a second component container profile associated with the second component container;

translating at least a portion of at least one of the second component container profile or the first component container profile to a third component container profile associated with the third component container; and

initializing a second component associated with the third container based, at least in part, on the third component container profile.

13. A computer program product comprising computer-readable instructions embodied on tangible, non-transient media, the computer program product operable when executed to:

identify, at a second component container contained in a first component container, a first component container profile associated with the first component container;

translate at least a portion of the first component container profile to a second component container profile associated with the second component container; and

initialize a component contained in the second component container based, at least in part, on the second component container profile.

14. The product of claim 13, wherein the first component container profile includes one or more first component container profile attributes, and wherein the one or more first component container profile attributes include at least one of the following:

a property of the first component container or a usage scenario description of the first component container or a property to be consumed by at least one of components directly or indirectly contained in the first container.

15. The product of claim 14, wherein the first component container is a runtime system, and the runtime system is associated with a usage scenario of either a productive system or a development system, wherein identifying the first component container profile includes identifying the usage scenario, and wherein initializing the component includes allocating more system resources to the component when the runtime system is the productive system than when the runtime system is the development system.

16. The product of claim 14, wherein translating the first component container profile to the second component container profile includes:

parsing the one or more first component container profile attributes for at least one attribute associated with the second component container;

translating the at least one first component container profile attribute associated with the second component container to at least one second component container profile attribute interpretable by the second component container; and

compiling the at least one translated second component container profile attribute into the second component container profile for use by the second component container.

17. The product of claim 16, wherein translating the first component container profile to the second component container profile further includes mapping the at least one second component container profile attribute from a first value to a second value based, at least in part, on a modification to the first component container.

18. The product of claim 13, wherein initializing the component is further based on one or more default attributes associated with the second component container.

19. The product of claim 13, wherein the second component container is a component nested within the first component container.

20. A system comprising:

one or more computers; and

a computer-readable medium coupled to the one or more computers having instructions stored thereon which, when executed by the one or more computers, cause the one or more computers to perform operations comprising;

identifying, at a second component container contained in a first component container, a first component container profile associated with the first component container;

translating at least a portion of the first component container profile to a second component container profile associated with the second component container; and

initializing a component contained in the second component container based, at least in part, on the second component container profile.