Mythics Blog

Common Misconceptions with WebCenter Distributed Capture

Posted on October 24, 2012 by Caleb Ely

Tags: Oracle, Mythics Consulting, Oracle Software, WebCenter

Oracle Document Capture(ODC) and Oracle Distributed Document Capture (ODDC) have been rebranded to WebCenter Capture and WebCenter Distributed Capture by Oracle. I will refer to them as Capture and Distributed Capture respectively in this article.

I have heard many people describe Distributed Capture as the Oracle licenses that allow Capture to work in a distributed fashion. The fact is that Capture is already capable of being used in a distributed fashion, but merely as a thick-client. What Distribute Capture adds is a thin-client version of Capture.

The table below outlines the important functionality differences between Capture and Distributed Capture:

Slide12_thumb.jpg

Some functionality and differences of the thin-client (Distributed Capture) from the thick-client (Capture) are important to understand.

  • Distributed Capture is a web-based client that is accessible using the Internet or a company intranet. It is supported in Internet Explorer 6-8 32-bit only and requires Active-X. No manual installation or configuration for each workstation is required. The client is downloaded and installed automatically the first time the user connects to the server through the Distributed Capture url.
  • Zonal recognition and OCR are not available through the distributed indexing interface. Additional processing can occur from the central Capture architecture. For example you could scan documents remotely and then index them centrally utilizing OCR.
  • Bar code recognition cannot be performed as part of a Distributed Capture’s scan profiles. This functionality can only occur through the recognition server, after indexing has occurred from the web-client and the batch has been sent to the central Capture server.
  • Capture and Distributed Capture share user security but have separate Administration configurations for Scan and Index Profiles. This means any profiles created in the Capture Administration component would need to be replicated in the Distributed Capture Administration component for those profiles to be available in both.
  • The Distributed Capture client uses the TWAIN driver to capture documents from desktop scanners while Capture uses ISIS or Adrenaline drivers intended for use with higher-capacity scanners.
  • A user cannot index a document in Distributed Capture that was scanned from a separate workstation. Scanned batches are saved in a local  folder on the workstation and these are the only document batches Distributed Capture can access. Once sent from Distributed Capture, all batches can be accessible from the Capture server for editing and indexing before they are committed to a repository.

In summary, both Capture and Distributed Capture are production-level enterprise document capture solutions. Capture is the thick-client and Distributed Capture a thin-client. They offer much of the same base functionality, such as document scanning and indexing, but there are also differences in features and the way they are used. There are benefits to the Distributed Capture client, such as it is web-based and doesn’t require installation. There are also features you can’t use, such as zonal recognition and barcode recognition, through the Distributed Capture client interface. Understanding these differences can help you know how to best utilize these two products in your individual use case.

 

Comments

  • ! No comments yet

Leave a Comment