Co-located service oriented architecture

• US 20050273518A1
• Filed: 05/19/2005
• Published: 12/08/2005
• Est. Priority Date: 05/21/2004
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: BEA Systems Incorporated (Oracle Corporation)
• Inventors: Kasi, Jayaram, Mihic, Matthew, Urhan, Tolga, Kapoor, Chet, Aletty, Ashok, Patrick, Paul B.
• Granted Patent: US 7,310,684 B2
• Time in Patent Office: Days
• US Class Current: 709/238
• CPC Class Codes: G06Q 10/00 Administration; Management

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 in a client, comprising:

conveying a message in a first direction along a first path in a message processing graph wherein the first path includes at least one message processing node;

affording each one of the at least one message processing node the opportunity to process the message;

providing the message to one of;

a service and service proxy; and

wherein the message includes an operation to be performed by a service which is external to the client.

2. The method of claim 1 wherein:

the first path is dynamically determined.

3. The method of claim 1 wherein:

the first path is dynamically determined based on message content.

4. The method of claim 1 wherein:

a message processing node in the at least one message processing node can be added to or removed from the message processing graph dynamically.

5. The method of claim 1 wherein:

a message processing node in the at least one message processing node can be configured dynamically.

6. The method of claim 1 wherein:

the first path includes a first message processing node to accept request messages and at least one second message processing node to accept response messages.

7. The method of claim 1 wherein:

a message processing node in the at least one message processing node 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 1, further comprising:

conveying a response message through the first path in a direction that is opposite of the first direction.

9. The method of claim 1 wherein:

each one of the at least one message processing node implements a common interface and/or a protocol.

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

convey a message in a first direction along a first path in a message processing graph wherein the first path includes at least one message processing node;

afford each one of the at least one message processing node the opportunity to process the message;

providing the message to one of;

a service and service proxy; and

wherein the message includes an operation to be performed by a service which is external to the client.

11. A client for processing a message, comprising:

a message processing graph;

a first path in the message processing graph wherein the first path includes at least one message processing node and wherein the first path is capable of conveying the message in a first direction through the message processing graph wherein each one of the at least one message processing node is capable of processing the message;

a component capable of providing the message to one of;

a service and service proxy; and

wherein the message includes an operation to be performed by a service which is external to the client.

12. The client of claim 11 wherein:

the first path is dynamically determined.

13. The client of claim 11 wherein:

the first path is dynamically determined based on message content.

14. The client of claim 11 wherein:

a message processing node in the at least one message processing node can be added to or removed from the message processing graph dynamically.

15. The client of claim 11 wherein:

a message processing node in the at least one message processing node can be configured dynamically.

16. The client of claim 11 wherein:

the first path includes a first message processing node to accept request messages and at least one second message processing node to accept response messages.

17. The client of claim 11 wherein:

a message processing node in the at least one message processing node 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.

18. The client of claim 11, further comprising:

conveying a response message through the first path in a direction that is opposite of the first direction.

19. The client of claim 11 wherein:

each one of the at least one message processing node implements a common interface and/or a protocol.