Ascent Capture 5 Web Validation Server Getting Started with Ascent Capture Web Validation Server

(1)

Ascent Capture 5

Web Validation Server ^™

Getting Started with Ascent Capture

Web Validation Server

10300253-000 Revision A

(2)

Copyright

The information contained in this document is the property of Kofax Image Products.

Neither receipt nor possession hereof confers or transfers any right to reproduce or disclose any part of the contents hereof, without the prior written consent of Kofax Image Products. No patent liability is assumed, however, with respect to the use of the information contained herein.

Trademarks

Ascent Capture Web Validation Server is a trademark, and Kofax and Ascent Capture are registered trademarks of Kofax Image Products.

Raster Imaging Technology copyrighted by Snowbound Software Corporation 1993-2001

All other product names and logos are trade and service marks of their respective companies.

Disclaimer

The instructions and descriptions contained in this manual were accurate for Ascent Capture at the time of this manual’s printing. However, succeeding products and manuals are subject to change without notification. Therefore, Kofax Image Products assumes no liability for damages incurred directly or indirectly from errors,

omissions, or discrepancies between the product and this manual.

An attempt has been made to state all allowable values where applicable throughout this manual. Any values or parameters that the customer uses beyond those stated may have unpredictable results.

(3)

How to Use This Guide

This Getting Started guide contains instructions for installing Ascent Capture Web Validation Server, as well as an overview of the product and a description of the user interface. It is intended to be used by system administrators who are installing the product to add Web-based validation capabilities to their Ascent Capture system.

This guide assumes you have a thorough understanding of Internet technologies and Web servers; Microsoft Internet Server and its components; your network and Web Server configuration; the browsers that your remote users will use; and Ascent Capture.

How This Guide is Organized

This guide is divided into the following chapters and appendices:

Chapter 1 – Overview, offers an overview of the Ascent Capture Web Validation Server product. It includes a general description of the modules provided with the product, and a list of the product’s key features.

Chapter 2 – Installing Ascent Capture Web Validation Server, explains how to install the various components that make up Ascent Capture Web Validation Server. It also lists the minimum and recommended operating requirements for the product.

Chapter 3 – Web Validation Server, explains how to add the Web Validation Server module to your Ascent Capture workflow. It includes a description of how the Web Validation Server module works, and an overview of the user interface. It also includes tips for creating batch classes that include Web Validation Server.

(10)

Chapter 4 – Remote Batch Manager, describes how system administrators can monitor the batches being processed by remote validation operators and the remote operators logged into the system. It includes a description of how Remote Batch Manager works, an overview of the user interface, and details about common tasks that can be performed with the module.

Chapter 5 – Remote Validation, describes how your remote validation operators access the Remote Validation interface in their browsers, and then validate documents available to them. It includes a description of how the Remote Validation module works, an overview of the user interface, and details about common tasks that can be performed with the module.

Appendix A – Log Files, provides a description of the log files generated by Web Validation Server.

Appendix B – User Tracking, describes the user tracking information logged for remote validation operators, including the differences between the data logged for remote operators compared to LAN-based operators.

Appendix C – IIS Settings, lists the minimum IIS settings that are required by Ascent Capture Web Validation Server. The minimum settings are automatically configured by a wizard that runs during installation.

Appendix D – Troubleshooting Tips, offers solutions and tips that may prove useful should you encounter problems.

Appendix E – Kofax Technical Support, lists the technical support options provided by Kofax Image Products.

Appendix F – Glossary, provides a list of terms used in this guide and the online help available from the Ascent Capture Web Validation Server modules.

(11)

Using Online Help

The online help provided with Ascent Capture Web Validation Server provides step- by-step instructions for using the product. Once displayed, the help system gives you several ways to look up information:

• Contents tab: This tab provides a categorized list of topics relating to the help system. The information is provided in a typical tree view format, with books and pages that link to associated topics. You can expand the books to locate additional topics within each category.

• Index tab: The Index tab lists pre-defined keywords associated with topics in the help system. You can select/enter a keyword to view the associated topics.

• Search tab: This tab provides a full-text search capability that allows you to locate help topics by specific search words that you supply.

Each Ascent Capture Web Validation Server module provides its own, separate help system. For example, the Web Validation Server module provides its own online help that is not integrated with the online help for the Remote Validation or Remote Batch Manager modules. In addition, the Ascent Capture Web Validation Server online help is not integrated with Ascent Capture online help.

! To access online help from the Web Validation Server module

1 From the Web Validation Server module, select Help menu | Web Validation Server Help Topics. The default topic and the Contents tab will display, from which you can access all topics in the help system for Web Validation Server.

2 Alternatively, click the Help button or press F1 from any Web Validation Server dialog box to display a topic that explains the dialog box.

! To access online help from Remote Validation or Remote Batch Manager 1 From the remote module, click the Help button on the module’s toolbar. The

default topic and the Contents tab will display, from which you can access all topics in the help system for the module.

2 Alternatively, click the Help button from any dialog box to display a topic that explains the dialog box. Then, if desired, click the “Show” button at the top of the topic to display the Contents tab, from which you can access all topics in the help system.

! To access Ascent Capture online help, select “Ascent Capture Help” from your Start menu.

(13)

Chapter 1

Overview

Introduction

Ascent Capture Web Validation Server delivers a trio of modules that extend the use of Ascent Capture’s validation capabilities to anyone equipped with a Web

connection, a PC, and a standard browser. After installation, Web Validation Server can easily be added to the Ascent Capture workflow to automatically send

documents to authorized remote operators for processing. Ascent Capture User Profiles control what documents go to which operators, and all activity can be recorded for centralized tracking and reporting. Once all documents in a batch are validated, the batch can be automatically processed by additional modules in the Ascent Capture workflow and released.

Installing Ascent Capture Web Validation Server is a snap. The software is installed and configured at your central site. Remote operators need only point their browsers to a specified Web address to be authenticated and receive documents to validate. In this way, validation can be performed by part-time workers at home, by subject- matter-experts in their offices, or operators in other time zones, with no specialized equipment or additional installation media required. If contract workers are employed, they can easily be removed as users when their work is finished so that they have no further access to the system.

This chapter introduces the modules provided with Ascent Capture Web Validation Server, and includes a list of key product features. The rest of this guide describes each module in more detail, and explains how to incorporate remote validation into your Ascent Capture processing flow.

(14)

Modules

Ascent Capture Web Validation Server provides the following modules:

• Web Validation Server is an unattended module that allows batches of documents to be routed to remote validation operators, and completed batches to be routed back into the Ascent Capture workflow. One component of Web Validation Server runs as an Ascent Capture client module that automatically routes batches and user information to/from the Ascent Capture server. Another component runs on an IIS Web server to transfer documents to/from remote validation operators. Refer to Chapter 3 for details about the Web Validation Server module.

• Remote Batch Manager is a browser-based monitoring module. System administrators can log into Remote Batch Manager to monitor the progress of batches being processed by remote validation operators, and view a list of remote operators logged into the system. Refer to Chapter 4 for details about the Remote Batch Manager module.

• Remote Validation is a browser-based validation module. It is a small Java application that is automatically downloaded the first time an operator logs in. Remote validation operators log into the Remote Validation module, receive documents to process, and validate index fields. When they are finished with a document, the next document available for them to process is automatically displayed. Refer to Chapter 5 for details about the Remote Validation module.

As an unattended module, Web Validation Server automatically processes batches ready for remote validation per the defined Ascent Capture workflow. Remote validation operators use the browser-based Remote Validation module to validate documents sent to them. When all documents for a batch are completed, the batch can be automatically moved through the rest of the Ascent Capture workflow for additional processing and/or release.

Figure 1-1 shows the relationship of the Ascent Capture Web Validation Server modules to a typical Ascent Capture system.

(15)

Figure 1-1. Ascent Capture Web Validation Server Modules

(16)

Features

With Ascent Capture Web Validation Server, you can quickly and easily add the power of the Internet to your Ascent Capture workflow. The following sections highlight many of the benefits provided with Ascent Capture Web Validation Server.

Easy Installation and Upgrades

Ascent Capture Web Validation Server is easy to install. Most of the software is installed at a Microsoft IIS Web server at your central site, with minimal user intervention and set up required.

For your remote operators, installation is as easy as pointing their browsers to a specific Web address where they are authenticated and, when connecting for the first time, a small Java application is installed for them. The application is saved for future use, and automatically updated if necessary. No other media is required.

Low Ongoing Cost

Ascent Capture Web Validation Server provides a cost effective way to increase the number of validation operators to meet your production requirements. It requires standard Internet/Intranet connections and browsers, and adds no per-user license fees.

Tight Integration with Ascent Capture

The Web Validation Server module is installed to your Ascent Capture installation folder as an Ascent Capture unattended module. Once installed, this custom module can be selected as part of the workflow when you define your batch classes with the Ascent Capture Administration module. Then, when batches based on those batch classes are created, they are automatically routed through Web Validation Server as part of your defined Ascent Capture workflow.

User Tracking

Tracking statistics for remote activity is recorded using the standard Ascent Capture methods. When User Tracking is enabled, statistical records for remote operators are recorded in four database tables, which can be merged into the standard Ascent Capture Stats.mdb file with the User Tracking Merge utility. In this way, both local and remote activity records are stored in a centralized database file that can be used

(17)

Familiar User Interface

As much as possible, all graphical user interfaces for Ascent Capture Web Validation Server mimic those of the standard Ascent Capture modules. For example, the Remote Validation module is very similar to the standard Ascent Capture Validation module. It provides many of the same features, such as an easy-to-use data entry panel, an image viewer, and more.

The Web Validation Server module is a custom module that does not require user intervention for processing. Its user interface is similar to that of the other Ascent Capture unattended modules, such as Recognition Server, OCR Full Text, and Release.

Production Oriented

Documents from all batches queued for Web Validation Server are intelligently sent and cached to as many remote operators as are logged into the system. Remote validation is performed on a document-by-document basis, which allows processing for a batch to be spread across multiple operators. Configurable control ensures that documents are never left in an idle state when operators are on break or between shifts, and completed batches are returned to the Ascent Capture workflow without operator intervention.

Data Security

Encryption and authentication settings can be configured using IIS as desired by the Web administrator. For example:

• The Secure Sockets Layer (SSL) protocol can be enabled for the encrypted transfer of data to and from the remote validation operators. Using SSL is highly recommended.

• An authentication scheme (such as Anonymous, Basic authentication, or NT challenge/response) can be configured to control access to content on the IIS Web server. You can enable the authentication scheme that meets your processing requirements.

Refer to your Microsoft IIS documentation for details on administering security for your Web server.

Internet/Intranet Support

Web Validation Server is suitable for Internet and/or Intranet configurations.

(18)

Effective Throughput

Web Validation Server assumes an effective throughput of at least 40K bits per second. Remote users can connect at slower rates, but may experience delays due to transmission speed. At 40K bits per second or greater, remote validation operators logged into the Remote Validation module under normal conditions should not experience delays due to connection speed.

Proxy Server Support

Ascent Capture Web Validation Server can run in a proxy server environment. For example, it allows the use of a proxy server between the Document Server

component and the Internet connection, and/or a proxy between the remote modules and the Internet connection. Refer to Figure 1-1.

(19)

Installing Ascent Capture Web

Validation Server

Introduction

Ascent Capture Web Validation Server is installed in a distributed way, meaning the software is installed in more than one place. Most of it is installed at the central site where Ascent Capture is located. Software must also be installed by users planning to run the software remotely. The components that must be installed are listed below.

See the section Modules in Chapter 1 for details regarding the different components and how they comprise a typical Ascent Capture Web Validation Server system.

At the Central Site

Document Server

• The Document Server software must be installed at an IIS Web server. The Batch Server must have access to the IIS Web server.

• A Web Validation Server hardware key must be attached to your IIS Web server.

Batch Server

• The Batch Server module must be installed on an Ascent Capture station.

During installation, it is registered as an Ascent Capture custom module.

• An Ascent Capture hardware key must be attached to your Batch Server station.

(20)

At Remote Sites

Remote Modules

• The remote modules (Remote Validation and Remote Batch Manager) must be installed via the Internet/Intranet on each remote station.

This chapter describes how to install the preceding items. It also includes operating requirements for your IIS Web server and remote modules.

Operating Requirements

This section provides information about the requirements for installing Ascent Capture Web Validation Server.

Ascent Capture Requirements

This section lists Ascent Capture requirements.

• Ascent Capture 5.0 (or higher) installed in a client/server configuration or as a standalone installation.

• Ascent Capture hardware key attached to each station as appropriate for the station.

Refer to your Getting Started with Ascent Capture guide for details.

IIS Web Server System Requirements

This section lists the requirements for your IIS Web server station:

• One of the following operating systems:

! Windows NT Server 4.0 with Service Pack 6a (or higher)

! Windows 2000 Server with Service Pack 1 (or higher)

• One of the following Microsoft Internet Information Server (IIS) versions:

! Microsoft Internet Information Server 4.0 (with Windows NT)

! Microsoft Internet Information Server 5.0 (with Windows 2000)

• TCP/IP protocol

• LAN access to Batch Server

(21)

IIS Web Server Hardware Requirements

This section lists the hardware requirements for installing Document Server on the IIS Web server.

Minimum

• Pentium II 300 MHz processor

• 128 Mbytes of memory

• 500 Mbytes of disk space for installation and working space during processing

• 800 X 600 SVGA display with 256 colors

• T1 telephone line (or better) for Internet connection

• Parallel port (standard mode) for hardware key Recommended

• Pentium II 450 MHz processor

• 256 Mbytes of memory (or higher)

• 500 Mbytes of disk space (or higher) for installation and working space during processing

• 1024 X 768 SVGA display with 65K colors

• T1 telephone line (or better) for Internet connection

• Parallel port (standard mode) for hardware key

Note If you plan on having a large number of remote users, you should install the maximum memory for optimal IIS Web server performance.

Remote Module Requirements

This section lists the hardware requirements for running the Remote Validation module and Remote Batch Manager module.

• Pentium II 300 MHz processor (or higher)

• 800 X 600 SVGA display with 256 colors (or higher)

• One of the following operating systems:

! Windows Me

! Windows 2000 Professional with Service Pack 1 (or higher)

! Windows NT 4.0 Workstation with Service Pack 6a (or higher)

(22)

! Windows 98 Second Edition

! Windows 98 with Service Pack 1 (or higher)

! Windows 95 with Service Pack 1 (or higher)

• Microsoft Internet Explorer 5.5

Note Microsoft Internet Explorer must include the Microsoft Virtual Machine.

• TCP/IP protocol

• Internet or Intranet access to the IIS Web server (40 Kbps or better)

• Cookies enabled

Hardware Key Requirements

Ascent Capture Web Validation Server requires hardware keys to be installed on some of your workstations.

• An Ascent Capture Web Validation Server hardware key must be installed on the IIS Web server

• One of the following Ascent Capture hardware keys must be installed on the Batch Server workstation:

! Scan hardware key: Supports custom module processing, in addition to the standard scan functions.

! Workstation hardware key: Supports custom module processing, in addition to the standard workstation functions.

! Custom Module hardware key: Supports custom module processing only.

No other Ascent Capture modules can run on a workstation where a custom module hardware key is installed.

(23)

Installing Ascent Capture Web Validation Server

This section explains how to perform a new Ascent Capture Web Validation Server installation. There are two main components to the Ascent Capture Web Validation Server: Document Server and Batch Server. These can be installed on separate computers or the same computer.

Important Installation Notes

Please read the following notes before you install Ascent Capture Web Validation Server.

Closing Other Applications

Before installing Ascent Capture Web Validation Server, you must close all other applications (including the Control Panel, virus detection software, and all toolbars) on your system.

Windows NT / Windows 2000 Installations

To install Ascent Capture Web Validation Server on a Windows NT or

Windows 2000 workstation, the logged-in user must have Administrator privileges.

Proxy Server Support

Ascent Capture Web Validation Server can run in a proxy server environment. For example, it allows the use of a proxy server between the Document Server

component and the Internet connection, and/or a proxy between the remote modules and the Internet connection.

To use a proxy server between the remote modules and the Internet connection, you must enable and configure the browser proxy server address and port number for every PC that uses a proxy server. To configure your proxy server settings in Microsoft Internet Explorer, open Internet Explorer and select Tools | Internet Options | Connections | LAN settings.

(24)

Installing Document Server

Installation of the Document Server involves the following basic steps, which should be done in the order listed. The Document Server must be installed at your IIS Web server station.

Step 1 Update your operating system, option pack, and service pack, if applicable, on the station to be used as your IIS Web server. This can be on the same or a different station as your Ascent Capture server station or Ascent Capture standalone station. (If you use different stations for your IIS Web server and Ascent Capture station, you must have LAN access between the stations.)

Step 2 Install the Document Server software at your IIS Web server.

Note You may already have some of the preceding items in place. For example, you may already have an IIS Web server station installed and configured. Even so, please read through all the procedures on the following pages to make sure your

installation matches the requirements for the Document Server.

Step 1 – Update your Operating System

Update your applicable operating system with Option Packs and Service Packs. If necessary, you can download them from the Microsoft Web site.

! To update Windows NT Server 4.0

1 Install the Windows NT 4.0 Option Pack on the Windows NT Server to be used as your IIS Web server. Choose the “Custom” installation option and select:

• Internet Information Server (IIS)

• Microsoft Data Access Components

• Microsoft Management Console

• Microsoft Transaction Server

• Other components as required. (The installation program will

automatically select additional components to be installed as required by the preceding items. Do not unselect these additional components.) It is recommended that you accept the directory defaults provided during the installation.

(25)

2 Install Service Pack 6a (or higher).

Important If you installed the Service Pack prior to installing the Windows NT 4.0 Option Pack, you must reinstall the Service Pack before continuing with the Document Server installation.

! To update Windows 2000 Server

1 Install Service Pack 1 (or higher) on the Windows 2000 Server to be used as your IIS Web server.

2 Add the Internet Information Services (IIS) Windows component to your server.

Note Internet Information Services (IIS) is installed on a Windows 2000 Server by default. However, if you upgraded to Windows 2000 Server, IIS will be installed by default only if IIS was installed on the previous version of Windows.

Step 2 – Install Document Server

Install Document Server at the IIS Web server station.

! To install Document Server

1 Shut down any applications (including the Control Panel, virus detection software, and toolbars) that might be running on the IIS Web server.

2 Insert the Ascent Capture Web Validation Server CD into the CD-ROM drive at your IIS Web server station. The CD supports AutoPlay, so the installation will automatically begin. (If it doesn’t, run Setup.exe from the root directory of the CD.)

3 Select Install Document Server. The initial Welcome screen will be displayed.

Click OK.

(26)

4 The System File Update dialog box will appear.

If you are installing on Windows NT, Microsoft Virtual Machine will be installed on your computer if it does not already exist or it has not been updated to the latest version.

Note The Microsoft Virtual Machine installation will ask you if you want to restart the computer. Select “Yes” since a reboot is required in order to continue with the setup program. Note that you will need to restart the installation program after the reboot to continue.

5 The Select Destination Folder dialog box will be displayed. Select the folder where Document Server files are to be installed and click Next.

6 Follow the instructions on your screen to install the software.

7 If this is a new installation, the ACWVS Configuration Wizard will appear.

The wizard will assist you in setting up the following:

• The ACWVS virtual directory.

• The anonymous user account (typically IUSR_computername, where computername is the name of your computer). This will be used as the logon account for remote users. Do not specify a domain user account.

• Automatic password synchronization settings.

To review the Document Server IIS Web server settings set by the ACWVS Configuration wizard, see Appendix C.

8 When prompted to do so, reboot your IIS Web server.

9 Attach the Ascent Capture Web Validation Server hardware key on your IIS Web server.

10 If the Document Server is installed on an NTFS partition, ensure that the Repository folder located in your Document Server WVS folder has full control permissions for the following users:

• The anonymous user account specified in the ACWVS Configuration wizard

• The user who will be logging on to the computer where the Web Validation Server module (Batch Server component) is to be run

(27)

Installing Batch Server

Installation of the Batch Server involves the following basic steps, which should be done in the order listed. Note that the Document Server must be installed at your IIS Web server first.

Step 1 Make sure Ascent Capture is installed on your computer. It can be installed in a client/server configuration or as a standalone station.

Step 2 Install the Batch Server software. Batch Server needs to be installed at an Ascent Capture station.

Step 1 – Install Ascent Capture

Install Ascent Capture on the computer where your Batch Server installation will reside. You can install it in a client/server configuration or as a standalone

installation. In addition, make sure you attach the necessary hardware keys to your Ascent Capture stations. For your scan stations, install and configure your Kofax hardware accelerators (if necessary).

Refer to the Getting Started with Ascent Capture guide, Ascent Capture Installation Road Map, and release notes for information about installing Ascent Capture, installing and configuring Kofax hardware accelerators, and attaching hardware keys.

Step 2 – Install Batch Server

Install Batch Server on your Ascent Capture standalone or client workstations. If Ascent Capture is installed in a client/server configuration, you must install Batch Server on the client station where you plan to run Batch Server. In addition, for batch class setup purposes, you must also install Batch Server on all stations where you plan to run the Administration module.

! To install Batch Server

1 Shut down any applications (including the Control Panel, virus detection software, and toolbars) that might be running on the workstation.

2 Insert the Ascent Capture Web Validation Server CD into the CD-ROM drive at your Ascent Capture standalone or client workstations. The CD supports AutoPlay, so the installation will automatically begin. (If it doesn’t, run Setup.exe from the root directory of the CD.)

3 Select Install Batch Server. The initial Welcome screen will be displayed.

(28)

4 From the Welcome screen, click OK. The Document Server Location dialog box will be displayed. Enter the path to your Document Server root installation folder (WVS) and click Next.

6 When the installation is complete, the initial menu screen will display. Click Exit to end the installation program.

7 Ensure that one of the following Ascent Capture hardware keys is attached to your Batch Server workstation:

• Ascent Capture Scan hardware key

• Ascent Capture Workstation hardware key

• Custom Module hardware key

Note The Batch Server is automatically registered as a custom module with Ascent Capture during the installation.

(29)

Installing the Remote Modules

This section explains how to install the Ascent Capture Web Validation Server remote modules. Note that the following remote modules are installed via the Internet/Intranet during the installation process:

• Remote Validation

• Remote Batch Manager

Note Access to each remote module is controlled by User Profile privileges set in the Ascent Capture Administration module. Refer to Chapter 3 for details about enabling User Profiles.

Installing Remote Validation and Remote Batch Manager

Installation of the remote modules involves the following basic steps, which should be done in the order listed. Note that the Document Server and Batch Server components must be installed first.

Step 1 Configure the necessary browser settings.

Step 2 Install the remote modules on your computer.

Step 1 – Configure Necessary Browser Settings

The browser security settings must be set to default levels. This will enable all required settings for the remote modules including the acceptance of cookies. If cookies are not enabled, the user is notified that they must enable cookies to continue the installation. Normally, the user’s browser settings will already be set to default levels.

Note The cookie is used to verify the remote modules are installed. No sensitive information is contained in the cookies.

! To configure necessary browser settings 1 Start your browser.

2 From the menu bar, select Tools | Internet Options | Security tab. The Internet Options dialog box will be displayed, as shown in Figure 2-1.

(30)

Figure 2-1. Internet Options Dialog Box - Security Tab

3 Select the appropriate Web content zone (for example, “Internet” or “Local Intranet”).

4 Click “Default Level.” Note that if the “Default Level” button is disabled, you are already using default level security settings.

5 Click OK to save your settings.

Step 2 – Install Remote Modules

Install the remote modules via the Internet/Intranet.

Note Each user will have to install the remote modules the first time they try to log in regardless of whether they are using the same computer. This is because the installation cookie is stored by user.

(31)

! To install the remote modules 1 Start your browser.

2 In the Address or Location box, enter the Web address of the Document Server. For example, enter:

http://YourServer/acwvs

where YourServer is the name of your IIS Web server on which the Document Server is installed. The installation page will appear, as shown in Figure 2-2.

Figure 2-2. Remote Modules – Installation Page

3 Wait for the download size message to appear. Then, click Install Now.

Note In some cases, you may be prompted to allow InstallShield and/or Kofax Image Products to install software on your computer. If this occurs, click Yes to continue the installation process.

(32)

Note If you have Netscape 6 installed on your machine, you will be warned that Netscape is not a supported browser.

5 Close your browser after the installation is complete.

6 To access a remote module, restart your browser and enter one of the following:

• For Remote Validation: http://YourServer/acwvs

• For Remote Batch Manager: http://YourServer/acwvs/rbm

Reinstalling the Remote Modules

If you need to reinstall the remote modules, you must point your browser to a different Document Server Web address.

! To reinstall the remote modules 1 Start your browser.

2 In the Address or Location box, enter the Web address of the Document Server. For example, enter:

http://YourServer/acwvs/setup

where YourServer is the name of your IIS Web server on which the Document Server is installed. The installation page will appear, as shown in Figure 2-2.

3 Wait for the download size message to appear. Then, click Install Now.

4 Follow the instructions on your screen to reinstall the software.

5 Close your browser after the installation is complete.

6 To access a remote module, restart your browser and enter one of the following:

• For Remote Validation: http://YourServer/acwvs

• For Remote Batch Manager: http://YourServer/acwvs/rbm

(33)

Uninstalling Ascent Capture Web Validation Server

This section explains how to uninstall Ascent Capture Web Validation Server components.

! To uninstall Document Server

1 Ensure all batches that contain the Web Validation Server queue have been processed.

Note If any batches exist in Web Validation Server, the uninstall will fail.

2 Open the Add/Remove Programs utility available from the Windows Control Panel where Document Server is installed.

3 Select “ACWVS Document Server 5.0” and click Add/Remove.

Note Uninstalling the Document Server will not remove or change your IIS Web server settings previously configured for Document Server. For example, it will not remove your ACWVS virtual directory or change its properties.

! To uninstall Batch Server

1 Remove the Web Validation Server queue from all Ascent Capture batch classes.

2 Open the Add/Remove Programs utility available from the Windows Control Panel where Batch Server is installed.

3 Select “ACWVS Batch Server 5.0” and click Add/Remove.

Note The uninstall program unregisters the custom module from Ascent Capture. If the Web Validation Server queue exists in any batch class, the uninstall program will fail.

(34)

! To uninstall the Remote Modules

1 Open the Add/Remove Programs utility available from the Windows Control Panel where the remote modules are installed.

2 Select “ACWVS Remote Modules 5.0” and click Add/Remove.

Note Uninstalling the remote modules will not delete your installation cookie. If you need to reinstall, refer to the section Reinstalling the Remote Modules on page 20.

(35)

Web Validation Server

Introduction

The Web Validation Server module allows Ascent Capture to route batches of documents to remote operators who can validate index fields via an

Internet/Intranet connection. Web Validation Server is an unattended module that can be added to the Ascent Capture workflow as part of a batch class, just like any other Ascent Capture queue.

Internally, the Web Validation Server comprises two components:

• The Document Server component runs on an IIS Web server to send and retrieve documents to/from remote operators via the Internet or Intranet.

• The Batch Server component runs on an Ascent Capture workstation with LAN access to the Document Server. If Ascent Capture is installed in a client/server configuration, this will be an Ascent Capture client station.

Batch Server is responsible for sending and retrieving batch and user information to/from the Document Server.

Figure 3-1 illustrates the components installed for Web Validation Server, and their relationship to Ascent Capture and the remote modules (Remote Validation and Remote Batch Manager).

(36)

Figure 3-1. Web Validation Server and Remote Modules

(37)

How Web Validation Server Works

When batches are queued for Web Validation Server, the Batch Server component transfers information about the batches and user profile information from the Ascent Capture database to the Document Server component. Then, remote validation operators who are logged into the Document Server via the Internet/Intranet receive the documents to be validated. See Figure 3-1.

Remote validation operators work on one document at a time from a Remote Validation module. The Remote Validation module is similar to the standard Ascent Capture Validation module, except that it runs in a browser. Just like Validation, Remote Validation allows operators to view documents and validate/enter index field data. However, unlike standard Validation processing, the documents that are sent to remote validation operators are not necessarily from the same batch or in sequential order. Refer to Chapter 5 for more information about the Remote Validation module.

Administrators can monitor the activities of the remote validation operators from the Remote Batch Manager module. With this module, administrators can view

information about the remote operators logged into the system, the documents the operators are processing, and more. Refer to the section Monitoring Remote Processing on page 45 for more information.

Once all of the index fields for a document are processed, the document is sent back to the Document Server. The Document Server “holds” the document until all documents from the batch are processed. As soon as all documents from a batch are processed, the Batch Server retrieves information about the batch (including user tracking data), closes the batch, and sends the batch to the next Ascent Capture module for processing.

Note Web Validation Server polls at specified intervals for batches to process, user profile information, and user tracking data. If any are found, they are transferred to/from the Document Server via the Batch Server component. Refer to the section Polling for Batches to Process on page 39 for details.

(38)

Quick Tour of Web Validation Server

The user interface for Web Validation Server is similar to other unattended Ascent Capture modules. It provides a menu bar from which you can select various operating preferences, an area that displays progress information about the batches being processed, and an event log into which messages are listed as processing events occur.

Figure 3-2. Web Validation Server - Main Screen

(39)

Batch Menu

Two options are available from the Batch menu:

Process Next Batch

Use this option to immediately poll for the next batch to

process (plus user profile information and user tracking data, if any) without waiting for the next scheduled polling time. Refer to Polling Interval in the section Tools Menu below for more information about polling times.

Note that between polling times, the amount of time (in minutes and seconds) that has passed since the last polling time is displayed in the status bar. Refer to the section Status Bar on page 30 for details.

Exit

Use this option to stop polling for batch and user information and exit Web Validation Server. This menu item exits the Batch Server component only.

However, once exited, the Batch Server component will not be available to transfer batch and user information to/from the Document Server component.

Refer to the section Exiting Web Validation Server on page 47.

Tools Menu

The options on the Tools menu allow you to select a polling interval and various logging options.

Polling Interval

As an unattended module, Web Validation

Server requires no user intervention to process batches. Once started, it automatically checks (or polls) for batches to process, user profile information, and user tracking data. The polling interval is the amount of time (in minutes) between polling times. You can select from 1 to 60 minutes. Refer to the section Polling for Batches to Process on page 39 for more information.

Logging Options

As documents are processed, messages are generated that describe the results of processing. The messages are listed in the Event Log area at the bottom of Web Validation Server’s main screen. (See Figure 3-2.) The logging options are:

• Auto-Scroll: Select this option to enable or disable scrolling in the Event Log area. When enabled, the list scrolls as messages are logged so that the last message is visible at the bottom of the log area.

(40)

• Log to File: In addition to displaying event messages in the Event Log area, you can log events to a log file. If you enable this feature, events are logged to the file InstallationPath\Images\BatchNumber\Log\BchSrv.txt, where

InstallationPath is the path to your Ascent Capture installation, and

BatchNumber is a folder created by Ascent Capture for storing images and log files. The name of the folder is a number assigned by Ascent Capture.

Note that batch log files are temporary; they are automatically deleted when a batch is released. You can review the log file for a batch at any time before the batch is released from Ascent Capture. If you want to be able to review your log files after your batches are released, you can copy the log files to a folder outside of the Ascent Capture installation folder. Refer to Appendix A for more information about Web Validation Server log files.

Recover Orphan Batches

When batches are queued for Web Validation Server, batch information is sent to the Document Server. At that point, the batch information exists in the Ascent Capture database, and also in the Document Server. This means that, for typical installations, information for batches being processed by Web Validation Server exists on two different workstations.

An orphan batch is one for which the Document Server’s batch information becomes corrupted or otherwise unavailable, and documents cannot be sent to remote operators or sent back into the Ascent Capture database. For example, this might occur after a catastrophic hardware failure that corrupts the batch information available to the Document Server.

The “Recover Orphan Batches” option allows you to re-establish batches for processing by Web Validation Server. Selecting this option causes batch information for the orphan batches to be resent from the Ascent Capture

database to the Document Server at the next polling time. Once resent, the batches will be available for remote processing in the state they were in before any previous remote processing occurred. Only orphan batches are resent; batches for which all information was intact in the Document Server are not resent.

Warning Using the “Recover Orphan Batches” option will cause any validation already performed by remote validation operators on the batches being

recovered to be lost. Therefore, the “Recover Orphan Batches” option should be used by system administrators with care, and only after all other options are considered. If you believe you have orphan batches, refer to Appendix D for troubleshooting tips before you attempt to recover the batches.

(41)

Help Menu

The Help menu provides two options:

Web Validation Server Help Topics

Use this option to display online help for Web Validation Server. Note that the topics are not integrated into the standard Ascent Capture help system. You can display Ascent Capture online help from the Ascent Capture program group.

About Web Validation Server

Select this option to display information about Web Validation Server, such as the version number of the software and copyright information. In addition, you can access the Kofax Technical Support Web pages from the About box.

Current Batch and Document Information

Even though the Web Validation Server module is an unattended module, you can monitor batch progress by watching the main screen. As batches are processed through the Web Validation Server module, information about the batches is displayed in the Current Batch Information, Current Batch Progress, and Current Document Information areas on the main screen. The information reflects the transfer of information from the Batch Server component to the Document Server component, and vice versa. Refer to Figure 3-2 for an example.

Event Log

As documents are processed, event messages are generated that describe the results of processing. The messages are listed in the Event Log area at the bottom of the Web Validation Server’s main screen.

Tip Some messages may be too long to be completely visible in the Event Log area.

For these messages, you can double-click on them to display the complete message.

If desired, you can specify that event messages also be logged to a log file. For more information about event logging, refer to the section Logging Options on page 27. For more information about Web Validation Server log files, refer to Appendix A.

(42)

Status Bar

The status bar at the bottom of the Web Validation Server screen displays information about the current action being performed by Web Validation Server. In addition, between

polling times, the time (in minutes and seconds) since the last polling time is displayed on the right side of the status bar.

Adding Web Validation Server to a Batch Class

Batches to be validated by remote operators are queued for Web Validation Server per the workflow specified in the batch classes. To send documents to remote validation operators, you must add the Web Validation Server module to your list of queues for a batch class. You do this from the Ascent Capture Administration module when you define your batch classes. Refer to your Getting Started with Ascent Capture guide or your Ascent Capture online help for details about batch classes.

(Ascent Capture online help keyword: Batch classes)

Note Web Validation Server must be installed before you can add it to a batch class.

Refer to Chapter 2 for more information about installing Web Validation Server.

! To add Web Validation Server to a batch class

1 From the Administration module, do one of the following:

• To create a new batch class, select the Batch class tree view tab. From the menu bar, select File | New | Batch Class. The Create Batch Class dialog box will display. From the General tab, enter/specify the desired settings.

• To edit an existing batch class, select the desired batch class from the Batch class tree view tab. From the menu bar, select Edit | Properties. The Batch Class Properties dialog box will display.

2 Select the Queues tab.

3 From the list of Available Queues, select “Web Validation Server” and click Add. Web Validation Server will appear in the list of Selected Queues in a position determined by the other modules already in the list. If desired, you can change its position.

Note If Validation is in the list, Web Validation Server must follow it. In addition, to use batch totals or custom validation scripts for any index field,

(43)

Batch Class Considerations

The following sections describe limitations for batch classes that include Web Validation Server.

Batch Editing

With Web Validation Server, remote validation operators cannot edit batches.

Therefore, unlike the standard Ascent Capture Validation and Verification modules, there is no option available to enable batch editing for remote validation operators. In addition, no Properties dialog box is available for the Web Validation Server module.

Ascent Capture Values

You can use Ascent Capture Values for index fields to be validated by remote validation operators. Refer to your Ascent Capture documentation for a list of available values. (Ascent Capture online help keyword: Ascent Capture Values) Note the following:

• {Remote Validation User ID}: This Ascent Capture Value has meaning only for documents processed through Web Validation Server. It expands to the user ID defined in the User Profile of the remote validation operator who processed the document. Note the following:

! If assigned to an index field, {Remote Validation User ID} will expand to the user ID of the first remote validation operator who processed the document. If the document is started by one remote operator and finished by another, the value will not change unless it is explicitly changed by the second operator.

! If used for a release value, {Remote Validation User ID} will expand to the user ID of the remote validation operator who completed the document.

• {Station ID}: This Ascent Capture Value expands to the station ID of the station on which the Batch Server component of Web Validation Server is running. It does not expand to an identifier for the remote station on which a document was processed.

Batch Totals

Because not all documents in a batch are processed by the same remote operator, Web Validation Server cannot process batch totals. To use batch totals, you must add the Validation module after Web Validation Server in the list of selected queues for the batch class. Otherwise, you will not be able to publish your batch class.

(44)

During remote validation, the Remote Validation module will validate index fields for which batch totals are specified, but will not calculate the batch totals. Then, when the batch is sent to Validation, the batch totals will be calculated and compared against the expected batch totals. (Ascent Capture online help keyword: Batch

totaling)

Sticky Fields

Because remote operators process documents in the order they are received, and the documents are not necessarily from the same batch or in sequential order, Web Validation Server cannot effectively retain a field value from one document to the next. Therefore, a publish warning will be generated when you publish a batch class for which sticky fields are defined and the Web Validation Server is part of the specified workflow.

During remote validation, the Remote Validation module will treat sticky fields as if the “sticky” attribute is set to False. No “sticky” values will be preserved from one document to the next. (Ascent Capture online help keyword: Field attributes)

Custom Validation Scripts

During remote validation, the Remote Validation module will perform the default validation for index fields. This includes verifying that the data meets the data type and length requirements defined for the field types associated with the index fields.

However, Remote Validation cannot process custom validation scripts. To add custom scripts to any batch class that includes Web Validation Server, you must add the Validation module after Web Validation Server in the list of selected queues for the workflow. Otherwise, you will not be able to publish your batch class.

Then, during processing, the Remote Validation module will validate index data based on the data type/length associated with each field. When the batch is sent to the Validation module, the index data processed by the remote validation operator will be validated against any custom scripts associated with the index fields. (Ascent Capture online help keyword: Validation scripts)

eDocuments (Non-Image Files)

Web Validation Server cannot process batches that contain non-image files.

Therefore, if you try to publish a batch class for which the non-image file support feature is enabled and Web Validation Server is defined as a processing queue, a

(45)

Enabling User Profiles

User Profiles allow you to define and manage user privileges for certain types of Ascent Capture processing. For example, they specify:

• User log in ID and optional password

• User access to batch classes

• User access to Ascent Capture modules

• Group profile membership

• Access to administrative functions and utilities

To use the Web Validation Server module, you must enable the Ascent Capture User Profiles feature and define the appropriate access rights for your users. This provides the mechanism for controlling:

• Remote access to the remote modules. Only valid users with appropriate module access rights will be able to log into the Remote Validation module and/or the Remote Batch Manager.

• Remote access to batch classes. Only valid users with appropriate batch class access rights will be able to process documents from the Remote Validation module.

• Access to Web Validation Server module. Only valid users with appropriate access rights will be able to run Web Validation Server. In addition, the user’s batch class access rights control which batches can be processed. Only batches based on the valid batch classes for the user who logs into Web Validation Server will be processed through Web Validation Server.

Table 3-1 lists the minimum access rights required for Web Validation Server users.

Table 3-1. Minimum Access Rights for Web Validation Server Operators User Profile

Item Web Validation

Server User Remote

Validation Operator Remote Batch Manager User

User ID " " "

Password ¹ " " "

Module access Web Validation Server Web Validation Server Batch Manager Batch class

access

All necessary batch classes

n/a

1 Passwords are optional, but highly recommended.

(46)

Note The Ascent Capture User Profiles feature must be enabled for processing with Web Validation Server to work. If the User Profiles feature is not enabled, you will not be able to publish batch classes that specify Web Validation Server as part of the workflow. In addition, if the User Profiles feature is disabled after your batch classes are published, your remote operators will not be able to log into the Remote

Validation and Remote Batch Manager modules. Refer to your Getting Started with Ascent Capture guide or your Ascent Capture online help for details about enabling and defining User Profiles. (Ascent Capture online help keyword: User profiles)

! To enable User Profiles

1 Start the Administration module.

2 From the menu bar, select Edit | User Profiles to display the User Profiles dialog box.

3 Check the check box to enable User Profiles.

4 To create or edit a user, do the following:

• To create a user, right-click in the Users section and select New from the context menu.

• To edit a user, right-click on the user listed in the Users section and select Edit from the context menu.

The User Profile Properties dialog box will display.

a From the General tab, enter the desired User ID and password, and other options as desired for the user.

b From the Assigned Batch Classes tab, select or edit the assigned batch classes for the user.

c From the Assigned Modules tab, select or edit the assigned modules for the user.

d From the Group Members tab, select or edit the assigned groups for the user.

Refer to Table 3-1 for a list of minimum access rights for Web Validation Server users.

5 Click Apply to save your changes. Then, click OK to close the User Profile Properties dialog box.

6 If you are finished editing User Profiles, click Save to save your changes, and

(47)

7 To create or edit a group, do the following:

• To create a group, right-click in the Groups section and select New from the context menu.

• To edit a group, right-click on the group listed in the Groups section and select Edit from the context menu.

The Group Profile Properties dialog box will display.

Note When Web Validation Server is installed, it is automatically assigned to everyone via the Everyone group. If desired, you can edit your User Profiles to restrict access.

a From the General tab, select or edit the name for the group.

b From the Assigned Batch Classes tab, select or edit the assigned batch classes for the group.

c From the Assigned modules tab, select or edit the assigned modules for the group.

d From the Members tab, select or edit the assigned members to be part of the group.

8 Click Apply to save your changes. Then, click OK to close the Group Profile Properties dialog box.

9 If the Save button is enabled, click Save to save your changes. Then, click Close to close the User Profiles dialog box.

(48)

Starting Web Validation Server

Processing batches through Web Validation Server requires that the Batch Server component and the Document Server component work together. The Batch Server allows batches and user information to be transferred to/from the Document Server, which in turn allows documents and other information to be transferred to/from remote validation operators. Refer to the section Introduction on page 23 for details about the Batch Server and Document Server components.

Typically, you will want to have the Batch Server and the Document Server running at the same time. That way, all batches queued for Web Validation Server can be processed without delay. If one component is running but the other is not, processing through Web Validation Server will not be able to complete.

For example, consider this scenario: With the Batch Server and Document Server components running, batches become queued for Web Validation Server. The Batch Server transfers the batches and user profile information to the Document Server, and documents from the batches are made available to remote validation operators logged into the system. If Batch Server is then shut down, the remote validation operators will still be able to receive documents to process from those already transferred to the Document Server. However, no finished batches or user tracking data will be transferred from the Document Server to the Batch Server. In addition, no new batches queued for Web Validation Server will be processed.

Document Server

The Document Server runs on an IIS Web server, which must be running for remote operators to log into the system and access documents.

Note If the IIS Web server station is shut down or the default Web site is taken offline, remote users will not be able to log into the Document Server, receive documents to process, or return finished documents and user information. Refer to your Microsoft Internet Information Server documentation for details about checking the status of your default Web site and bringing Web sites online.

(49)

Batch Server

You can start the Batch Server from the Windows Start menu, the Ascent Capture Batch Manager, or from the command line. Once started, any batches ready for Web Validation Server will be sent to the Document Server for distribution to remote validation operators. Any finished batches available from the Document Server will be transferred to the Batch Server and made available to the next queue in the Ascent Capture workflow.

Notes If Batch Server is not running, batches to process, user profile information, and user tracking data will not be sent to the Document Server. In addition, completed batches will not be received from the Document Server.

Unlike other Ascent Capture unattended modules (Recognition Server, OCR Full Text, and Release), Batch Server cannot run as a service.

! To start Batch Server from the Start menu

1 Click Start | Programs | Ascent Capture | Web Validation Server. The Batch Server component will start.

2 Any user profile changes and batches queued for Web Validation Server will be transferred to the Document Server. Any finished batches and user tracking statistics will be transferred from the Document Server. Batch Server will remain open until you explicitly close it.

! To start Batch Server from Batch Manager

1 From Ascent Capture Batch Manager’s list of batches, select a batch that is ready for Web Validation Server. Such batches will show “Web Validation Server” in the Queue column and “Ready” in the Status column.

2 Do one of the following:

• Right-click the batch name. From the context menu, select Process.

• Select the Process Batch button from the toolbar.

The Batch Server component will start.

3 The selected batch will be transferred to the Document Server. When the transfer is complete, Batch Server will automatically close.

Ascent Capture 5 Web Validation Server Getting Started with Ascent Capture Web Validation Server

Ascent Capture 5

Web Validation Server ™

Getting Started with Ascent Capture

Web Validation Server

Contents

How to Use This Guide

How This Guide is Organized

Related Documentation

Using Online Help

Chapter 1

Overview

Introduction

Modules

Features

Easy Installation and Upgrades

Low Ongoing Cost

Tight Integration with Ascent Capture

Production Oriented

Data Security

Internet/Intranet Support

Effective Throughput

Proxy Server Support

Installing Ascent Capture Web

Validation Server

Introduction

At the Central Site

At Remote Sites

Operating Requirements

Ascent Capture Requirements

IIS Web Server System Requirements

IIS Web Server Hardware Requirements

Remote Module Requirements

Hardware Key Requirements

Installing Ascent Capture Web Validation Server

Important Installation Notes

Installing Document Server

Installing Batch Server

Installing the Remote Modules

Installing Remote Validation and Remote Batch Manager

Reinstalling the Remote Modules

Uninstalling Ascent Capture Web Validation Server

Web Validation Server

Introduction

How Web Validation Server Works

Quick Tour of Web Validation Server

Batch Menu

Tools Menu

Help Menu

Current Batch and Document Information

Event Log

Status Bar

Adding Web Validation Server to a Batch Class

Batch Class Considerations

Enabling User Profiles

Starting Web Validation Server

Document Server

Batch Server

Web Validation Server ^™