Downloads

Administration › Downloads has the programs that go on other computers. Each download is made for your server: it carries the server's address, so it connects by itself after a simple install. You need the Settings permission (administrators have it).

Each card says what the program is for, when you need it, what it needs, three install steps, and who is connected now.

Scan Agent

Connects a scanner on a Windows PC to DocView Capture in the browser.

• When you need it: on every PC with a scanner (TWAIN or WIA). Not needed for importing files.
• Needs: Windows 10 or 11 and the scanner's driver. No administrator rights.

To install:

1. Download it on the scanning PC. (Operators can also open Scan there: it offers the same download.)
2. Open the downloaded file. If Windows warns, choose More info › Run anyway.
3. It installs for that Windows user and connects within seconds. Pick the scanner on the Scan screen.

There is one download for every PC: it installs the 64-bit or the 32-bit agent, as the PC's scanner drivers need. Only the newest version is offered. The card shows how many Scan screens were used in the last 24 hours. See Scan Agent.

DocView Worker

Does the automatic work: OCR, separation, classification, extraction, export and import polling.

• When you need it: the single-PC installation already has one. Add DocView Workers on other computers for more pages per hour, or install one on an IIS server that has none yet.
• Needs: 64-bit Windows 10/11 or Windows Server 2019 or later, 4 cores and 8 GB RAM recommended, administrator rights to install, network access to the database server and to the shared storage.

To install:

1. Select Download DocView Setup on the computer that will run the DocView Worker (or copy the file there).
2. Run it. Windows asks for administrator rights. Setup already knows your server and its worker key: click Next through the pages (you can change the DocView Worker's name and program folder), then Install.
3. Setup gets the DocView Worker from your server, installs the Windows service DocView Worker and starts it. Within a minute it appears under Administration › DocView Workers, where you choose what it does. See DocView Workers.

Run the same Setup on as many computers as you need: each one becomes another DocView Worker.

Upgrading from version 1.6 or earlier: Setup replaces the old service DocViewCaptureWorker with DocViewWorker and keeps its settings, its name in DocView Workers and its database access.

Below the button, Or the package to install by hand gives the DocView Worker as a zip with Install.cmd, for computers where you prefer a script.

What Setup does for you:

• asks your server for the database and storage settings (nothing to type);
• when SQL Server runs on the same computer, gives the DocView Worker's service account access to the database;
• adds DocView Worker to Settings › Apps, with an uninstaller.

The DocView Worker asks the server for its settings every time it starts, so if the database moves, DocView Workers follow by themselves.

Before you add DocView Workers on other computers

The card warns you when one of these is missing:

• An HTTPS site address. DocView Workers on other computers connect over HTTPS only. Set the address under Setup › Site address. A DocView Worker on the server itself works over HTTP.
• Shared storage. Page images must be in a network share or cloud storage (Azure Blob Storage, Amazon S3 or Google Cloud Storage) that every computer can reach (Setup › Storage), not in a folder on the server.
• Database access. With Windows sign-in to SQL Server, the DocView Worker computer's account (for example CONTOSO\OCR01$) needs db_owner on the database. The installer tells you the exact name.
• Stored passwords. If you keep passwords in DocView Capture (mailbox imports, SFTP exports, cloud OCR keys), all servers need the same key certificate: see More than one server in Install on IIS.

DocView Workers in the cloud

On Azure, AWS and Google Cloud, you don't download DocView Workers: the deployment runs them for you. To add more, change the number of DocView Workers, as each installation page explains. With Docker, run docker compose up -d --scale worker=3.

Worker key

Every DocView Worker download carries the server's worker key. Anyone with the file can connect a DocView Worker to your server, so keep downloads in safe places. Issue a new DocView Worker key makes all earlier downloads stop working; DocView Workers already installed keep working.

DocView Setup can also add a DocView Worker without the personalised download: run any DocView Setup, choose Additional DocView Worker, and give the server's address and the worker key.

DocView OmniRead

DocView's own recognition service: reads printed and handwritten text, barcodes and documents on your own hardware, without a cloud service.

• When you need it: for better recognition than the built-in OCR, or to run recognition on a separate, stronger computer.
• Needs: 64-bit Windows or Linux, 8 GB RAM or more. It runs on the processor; no graphics card is needed.

To install:

1. Select Download DocView Setup on the computer that will run OmniRead.
2. Run it. Windows asks for administrator rights. Choose whether other computers use the service (it then listens on the network and Windows Firewall allows its port, 5300 by default), and whether to download the recognition models now (about 0.2 GB; the vision model is about 1.5 GB more).
3. Setup gets OmniRead from your server and installs the Windows service DocView OmniRead. It then tells your server the service's address, so it appears under Settings › DocView OmniRead by itself. Choose OmniRead as the recognition engine in a Batch Setup. See DocView OmniRead.

Install it on more computers to share the work: DocView uses all the services it knows, in turn.

Or the OmniRead program on its own below the button is the OmniRead installer by itself (double-click to install).

Release files

The downloads are made from three files: DocView Setup (DocViewCapture-Setup-<version>.exe), the DocView Worker package (DocViewWorker-Setup-<version>.zip) and DocView OmniRead (DocViewOmniRead-<version>-win-x64.exe). The table at the end of the page shows which ones this server has and where they are: With the release on this server (in the release's folders), or Added here.

When a part is missing — usually on a cloud installation, where the release has no folder of its own — a site administrator adds it: choose the files under Release files and select Add. They are kept in DocView Capture's document storage (a folder, Azure Blob Storage, Amazon S3 or Google Cloud Storage), so they work on any server. Adding a newer version replaces the older one. Only site administrators see this section, and adding or removing a file is recorded in the audit log.

Troubleshooting

See also Troubleshooting.