Native format tunneling

A method comprising:

• polling, by a first adapter of a sending application, a routing module and a mapping module of an integration server, the sending application sending a message to a receiving application, the message comprising message content in an original message format, the integration server being implemented on one or more processors and utilizing one or more open standard file formats, the polling comprising a request for an identity of the receiving application from the routing module and for a receiving application file format used by the receiving application from the mapping module;
• wrapping, at the first adapter, the message in a markup language file envelope that corresponds to one of the one or more open standard file formats of the integration server if the receiving application file format is identical to a sending application file format used by the sending application, the wrapping comprising adding a message header in the one of the one or more open standard file formats of the integration server while leaving the message content unchanged and without mapping or converting the message content to a file according to any of the one or more open standard file formats of the integration server;
• sending the message in the markup language file envelope to a second adapter of the receiving application via one or more pipeline services on the integration server;
• the one or more pipeline services utilizing the message header for logical routing of the message;
• unwrapping the message from the markup language file envelope at the second adapter;
• and
• passing the message content to the receiving application substantially in the original message format;
• wherein the markup language corresponds to extensible markup language (XML).

A system comprising:

• an integration server implemented on one or more processors, the integration server comprising a routing module and a mapping module and utilizing one or more open standard file formats;
• and
• a sending application comprising a first adapter, the first adapter polling the routing module and the mapping module to determine an identity of a receiving application for a message sent from the sending application and a receiving application file format used by the receiving application, the identity being determined from the routing module and the receiving application file format being determined from the mapping module, the message comprising message content in an original message format, the first adapter wrapping the message in a markup language file envelope that corresponds to one of the one or more open standard file formats of the integration server if the receiving application file format is identical to a sending application file format used by the sending application, the wrapping comprising adding a message header in the one of the one or more open standard file formats of the integration server while leaving the message content unchanged and without mapping or converting the message content according to any of the one or more open standard file formats of the integration server, the first adapter sending the message in the markup language file envelope to a second adapter of the receiving application via one or more pipeline services on the integration server;
• the one or more pipeline services utilizing the message header for logical routing of the message;
• wherein the markup language corresponds to extensible markup language (XML).