Native format tunneling
First Claim
1. A method comprising:
- receiving at an exchange infrastructure providing collaborative processing among internal components and external components of an enterprise that is implemented on one or more processors a poll from a first application using a first file format to determine, by an application integration system, an identity of a second application and that the second application uses the first file format, the application integration system comprising a routing module and a mapping module, the routing module determining the identity of the second application, the mapping module determining an application format used by the second application, the first file format differing from and being incompatible with an open standard language supported by the exchange infrastructure;
transmitting, by the exchange infrastructure, data to the first application indicating the identity of the second application and that the second application uses the first file format;
receiving, at the exchange infrastructure, a message from the first application;
generating, at the exchange infrastructure upon determining that the second application uses the first file format, a markup language file envelope comprising content of the message unchanged and a header in the open standard language, the header comprising routing information for the message, the content remaining in the first file format without being converted or mapped to the open standard language;
routing the markup language file envelope through the exchange infrastructure via one or more pipeline services for delivery to the second application; and
wherein the open standard language is one of extensible markup language (XML), Simple Object Access Protocol (SOAP), or Web Services Description Language (WSDL).
2 Assignments
0 Petitions
Accused Products
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.
-
Citations
17 Claims
-
1. A method comprising:
-
receiving at an exchange infrastructure providing collaborative processing among internal components and external components of an enterprise that is implemented on one or more processors a poll from a first application using a first file format to determine, by an application integration system, an identity of a second application and that the second application uses the first file format, the application integration system comprising a routing module and a mapping module, the routing module determining the identity of the second application, the mapping module determining an application format used by the second application, the first file format differing from and being incompatible with an open standard language supported by the exchange infrastructure; transmitting, by the exchange infrastructure, data to the first application indicating the identity of the second application and that the second application uses the first file format; receiving, at the exchange infrastructure, a message from the first application; generating, at the exchange infrastructure upon determining that the second application uses the first file format, a markup language file envelope comprising content of the message unchanged and a header in the open standard language, the header comprising routing information for the message, the content remaining in the first file format without being converted or mapped to the open standard language; routing the markup language file envelope through the exchange infrastructure via one or more pipeline services for delivery to the second application; and wherein the open standard language is one of extensible markup language (XML), Simple Object Access Protocol (SOAP), or Web Services Description Language (WSDL). - View Dependent Claims (2, 3, 4, 5, 6)
-
-
7. An article of manufacture comprising a non-transitory computer readable storage medium storing instructions that, when implemented by one or more processors, cause the one or more processors to perform operations comprising:
-
receiving at an exchange infrastructure providing collaborative processing among internal components and external components of an enterprise that is implemented on one or more processors a poll from a first application using a first file format to determine, by an application integration system, an identity of a second application and that the second application uses the first file format, the application integration system comprising a routing module and a mapping module, the routing module determining the identity of the second application, the mapping module determining an application format used by the second application, the first file format differing from and being incompatible with an open standard language supported by the exchange infrastructure; transmitting, by the exchange infrastructure, data to the first application indicating the identity of the second application and that the second application uses the first file format; receiving, at the exchange infrastructure, a message from the first application; generating, at the exchange infrastructure upon determining that the second application uses the first file format, a markup language file envelope comprising the content of message unchanged and a header in the open standard language, the header comprising routing information for the message, the content remaining in the first file format without being converted or mapped to the open standard language; routing the markup language file envelope through the exchange infrastructure via one or more pipeline services for delivery to the second application; and wherein the open standard language is one of extensible markup language (XML), Simple Object Access Protocol (SOAP), or Web Services Description Language (WSDL). - View Dependent Claims (8, 9, 10, 11, 12)
-
-
13. A system comprising:
-
one or more processors; and memory coupled to the at least one or more processors storing instructions that, when implemented by the one or more processors, cause the one or more processors to perform operations comprising; receiving at an exchange infrastructure providing collaborative processing among internal components and external components of an enterprise that is implemented on one or more processors a poll from a first application using a first file format to determine, by an application integration system, an identity of a second application and that the second application uses the first file format, the application integration system comprising a routing module and a mapping module, the routing module determining the identity of the second application, the mapping module determining an application format used by the second application, the first file format differing from and being incompatible with an open standard language supported by the exchange infrastructure; transmitting, by the exchange infrastructure, data to the first application indicating the identity of the second application and that the second application uses the first file format; receiving, at the exchange infrastructure, a message from the first application; generating, at the exchange infrastructure upon determining that the second application uses the first file format, a markup language file envelope comprising content of the message unchanged and a header in the open standard language, the header comprising routing information for the message, the content remaining in the first file format without being converted or mapped to the open standard language; and routing the markup language file envelope through the exchange infrastructure via one or more pipeline services for delivery to the second application; wherein the open standard language is one of extensible markup language (XML), Simple Object Access Protocol (SOAP), or Web Services Description Language (WSDL). - View Dependent Claims (14, 15, 16, 17)
-
Specification