OnBase 12 Optimized Upload and Download Handlers
In OnBase 12, big changes have gone into improving how documents are uploaded (imported) and downloaded (retrieved). Improving how document file data is transferred has shown to greatly improve performance of these actions over the old method. The new method increases efficiency with CPU, memory and network resources. The enhancements affect clients and modules making SOAP web service requests such as the Unity Client, Disconnected Scanning and the ActiveX Controls.
New Optimized Upload and Download Handlers
With the new optimized upload and download handlers the binary file data is streamed. No encoding or decoding is done, file sizes are not bloated and the data is streamed from disk.
- CPU and memory usage on clients and servers are reduced because they do not have to spend time on an intensive base64 encoding or decoding process.
- Bandwidth used to upload and download document data is reduced because they are not base64 encoded. Base64 encoding is typically 33% larger.
- Memory usage is further reduced during the transfer because the file is sent and received to disk instead of memory.
The new transfer method for downloading/retrieval was actually available in the Unity Client in OnBase version 11 but has been updated to include more modules in addition to uploading.
- Unity Client and other Unity based clients for upload and download
- ActiveX Web Client for downloading (but only when the ActiveX viewer is used, such as with image and PDF documents)
- Desktop for uploading and downloading
- Disconnected Scanning for uploading
- Front Office Scanning for uploading
- Unity API for uploading and downloading
So what kind of improvements am I talking about? Here are some results from tests that were run using the old and new methods. For the WAN setup, bandwidth was limited to 10Mb/sec and 100ms latency. Many factors can affect uploading and downloading of documents, so your results will vary.
