Service oriented architecture with message processing pipelines

• US 20060031432A1
• Filed: 05/19/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/132,558
• Publication Number:
  US 20060031432A1
• Time in Patent Office: Days
• US Class Current: 709/220
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues
• CPC Class Codes: H04L 41/0681 Configuration of triggering conditions
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561

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 request message in a first message processing pipeline;

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

wherein the first message processing pipeline is dynamically configurable; and

wherein the at least one first message processing stage implements an interface and/or a protocol that is compatible with the first message processing pipeline.

2. The method of claim 1 wherein:

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

a service and another service proxy.

3. 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 a message processing pipeline.

4. The method of claim 1, further comprising:

accepting a response message in a second message processing pipeline; and

processing the response message with at least one second message processing stage in the second message processing pipeline.

5. 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.

6. The method of claim 1 wherein:

the at least one first message processing stages share a context through which they can exchange information.

7. The method of claim 1 wherein:

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

8. The method of claim 7 wherein:

the message processing graph includes a single node to accept a request and at least one node to accept a response.

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 request 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 request message in a first message processing pipeline;

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

wherein the first message processing pipeline is dynamically configurable; and

wherein the at least one first message processing stage implements an interface and/or a protocol that is compatible with a message processing pipeline.

12. A service proxy for processing messages, comprising:

a first message processing pipeline configured to accept a request message;

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

wherein the first message processing pipeline is dynamically configurable; and

wherein the at least one first message processing stage implements a programmatic interface that is compatible with the first message processing pipeline.

13. 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.

14. 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 a message processing pipeline.

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

a second message processing pipeline configured to accept a response message; and

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

16. 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.

17. The service proxy of claim 12 wherein:

the at least one first message processing stage share a context through which they can exchange information.

18. The service proxy of claim 12 wherein:

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

19. The service proxy of claim 17 wherein:

the message processing graph includes a single node to accept a request and at least one node to accept a response.

20. The service proxy of claim 17 wherein:

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