Service oriented architecture with message processing pipelines

• US 20050267947A1
• Filed: 05/18/2005
• Published: 12/01/2005
• 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,841
• Publication Number:
  US 20050267947A1
• Time in Patent Office: Days
• US Class Current: 709/217
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 67/564 Enhancement of application control based on intercepted application data
• CPC Class Codes: H04L 67/566 Grouping or aggregating service requests, e.g. for unified processing
• CPC Class Codes: H04L 69/22 Parsing or analysis of headers

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 processing messages for a service proxy, comprising:

accepting a message in a first message processing pipeline;

processing the message with at least one first message processing stage in the first message processing pipeline; and

wherein the first message processing pipeline is incorporated into a message processing graph.

2. The method of claim 1, further comprising:

accepting a next message in a second message processing pipeline;

processing the next message with at least one second message processing stage in the second message processing pipeline; and

wherein the message is a request and wherein the next message is a response.

3. The method of claim 1 wherein:

a message processing stage can be dynamically added to and/or removed from a message processing pipeline.

4. The method of claim 1 wherein:

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

a service and another service proxy.

5. The method of claim 1 wherein:

a message processing stage is capable of operating on a message in series with other message processing stages in the same message processing pipeline.

6. The method of claim 1 wherein:

a message processing stage implements a programmatic interface that is compatible with a message processing pipeline.

7. The method of claim 1 wherein:

a message processing stage is capable of performing at least one of the following;

message authentication, message authorization, message validation, message transformation, message routing, performance monitoring, message tracking, message archiving, message logging, message publication, error reporting, and a user-defined process.

8. The method of claim 7 wherein:

the message processing graph includes a single request endpoint and one or more response endpoints.

9. The method of claim 7 wherein:

the message processing graph includes a plurality of message processing nodes that cooperate to process a message.

10. The method of claim 1, further comprising:

providing the message to one of;

a service and another service proxy.

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

accept a message in a first message processing pipeline;

process the message with at least one first message processing stage in the first message processing pipeline; and

wherein the first message processing pipeline is incorporated into a message processing graph.

12. A service proxy for processing messages, comprising:

a first message processing pipeline configured to accept a message;

at least one first message processing stage in the first message processing pipeline configured to process the message; and

wherein the first message processing pipeline is incorporated into a message processing graph.

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

a second message processing pipeline configured to accept a next message;

at least one second message processing stage in the second message processing pipeline configured to process the next message; and

wherein the message is a request and wherein the next message is a response.

14. The service proxy of claim 12 wherein:

a message processing stage can be dynamically added to and/or removed from a message processing pipeline.

15. The service proxy of claim 12 wherein:

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

a service and another service proxy.

16. The service proxy of claim 12 wherein:

a message processing stage is capable of operating on a message in series with other message processing stages in the same message processing pipeline.

17. The service proxy of claim 12 wherein:

a message processing stage implements a programmatic interface that is compatible with a message processing pipeline.

18. The service proxy of claim 12 wherein:

a message processing stage is capable of performing at least one of the following;

message authentication, message authorization, message validation, message transformation, message routing, performance monitoring, message tracking, message archiving, message logging, message publication, error reporting, and a user-defined process.

19. The service proxy of claim 18 wherein:

the message processing graph includes a single request endpoint and one or more response endpoints.

20. The service proxy of claim 18 wherein:

the message processing graph includes a plurality of message processing nodes that cooperate to process a message.