Allocating optimized resources for components based on derived component profiles

• US 9,323,510 B2
• Filed: 04/13/2012
• Issued: 04/26/2016
• Est. Priority Date: 04/13/2012
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP SE
• Inventors: Koutyrine, Oleg, Hoursanov, Andrey
• Primary Examiner(s): Bullock, Jr., Lewis A
• Assistant Examiner(s): Gooray, Mark
• Application Number:
  US13/446,821
• Publication Number:
  US 20130275990A1
• Time in Patent Office: 1,474 Days
• Field of Search: None
• US Class Current: 1/1
• 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, the first component container profile including a set of attributes, wherein the first component container is a runtime system;

translating at least a portion of the first component container profile to a second component container profile associated with the second component container, wherein translating includes, prior to initializing a component contained in the second component container;

identifying, from the first component container profile, a first set of attributes relevant to the second component container, wherein identifying the first set of attributes relevant to the second component container includes parsing the set of attributes in the first component container profile to identify a usage scenario of the first component container, wherein the usage scenario is either a productive system or a development system;

filtering out, from the first component container profile, a second set of attributes irrelevant to the second component container;

translating the first set of attributes to a third set of attributes based on a translation rule set, the third set of attributes interpretable by the second component container, wherein translating the first set of attributes to the third set of attributes is based on a translation rule set corresponding to the identified usage scenario; and

compiling the translated third set of attributes into the second component container profile for use by the second component container; and

initializing the component contained in the second component container based, at least in part, on the compiled second component container profile, and wherein initializing the component includes allocating more system resources to the component when the usage scenario is the productive system than when the usage scenario is the development system.

2. The method of claim 1, set of attributes in the first component container profile comprises at least one of the following:

a property of the first component container, 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 component container.

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

4. The method of claim 3, 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.

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

6. 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.

7. 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.

8. 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.

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

10. 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.

11. 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, the first component container profile including a set of attributes, wherein the first component container is a runtime system;

translate at least a portion of the first component container profile to a second component container profile associated with the second component container, wherein translating includes, prior to initializing a component contained in the second component container;

identifying, from the first component container profile, a first set of attributes relevant to the second component container, wherein identifying the first set of attributes relevant to the second component container includes parsing the set of attributes in the first component container profile to identify a usage scenario of the first component container, wherein the usage scenario is either a productive system or a development system;

filtering out, from the first component container profile, a second set of attributes irrelevant to the second component container;

translating the first set of attributes to a third set of attributes based on a translation rule set, the third set of attributes interpretable by the second component container, wherein translating the first set of attributes to the third set of attributes is based on a translation rule set corresponding to the identified usage scenario; and

compiling the translated third set of attributes into the second component container profile for use by the second component container; and

initialize the component contained in the second component container based, at least in part, on the compiled second component container profile, and wherein initializing the component includes allocating more system resources to the component when the usage scenario is the productive system than when the usage scenario is the development system.

12. The product of claim 11, wherein the set of attributes in the first component container profile comprises at least one of the following:

a property of the first component container, 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 component container.

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

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

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

16. 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, the first component container profile including a set of attributes, wherein the first component container is a runtime system;

translating at least a portion of the first component container profile to a second component container profile associated with the second component container, wherein translating includes, prior to initializing a component contained in the second component container;

identifying, from the first component container profile, a first set of attributes relevant to the second component container, wherein identifying the first set of attributes relevant to the second component container includes parsing the set of attributes in the first component container profile to identify a usage scenario of the first component container, wherein the usage scenario is either a productive system or a development system;

filtering out, from the first component container profile, a second set of attributes irrelevant to the second component container;

translating the first set of attributes to a third set of attributes based on a translation rule set, the third set of attributes interpretable by the second component container, wherein translating the first set of attributes to the third set of attributes is based on a translation rule set corresponding to the identified usage scenario; and

compiling the translated third set of attributes into the second component container profile for use by the second component container; and

initializing the component contained in the second component container based, at least in part, on the compiled second component container profile, and wherein initializing the component includes allocating more system resources to the component when the usage scenario is the productive system than when the usage scenario is the development system.