Adaptive enterprise service bus (ESB) runtime system and method

• US 8,570,905 B2
• Filed: 09/26/2008
• Issued: 10/29/2013
• Est. Priority Date: 09/26/2008
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Hulse, Brian, Jackson, Callum P.
• Primary Examiner(s): Banks Harold, Marsha D
• Assistant Examiner(s): WYLLIE, CHRISTOPHER T
• Application Number:
  US12/238,472
• Publication Number:
  US 20100080148A1
• Time in Patent Office: 1,859 Days
• Field of Search: 370/255
• US Class Current: 370/257
• CPC Class Codes: G06F 11/34 Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
• CPC Class Codes: G06F 9/54 Interprogram communication
• CPC Class Codes: H04L 41/0826 for reduction of network costs H04L41/0833 takes precedence
• CPC Class Codes: H04L 45/70 Routing based on monitoring results

Abstract

Disclosed are embodiments of an adaptive enterprise service bus (ESB) runtime system and an associated method, which build, at a restart, only the most advantageous path configuration between composable units (e.g., between applications and/or between primitives within a single application). Specifically, during the execution of instantiations of modeled paths and branches thereof, metrics (e.g., the number of times each flow and each branch are activated, the CPU usage associated with building each flow and each branch, etc.) are collected. Then, at a restart of the runtime system, a cost-benefit analysis is performed on the collected metrics and, based on the results of this cost-benefit analysis, only selected ones of the paths and the branches thereof are built (e.g., paths and branches for which operational usefulness outweighs building costs). Other paths and branches are built only as required, during running of the runtime system.

Claims

1. An adaptive enterprise service bus (ESB) runtime system comprising:

a processor operable to receive a model for an enterprise system bus (ESB), said model comprising a plurality of paths between composable units with at least one of said paths comprising a plurality of branches and said processor being further operable to build executable instantiations of said paths and said branches;

a server operable to execute, during each running of said runtime system, said executable instantiations of said paths and said branches built by said processor so as to allow communication between said composable units;

a monitor collecting, during executing of said executable instantiations by said server, metrics associated with said paths and said branches; and

,

an analyzer receiving said metrics and performing a cost-benefit analysis based on said metrics,

said processor further building, at a restart of said runtime system and based on results of said cost-benefit analysis, executable instantiations of only selected ones of said paths and said branches.

2. The system of claim 1, said processor, for an initial running of said runtime system, building executable instantiations of only required ones of said paths and said branches on-demand.

3. The system of claim 1, said processor, for an initial start-up of said runtime system, building executable instantiations of all of said paths and said branches.

4. The system of claim 1, said processor, at an initial start-up of said runtime system, selecting to build and building executable instantiations of only a portion of said paths and said branches, based on pre-loaded historical data, and

said processor, after said initial start-up and during an initial running of said runtime system, further building executable instantiations of any additional portions of said paths and said branches, as required, on demand.

5. The system of claim 1, said processor further receiving said model from an integration developer.

6. The system of claim 1, said metrics comprising:

a number of times each of said paths and each of said branches is activated, during each running of said runtime system; and

at least one of an amount of computer processing unit usage associated with building each of said paths and each of said branches, an amount of time associated with building each of said paths and each of said branches and an actual cost associated with building each of said paths and each of said branches.

7. The system of claim 1, said processor ensuring that all executable instantiations of said paths and said branches built during a given running of said runtime system will remain built at least until said runtime system is restarted.

8. An adaptive enterprise service bus (ESB) runtime method, said method comprising:

receiving, by a computer system, a model for an enterprise system bus (ESB), said model comprising a plurality of paths between composable units, at least one of said paths comprising a plurality of branches;

building, by said computer system, executable instantiations of at least some of said paths and said branches;

executing, by said computer system and during each running of a runtime system, at least some of said executable instantiations so as to allow communication between said composable units;

during said executing of said at least some of said executable instantiations, collecting, by monitors in communication with said computer system, metrics associated with said paths and said branches; and

performing, by said computer system, a cost-benefit analysis based on said metrics,

said building further comprises building, at a restart of said runtime system and based on results of cost-benefit analysis, executable instantiations of only selected ones of said paths and said branches.

9. The method of claim 8, said building further comprising, after said receiving of said model and during an initial running of said runtime system, building executable instantiations of only required ones of said paths and said branches on demand.

10. The method of claim 8, said building further comprising, after said receiving of said model and at an initial start-up of said runtime system, building executable instantiations of all of said paths and said branches.

11. The method of claim 8, said building further comprising:

after said receiving of said model, at an initial start-up of said runtime system, and based on pre-loaded historical data, selecting and building executable instantiations of only a portion of said paths and said branches; and

during an initial running of said runtime system, further building executable instantiations of any additional portions of said paths and said branches as required, on demand.

12. The method of claim 8, said receiving of said model comprising receiving said model from an integration developer.

13. The method of claim 8, said collecting comprising:

determining a number of times each of said paths and each of said branches is activated, during each running of said runtime system; and

determining at least one of an amount of computer processing unit usage associated with building each of said paths and each of said branches, an amount of time associated with building each of said paths and each of said branches and an actual cost associated with building each of said paths and each of said branches.

14. The method of claim 8, further comprising ensuring that all executable instantiations of said paths and said branches built during a given running of said runtime system will remain built at least until said runtime system is restarted.

15. A computer program product comprising a non-transitory storage medium readable by a computer and storing computer usable program code executable by said computer to perform an adaptive enterprise service bus (ESB) runtime method, said adaptive enterprise service bus (ESB) runtime method comprising:

receiving a model for an enterprise system bus (ESB), said model comprising a plurality of paths between composable units, at least one of said paths comprising a plurality of branches;

building, by said computer, executable instantiations of at least some of said paths and said branches;

executing, during each running of a runtime system, at least some of said executable instantiations so as to allow communication between said composable units;

during said executing of said at least some of said executable instantiations, collecting, by monitors in communication with said computer, metrics associated with said paths and said branches; and

performing, by said computer, a cost-benefit analysis based on said metrics,

said building further comprising building, at a restart of said runtime system and based on results of a cost-benefit analysis, executable instantiations of only selected ones of said paths and said branches.

16. The computer program product of claim 15, said building further comprising, after said receiving of said model and during an initial running of said runtime system, building executable instantiations of only required ones of said paths and said branches, on demand.

17. The computer program product of claim 15, said building further comprising, after said receiving of said model and during an initial start-up of said runtime system, building executable instantiations of all of said paths and said branches.

18. The computer program product of claim 15, said building further comprising:

after said receiving of said model, at an initial start-up of said runtime system, and based on pre-loaded historical data, selecting and building executable instantiations of only a portion of said paths and said branches; and

during an initial running of said runtime system, building executable instantiations of any additional portions of said paths and said branches as required, on demand.

19. The computer program product of claim 15, said receiving of said model comprising receiving said model from an integration developer.

20. The computer program product of claim 15, said collecting comprising:

determining a number of times each of said paths and each of said branches is activated, during each running of said runtime system; and

determining at least one of an amount of computer processing unit usage associated with building each of said paths and each of said branches, an amount of time associated with building each of said paths and each of said branches and an actual cost associated with building each of said paths and each of said branches.