Providing dynamic latency in an integration flow

• US 10,164,854 B2
• Filed: 11/20/2015
• Issued: 12/25/2018
• Est. Priority Date: 11/20/2015
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Hosie, John, Ross, Martin A., Stirling, Craig H., Storey, Dominic J.
• Primary Examiner(s): Lazaro, David R
• Assistant Examiner(s): Henry, Mariegeorges A
• Application Number:
  US14/947,307
• Publication Number:
  US 20170149641A1
• Time in Patent Office: 1,131 Days
• Field of Search: 709224, 709223
• CPC Class Codes: G06F 9/5033 considering data affinity
• CPC Class Codes: H04L 41/5009 Determining service level performance parameters or violations of service level contracts, e.g. violations of agreed response time or mean time between failures [MTBF]
• CPC Class Codes: H04L 43/0852 Delays

Abstract

Providing dynamic latency in an integration flow. An integration flow connecting multiple integration nodes and including at least one repeat node is managed, wherein a repeat node repeats by sending a message, a variation of a message, or an element of a message to multiple paths or to a single path multiple times. A repeat node is registered with a workload manager component for monitoring. Data relating to the effect on performance by the integration flow including the monitored repeat node is collected. Required latencies or variations of latencies between firing of repeats of the repeat node based on the collected data are determined. The latencies or variations of latencies between firing of the repeats of the repeat node are instructed to influence dynamically a flow of elements through the repeat node.

Claims

1. A computer-implemented method of providing dynamic latency in an integration flow, comprising:

managing an integration flow connecting multiple integration nodes and including at least one repeat node, wherein a repeat node repeats by sending at least an element of a message to at least one path multiple times;

registering one repeat node of the at least one repeat node for monitoring with a workload manager component;

collecting data relating to an effect on performance by the integration flow including the one repeat node;

determining at least one latency between firing of repeats of the one repeat node based on the collected data, wherein the at least one latency comprises a first time;

determining a priority of a first repeat of the one repeat node based on a priority of an incoming message;

weighting the at least one latency for the repeats for the incoming message based on the priority, wherein weighting the latency based on the priority further comprises;

multiplying a first ratio by a delay time to generate a weighted latency having a second time, wherein the first ratio is based on a numerator comprising the priority of the incoming message and a denominator comprising a lowest priority for incoming messages; and

instructing the weighted latency between firing of the repeats of the one repeat node to influence dynamically a flow of elements through the one repeat node, and wherein the instructed weighted latency causes the repeat node to delay, by the second time, respective sendings of the at least an element of the incoming message to the at least one path.

2. The computer-implemented method as claimed in claim 1, wherein the determining at least one latency is based on an impact of repeats of the one repeat node on applications as determined by the collected data.

3. The computer-implemented method as claimed in claim 1, wherein the determining at least one latency is based on an impact of repeats of the repeat node on components downstream of the integration flow as determined by the collected data.

4. The computer-implemented method as claimed in claim 1, wherein the collecting data relating to the effect on performance collects data from system resources, including applications or resources in the integration flow and in other integration flows, and applications or resources in systems effected by the one repeat node;

service level agreement components; and

application metrics.

5. The computer-implemented method as claimed in claim 1, wherein the workload manager component is an external component and the instructing provides additional code to the repeat node.

6. The computer-implemented method as claimed in claim 1, wherein the collecting data and the determining latencies between firing of repeats of the repeat node based on the collected data, includes:

determining whether one or more applications in a system or downstream of the system is reaching a predefined threshold of performance; and

instructing latencies in repeats of the repeat node for one or more applications.

7. The computer-implemented method as claimed in claim 6, further including learning correlations between instructed latencies in a particular repeat node and the effect on performance of applications.

8. The computer-implemented method as claimed in claim 6, wherein the applications are real time traffic serving applications and thresholds are set in service level agreements.

9. The computer-implemented method as claimed in claim 1, wherein the integration flow is an aggregation pattern and the one repeat node is an aggregation node with branching or iterating repeats.

10. A computer system for providing dynamic latency in an integration flow, comprising:

a memory; and

a processor in communications with the memory, wherein the computer system is configured to perform a method, said method comprising;

managing an integration flow connecting multiple integration nodes and including at least one repeat node, wherein a repeat node repeats by sending at least an element of a message to at least one path multiple times;

registering one repeat node of the at least one repeat node for monitoring with a workload manager component;

collecting data relating to an effect on performance by integration flow including the one repeat node;

determining at least one latency between firing of repeats of the one repeat node based on the collected data, wherein the at least one latency comprises a first time;

determining a priority of a first repeat of the one repeat node based on a priority of an incoming message;

weighting the at least one latency for the repeats for the incoming message based on the priority, wherein weighting the latency based on the priority further comprises;

multiplying a first ratio by a delay time to generate a weighted latency having a second time, wherein the first ratio is based on a numerator comprising the priority of the incoming message and a denominator comprising a lowest priority for incoming messages; and

instructing the weighted latency between firing of the repeats of the one repeat node to influence dynamically a flow of elements through the one repeat node, and wherein the instructed weighted latency causes the repeat node to delay, by the second time, respective sendings of the at least an element of the incoming message to the at least one path.

11. The computer system as claimed in claim 10, wherein the determining at least one latency is based on an impact of repeats of the one repeat node on applications as determined by the collected data.

12. The computer system as claimed in claim 10, wherein the collecting data and the determining latencies between firing of repeats of the repeat node based on the collected data, includes:

determining whether one or more applications in a system or downstream of the system is reaching a predefined threshold of performance; and

instructing latencies in repeats of the repeat node for one or more applications.

13. The computer system as claimed in claim 10, wherein the integration flow is an aggregation pattern and the one repeat node is an aggregation node with branching or iterating repeats.

14. A computer program product for providing dynamic latency in an integration flow, comprising:

a computer readable storage medium readable by a processing circuit and storing instructions for execution by the processing circuit for performing a method comprising;

managing an integration flow connecting multiple integration nodes and including at least one repeat node, wherein a repeat node repeats by sending at least an element of a message to at least one path multiple times;

registering one repeat node of the at least one repeat node for monitoring with a workload manager component;

collecting data relating to an effect on performance by the integration flow including the one repeat node;

determining at least one latency between firing of repeats of the one repeat node based on the collected data, wherein the at least one latency comprises at least a first time;

determining a priority of a first repeat of the one repeat node based on a priority of an incoming message;

weighting the at least one latency for the repeats for the incoming message based on the priority, wherein weighting the latency based on the priority further comprises;

multiplying a first ratio by a delay time to generate a weighted latency having a second time, wherein the first ratio is based on a numerator comprising the priority of the incoming message and a denominator comprising a lowest priority for incoming messages; and

instructing the weighted latency between firing of the repeats of the one repeat node to influence dynamically a flow of elements through the one repeat node, and wherein the instructed weighted latency causes the repeat node to delay, by the second time, respective sendings of the at least an element of the incoming message to the at least one path.

15. The computer program product as claimed in claim 14, wherein the determining at least one latency is based on an impact of repeats of the one repeat node on applications as determined by the collected data.

16. The computer program product as claimed in claim 14, wherein the collecting data and the determining latencies between firing of repeats of the repeat node based on the collected data, includes:

determining whether one or more applications in a system or downstream of the system is reaching a predefined threshold of performance; and

instructing latencies in repeats of the repeat node for one or more applications.