Service oriented architecture with interchangeable transport protocols

• US 20060069791A1
• Filed: 05/18/2005
• Published: 03/30/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/131,838
• Publication Number:
  US 20060069791A1
• Time in Patent Office: Days
• US Class Current: 709/230
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• 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/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 a service proxy, comprising:

accepting a message in a first representation from a first transport protocol;

converting the first representation to a second representation;

affording at least one message processing node the opportunity to process the second representation;

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

wherein the first transport protocol supports at least one of;

File Transport Protocol (FTP), Hypertext Transfer Protocol (HTTP), HTTP/Secure (HTTP/S), Simple Object Access Protocol (SOAP), Java Message Service (JMS), Web Services Reliable Messaging (WS-RM).

2. The method of claim 1 wherein:

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

a service and another service proxy.

3. The method of claim 1, further comprising:

converting the second representation to a third representation; and

providing via a second transport protocol the second representation to one of;

a service and another service proxy.

4. The method of claim 1 wherein:

a transport protocol can be configured to follow a service level agreement.

5. The method of claim 1 wherein:

a transport protocol can be configured for one of;

asynchronous communication and synchronous communication.

6. 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 then service proxy dynamically.

7. The method of claim 1 wherein:

a transport protocol can be configured dynamically.

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

9. The method of claim 1 wherein:

the first transport protocol is provides communication between the service proxy and an endpoint.

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

accept a message in a first representation from a first transport protocol;

convert the first representation to a second representation;

afford at least one message processing node the opportunity to process the second representation;

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

wherein the first transport protocol supports at least one of;

File Transport Protocol (FTP), Hypertext Transfer Protocol (HTTP), HTTP/Secure (HTTP/S), Simple Object Access Protocol (SOAP), Java Message Service (JMS), Web Services Reliable Messaging (WS-RM).

11. A service proxy, comprising:

a first transport layer capable of accepting a message in a first representation over a first transport protocol;

a first component capable of converting the first representation to a second representation;

at least one message processing node capable of processing the second representation;

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

wherein the first transport protocol supports at least one of;

File Transport Protocol (FTP), Hypertext Transfer Protocol (HTTP), HTTP/Secure (HTTP/S), Simple Object Access Protocol (SOAP), Java Message Service (JMS), Web Services Reliable Messaging (WS-RM).

12. The service proxy of claim 11 wherein:

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

a service and another service proxy.

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

a second component capable of converting the second representation to a third representation; and

a second transport layer capable of providing the third representation over a second transport protocol to one of;

a service and another service proxy.

14. The service proxy of claim 11 wherein:

a transport layer can be configured to follow a service level agreement.

15. The service proxy of claim 11 wherein:

a transport protocol can be configured for one of;

asynchronous communication and synchronous communication.

16. The service proxy of claim 11 wherein:

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

17. The service proxy of claim 11 wherein:

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

18. The service proxy 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.

19. The service proxy of claim 11 wherein:

the first transport protocol is provides communication between the service proxy and an endpoint.