IP Library Granted Patent US 8,271,407
Granted Patent B2
US 8,271,407 · App. 12/588,174 · Granted Sep 18, 2012

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

Assignee: Software AG
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,271,407
App. No.
12/588,174
Granted
Sep 18, 2012
Kind
B2
Abstract

The present invention concerns a method for the rule-based monitoring of a component (C 1 ) added to a service-oriented architecture (SOA), the SOA comprising a plurality of components (C 2 , . . . , Cn) being monitored by a plurality of monitoring components (M 2 , . . . , Mn), the method comprising the following steps: a. selecting a component (C 2 ) from the plurality of components (C 2 , . . . , Cn) of the SOA which is similar to the added component (C 1 ) based on a similarity-metric; b. selecting at least one rule (R 2 ) from the monitoring component (M 2 ) of the selected component (C 2 ), wherein the at least one rule (R 2 ) has already been validated during the operation of the SOA; and c. adding the at least one rule (R 2 ) to a new monitoring component (M 1 ) of the added component (C 1 ).

Claims (33)

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

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

b. selecting at least one rule (R 2 ) from the monitoring component (M 2 ) of the selected component (C 2 ), wherein the at least one rule (R 2 ) has already been validated during the operation of the SOA;

c. adding the at least one rule (R 2 ) to a new monitoring component (M 1 ) of the added component (C 1 ); and

d. providing the new monitoring component (M 1 ) and the at least one added rule (R 2 ) to a learning-phase to determine at least one parameter of the at least one rule (R 2 ).

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

3. The method of claim 2 , wherein the component (C 2 ) 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 (C 1 , C 2 , . . . , 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 (C 1 , C 2 , . . . , 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 (C 1 , C 2 , . . . , 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 (M 2 ) has undergone a learning-phase to obtain the at least one rule (R 2 ).

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

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

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

11. A monitoring system for the rule-based monitoring of a component (C 1 ) added to a service-oriented architecture (SOA), the SOA comprising a plurality of components (C 2 , . . . , Cn) being monitored by a plurality of monitoring components (M 2 , . . . , 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 (C 2 ) from the plurality of components (C 2 , . . . Cn) of the SOA which is similar to the added component (C 1 ) based on a similarity-metric;

b. select at least one rule (R 2 ) from the monitoring component (M 2 ) of the selected component (C 2 ), wherein the at least one rule (R 2 ) has already been validated during the operation of the SOA;

c. add the at least one rule (R 2 ) to a new monitoring component (M 1 ) of the added component (C 1 ); and

d. provide the new monitoring component (M 1 ) and the at least one added rule (R 2 ) to a learning-phase to determine at least one parameter of the at least one rule (R 2 ).

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

13. The system of claim 12 , wherein the component (C 2 ) 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 (C 1 , C 2 , . . . , 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 (M 2 ) has undergone a learning-phase to obtain the at least one rule (R 2 ) and/or a testing-phase to validate the at least one rule (R 2 ) during the operation of the SOA.

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

17. The system of claim 11 , wherein the components (C 1 , C 2 , . . . , 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 (C 1 , C 2 , . . . , 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 (M 1 ) and the at least one added rule (R 2 ) to a testing-phase to validate the at least one rule (R 2 ) 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 (C 1 ) added to a service-oriented architecture (SOA), the SOA comprising a plurality of components (C 2 , . . . , Cn) being monitored by a plurality of monitoring components (M 2 , . . . , Mn), at least:

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

b. select at least one rule (R 2 ) from the monitoring component (M 2 ) of the selected component (C 2 ), wherein the at least one rule (R 2 ) has already been validated during the operation of the SOA;

c. add the at least one rule (R 2 ) to a new monitoring component (M 1 ) of the added component (C 1 ); and

d. provide the new monitoring component (M 1 ) and the at least one added rule (R 2 ) to a learning-phase to determine at least one parameter of the at least one rule (R 2 ).

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 25, 2024
From: SOFTWARE AG
To: INTERNATIONAL BUSINESS MACHINES CORPORATION
Reel/Frame 069048/0240 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 8, 2009
From: RISTOW, GERALD; VOEGELE, JOACHIM
To: SOFTWARE AG
Reel/Frame 023638/0219 →
Priority Claims (1)
EP 08017502 · Oct 6, 2008 · regional
Continuity (1)
Related Publication 20100088256A1 · Apr 8, 2010