Dynamically configurable service oriented architecture

• US 20060031930A1
• 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/133,117
• Publication Number:
  US 20060031930A1
• Time in Patent Office: Days
• US Class Current: 726/14
• CPC Class Codes: H04L 41/0681 Configuration of triggering conditions
• CPC Class Codes: H04L 41/0893 Assignment of logical groups to network elements
• CPC Class Codes: H04L 41/0894 Policy-based network configuration management
• CPC Class Codes: H04L 41/12 Discovery or management of network topologies
• CPC Class Codes: H04L 41/22 comprising specially adapted graphical user interfaces [GUI]
• CPC Class Codes: H04L 41/5003 Managing SLA; Interaction between SLA and QoS
• CPC Class Codes: H04L 41/5009 Determining service level performance parameters or violations of service level contracts, e.g. violations of agreed response time or mean time between failures [MTBF]
• CPC Class Codes: H04L 41/5054 Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/133 Protocols for remote procedure calls [RPC]
• CPC Class Codes: H04L 69/08 Protocols for interworking; Protocol conversion

Abstract

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

Claims

1. A method for configuring a service proxy, comprising:

propagating first information for configuring a first transformation between a reception protocol and a transmission protocol;

propagating second information for configuring a potential message processing path capable of processing a message that has been received with the reception protocol, and capable of providing the message for transmission via the transmission protocol;

wherein the potential message processing path includes at least one message processing node capable of processing the message; and

wherein the at least one message processing node implements an interface and/or a protocol that is compatible with the service proxy.

2. The method of claim 1, further comprising:

propagating third information for configuring a second transformation between a reception message format and a transmission message format.

3. The method of claim 1, further comprising:

propagating third information for configuring a security scheme and/or authentication.

4. The method of claim 1, further comprising:

propagating third information for configuring at least one of the following;

quality of service, service level agreement, event tracking, metrics collection, monitoring, load balancing alternatives, failover alternatives, transmission retry policy, and transmission timeout policy.

5. The method of claim 1 wherein:

the service proxy is capable of accepting the message from one of;

a client and another service proxy.

6. The method of claim 1 wherein:

the service proxy is capable of providing the message to one of;

a service and another service proxy.

7. The method of claim 1, further comprising:

propagating third information for configuring one or more stages in a message processing node wherein the configuring of the one or more stages can include adding and/or removing a stage.

8. The method of claim 1 wherein:

propagating third information for configuring the potential message processing path includes adding and/or removing one or more of the at least one message processing node.

9. The method of claim 1 wherein:

configuration of the service proxy is dynamic.

10. The method of claim 1, further comprising:

configuring at least one of the following for one of the at least one message processing node;

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.

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

propagate first information for configuring a first transformation between a reception protocol and a transmission protocol;

propagate second information for configuring a potential message processing path capable of processing a message that has been received with the reception protocol, and capable of providing the message for transmission to the transmission protocol;

wherein the potential message processing path includes at least one message processing node capable of processing the message; and

wherein the at least one message processing node implements an interface and/or a protocol that is compatible with the service proxy.

12. A system for configuring a service proxy, comprising:

a configuration component capable of;

propagating first information for configuring a first transformation between a reception protocol and a transmission protocol;

propagating second information for configuring a potential message processing path capable of processing a message that has been received with the reception protocol, and capable of providing the message for transmission to the transmission protocol;

wherein the potential message processing path includes at least one message processing node capable of processing the message; and

wherein the at least one message processing node implements an interface and/or a protocol that is compatible with the service proxy.

13. The configuration component of claim 12, further capable of:

propagating third information for configuring a second transformation between a reception message format and a transmission message format.

14. The configuration component of claim 12, further capable of:

propagating third information for configuring security scheme and/or authentication.

15. The configuration component of claim 12, further capable of:

propagating third information for configuring at least one of the following;

quality of service, service level agreement, event tracking, metrics collection, monitoring, load balancing alternatives, failover alternatives, transmission retry policy, and transmission timeout policy.

16. The system of claim 12 wherein:

the service proxy is capable of accepting the message from one of;

a client and another service proxy.

17. The system of claim 12 wherein:

the service proxy is capable of providing the message to one of;

a service and another service proxy.

18. The configuration component of claim 12, further capable of:

propagating third information for configuring one or more stages in a message processing node wherein the configuring of the one or more stages can include adding and/or removing a stage.

19. The configuration component of claim 12, further capable of:

propagating third information for configuring the potential message processing path includes adding and/or removing one or more of the at least one message processing node.

20. The configuration component of claim 12, further capable of:

configuration of the service proxy is dynamic.

21. The configuration component of claim 12, further capable of:

configuring at least one of the following for one of the at least one message processing node;

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.