TRACKING OF DOCUMENT STATUS THROUGH MULTIPLE COMPUTER NETWORKS

• US 20180075004A1
• Filed: 12/09/2016
• Published: 03/15/2018
• Est. Priority Date: 09/15/2016
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP SE
• Inventors: Ubillus, Alexander, Yue, Kam, Thiyagarajan, Arun, Vijil, Veronica, Liang, Huihang, Pinto, Orville, Sun, Jiawei, Schroeder, Giso
• Granted Patent: US 11,057,288 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 16/11 File system administration, e.g. details of archiving or snapshots file system backup G06F11/14
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G06Q 30/0633 Lists, e.g. purchase orders, compilation or processing
• CPC Class Codes: H04L 43/0894 Packet rate
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/535 Tracking the activity of the user network monitoring arrangements H04L43/00; recording of computer activity G06F11/34

Abstract

In an example embodiment, a first function is performed on the first document received at first middleware management architecture, causing a change in the status of the first document. The change is logged in a record corresponding to the first document in a memory. Then the first document is sent to a second network via a transmission protocol layer. A notification of a change in the status of the first document within the second layer is received in a layer other than the transmission protocol layer, from the second network. The change in the second network is logged in the record corresponding to the first document in the memory. Information corresponding to the change in the status of the first document at the middleware management architecture and the change in the status of the first document in the second network is reported to the first network.

Claims

1. A system comprising:

at least one processor;

a memory; and

a middleware management architecture engine stored in the memory and executable by the at least one processor to perform operations comprising;

performing a first function on a first document received from a first network, causing a change in the status of the first document, the first document being a file stored at the first network;

logging the change in the status of the first document in a record corresponding to the first document in the memory;

causing the first document to be sent to a second network via a transmission protocol layer;

receiving a notification of a change in status of the first document within the second network;

logging the change to the status of the first document in the second network in the record corresponding to the first document in the memory; and

causing the reporting, to the first network, of information corresponding to the change in the status of the first document in the middleware management architecture and the change in the status of the first document in the second network.

2. The system of claim 1, further comprising:

an integration layer configured to perform operations comprising;

receiving a first communication comprising the first document from the first network;

transforming the first communication into a format compatible with the engine;

sending the first communication to the middleware management architecture engine;

transforming a second communication comprising the first document into a format compatible with the second network;

sending the second communication to the second network via a transmission protocol layer;

receiving, in a layer other than the transmission protocol layer, from the second network, in a third communication, a notification of a change in status of the first document within the second network;

transforming the third communication into a format compatible with the middleware management architecture engine; and

sending the third communication to the middleware management architecture engine.

3. The system of claim 2, wherein the integration layer and the middleware management architecture engine are contained within a middleware management architecture.

4. The system of claim 1, further comprising an integration server to perform operations comprising:

receiving a first communication comprising the first document from the first network;

transforming the first communication into a format compatible with the middleware management architecture engine;

sending the first communication to the middleware management architecture engine;

transforming a second communication comprising the first document into a format compatible with the second network;

sending the second communication to the second network via a transmission protocol layer;

receiving, in a layer other than the transmission protocol layer, from the second network, in a third communication, a notification of a change in status of the first document within the second network;

transforming the third communication into a format compatible with the middleware management architecture engine; and

sending the third communication to the middleware management architecture engine.

5. The system of claim 1, further comprising a buffer containing a queue, and the first document is sent to the first network by placing the first document in the queue and sending a plurality of document in the queue in a batch mode when the queue becomes full.

6. A method of tracking status of a computerized document through multiple computer networks, the method comprising:

receiving, at a middleware management architecture, a first document from a first network, the first document being a file stored at the first network;

performing, at the middleware management architecture, a first function on the first document, causing a change in the status of the first document;

logging the change in the status of the first document in a record corresponding to the first document in a memory;

sending the first document to a second network via a transmission protocol layer;

receiving, in a layer other than the transmission protocol layer, from the second network, a notification of a change in status of the first document within the second network;

logging the change to the status of the first document in the second network in the record corresponding to the first document in the memory; and

reporting, to the first network, information corresponding to the change in the status of the first document in the middleware management architecture and the change in the status of the first document in the second network.

7. The method of claim 6, further comprising:

sending the first document to a third network via a transmission protocol layer;

receiving, in the layer other than the transmission protocol layer, from the second network, a notification of a change in status of the first document within the second network; and

logging the change to the status of the first document in the third network in the record corresponding to the first document in the memory.

8. The method of claim 6, wherein the sending of the first document include placing the first document in a queue within a buffer and sending a plurality of document in the queue in a batch mode when the queue becomes full.

9. The method of claim 8, wherein a size of the buffer is larger than a size of the queue.

10. The method of claim 9, further comprising:

examining status updates for the first document to determine whether the first document was successfully sent to the first network; and

in response to a determination that the first document was not successfully sent to the first network, placing the first document back in the queue.

11. The method of claim 10, wherein both the queue and buffer sizes are dynamically determined based on network bandwidth.

12. The method of claim 10, wherein both the queue and buffer sizes are dynamically determined based on processing load.

13. The method of claim 12, wherein both the queue and buffer sizes are also dynamically determined based on network bandwidth.

14. A non-transitory machine-readable storage medium comprising instructions, which when implemented by one or more machines, cause the one or more machines to perform operations comprising:

receiving, at a middleware management architecture, a first document from a first network, the first document being a file stored at the first network;

performing, at the middleware management architecture, a first function on the first document, causing a change in the status of the first document;

logging the change in the status of the first document in a record corresponding to the first document in a memory;

sending the first document to a second network via a transmission protocol layer;

receiving, in a layer other than the transmission protocol layer, from the second network, a notification of a change in status of the first document within the second network;

logging the change to the status of the first document in the second network in the record corresponding to the first document in the memory; and

reporting, to the first network, information corresponding to the change in the status of the first document in the middleware management architecture and the change in the status of the first document in the second network.

15. The non-transitory machine-readable storage medium of claim 14, further comprising:

sending the first document to a third network via a transmission protocol layer;

receiving, in the layer other than the transmission protocol layer, from the second network, a notification of a change in status of the first document within the second network; and

logging the change to the status of the first document in the third network in the record corresponding to the first document in the memory.

16. The non-transitory machine-readable storage medium of claim 14, wherein the sending of the first document include placing the first document in a queue within a buffer and sending a plurality of document in the queue in a batch mode when the queue becomes full.

17. The non-transitory machine-readable storage medium of claim 16, wherein a size of the buffer is larger than a size of the queue.

18. The non-transitory machine-readable storage medium of claim 17, further comprising:

examining status updates for the first document to determine whether the first document was successfully sent to the first network; and

in response to a determination that the first document was not successfully sent to the first network, placing the first document back in the queue.

19. The non-transitory machine-readable storage medium of claim 18, wherein both the queue and buffer sizes are dynamically determined based on processing load.

20. The non-transitory machine-readable storage medium of claim 19, wherein both the queue and buffer sizes are also dynamically determined based on network bandwidth.