Failsafe service oriented architecture

• US 20050270970A1
• Filed: 05/19/2005
• Published: 12/08/2005
• 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,566
• Publication Number:
  US 20050270970A1
• Time in Patent Office: Days
• US Class Current: 370/216
• CPC Class Codes: H04L 63/168 above the transport layer
• CPC Class Codes: H04L 63/20 for managing network security; network security policies in general filtering policies H04L63/0227
• CPC Class Codes: H04L 67/2871 Implementation details of single intermediate entities
• CPC Class Codes: H04L 67/563 Data redirection of data network streams
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561
• CPC Class Codes: H04L 67/567 Integrating service provisioning from a plurality of service providers
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]

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 communicating a message to a process, comprising:

exposing a second interface wherein the second interface is a facade for a first interface;

accepting the message via the second interface;

selecting the process wherein the process is able to accept the message;

providing the message to the process via the first interface; and

wherein a change to the first interface does not require a change to the second interface.

2. The method of claim 1 wherein:

an interface includes at least one of the following;

a message format, a transport protocol, an address, a service definition, and a security scheme.

3. The method of claim 1 wherein:

the second interface is a service-based interface.

4. The method of claim 1, wherein the providing includes:

dynamically mapping the request to the first interface.

5. The method of claim 1, wherein the providing includes:

performing at least one of the following;

converting a message format to a format compatible with the first interface, sending the message to the process using a transport protocol that is compatible with the first interface, using a security scheme that is compatible with the first interface.

6. The method of claim 1 wherein the selecting includes:

selecting the process from a plurality of processes using one of the following selection techniques;

round robin, random and weighted random.

7. The method of claim 1 wherein the selecting includes:

selecting the process from a plurality of processes based on evaluation of a conditional expression.

8. The method of claim 1, further comprising:

accepting a response from the process; and

providing the response to a second process using the second interface.

9. The method of claim 1 wherein:

a transport protocol is one of;

File Transfer Protocol (FTP), Hypertext Transfer Protocol (HTTP), HTTP/Secure (HTTPS), Java Message Service (JMS), file and electronic mail.

10. A service proxy capable of performing the method of claim 1.

11. A system comprising one or more components capable of performing the following steps:

exposing a second interface wherein the second interface is a facade for a first interface;

accepting a message from the second interface;

selecting a process wherein the process is able to accept the message;

providing the message to the process via the first interface; and

wherein a change to the first interface does not require a change to the second interface.

12. A machine readable medium having instructions stored thereon that when used cause a system to:

expose a second interface wherein the second interface is a facade for a first interface;

accept a message via the second interface;

select a process wherein the process is able to accept the message;

provide the message to the process via the first interface; and

wherein a change to the first interface does not require a change to the second interface.

13. The machine readable medium of claim 12 wherein:

an interface includes at least one of the following;

a message format, a transport protocol, an address, a service definition, and a security scheme.

14. The machine readable medium of claim 12 wherein:

the second interface is a service-based interface

15. The machine readable medium of claim 12, further comprising instructions that when used cause the system to:

dynamically map the request to the first interface.

16. The machine readable medium of claim 12, further comprising instructions that when used cause the system to:

perform at least one of the following;

converting a message format to a format compatible with the first interface, sending the message to the process using a transport protocol that is compatible with the first interface, using a security scheme that is compatible with the first interface.

17. The machine readable medium of claim 12, further comprising instructions that when used cause the system to:

select the process from a plurality of processes using one of the following selection techniques;

round robin, random and weighted random.

18. The machine readable medium of claim 12, further comprising instructions that when used cause the system to:

select the process from a plurality of processes based on evaluation of a conditional expression.

19. The machine readable medium of claim 12, further comprising instructions that when used cause the system to:

accept a response from the process; and

provide the response to a second process using the second interface.

20. The machine readable medium of claim 12 wherein:

a transport protocol is one of;

File Transfer Protocol (FTP), Hypertext Transfer Protocol (HTTP), HTTP/Secure (HTTPS), Java Message Service (JMS), file and electronic mail.