The setup wizard – DocView Capture

After installation, DocView Capture opens a setup wizard in your browser. It asks for everything the server needs, tests it for you, and keeps it safely on the server. You never edit a settings file or type a connection string into a configuration file.

The wizard opens by itself the first time you go to DocView Capture. It takes about three minutes.

Before you start: the setup token

In a browser on the server itself (for example the PC you installed on), the wizard opens straight away.
From another computer, the wizard first asks for the setup token. This stops anyone else on the network from setting up your server before you do.

You find the setup token:

on the last screen of the installer;
in the file C:\ProgramData\DocViewCapture\config\setup-token.txt on the server (only administrators of the server can open it);
in the web app's log (search for "setup token").

Type or paste it and select Continue. The token stops working as soon as the setup is finished.

Step 1: Database

DocView Capture keeps batches, settings and users in a SQL Server database.

SQL Server. SQL Server on this computer is listed as buttons, for example .\SQLEXPRESS. Select one, or type the name of another server, for example sql01, sql01\SQLEXPRESS or myserver.database.windows.net for Azure SQL.
Database name. Keep DocViewCapture unless you need another name.
Sign in to SQL Server with:
- Windows sign-in (recommended): DocView Capture signs in as the account it runs as. No password is stored.
- A SQL login: for Azure SQL, or a server in another domain. Type the login and password.
Leave Trust the server's own certificate ticked for SQL Server Express. Untick it for Azure SQL and servers with a proper certificate.
Select Test connection. The wizard tells you what it found, for example "The database DocViewCapture does not exist yet: Create database makes it."
Select Create database and continue. This takes up to a minute.

An existing DocView Capture database is kept and upgraded, not replaced.

Note: The installers give DocView Capture permission to create databases on SQL Server on the same computer. For a SQL Server elsewhere, ask your database administrator to create an empty database and give the web app's account (or a SQL login) db_owner on it, then choose Test connection again.

Step 2: Administrator account

Create the account you sign in with to manage DocView Capture:

User name, for example admin;
Your name;
E-mail (optional);
Password, at least 10 characters. The bar under it shows how strong it is. Type it twice.

Select Create account and continue. You are signed in straight away. From now on, the wizard's first two steps are locked: nobody can create another administrator or change the database through it.

Step 3: Storage

Choose where page images and the files made for export are kept:

A folder (default C:\ProgramData\DocViewCapture\Storage). Fine when everything runs on one server. If DocView Workers will run on other computers, use a network share such as \\fileserver\DocViewCapture that the server's account can change.
Azure Blob Storage. Paste the storage account's connection string (Azure portal › storage account › Access keys). The container is created if it does not exist.
Amazon S3. Type the bucket name and region (for example eu-west-2), and optionally a folder in the bucket. On AWS, choose This server's AWS role: no key is stored. Elsewhere, choose An access key and type the access key ID and secret. The bucket must exist. Under S3-compatible storage you can type the address of another service that works like S3.
Google Cloud Storage. Type the bucket name, and optionally a folder. On Google Cloud, choose This server's own service account. Elsewhere, paste a service account key (JSON). The bucket must exist, and the account needs the Storage Object Admin role on it.

Select Test, then Save and continue. Keys and connection strings are kept protected on the server.

Note: Once there are batches, storage cannot be changed here, because their page images would stay behind in the old place.

Step 4: Site address and time zone

Site address: the address people type in their browser, for example https://capture.example.com. DocView Workers and scanning PCs you download from this server connect to it. On a single PC, http://localhost:5210 is fine. Use HTTPS when other computers connect.
Time zone of your organisation.

Step 5: Extras (optional)

Each of these can be done later; select Skip to leave them:

E-mail: the SMTP server for scheduled reports and messages. You can send a test e-mail later under Administration › Settings › E-mail.
Your first Batch Setup: pick a ready-made template, for example Supplier invoices, and a name. See Batch Setup templates.
Sample documents: loads six sample invoices as a batch, so you can see DocView Capture read them straight away.

Step 6: Finish

Check the summary and select Finish setup. From the last page you can:

start using DocView Capture (see the Quick start);
open Downloads for the Scan Agent, more DocView Workers and DocView OmniRead.

Changing things later

Administrators can open Setup again (address /setup, or the Setup button on the Downloads page) to change the storage, the site address and time zone, or to use the extras. The database and the first administrator are never changed through the wizard; add more people under Users, roles and permissions.

Servers in containers and the cloud

The Azure, AWS, Google Cloud and Docker installations set the database and storage for you. The wizard then:

skips the database step. If the database is not ready yet (a new cloud database can take a few minutes to start), it shows Waiting for the database with a Check again button, and creates the tables by itself as soon as it can;
asks for the setup token that the deployment shows at the end (or in its outputs);
fills in the administrator's e-mail address you gave the deployment;
shows the storage as fixed.

Everything the wizard sets can also be set with environment variables, for example ConnectionStrings__DocViewCapture, Storage__Provider, Bootstrap__AdminPassword, Site__PublicUrl and Setup__Token. Values set that way win over the wizard, and the wizard shows them as fixed. See the Configuration reference.

If something goes wrong

"Cannot connect" on Test connection. Check the server name. A SQL Server Express on another computer must have TCP/IP turned on and the firewall must allow it. With Windows sign-in, the account shown on the page needs a login on that server.
"This account may not create databases". Ask your database administrator for an empty database (step 1, note).
The wizard asks for a setup token on the server itself. You are probably going through a proxy or a different address. Use http://localhost:<port>/setup on the server, or enter the token.
"That is not the setup token". Copy it again from the installer or from setup-token.txt. After many wrong tries in a row, wait a minute before trying again.