File transfer using xml

Patent metadata

Field	Value
Publication number	US-2017163719-A1
Application number	US-201715441095-A
Country	US
Kind code	A1
Filing date	Feb 23, 2017
Priority date	Apr 25, 2012
Publication date	Jun 8, 2017
Grant date	—

Abstract

A tangible, machine readable storage medium stores instructions and implements a method when the instructions are executed by a processor. A source file is received by a gateway engine. The source file is a binary file. The source file is portioned into multiple parts by a breakdown engine. The multiple parts are transferred by a reliable transfer engine using a single port according to a messaging protocol to transfer messages reliably between nodes in the presence of any of software failures, component failures, system failures, or network failures. The multiple parts are reassembled into a copy of the source file by a reassembly engine.

First claim

1 .- 15 . (canceled)

16 . A non-transitory machine readable storage medium storing instructions that, when executed by a processor, cause the processor to:
receive a source file to be transferred to a destination node, the source file being a binary data file; portion the source file into multiple parts, wherein each of the multiple parts includes a chunk of the binary data of the source file; for each of the multiple parts, create an XML document containing a reference to the corresponding chunk of binary data of the respective part; and transmit each of the XML documents to the destination node through a single port, wherein the destination node is to utilize the references in the transmitted XML documents to obtain and reassemble the corresponding chunks of binary data into a copy of the source file.

17 . The non-transitory machine readable storage medium of claim 16 , wherein to transmit each of the XML documents to the destination node, the processor is to:
determine whether a communication channel connected to the port supports Message Transmission Optimization Mechanism (MTOM); in response to a determination that the communication channel supports MTOM, transmit the respective XML document to the destination node through the communication channel; and in response to a determination that the communication channel does not support MTOM, replace the reference to the chunk of binary data in the respective XML document with an encoded representation of the binary data, and transmit the respective XML document containing the encoded representation of the binary data to the destination node through the communication channel.

18 . The non-transitory machine readable storage medium of claim 16 , wherein the instructions are to cause the processor to encode the chunk of binary data of each of the multiple parts in XML by (i) storing the binary data in a container and referencing the binary data in XML, or by (ii) using Base 64 encoding.

19 . The non-transitory machine readable storage medium of claim 16 , wherein the instructions are to cause the processor to add a security protocol layer to each of the multiple parts.

20 . A method for transferring a binary file across web service channels using XML, the method comprising:
receiving, at a computing system, a source file to be transferred to a destination node, the source file being a binary data file; portioning, by a processor of the computing system, the source file into multiple parts, wherein each of the multiple parts includes a chunk of the binary data of the source file; creating, by the processor, an XML document for each of the multiple parts, wherein the XML document contains a reference to the corresponding chunk of binary data of the respective part; and transmitting, by the processor, each of the XML documents to the destination node through a single port, wherein the destination node is to utilize the references in the transmitted XML documents to obtain and reassemble the corresponding chunks of binary data into a copy of the source file.

21 . The method of claim 20 , wherein transmitting each of the XML documents to the destination node includes:
determining, by the processor, whether a communication channel connected to the port supports Message Transmission Optimization Mechanism (MTOM); in response to a determination that the communication channel supports MTOM, transmitting the respective XML document to the destination node through the communication channel; and in response to a determination that the communication channel does not support MTOM, replacing the reference to the chunk of binary data in the respective XML document with an encoded representation of the binary data, and transmitting the respective XML document containing the encoded representation of the binary data to the destination node through the communication channel.

22 . The method of claim 20 , further comprising:
encoding, by the processor, the chunk of binary data of each of the multiple parts in XML by (i) storing the binary data in a container and referencing the binary data in XML, or by (ii) using Base 64 encoding.

23 . The method of claim 20 , further comprising:
adding a security protocol layer to each of the multiple parts.

24 . A system for transferring files using XML, comprising:
a processor; and a memory device storing instructions that when executed by the processor cause the processor to:
receive a source file to be transferred to a destination node, the source file being a binary data file;
portion the source file into multiple parts, wherein each of the multiple parts includes a chunk of the binary data of the source file;
for each of the multiple parts, create an XML document containing a reference to the corresponding chunk of binary data of the respective part; and
transmit each of the XML documents to the destination node through a single port.

25 . The system of claim 24 , wherein to transmit each of the XML documents to the destination node, the processor is to:
determine whether a communication channel connected to the port supports Message Transmission Optimization Mechanism (MTOM); in response to a determination that the communication channel supports MTOM, transmit the respective XML document to the destination node through the communication channel; and in response to a determination that the communication channel does not support MTOM, replace the reference to the chunk of binary data in the respective XML document with an encoded representation of the binary data, and transmit the respective XML document containing the encoded representation of the binary data to the destination node through the communication channel.

26 . The system of claim 24 , wherein the instructions are further to cause the processor to assign a message number to each of the multiple parts beginning at 1 and increasing by 1 for each subsequent part, the message numbers assigned in the same order in which the XML documents corresponding to the multiple parts are sent to the destination node.

27 . The system of claim 24 , wherein the destination node is to utilize the references in the transmitted XML documents to obtain and reassemble the corresponding chunks of binary data into a copy of the source file.

28 . The system of claim 24 , wherein the processor is to encode the chunk of binary data in each of the multiple parts in XML by (i) storing the binary data in a container and referencing the binary data in XML, or by (ii) using Base 64 encoding.

29 . The system of claim 24 , wherein the instructions are to cause the processor to:
embed each of the)(MIL documents in a SOAP message; and stream the respective SOAP message and referenced binary data as a multi-part MIME to the destination node.

30 . The system of claim 24 , wherein the processor is to create the XML document for each of the multiple parts using XML-binary Optimized Packaging (XOP) protocol.

Assignees

• Hewlett Packard Entpr Dev Lp

Inventors

• Melvin Jonathan

Classifications

• H04L67/2823

  Electricity · mapped topic

• H04L67/06 Primary

  specially adapted for file transfer, e.g. file transfer protocol [FTP] · CPC title

• H04L67/565

  Conversion or adaptation of application format or content (adding application control or application functional data H04L67/561) · CPC title

• G06F16/116

  Details of conversion of file system types or formats · CPC title

• H04L67/02

  based on web technology, e.g. hypertext transfer protocol [HTTP] · CPC title