초록 ▼

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

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.

대표청구항 ▼

What is claimed is: 1. A method for processing messages, 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 opp

What is claimed is: 1. A method for processing messages, 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; wherein the message includes an operation to be performed by a service external to the first path wherein the first path is dynamically configured using configuration information from a console, wherein the console uses a session to update the configuration in a batch, batch changes being validated before updating core configuration data. 2. 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. 3. The method of claim 1 wherein: a message processing node in the at least one message processing node can be configured dynamically. 4. 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. 5. 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. 6. 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. 7. The method of claim 1 wherein: each one of the at least one message processing node implements a common interface and/or a protocol. 8. 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 wherein the message includes an operation to be performed by a service external to the first path wherein the first path is dynamically configured using configuration information from a console, wherein the console uses a session to update the configuration in a batch, batch changes being validated before updating core configuration data. 9. A system 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 first path, wherein the first path is dynamically configured using configuration information from a console, wherein the console uses a session to update the configuration in a batch, batch changes being validated before updating core configuration data. 10. The system of claim 9 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. 11. The system of claim 9 wherein: a message processing node in the at least one message processing node can be configured dynamically. 12. The system of claim 9 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. 13. The system of claim 9 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. 14. The system of claim 9, further comprising: conveying a response message through the first path in a direction that is opposite of the first direction. 15. The system of claim 9 wherein: each one of the at least one message processing node implements a common interface and/or a protocol. 16. A method for processing messages, 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; wherein the message includes an operation to be performed by a service external to the first path wherein at least one message processing node is dynamically configured using configuration information from a console, wherein the console uses a session to update the configuration in a batch, batch changes being validated before updating core configuration data.