Service oriented architecture with monitoring

• US 20060031481A1
• Filed: 05/18/2005
• Published: 02/09/2006
• Est. Priority Date: 05/21/2004
• Status: Abandoned Application

• Current Assignee: BEA Systems Incorporated (Oracle Corporation)
• Original Assignee: BEA Systems Incorporated (Oracle Corporation)
• Inventors: Kasi, Jayaram, Mihic, Matthew, Urhan, Tolga, Kapoor, Chet, Aletty, Ashok, Patrick, Paul B.
• Application Number:
  US11/131,794
• Publication Number:
  US 20060031481A1
• Time in Patent Office: Days
• US Class Current: 709/224
• CPC Class Codes: G06F 11/0772 Means for error signaling, e.g. using interrupts, exception flags, dedicated error registers
• CPC Class Codes: G06F 11/0793 Remedial or corrective actions recovery from an exception in an instruction pipeline G06F9/3861; by retry G06F11/1402; for recovering from a failure of a protocol instance or entity H04L69/40
• CPC Class Codes: G06F 11/1474 in transactions G06F16/20 takes precedence
• CPC Class Codes: G06F 11/3495 for systems
• CPC Class Codes: H04L 43/022 by sampling
• CPC Class Codes: H04L 63/104 Grouping of entities
• CPC Class Codes: H04L 63/166 at the transport layer
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 67/142 Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54

Abstract

A system, method and media for a service oriented architecture. This description is not intended to be a complete description of, or limit the scope of, the invention. Other features, aspects and objects of the invention can be obtained from a review of the specification, the figures and the claims.

Claims

1. A method for monitoring a plurality of service proxies, comprising:

collecting data from at least one of;

a service proxy, a service proxy component, and a process capable of monitoring a service proxy;

aggregating the data over time; and

triggering evaluation of a rule.

2. The method of claim 1 wherein the step of aggregating includes:

retaining more recently collected data than less recently collected data.

3. The method of claim 1, further comprising:

publishing the collected data and/or the aggregated data.

4. The method of claim 1 wherein:

the triggering is based on a change in aggregated data at a specified granularity.

5. The method of claim 1 wherein:

the triggering is based on an elapse of time.

6. The method of claim 1 wherein:

the triggering is based on an occurrence of an event.

7. The method of claim 1 wherein:

a rule includes one or more expressions that evaluate to true or false; and

wherein an expression can include nested expressions.

8. The method of claim 1 wherein:

a service proxy is an intermediary between a client and one of;

a service and another service proxy.

9. The method of claim 1 wherein:

aggregation follows a configurable aggregation window.

10. A machine readable medium having instructions stored thereon to cause a system to:

collect data from at least one of;

a service proxy, a service proxy component, and a process capable of monitoring a service proxy;

aggregate the data over time; and

trigger evaluation of a rule.

11. A service proxy for processing messages, comprising:

a first component configured to collect data from at least one of;

a service proxy, a service proxy component, and a process capable of monitoring a service proxy;

a second component configured to aggregate the data over time; and

a third component configured to trigger evaluation of a rule.

12. The service proxy of claim 11 wherein the second component is further configured to:

retain more recently collected data than less recently collected data.

13. The service proxy of claim 11, further comprising:

a fourth component configured to publish the collected data and/or the aggregated data.

14. The service proxy of claim 11 wherein:

the triggering is based on a change in aggregated data at a specified granularity.

15. The service proxy of claim 11 wherein:

the triggering is based on an elapse of time.

16. The service proxy of claim 11 wherein:

the triggering is based on an occurrence of an event.

17. The service proxy of claim 11 wherein:

a rule includes one or more expressions that evaluate to true or false; and

wherein an expression can include nested expressions.

18. The service proxy of claim 11 wherein:

a service proxy is an intermediary between a client and one of;

a service and another service proxy.

19. The service proxy of claim 11 wherein:

aggregation follows a configurable aggregation window.