Method and monitoring system for the rule-based monitoring of a service-oriented architecture

• US 8,271,407 B2
• Filed: 10/06/2009
• Issued: 09/18/2012
• Est. Priority Date: 10/06/2008
• Status: Active Grant

• Current Assignee: Software AG
• Original Assignee: Software AG
• Inventors: Ristow, Gerald, Voegele, Joachim
• Primary Examiner(s): Rivas, Omar Fernandez
• Assistant Examiner(s): COUGHLAN, PETER D
• Application Number:
  US12/588,174
• Publication Number:
  US 20100088256A1
• Time in Patent Office: 1,078 Days
• Field of Search: None
• US Class Current: 706/12
• CPC Class Codes: G06N 5/025 Extracting rules from data

Abstract

The present invention concerns a method for the rule-based monitoring of a component (C1) added to a service-oriented architecture (SOA), the SOA comprising a plurality of components (C2, . . . , Cn) being monitored by a plurality of monitoring components (M2, . . . , Mn), the method comprising the following steps:

• • a. selecting a component (C2) from the plurality of components (C2, . . . , Cn) of the SOA which is similar to the added component (C1) based on a similarity-metric;
  • b. selecting at least one rule (R2) from the monitoring component (M2) of the selected component (C2), wherein the at least one rule (R2) has already been validated during the operation of the SOA; and
  • c. adding the at least one rule (R2) to a new monitoring component (M1) of the added component (C1).

Claims

1. A method for the rule-based monitoring of a component (C1) added to a service-oriented architecture (SOA), the SOA comprising a plurality of components (C2, . . . , Cn) being monitored by a plurality of monitoring components (M2, . . . , Mn), the method comprising:

a. selecting a component (C2) from the plurality of components (C2, . . . , Cn) of the SOA which is similar to the added component (C1) based on a similarity-metric;

b. selecting at least one rule (R2) from the monitoring component (M2) of the selected component (C2), wherein the at least one rule (R2) has already been validated during the operation of the SOA;

c. adding the at least one rule (R2) to a new monitoring component (M1) of the added component (C1); and

d. providing the new monitoring component (M1) and the at least one added rule (R2) to a learning-phase to determine at least one parameter of the at least one rule (R2).

2. The method of claim 1, wherein the similarity-metric calculates a similarity-value indicating the similarity of the added component (C1) with the plurality of components (C2, . . . , Cn) of the SOA and wherein the component (C2) with the highest similarity-value is selected.

3. The method of claim 2, wherein the component (C2) is only selected in a if the similarity-value is greater or equal to a pre-defined value.

4. The method of claim 2, wherein the components (C1, C2, . . . , Cn) are services and wherein the similarity-value is calculated based on any of the group of information comprising the number and/or the names of operations provided by the services, their input parameter types and/or their output parameter types.

5. The method of claim 2, wherein the components (C1, C2, . . . , Cn) are application servers and wherein the similarity-value is calculated based on any of the group of information comprising their product types, product versions, used software, and/or used hardware.

6. The method of claim 2, wherein the components (C1, C2, . . . , Cn) are computer hardware and wherein the similarity-value is calculated based on any of the group of information comprising their operating systems, operating system versions and/or hardware configurations.

7. The method of claim 2, wherein the selected monitoring component (M2) has undergone a learning-phase to obtain the at least one rule (R2).

8. The method of claim 1, wherein the similarity-metric categorizes the components (C1, C2, . . . , Cn) into groups such as service, application server and/or computer hardware.

9. The method of claim 1, wherein the selected monitoring component (M2) has undergone a testing-phase to validate the at least one rule (R2) during the operation of the SOA.

10. The method of claim 1, further comprising providing the new monitoring component (M1) and the at least one added rule (R2) to a testing-phase to validate the at least one rule (R2) during the operation of the SOA.

11. A monitoring system for the rule-based monitoring of a component (C1) added to a service-oriented architecture (SOA), the SOA comprising a plurality of components (C2, . . . , Cn) being monitored by a plurality of monitoring components (M2, . . . , Mn), the monitoring system comprising:

at least one processor in communication with the plurality of monitoring components, the at least one processor being configured to execute instructions to at least;

a. select a component (C2) from the plurality of components (C2, . . . Cn) of the SOA which is similar to the added component (C1) based on a similarity-metric;

b. select at least one rule (R2) from the monitoring component (M2) of the selected component (C2), wherein the at least one rule (R2) has already been validated during the operation of the SOA;

c. add the at least one rule (R2) to a new monitoring component (M1) of the added component (C1); and

d. provide the new monitoring component (M1) and the at least one added rule (R2) to a learning-phase to determine at least one parameter of the at least one rule (R2).

12. The system of claim 11, wherein the similarity-metric calculates a similarity-value indicating the similarity of the added component (C1) with the plurality of components (C2, . . . , Cn) of the SOA and wherein the component (C2) with the highest similarity-value is selected.

13. The system of claim 12, wherein the component (C2) is only selected in (a) if the similarity-value is greater or equal to a pre-defined value.

14. The system of claim 12, wherein the components (C1, C2, . . . , Cn) include computer hardware and wherein the similarity-value is calculated based on any of the group of information comprising their operating systems, operating system versions and/or hardware configurations.

15. The system of claim 12, wherein the selected monitoring component (M2) has undergone a learning-phase to obtain the at least one rule (R2) and/or a testing-phase to validate the at least one rule (R2) during the operation of the SOA.

16. The system of claim 11, wherein the similarity-metric categorizes the components (C1, C2, . . . , Cn) into groups such as service, application server and/or computer hardware.

17. The system of claim 11, wherein the components (C1, C2, . . . , Cn) include services and wherein the similarity-value is calculated based on any of the group of information comprising the number and/or the names of operations provided by the services, their input parameter types and/or their output parameter types.

18. The system of claim 11, wherein the components (C1, C2, . . . , Cn) include application servers and wherein the similarity-value is calculated based on any of the group of information comprising their product types, product versions, used software, and/or used hardware.

19. The system of claim 11, wherein the at least one processor is configured to execute further instructions to at least providing the new monitoring component (M1) and the at least one added rule (R2) to a testing-phase to validate the at least one rule (R2) during the operation of the SOA.

20. A non-transitory computer readable storage medium tangibly storing a computer program comprising instructions that, when executed via at least one processor of a monitoring system for the rule-based monitoring of a component (C1) added to a service-oriented architecture (SOA), the SOA comprising a plurality of components (C2, . . . , Cn) being monitored by a plurality of monitoring components (M2, . . . , Mn), at least:

a. select a component (C2) from the plurality of components (C2, . . . , Cn) of the SOA which is similar to the added component (C1) based on a similarity-metric;

b. select at least one rule (R2) from the monitoring component (M2) of the selected component (C2), wherein the at least one rule (R2) has already been validated during the operation of the SOA;

c. add the at least one rule (R2) to a new monitoring component (M1) of the added component (C1); and

d. provide the new monitoring component (M1) and the at least one added rule (R2) to a learning-phase to determine at least one parameter of the at least one rule (R2).