Native Format Tunneling

• US 20100180047A1
• Filed: 03/16/2010
• Published: 07/15/2010
• Est. Priority Date: 12/13/2002
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Dahl, Andreas, Surma, Peter, Rossmanith, Stefan, Hofmann, Christoph
• Granted Patent: US 8,205,007 B2
• Time in Patent Office: Days
• US Class Current: 709/236
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 69/326 in the transport layer [OSI layer 4] H04L69/16 takes precedence

Abstract

Systems and techniques are disclosed for transmitting a message through an application integration system without having to convert the message from a format that native to both a sending application and a receiving application. A computer-implemented method for transmitting a message from a sending application through an application integration system can include determining a receiving application of the message, and determining a file format used by the receiving application. If the file format used by the receiving application is substantially identical to a file format used by the sending application, the method can include wrapping the message in a markup language file envelope according to a markup language used by the application integration system. The message can then be routed in the markup language file envelope to the receiving application.

Claims

1. A method comprising:

determining, at an exchange infrastructure implemented on one or more processors, that a message received by the exchange infrastructure from a first application is to be routed between the first application and a second application that both use a first file format that differs from and is incompatible with an open standard language supported by the exchange infrastructure;

generating, at the exchange infrastructure, a file envelope comprising the message and a header in the open standard language, the header comprising routing information for the message, the message remaining in the first file format without conversion or mapping to the open standard language; and

routing the file envelope through the exchange infrastructure for delivery to the second application.

2. The method of claim 1, wherein the open standard language comprises one or more of SOAP, WSDL, and XML.

3. The method of claim 1, further comprising:

receiving the message at the exchange infrastructure from the first application, which is implemented on other one or more processors than the exchange infrastructure.

4. The method of claim 1, further comprising:

determining, by the exchange infrastructure, the first file format.

5. The method of claim 1, further comprising:

determining, at the exchange infrastructure, that a second message received by the exchange infrastructure from a third application that uses a third file format is to be routed between the third application and a fourth application that uses a fourth file format that differs from and is incompatible with the third file format, one or both of the third file format and the fourth file format differing from and being incompatible with the open standard language; and

converting, at the exchange infrastructure, the second message into a converted second message in the open standard language; and

routing the converted second message through the exchange infrastructure for delivery to the fourth application.

6. The method of claim 5, further comprising:

converting the converted second message from the open standard language to the fourth file format at the exchange infrastructure.

7. The method of claim 1, wherein the first provider comprises an external software component that communicates with the exchange infrastructure over a network and the first file format comprises a proprietary file format, the method further comprising generating a proxy by the exchange infrastructure to implement an interface for the external software component locally within the exchange infrastructure using the open standard language.

8. An article of manufacture comprising a computer readable storage medium storing instructions that, when implemented by one or more processors, cause the one or more processors to perform operations comprising:

determining, at an exchange infrastructure implemented on one or more processors, that a message received by the exchange infrastructure from a first application is to be routed between the first application and a second application that both use a first file format that differs from and is incompatible with an open standard language supported by the exchange infrastructure;

generating, at the exchange infrastructure, a file envelope comprising the message and a header in the open standard language, the header comprising routing information for the message, the message remaining in the first file format without conversion or mapping to the open standard language; and

routing the file envelope through the exchange infrastructure for delivery to the second application.

9. The article of claim 8, wherein the open standard language comprises one or more of SOAP, WSDL, and XML.

10. The article of claim 8, wherein the operations further comprise:

receiving the message at the exchange infrastructure from the first application, which is implemented on other one or more processors than the exchange infrastructure.

11. The article of claim 8, wherein the operations further comprise:

determining, by the exchange infrastructure, the first file format.

12. The article of claim 8, wherein the operations further comprise:

determining, at the exchange infrastructure, that a second message received by the exchange infrastructure from a third application that uses a third file format is to be routed between the third application and a fourth application that uses a fourth file format that differs from and is incompatible with the third file format, one or both of the third file format and the fourth file format differing from and being incompatible with the open standard language; and

converting, at the exchange infrastructure, the second message into a converted second message in the open standard language; and

routing the converted second message through the exchange infrastructure for delivery to the fourth application.

13. The article of claim 12, wherein the operations further comprise:

converting the converted second message from the open standard language to the fourth file format at the exchange infrastructure.

14. The article of claim 8, wherein the first provider comprises an external software component that communicates with the exchange infrastructure over a network and the first file format comprises a proprietary file format, the method further comprising generating a proxy by the exchange infrastructure to implement an interface for the external software component locally within the exchange infrastructure using the open standard language.

15. A system comprising:

one or more processors; and

one or more computer readable storage media storing instructions that, when implemented by the one or more processors, cause the one or more processors to perform operations comprising;

determining, at an exchange infrastructure implemented on one or more processors, that a message received by the exchange infrastructure from a first application is to be routed between the first application and a second application that both use a first file format that differs from and is incompatible with an open standard language supported by the exchange infrastructure;

generating, at the exchange infrastructure, a file envelope comprising the message and a header in the open standard language, the header comprising routing information for the message, the message remaining in the first file format without conversion or mapping to the open standard language; and

routing the file envelope through the exchange infrastructure for delivery to the second application.

16. The system of claim 15, wherein the open standard language comprises one or more of SOAP, WSDL, and XML.

17. The system of claim 15, wherein the operations further comprise:

receiving the message at the exchange infrastructure from the first application, which is implemented on other one or more processors than the exchange infrastructure.

18. The system of claim 15, wherein the operations further comprise:

determining, at the exchange infrastructure, that a second message received by the exchange infrastructure from a third application that uses a third file format is to be routed between the third application and a fourth application that uses a fourth file format that differs from and is incompatible with the third file format, one or both of the third file format and the fourth file format differing from and being incompatible with the open standard language; and

converting, at the exchange infrastructure, the second message into a converted second message in the open standard language; and

routing the converted second message through the exchange infrastructure for delivery to the fourth application.

19. The system of claim 18, wherein the operations further comprise:

converting the converted second message from the open standard language to the fourth file format at the exchange infrastructure.

20. The system of claim 15, wherein the first provider comprises an external software component that communicates with the exchange infrastructure over a network and the first file format comprises a proprietary file format, the method further comprising generating a proxy by the exchange infrastructure to implement an interface for the external software component locally within the exchange infrastructure using the open standard language.