Getting Started with. Ascent Capture Internet Server Revision A

Transcription

1 Ascent Capture Internet Server 5 Getting Started with Ascent Capture Internet Server Revision A

2 Copyright Copyright 2001 Kofax Image Products. All Rights Reserved. Printed in USA. 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 Internet Server is a trademark, and Kofax, Ascent Capture, and Adrenaline are registered trademarks of Kofax Image Products. All other product names and logos are trade and service marks of their respective companies. Disclaimer The instructions and descriptions contained in this document were accurate at the time of printing. However, succeeding products and documents are subject to change without notice. Therefore, Kofax Image Products assumes no liability for damages incurred directly or indirectly from errors, omissions, or discrepancies between the product and this document. An attempt has been made to state all allowable values where applicable throughout this document. Any values or parameters used beyond those stated may have unpredictable results.

3 Contents How to Use This Guide...vii Introduction...vii How This Guide is Organized...vii Related Documentation...viii 1 Overview...1 Introduction... 1 Components... 2 Features Installing ACI Server...5 Introduction... 5 Operating Requirements... 6 Installing ACI Server... 8 Important Installation Notes... 8 Closing Other Applications... 8 Information You Need During the Installation... 8 Windows 2000/Windows NT Installations... 8 UNC Support... 8 Read-Only Files... 9 ACIS Configuration Wizard for IIS Settings... 9 Proxy Server Support... 9 Custom Module Support... 9 Server Certificates Getting Started with Ascent Capture Internet Server 5 iii

4 Contents Setting Up Your Central Site...11 Step 1 Install Windows 2000 Server or Windows NT Server...11 Step 2 Install Ascent Capture...12 Step 3 Install the ACI Server Software on the IIS Web Server...13 Step 4 - Synchronize Date/Time Settings...16 Setting Up a Remote Station...17 Step 1 Install Ascent Capture...17 Step 2 Configure the Appropriate Internet Explorer Security Settings...18 Step 3 Install the ACI Server Remote Synchronization Agent...20 Step 4 Download Batch Classes and Configure Polling Times...22 Upgrading ACI Server...23 Converting Batches From Previous Releases...23 Upgrading Your Central Site...23 Step 1 Stop the Default Web Site on Your IIS Web Server...24 Step 2 Upgrade Ascent Capture and Republish Batch Classes...24 Step 3 Upgrade the ACI Server Software on the IIS Web Server...25 Step 4 Restart the Default Web Site on Your IIS Web Server...26 Upgrading Your Remote Site...26 Step 1 Process Batches...26 Step 2 Upgrade Ascent Capture...27 Step 3 Upgrade the Remote Synchronization Agent Software...27 Step 4 Download Batch Classes and Configure Polling Times...29 Uninstalling ACI Server Configuring ACI Server...31 Introduction...31 ACI Server Web Pages Overview...32 Central Administration Page...33 Installation Page...34 Client Configuration Page...35 Manual Synchronization Page...36 Change Password Page...37 Remote Synchronization Agent Windows Taskbar Icon...38 Configuring ACI Server Settings...39 Ascent Capture Modules...39 Using the Quality Control Module...40 Using Custom Modules...40 Polling...41 Configuring Polling Times...42 iv Getting Started with Ascent Capture Internet Server 5

5 Contents 4 Using ACI Server...49 Introduction Downloading Batch Classes from the Central Site Initiating the Download Process Creating and Processing Batches at the Remote Station Uploading Batches to the Central Site Monitoring Batch Activity Batch Class Considerations Image Folders OCR Dictionaries User Tracking Partial Batch Release Database Validation Monitoring Event Log Activity A Glossary...61 B Custom Module Registration...65 Introduction Registering a Custom Module C IIS Settings...67 Introduction ACIS Required Properties Ascent Required Properties Ascent Capture and IIS Web Server on Different Computers Upload Required Properties Anonymous User Account Allow IIS to Control Password Settings NTFS Security Settings ACIS Folder Permissions Ascent Folder Permissions Images Folder Permissions Upload Folder Permissions Scripts Folder Permissions Getting Started with Ascent Capture Internet Server 5 v

6 Contents Common Files Permissions...79 System Variables TEMP Folder Permissions...79 Identifying Your Component Services or Transaction Server User...80 D Kofax Technical Support...83 Introduction...83 First Line Support...83 Internet Support Support...83 Pay-As-You-Go Support...83 Kofax Scanner Configurator...84 Contact Numbers...84 Index...85 vi Getting Started with Ascent Capture Internet Server 5

7 How to Use This Guide Introduction This Getting Started guide provides information about installing and using the Ascent Capture Internet Server module (ACI Server). It is intended to be used by system administrators who are installing ACI Server to add remote scanning capabilities to their Ascent Capture installation. This guide assumes that you have a working knowledge of the Internet and Web servers, Microsoft Internet Information Server and its components, your network configuration, and Ascent Capture. How This Guide is Organized This guide consists of the following chapters and appendices: Chapter 1 provides an overview of the ACI Server module. Chapter 2 explains how to install the ACI Server module. It provides instructions for installing and configuring a Web server at your central site, as well as installing the software on your remote stations. It also lists the minimum and recommended operating requirements for the product. Chapter 3 describes the ACI Server user interface. It also explains how to configure settings to manage Ascent Capture batch processing activity between your central site and remote stations. Chapter 4 explains how to download batch classes and settings from your central site, process and upload batches and data from your remote site, and monitor batch processing activity. Appendix A provides a glossary of ACI Server terms. Appendix B explains how to register Ascent Capture custom modules. Getting Started with Ascent Capture Internet Server 5 vii

8 How to Use This Guide Appendix C lists the IIS settings that are automatically configured by the ACIS Configuration Wizard during installation. Also included is information about additional settings beyond those set by the wizard that your configuration may require. Appendix D provides information on the technical support options available for Kofax products. Related Documentation ACI Server includes the following printed and browser-based documentation: This Getting Started with Ascent Capture Internet Server 5 guide provides instructions for installing, configuring, and using the ACI Server module with Ascent Capture. All of the ACI Server browser pages provide links to online help pages, which describe the user interface items on the pages. Just click the Help link on the navigation bar from any ACI Server page to access the information. Late-breaking information is provided in release notes, available from your ACI Server package and the Kofax Web site. You should read through these notes carefully, as they contain information that is not included in the Getting Started with Ascent Capture Internet Server 5 guide or help pages. For more information about Ascent Capture, refer to the following documentation available from your Ascent Capture software package: The Getting Started with Ascent Capture 5 guide The Ascent Capture 5 Installation Roadmap The Ascent Capture 5 release notes The online help (available from any Ascent Capture module) For more information about Microsoft products, including Microsoft Internet Information Server, refer to your Microsoft documentation. Tip For additional information about Ascent products, visit the Kofax Web site at and go to the Technical Support page. The Technical Support page provides product-specific information, such as current revision levels, the latest drivers and software patches, Frequently Asked Questions (FAQs), and technical tips. In addition, updates to product release notes and other documentation (if any) are available from the Technical Support page. viii Getting Started with Ascent Capture Internet Server 5

9 Chapter 1 Overview Introduction The Ascent Capture Internet Server (ACI Server) module adds Internet/Intranet processing capabilities to Ascent Capture. With this module, Ascent Capture stations can be connected to a central site via the Internet (or Intranet) to assist in the production document and data capture process. Batches can be scanned and processed at the remote site, and then uploaded to the central site for further processing and release. This chapter describes the following: ACI Server components ACI Server features Getting Started with Ascent Capture Internet Server 5 1

10 Chapter 1 Components ACI Server components are installed at your central site and one or more remote stations as follows: The ACI Server software is installed on an IIS Web server at your central site. It acts as a broker between your central Ascent Capture database and your remote stations. The Remote Synchronization Agent is installed on stations at your remote sites to manage batch classes downloaded from the central site and upload completed batches to the central site. Batches created at a remote station are processed through all the modules set to run at the remote site. When the remote processing is complete, the batches can be uploaded to the central site. Once uploaded, the batches are integrated into the central site s Ascent Capture system for further processing and release. Remote Site Central Site Remote Station (Standalone) Remote Station (Standalone) Internet Firewall IIS Web Server Admin Station Recognition Station OCR Station Release Station Ascent Capture Server LAN Client LAN Client LAN Client LAN Client Ascent Capture Database Scan Station QC Station Validation Station LAN Client LAN Client LAN Client Figure 1-1. Example Ascent Capture Internet Server Configuration 2 Getting Started with Ascent Capture Internet Server 5

11 Overview Features ACI Server eliminates the common and costly practice of shipping documents from remote offices to a central site for processing. It supports remote scanning and processing of documents via the Internet or Intranet, and allows IT and IS managers to develop and implement enterprise-wide capture solutions. With ACI Server, documents can be scanned inexpensively at remote stations and then automatically uploaded to the central site, securely and reliably. In addition, ACI Server provides the following: Centralized administration: The Ascent Capture system administrator can centrally manage configuration information, schedules for uploading batches, and batch class definitions for all remote stations. Quick and easy deployment: The central site s Web server can be configured quickly and easily using Microsoft Internet Information Server (IIS). Remote stations can be configured quickly and easily using Microsoft Internet Explorer. Data security: Authentication and encryption settings can be configured using IIS as desired by the Web administrator. For example, an authentication scheme (such as Anonymous, Basic authentication, or NT challenge/ response) can be configured to control access to content on the central site s Web server. If desired, the Secure Sockets Layer (SSL) protocol can be enabled for encrypted transfer of data between the central and remote sites. Refer to your Microsoft documentation for details on administering security for your central site s Web server. Offline capability: With ACI Server, remote stations do not have to be connected to the central Ascent Capture server while processing batches. You can set your remote stations to synchronize with your central site at predetermined intervals or on demand. Internet/Intranet support: ACI Server is suitable for Internet and/or Intranet configurations. Scalable: Multiple Web servers can be deployed across one central site. One or more remote stations can be set up to use a Web server. Customizable Web pages: The interface for the software that runs from remote stations is in the form of ASP and HTML pages. You can use any HTML editor, or even Notepad, to change the look of the pages to suit your own needs. For example, you may want to add your own company logo. Getting Started with Ascent Capture Internet Server 5 3

12 Chapter 1 4 Getting Started with Ascent Capture Internet Server 5

13 Chapter 2 Installing ACI Server Introduction The ACI Server module is installed in a distributed way, meaning the software is installed in more than one place. Most of it is installed on a Microsoft Information Internet Server (IIS) Web server at your central site. Software must also be installed on your remote stations to allow the stations to periodically connect to the server to download batch classes and upload completed batches. The components that must be installed are listed below. At the Central Site Ascent Capture must be installed at your central site. It can be installed in a client/server configuration or as a standalone installation. ACI Server software must be installed on an IIS Web server at your central site. The IIS Web server must have access to the Ascent Capture database. Ascent Capture hardware keys must be attached to your Ascent Capture stations, and an ACI Server hardware key must be attached to your IIS Web server. At the Remote Sites Ascent Capture must be installed as a standalone installation on each remote station. The ACI Server Remote Synchronization Agent must be installed on all remote standalone stations. An Ascent Capture hardware key must be attached to your remote stations. This chapter describes how to install and configure the items listed above. It also includes operating requirements for your IIS Web server and remote stations. Getting Started with Ascent Capture Internet Server 5 5

14 Chapter 2 Operating Requirements Your IIS Web server and remote stations must meet the following minimum operating requirements: Central Site Ascent Capture Requirements Ascent Capture 5 installed in a client/server configuration or as a standalone installation. Ascent Capture hardware key attached to each station as appropriate for the station. IIS Web Server System Requirements One of the following:! Windows 2000 Server with Service Pack 1 (or higher)! Windows NT Server 4.0 with Service Pack 6a (or higher) One of the following, as appropriate:! Microsoft Internet Information Services 5.0 for Windows 2000 Server! Microsoft Internet Information Server 4.0 for Windows NT Server TCP/IP protocol LAN access to the Ascent Capture database at your central site ACI Server hardware key attached to the IIS Web server IIS Web Server Hardware Requirements 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 Parallel port for hardware key 6 Getting Started with Ascent Capture Internet Server 5

15 Installing ACI Server Recommended Pentium III 1 GHz processor (or higher) 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 Parallel port for hardware key Remote Station Ascent Capture Requirements Ascent Capture 5 installed as a standalone installation Ascent Capture Scan hardware key Remote Station System Requirements One of the following operating systems:! Windows 2000 Professional with Service Pack 1 (or higher)! Windows NT 4.0 Server or Workstation with Service Pack 6a (or higher)! Windows 98 with Service Pack 1 (or higher)! Windows 98 Second Edition! Windows Me TCP/IP protocol Internet Explorer 5.0 (or higher) Internet or Intranet access to your IIS Web server Remote Station Hardware Requirements Refer to your Getting Started with Ascent Capture 5 guide and your Ascent Capture 5 Installation Road Map for details. In addition, you should have a working knowledge of the Internet and Web servers; Microsoft Internet Information Server and its components; your network configuration; and Ascent Capture. Refer to your Microsoft documentation for information about Microsoft products. Refer to your Ascent Capture documentation for information about Ascent Capture. Getting Started with Ascent Capture Internet Server 5 7

16 Chapter 2 Installing ACI Server The following sections describe how to install and configure the ACI Server software at your central site and your remote stations. Please read through the important installation notes below before you install the software. If you are upgrading from a previous release of ACI Server, read the important installation notes below, and then refer to the section Upgrading ACI Server on page 23 for more details. Important Installation Notes Read the following before you install/upgrade ACI Server at your central site and remote stations. Closing Other Applications Before installing ACI Server, you must close all other applications (including the Control Panel, virus detection software, and all toolbars) on your system. Information You Need During the Installation For remote sites, you will need to know the location or Web address of your central site ACI Server. Example: to your server/acis Windows 2000/Windows NT Installations To install ACI Server on a Windows 2000 or Windows NT operating system, the logged-in user must have Administrator privileges. UNC Support ACI Server supports Uniform Naming Convention (UNC) format. If you install Ascent Capture in a client/server network environment at your central site, you must specify UNC paths during the installation. 8 Getting Started with Ascent Capture Internet Server 5

17 Installing ACI Server Read-Only Files In some cases, you may be prompted to overwrite read-only files during installation. This might happen, for example, if another application has files in memory when you install ACI Server. If this occurs, you must choose to overwrite the files in order for ACI Server to install correctly. If desired, you can make a note about the files being overwritten for future reference. ACIS Configuration Wizard for IIS Settings The ACIS Configuration Wizard sets basic IIS settings for an IIS Web server based on the assumption that you have FAT partitions. If your configuration is different, you will need to set additional settings after the installation, as documented in the ACI Server installation procedure starting on page 13. Regardless of your configuration, you should verify that all of your settings are correct before attempting to use ACI Server. For more information about configuration settings, refer to Appendix C, IIS Settings. Proxy Server Support ACI Server can run in a proxy server environment. To use a proxy server, 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. Custom Module Support ACI Server supports Ascent Capture custom modules. If you plan on using a custom module at your remote stations, you must register the custom module at your central site and at each remote station after you install ACI Server. For more information about custom modules, refer to the section Using Custom Modules in Chapter 3. Note Installing ACI Server on a remote station disables the Ascent Capture Administration module on that station. Therefore, to register custom modules at remote stations, you must use the command line method. For instructions on registering custom modules from the command line, refer to Appendix B. Getting Started with Ascent Capture Internet Server 5 9

18 Chapter 2 Server Certificates When using an SSL secured IIS Web server (in either IIS 4 or 5) with certificates that you create for the server, you will not be able to install the Remote Synchronization Agent if problems occur with your certificates. This is true even though you may be able to view the Installation page through Internet Explorer by ignoring any warnings about invalid certificates. In addition, the Remote Synchronization Agent cannot automatically synchronize with your central site if problems occur with your certificates. The problematic certificates generate warnings and display one or more prompts that require user response, which interferes with the automated nature of the Remote Synchronization Agent. This is true even though you may be able to view and use the Manual Synchronization page through Internet Explorer by ignoring any warnings about invalid certificates. Typical problems with certificates are: The certificate authority is invalid (or not trusted) The certificate date is invalid The certificate name does not match the host name Note To avoid problems, make certain that the certificates you create are valid before you attempt to install or use the Remote Synchronization Agent at a remote site. 10 Getting Started with Ascent Capture Internet Server 5

19 Installing ACI Server Setting Up Your Central Site Setting up your central site involves the following basic steps, which should be done in the order listed. You must set up the central site before you can install the remote stations. Step 1 Step 2 Step 3 Step 4 Install Windows 2000 Server or Windows NT Server and applicable Service Pack on the station to be set up 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.) Make sure Ascent Capture is installed at your central site. It can be installed in a client/server configuration or as a standalone station. Install the ACI Server software on your IIS Web server. If your IIS Web server and your Ascent Capture server (or standalone installation) are installed on different stations, make certain that the date/time settings on both stations are synchronized. Note You may already have some of the above items in place. For example, you may have an IIS Web server installed and configured. Even so, please read through all the procedures on the following pages to make sure your installation matches the requirements for ACI Server. Step 1 Install Windows 2000 Server or Windows NT Server Install the applicable operating system at your central site.! To install Windows 2000 Server 1 Install Windows 2000 Server on the station 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, IIS will be installed by default only if IIS was installed on the previous version of Windows. Getting Started with Ascent Capture Internet Server 5 11

20 Chapter 2! To install Windows NT Server Install Windows NT Server 4.0 on the station to be used as your IIS Web server. 2 Install the Windows NT 4.0 Option Pack. (If necessary, you can download it from the Microsoft Web site.) 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.) Accept the directory defaults provided during installation. 3 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 installation. Step 2 Install Ascent Capture Install Ascent Capture at your central site using the ACI Server CD. 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 your Ascent Capture documentation for details on installing and using Ascent Capture, installing and configuring Kofax hardware accelerators, and attaching hardware keys. Note You must define and publish batch classes in Ascent Capture before your remote sites can download them. To ensure successful processing, administrators should be aware of important issues that affect batch classes. These issues are outlined in the section Batch Class Considerations in Chapter Getting Started with Ascent Capture Internet Server 5

21 Installing ACI Server Step 3 Install the ACI Server Software on the IIS Web Server At the end of the ACI Server installation, an ACIS Configuration Wizard will run to help set up basic IIS settings for ACI Server. It will set typical configuration settings for an IIS Web server using FAT partitions. Follow the installation procedure carefully as it contains important notes about settings you must change if your computer varies from the expected typical configuration.! To install ACI Server 1 Insert the ACI Server CD into the CD-ROM drive on your IIS Web server. The CD supports AutoPlay, so the installation will automatically begin. (If it doesn t, run Setup.exe from the root directory on the CD.) 2 Select Central Site Install ACI Server. 3 Follow the instructions on your screen to install the software. Note: The default destination for the software is C:\Inetpub\wwwroot\ACIS. It is recommended that you install to that folder. The installation will install Microsoft Data Access Components (MDAC) 2.5. For Windows NT Server installations only, the installation will install Microsoft Posting Acceptor If this is a new installation, the ACIS Configuration Wizard will appear. The wizard will assist you in setting up the following: The ACI Server Web site (ACIS) The Ascent virtual directory to point to your Ascent Capture root installation directory The Upload virtual directory to temporarily store batches being uploaded from your remote sites 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. The ACIS Configuration Wizard enables anonymous access for each of the ACI Server directories. Anonymous access is required to allow remote stations to automatically poll the central site. When selecting the anonymous user account, be sure to take the following into consideration:! If IIS is installed on a domain controller, ensure the anonymous user account has permissions on the Ascent Capture server. By default, the anonymous user account will be a domain-wide account. Getting Started with Ascent Capture Internet Server 5 13

22 Chapter 2! If IIS is installed on a member server (rather than a domain controller), ensure the anonymous user account is a domain-wide account that has permissions on the IIS Web server and the Ascent Capture server.! If IIS is not installed within a domain, ensure the anonymous user account exists on both the IIS Web server and the Ascent Capture server and has the same password. The IIS Web server virtual directories can be displayed using Internet Services Manager. For a quick overview of the IIS Web server properties set by the ACIS Configuration Wizard, see Table 2-1 on page 15. For details, see Appendix C. 5 When prompted to do so, reboot your IIS Web server. 6 Verify the user name specified for the anonymous user account has Log on locally permission for the IIS Web server or is a member of a group that has this permission. This is a Microsoft security requirement for anonymous or basic authentication. To identify if your anonymous user account has Log on locally permission, see the procedure To display users with Log on locally rights in Appendix C. 7 If Ascent Capture is installed on the same machine as the IIS Web server and your anonymous user account is a domain account, you need to clear the Allow IIS to control password setting set by the ACIS Configuration wizard for the anonymous user account. Note that with Windows NT, this property is called Enable Automatic Password Synchronization. For details, see the section Allow IIS to Control Password Settings in Appendix C. 8 If you installed ACI Server and/or Ascent Capture on NTFS partitions, you must set the required NTFS security settings documented in Table 2-2 on page 15. For more information on these settings, see the section NTFS Security Settings in Appendix C. Important A reboot is required for NTFS security setting changes to take effect. 9 Attach the ACI Server hardware key to the parallel port on your IIS Web server. If Ascent Capture is installed as a standalone station on the same computer, you will need to have both your Ascent Capture hardware key and your ACI Server hardware key attached to that station. You can attach them in any order. 14 Getting Started with Ascent Capture Internet Server 5

23 Installing ACI Server Table 2-1. Virtual Directory Required Settings Virtual Directory Access Rights Network Directory Application Name Execute Permissions (Windows 2000) Permissions (Windows NT) ACIS read N/A Ascent scripts and executables execute (including script) Ascent read User must have full control permission, if Ascent Capture and IIS are on different computers N/A None None Upload write N/A N/A None None Table 2-2. NTFS Required Security Settings Folder (on an NTFS partition) Default Location Anonymous User Permissions Windows 2000 Component Services User Permissions 1 Windows NT Transacation Server User Permissions 2 Ascent Images C:\Program Files\Ascent where Ascent Capture is installed C:\Program Files\Ascent\Images where Ascent Capture is installed full control N/A N/A write N/A N/A Scripts C:\Inetpub\Scripts if ACI Server is installed on Windows NT read and execute N/A N/A ACIS C:\Inetpub\wwwroot\ACIS where ACI Server is installed full control read and execute read and execute Upload Common Files Temp C:\Inetpub\wwwroot\ACIS\Upload where ACI Server is installed C:\Program Files\Common Files where ACI Server is installed C:\Temp where ACI Server is installed full control N/A N/A full control full control full control full control full control full control 1 if using High (Isolated) or Medium (Pooled) application processes 2 if running ACI Server in a separate memory space Getting Started with Ascent Capture Internet Server 5 15

24 Chapter 2 Step 4 - Synchronize Date/Time Settings If your IIS Web server and your Ascent Capture server (or standalone installation) are installed on different stations, make certain that you synchronize the date/time settings on both stations. Note The date/time on your IIS Web server must be the same or ahead of the date/time on your Ascent Capture station. If this is not the case, your remote stations will not be able to download batch classes. If they attempt to do so, the message The Central Site changed the published batch classes while they were being retrieved. Please try again later. will display.! To synchronize date/time settings 1 On your Ascent Capture station: a Display the date/time setting utility as appropriate for your operating system. For example, on Windows 2000 Server, select Start Settings Control Panel Date/Time. For details, refer to the Microsoft documentation for your operating system. b Set the appropriate Date/Time, Time Zone, and Daylight Savings Time settings. 2 On your IIS Web server, set the date/time settings to match the settings on your Ascent Capture station. If possible, set the times on both stations to match to the second. If this is not possible, set the time on the IIS Web server to be ahead of the time on the Ascent Capture station. Note Computer clocks often drift and may not stay synchronized over a period of time. Ensure that you regularly review your date/time settings for the IIS Web server and Ascent Capture station or obtain software that does it automatically for you. 16 Getting Started with Ascent Capture Internet Server 5

25 Installing ACI Server Setting Up a Remote Station Installing and configuring the Remote Synchronization Agent on a remote station involves the following basic steps, which should be performed in the order listed: Step 1 Step 2 Step 3 Step 4 Make sure Ascent Capture is installed on the remote station as a standalone installation. Configure the necessary Internet Explorer Security settings. Install the Remote Synchronization Agent on your remote station. The installation process will disable the Administration module at the remote station. Configure polling times and download batch classes. Step 1 Install Ascent Capture To install the ACI Server Remote Synchronization Agent, Ascent Capture must already be installed on the remote workstation. Install Ascent Capture using the ACI Server CD. It must be installed as a standalone station. In addition, make sure you attach an Ascent Capture Scan hardware key to your remote workstation. Important If you intend to use a Kofax hardware accelerator (for example, an Adrenaline 1700) on your scan stations with Ascent Capture, do not install the drivers that are shipped with the accelerator. The drivers that you need are included on the ACI Server CD and will be installed when you install Ascent Capture. Refer to your Ascent Capture documentation for details on installing and using Ascent Capture, installing and configuring Kofax hardware accelerators, and attaching hardware keys. Getting Started with Ascent Capture Internet Server 5 17

26 Chapter 2 Step 2 Configure the Appropriate Internet Explorer Security Settings You can set Internet Explorer security settings from your Windows Control Panel or from your browser. The instructions below explain how to set them from your browser. Refer to your Windows documentation for information on setting Internet settings from the Control Panel.! To configure Internet Explorer security settings 1 Run Internet Explorer on the remote station. 2 From the menu bar, select Tools Internet Options Security tab. The Internet Options dialog box will be displayed. Figure 2-1. Internet Options Dialog Box - Security Tab 18 Getting Started with Ascent Capture Internet Server 5

27 Installing ACI Server 3 Select the desired zone. (For example, Internet zone or Intranet zone. ) Then, select Custom Level. The Security Settings dialog box will be displayed. Figure 2-2. Security Settings Dialog Box 4 Enable all of the ActiveX controls and plug-ins, Downloads, and Scripting options. 5 Click OK from the Security Settings dialog box. 6 Click OK from the Internet Options dialog box. Getting Started with Ascent Capture Internet Server 5 19

28 Chapter 2 Step 3 Install the ACI Server Remote Synchronization Agent You may install the Remote Synchronization Agent via the Web or from the ACI Server CD. Warning Do not attempt to install the Remote Synchronization Agent on your IIS Web server and/or the Ascent Capture server at your central site. The Ascent Capture Administration module is automatically disabled from any station on which the Remote Synchronization Agent installation program is run. If you attempt to install the Remote Synchronization Agent on your IIS Web server or the Ascent Capture server at your central site, your central Ascent Capture installation will become unusable. In addition, if you want to keep any batch classes already defined at your remote station, export them into.cab files before you install the Remote Synchronization Agent. Then, you can send the.cab files to your central site. Your central site administrator can import them into the central site s system, republish them, and make them available to download to your remote station. If you do not export your batch classes before installing the Remote Synchronization Agent, you will not be able to recover them. For more information on exporting and importing batch classes, see your Ascent Capture documentation. The Remote Synchronization Agent will add an icon ( ) to the Windows taskbar and Startup menu on the remote station. The icon will appear the next time you reboot the station. The Remote Synchronization Agent icon must exist for automatic polling to occur. Refer to Chapter 3 for more information about the Windows taskbar icon. 20 Getting Started with Ascent Capture Internet Server 5

29 Installing ACI Server! To install from the Web 1 Run Internet Explorer. In the Address box, enter the location or Web address of your central site ACI Server. A page similar to Figure 2-3 will be displayed. Note If you are prompted to install the InstallFromTheWeb software, choose to install it. Figure 2-3. ACI Server Installation Page 2 Click the installfromtheweb button. The Remote Synchronization Agent will be installed on your remote station. 3 Follow the instructions on your screen to install the software. 4 If prompted to do so, reboot your remote station. Note The first time you open an ACI Server Web page, you will get a message indicating that all existing batch classes will be deleted. This is because, with ACI Server, all batch classes must be administered by the central site. To use ACI Server, click Yes. Getting Started with Ascent Capture Internet Server 5 21

30 Chapter 2! To install from the Ascent Capture Internet Server CD 1 Insert the ACI Server CD into the CD-ROM drive on your remote 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.) 2 Select Remote Site Install Remote Synchronization Agent. 3 Follow the instructions on your screen to install the software. 4 If prompted to do so, reboot your remote station. Note The first time you open an ACI Server Web page, you will get a message indicating that all existing batch classes will be deleted. This is because, with ACI Server, all batch classes must be administered by the central site. To use ACI Server, click Yes. Step 4 Download Batch Classes and Configure Polling Times After installing the Remote Synchronization Agent on your remote station, you can configure polling times for your remote station and download batch classes from the central site. Then, you will be ready to process batches at your remote site. Refer to Chapters 3 and 4 for instructions on performing these tasks. 22 Getting Started with Ascent Capture Internet Server 5

31 Installing ACI Server Upgrading ACI Server The following sections describe how to upgrade and configure the ACI Server module at your central site and remote stations. Converting Batches From Previous Releases After the central site has been upgraded, remote sites can continue to create and process version 3.x or 4.x batches to send to the central site. When the batches are uploaded to the central site, the batches are converted to 5.x batches. Note Until a remote site is upgraded, it will not be able to download 5.x batch classes for processing. Upgrading Your Central Site Upgrading your central site involves the following basic steps, which must be done in the order listed. Step 1 Step 2 Step 3 Step 4 Stop the Default Web Site on your IIS Web server. It must remain stopped during the entire central site upgrade process. Failure to do so may cause loss of batch classes and functionality at your remote sites. Upgrade the Ascent Capture software at your central site and republish your batch classes. For client/server configurations, you must upgrade the Ascent Capture server software and at least one client station. Upgrade the ACI Server software on your IIS Web server. Restart the Default Web Site on your IIS Web server. Note You must upgrade Ascent Capture and ACI Server at your central site before you upgrade your remote stations. In addition, you must prohibit remote stations from synchronizing with your central site during the entire central site upgrade process. Getting Started with Ascent Capture Internet Server 5 23

32 Chapter 2 Step 1 Stop the Default Web Site on Your IIS Web Server You must stop the Default Web Site before you upgrade Ascent Capture at your central site. In addition, you must not start it again until after you upgrade ACI Server at your central site. Doing so will prohibit remote sites from synchronizing during the central site upgrade process. Warning It is very important that you stop the Default Web Site for the entire central site upgrade process. If you do not, and a remote station attempts to synchronize with your central site before both Ascent Capture and ACI Server are upgraded, the remote station will lose all published batch classes and will not be able to function. If this occurs, you must complete the upgrade at the central site. Then, you must upgrade Ascent Capture and the Remote Synchronization Agent on the remote station to restore its functionality.! To stop the Default Web Site 1 On your IIS Web server, do one of the following: Windows 2000 Server: Select Start Programs Administrative Tools Internet Services Manager. Windows NT Server: Select Start Programs Windows NT 4.0 Option Pack Microsoft Internet Information Server Internet Service Manager. 2 Expand the Internet Information Services tree to display the Default Web Site. 3 Right-click the Default Web Site folder, and select Stop. Step 2 Upgrade Ascent Capture and Republish Batch Classes Upgrade your Ascent Capture software at your central site. Use the version of Ascent Capture distributed on the ACI Server CD. In addition, make sure to attach the necessary hardware keys to your Ascent Capture stations. For standalone installations, upgrade your standalone Ascent Capture station. For client/server installations, upgrade the Ascent Capture server station. Then, upgrade at least one client station. Note When upgrading a client/server installation, batch classes are converted to the new format when you upgrade the first client station. Therefore, you must upgrade at least one Ascent Capture client station before you allow remote stations to synchronize with your central site. 24 Getting Started with Ascent Capture Internet Server 5

33 Installing ACI Server For all installations, republish your batch classes. Refer to your Ascent Capture documentation for details on installing and using Ascent Capture, installing and configuring Kofax hardware accelerators, and attaching hardware keys. Step 3 Upgrade the ACI Server Software on the IIS Web Server Upgrade the ACI Server software at your central site. Any previously defined ACI Server configuration settings will be saved during the upgrade process.! To upgrade ACI Server 1 Make certain that your Default Web Site on your IIS Web server is stopped. To do so, refer to Step 1 on page Insert the ACI Server CD into the CD-ROM drive on your IIS Web server. 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 Central Site Install ACI Server. 4 Follow the instructions on your screen to install the software. Note You must choose to overwrite any read-only files during the installation in order for ACI Server to install correctly. 5 When prompted to do so, reboot your IIS Web server. 6 Attach the ACI Server hardware key to the parallel port on your IIS Web server. Note If Ascent Capture is installed as a standalone station on the same computer, you will need to have both your Ascent Capture hardware key and your ACI Server hardware key attached to that station. You can attach them in any order. Getting Started with Ascent Capture Internet Server 5 25

34 Chapter 2 Step 4 Restart the Default Web Site on Your IIS Web Server After you upgrade Ascent Capture and ACI Server at your central site, you can restart the Default Web Site on your IIS Web server. 1 On your IIS Web server, do one of the following: Windows 2000 Server: Select Start Programs Administrative Tools Internet Services Manager. Windows NT Server: Select Start Programs Windows NT 4.0 Option Pack Microsoft Internet Information Server Internet Service Manager. 2 Expand the Internet Information Services tree to display the Default Web Site. 3 Right-click the Default Web Site folder, and select Start. Upgrading Your Remote Site Follow these steps for each remote station: Step 1 Step 2 Step 3 Step 4 Process all batches on the remote station and upload them to your central site. Upgrade your Ascent Capture software. It must be installed as a standalone installation. Upgrade the ACI Server Remote Synchronization Agent. Download batch classes and configure polling times. Note The central site must be upgraded before the remote stations. Step 1 Process Batches Finish processing any Ascent Capture batches at the remote station before you upgrade Ascent Capture or the ACI Server Remote Synchronization Agent. All completed batches must be uploaded to the central site. 26 Getting Started with Ascent Capture Internet Server 5

35 Installing ACI Server Step 2 Upgrade Ascent Capture Upgrade the Ascent Capture software on your remote station. To do so, use the version of Ascent Capture distributed on the ACI Server CD. In addition, make sure you attach the necessary hardware keys. Refer to your Ascent Capture documentation for details on installing and using Ascent Capture, installing and configuring Kofax hardware accelerators, and attaching hardware keys. Step 3 Upgrade the Remote Synchronization Agent Software Upgrade the Remote Synchronization Agent on the remote station. Any previously defined ACI Server configuration settings (such as polling times) will be saved during the upgrade process. Note You may upgrade the Remote Synchronization Agent via the Web or from the ACI Server CD.! To upgrade from the Web 1 Close the Remote Synchronization Agent on your remote station. To do so, right-click the Remote Synchronization Agent icon located on the Windows taskbar and click Close. 2 Run Internet Explorer. In the Address box, enter the location or Web address of your central site ACI Server Web site. A page similar to Figure 2-4 will be displayed. Note You may be prompted to install the InstallFromTheWeb software. If you are, choose to install it. Getting Started with Ascent Capture Internet Server 5 27

36 Chapter 2 Figure 2-4. ACI Server Installation Page 3 Click the installfromtheweb button. The Remote Synchronization Agent will be installed on your remote station. 4 Follow the instructions on your screen to install the software. 5 When prompted to do so, reboot your remote station.! To upgrade from the Ascent Capture Internet Server CD 1 Close the Remote Synchronization Agent on your remote station. To do so, right-click the Remote Synchronization Agent icon located on the Windows taskbar and click Close. 2 Insert the ACI Server CD into the CD-ROM drive on your remote 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 Remote Site Install Remote Synchronization Agent. 4 Follow the instructions on your screen to install the software. 5 When prompted to do so, reboot your remote station. 28 Getting Started with Ascent Capture Internet Server 5

37 Installing ACI Server Step 4 Download Batch Classes and Configure Polling Times After upgrading the Remote Synchronization Agent, you can modify the remote station configuration settings (such as polling times) and download batch classes. Refer to Chapters 3 and 4 for instructions on performing these tasks. Note If you uninstalled and reinstalled the Remote Synchronization Agent, you must reconfigure polling times for the remote station (if they are not controlled by the central site). Then, download batch classes from your central site before using the Remote Synchronization Agent software. Getting Started with Ascent Capture Internet Server 5 29

38 Chapter 2 Uninstalling ACI Server This section explains how to uninstall ACI Server components.! To uninstall the remote site ACI Server Remote Synchronization Agent 1 Close the ACI Server Remote Synchronization Agent. To do so, right-click the Windows taskbar icon and select Close. 2 Open the Add/Remove Programs utility available from the Windows Control Panel. 3 Select ACIS Remote Synchronization Agent and click Add/Remove. Warning Do not continue to scan batches at your remote station after you uninstall the Remote Synchronization Agent. You will be able to process the batches through the modules set to run at the remote station, but you will not be able to upload them to your central site or release them at your remote site. Note the following: You will not be able to reinstall the Remote Synchronization Agent with batches in progress in the system. You will not be able to recover batches by reinstalling Ascent Capture on the station. You will be able to install Ascent Capture, but the batches will be in a Completed state and unavailable to queues on the station. If you want to use Ascent Capture on the station (without support for remote processing), you must uninstall the Remote Synchronization Agent and reinstall Ascent Capture on that station.! To uninstall the central site ACI Server software 1 Open the Add/Remove Programs utility available from the Windows Control Panel. 2 Select Ascent Capture Internet Server and click Add/Remove. Note Uninstalling the ACI Server will not remove or change your IIS Web server settings previously configured for ACI Server. For example, it will not remove your ACIS virtual directory or change its properties. To reinstall the ACI Server components, follow the installation instructions as described earlier in this chapter. 30 Getting Started with Ascent Capture Internet Server 5

39 Chapter 3 Configuring ACI Server Introduction After completing the installation process, you can configure ACI Server settings to help manage Ascent Capture batch processing activity between your central site and the remote stations. This chapter introduces the ACI Server Web pages and explains which ones you use to configure settings. This chapter covers the following topics: ACI Server Web pages ACI Server configuration settings Getting Started with Ascent Capture Internet Server 5 31

40 Chapter 3 ACI Server Web Pages Overview Once ACI Server is successfully installed at the central site, you can access an installation page via the browser on a remote station. From the installation page, you can install the Remote Synchronization Agent on the remote station. Then, you can use the ACI Server Web pages to configure settings and perform other tasks. This section provides an overview of the ACI Server Web pages as listed below: Central Administration page (used by the system administrator) Installation page (used to install the Remote Synchronization Agent at the remote site) Client Configuration page Manual Synchronization page Change Password page The Central Administration page is used by the system administrator. The other ACI Server Web pages are used primarily by remote users. It is a good idea to familiarize yourself with these pages, from which you perform most ACI Server configuration and processing tasks. Central Site Remote Site Installation Help Central Administration Client Configuration Manual Synchronization Change Password Help Help Download Batch Classes Help Upload Batches Help Support Figure 3-1. ACI Server Web Pages 32 Getting Started with Ascent Capture Internet Server 5

41 Configuring ACI Server Central Administration Page From the Central Administration page, ACI Server system administrators configure centrally controlled settings for remote stations. For details, see the section Configuring Central Settings on page 44. The name of the page is central_admin.asp. To open the Central Administration page, start your browser and enter the following in the Address bar: to your server/acis/central_admin.asp Note The Central Administration page cannot be accessed via the navigation bar from any other ACI Server Web page. Figure 3-2. ACI Server Central Administration Page Getting Started with Ascent Capture Internet Server 5 33

42 Chapter 3 Installation Page The Installation page is the default page for your ACI Server Web site. You use this page to install the Remote Synchronization Agent on a remote station. You also use the Installation page links to open other ACI Server Web pages. The name of the page is default.asp. To open the Installation page, start your browser and enter the following in the Address bar: to your server/acis Figure 3-3. ACI Server Installation Page 34 Getting Started with Ascent Capture Internet Server 5

43 Configuring ACI Server Client Configuration Page From the Client Configuration page, you can configure polling times for a remote station if centrally controlled settings are not in effect. For details, see the section Configuring Remote Station Settings on page 47. Note If polling times are being centrally controlled, the options on this page will be unavailable and you will not be able to change them. In this case, you can use the Client Configuration page to view the selected settings. The name of the page is client_config.htm. To open the Client Configuration page, select it from the navigation bar on the Installation page, the Manual Synchronization page, or the Change Password page. Or, start your browser and enter the following in the Address bar: to your server/acis/client_config.htm Figure 3-4. ACI Server Client Configuration Page Getting Started with Ascent Capture Internet Server 5 35

44 Chapter 3 Manual Synchronization Page From the Manual Synchronization page, you can download batch classes or upload completed batches in between the regularly scheduled polling times. You can also view the ACI Server status log. For details, see the sections Downloading Batch Classes from the Central Site, Uploading Batches to the Central Site, or Monitoring Batch Activity in Chapter 4. The Manual Synchronization page also lists the number of pages remaining until the ACI Server license reaches its monthly limit for uploading pages to the central site. If the limit is reached, the central site does not accept additional batches until the beginning of the next month, when the license is reset. A warning will display in the status log when a batch is sent and the license is running low. The name of the page is manual_synch.asp. To open the Manual Synchronization page, select it from the navigation bar on the Installation page, the Client Configuration page, or the Change Password page. Or, start your browser and enter the following in the Address bar: to your server/acis/manual_synch.asp Figure 3-5. ACI Server Manual Synchronization Page 36 Getting Started with Ascent Capture Internet Server 5

45 Configuring ACI Server Change Password Page From the Change Password page, you can modify your Ascent Capture password if the User Profiles feature is enabled at the central site. The new password will become effective the next time: A remote station automatically polls the central site. A user at the remote site downloads batch classes from the Manual Synchronization page. A user at the remote site clicks the Synchronize Now button located on the Remote Synchronization Agent dialog box. The name of the page is PwChange.asp. To open the Change Password page, select it from the navigation bar on the Installation page, Manual Synchronization page, or the Client Configuration page. Or, start your browser and enter the following in the Address bar: to your server/acis/pwchange.asp Note The Change Password page cannot be accessed unless User Profiles are enabled at the central site. Figure 3-6. ACI Server Change Password Page Getting Started with Ascent Capture Internet Server 5 37

46 Chapter 3 Remote Synchronization Agent Windows Taskbar Icon Installing the Remote Synchronization Agent on a remote station adds an icon to the Windows taskbar. After installation, you must reboot your system for the icon to appear. Close Status About Figure 3-7. Remote Synchronization Agent Windows Taskbar Icon and Menu Right-click on the Windows taskbar icon to display the menu, as shown in Figure 3-7. The menu gives you a shortcut method to access some of the functions that are available from the ACI Server pages. If desired, you can use the menu for the Remote Synchronization Agent Windows taskbar icon to initiate a polling event. The menu for the Remote Synchronization Agent Windows taskbar icon offers the following options: Close Status About Select this option to close the Remote Synchronization Agent and clear the Windows taskbar icon. Note that automatic polling will not occur when the Remote Synchronization Agent is closed. When you reboot the remote station, the Remote Synchronization Agent will be started again and the Windows taskbar icon will be restored. Select this option to access the Synchronize Now button that allows you to immediately synchronize with, or poll, the central site. For instructions, refer to the sections Downloading Batch Classes from the Central Site and Uploading Batches to the Central Site in Chapter 4. The Status option also displays a log that lists synchronization, or polling, activity. See the section Monitoring Batch Activity in Chapter 4. Select this option to display an About box, which contains version information about the ACI Server Remote Synchronization Agent. From the About box, you can select the Tech Support button to automatically open your browser to the Kofax Technical Support site. With the Remote Synchronization Agent Windows taskbar icon, you can also do the following: Display the next scheduled polling time by holding your cursor over the icon. Display the status log by double-clicking the icon. 38 Getting Started with Ascent Capture Internet Server 5

47 Configuring ACI Server Configuring ACI Server Settings You can use the ACI Server Web pages to configure settings for managing batch processing activity between the central site and the remote stations. In particular, you can do the following: Select where you want to run each Ascent Capture module Configure polling times Ascent Capture Modules The ACI Server administrator can configure settings that determine which Ascent Capture modules run at the central site and which run at remote stations. These settings are configured from the Central Administration page. The procedure is explained in detail in the section Configuring Central Settings on page 44. Any module (including custom modules) can be run at any site, with these exceptions: the Scan module must be run at a remote station and the Release module must be run at the central site. These selections are already made on the Central Administration page, and you cannot change them. Also, once batches are uploaded from remote stations to your central site, ACI Server does not allow them to return to the remote stations for further processing. To illustrate, suppose that you have batch classes defined with the following processing queues: Scan Quality Control Validation Verification Release Using the Central Administration page, you can specify which modules are to run at the central site and which are to run at the remote stations. For example, you might set up the Scan and Quality Control modules to run at the remote station and the other modules to run at the central site. Once a batch is processed through the Scan and Quality Control modules, it will be routed to the central site. Getting Started with Ascent Capture Internet Server 5 39

48 Chapter 3 Using the Quality Control Module Because you can use the Quality Control module as either a regular processing module or as an exception queue, keep the following in mind: Exception batches are automatically routed to the Quality Control module at the site where the exception occurs, regardless of the Quality Control site designation listed on the ACI Server Central Administration page. Batches without exceptions are routed to the Quality Control module site listed on the ACI Server Central Administration page, if the Quality Control module is defined as part of the batch class definition. Tip It is recommended that you specify Quality Control as a processing module to run at your remote station. This will force all batches through Quality Control before they are uploaded to the central site. This way, problems that occur at the remote site can be fixed there. To illustrate, consider this scenario: During processing at your remote station, a document is rejected because its pages are too light. To fix the problem, the document must be rescanned. Since the pages to be scanned would be physically available at the remote station, you could easily rescan them and continue processing. If the batch is sent to the central site, you would not have easy access to the pages to be rescanned. For instructions on selecting sites for Ascent Capture batch processing, see the section Configuring Central Settings on page 44. Using Custom Modules If you plan on using a custom module at your remote sites, you must: Register the custom module at your central site and at each remote site. Refer to Appendix B for details. Note that you must make the custom module s executable and registration files available to your remote stations. Add the custom module to the desired batch class at the central site. When your batch class is complete, publish it. From the ACI Server Central Administration page, select the custom module to run at remote sites. Refer to the section Configuring Central Settings on page 44. Download batch classes to your remote sites. 40 Getting Started with Ascent Capture Internet Server 5

49 Configuring ACI Server Polling Polling refers to the process whereby your remote stations connect to the IIS Web server at your central site and do the following: Upload completed batches from the remote station to the central site. All completed batches will be uploaded. Upload user tracking statistics, if enabled, from the remote station to the central site for completed batches. Download configuration settings from the central site to the remote station. Any new or updated configuration settings submitted from the Central Administration page will be downloaded. For details, refer to the section Central Administration Page on page 34, or contact your system administrator. Download batch classes from the central site to the remote station. Any new or updated batch classes published at the central site will be downloaded. Download user profile settings, if enabled, from the central site to the remote station. Download the settings for the patch code reserved for batch separator sheets, if utilized, from the central site to the remote station. For details about batch separator sheets, see the Ascent Capture online help. Polling can occur in the following situations: When the polling time occurs, as defined for all remote stations from the Central Administration page, or for an individual remote station from the Client Configuration page. See the sections Configuring Central Settings on page 44 and Configuring Remote Station Settings on page 47. When a remote user clicks download classes from the navigation bar on the Manual Synchronization page. When a remote user clicks upload batches from the navigation bar on the Manual Synchronization page. When a remote user clicks the Synchronize Now button located on the Remote Synchronization Agent dialog box. See the section Remote Synchronization Agent Windows Taskbar Icon on page 39. Getting Started with Ascent Capture Internet Server 5 41

50 Chapter 3 Configuring Polling Times There are two methods for configuring regularly scheduled polling times: Central site control: The same polling options are defined for all remote stations. To enable centrally controlled polling options, the administrator sets them from the Central Administration page, as explained in the section Configuring Central Settings. Remote station control: Polling options for each remote station are defined independently of one another. To configure remote station settings, use the Client Configuration page, as explained in the section Configuring Remote Station Settings on page 47. Configuring Central Settings (For Administrators Only) You select which Ascent Capture modules are run at your remote stations from the Central Administration page, as shown in Figure 3-8. If desired, you can also select uniform polling times for all remote stations using the Central Administration page. If you want your remote stations to configure their own polling times, do not select the Central control of polling times check box. Note The Central Administration page is intended to be used by system administrators, and should be used with caution. Each setting on this page affects every remote station.! To configure centrally controlled settings 1 Start your browser and open the Central Administration page. The Central Administration page will be displayed, as shown in Figure Getting Started with Ascent Capture Internet Server 5

51 Configuring ACI Server Figure 3-8. ACI Server Central Administration Page For more information about this page, click the Help option from the navigation bar. 2 From the Central Administration page, select which Ascent Capture modules (including custom modules) to run at the central site, and which to run at the remote stations. Note that your selections apply to all remote stations, and they take effect individually, as each remote station polls the central site. For additional guidelines, refer to the section Ascent Capture Modules on page 41. Getting Started with Ascent Capture Internet Server 5 43

52 Chapter 3 3 Select the Central control of polling times check box to enable central control of polling times. The polling options will be unavailable until you enable this option. Note the following: If you enable this option, your polling time selections will affect all the remote stations. The remote stations will be prohibited from setting their own polling times. The next time a remote station polls the central site, the settings will be downloaded to the remote station. If you do not select this option, the remote stations will be able to set their own polling times. 4 Specify the Local time to start polling the central site. This defines the next time/date on which the remote stations will poll the central site. Time Select the time to start polling. Date Select the date to start polling. 5 Specify the Polling frequency. This defines how often the remote stations will poll the central site. The remote stations will always poll for new batch classes and settings at the specified interval, starting with the time/date specified with the Local time to start polling the central site option in the previous step. Note that the polling intervals are not impacted by connection failures. The remote stations will continue to poll as specified, whether or not they are successful. Never Select this option if you do not want your remote station to automatically poll the central site at a defined interval. The remote station will poll at the time specified by the Local time to start polling the central site option. Note that you can manually change the Local time to start polling the central site option to force each instance of polling without using a regularly scheduled time. Every Select this option if you want your remote station to automatically poll the central site at a defined interval. Then, select the desired interval in minutes, hours, or days. 44 Getting Started with Ascent Capture Internet Server 5

53 Configuring ACI Server 6 Specify how often you want your remote station to retry if the connection between the remote station and your central site fails. Your selections do not impact the selected polling intervals; they only define your remote station s behavior in the event of a connection failure. Your remote station will always poll as specified by the Polling frequency selections. Never Select this option if you do not want the remote station to retry after a connection failure. Up to / Every Choose this option if you want the remote station to retry after a connection failure. Select how often you want the remote station to retry, and for how long. You can specify the settings in minutes, hours, or days. 7 Click Submit to save your settings. Your selections will be saved to the IIS Web server at the central site. They become effective individually at each remote station, the next time polling occurs (according to the station s previous polling settings). See the section Polling on page 43. After you click Submit, a message will appear to confirm that your changes have been saved. To return to the Central Administration page, click the hypertext below the confirmation message. If you click Reset, the selections are restored to the previously saved settings. Configuring Remote Station Settings To configure polling options for a remote station, you use the Client Configuration page, as shown in Figure 3-9. The selections on the Client Configuration page will affect your remote station only, and they are available only if the ACI Server administrator has cleared the Central control of polling options from the Central Administration page.! To configure remote station settings 1 From a remote station, start your browser and open the Client Configuration page. The Client Configuration page will be displayed, as shown in Figure 3-9. Getting Started with Ascent Capture Internet Server 5 45

54 Chapter 3 Figure 3-9. ACI Server Client Configuration Page For more information about this page, click the Help option from the navigation bar. Note If the following message is displayed when you attempt to open the Client Configuration page, the polling times for your remote station are being controlled by the central site. In this case, you can display the page, but the options will be disabled and you will not be able to change them. Click OK to close the message box and view the selected polling times. 46 Getting Started with Ascent Capture Internet Server 5

55 Configuring ACI Server If the options on the Client Configuration page are available, you can choose polling times and other settings for your remote station. The selections will affect your remote station only. If the options are unavailable and you want to change them, contact your system administrator. If you are a system administrator, refer to the section Configuring Central Settings starting on page Specify the Local time to start polling the central site. This defines the next time/date on which the remote stations will poll the central site. Time Select the time to start polling. Date Select the date to start polling. 3 Specify the Polling frequency. This defines how often the remote station will poll the central site. The remote station will always poll for new batch classes and settings at the specified interval, starting with the time/date specified with the Local time to start polling the central site option. Note that the polling intervals are not impacted by connection failures. Your remote station will continue to poll as specified, whether or not it was successful. Never Select this option if you do not want your remote station to automatically poll the central site at a defined interval. The remote station will poll only at the time defined by the Local time to start polling the central site. Every Select this option if you want your remote station to automatically poll the central site at a defined interval. Then, select the desired interval in minutes, hours, or days. 4 Specify how often you want your remote station to retry if the connection between the remote station and your central site fails. Your selections do not impact the selected polling intervals; they only define your remote station s behavior in the event of a connection failure. Your remote station will always poll as specified by the Polling frequency selections. Never Select this option if you do not want your remote station to retry after a connection failure. Up to / Every Choose this option if you want your remote station to retry after a connection failure. Select how often you want your remote station to Getting Started with Ascent Capture Internet Server 5 47

56 Chapter 3 retry, and for how long. Your settings can be specified in minutes, hours, or days. 5 Click Submit to save your settings. Your selections will be saved to the remote station on which you are working. They go into effect immediately. If you click Reset, the selections are restored to the previously saved settings. 48 Getting Started with Ascent Capture Internet Server 5

57 Chapter 4 Using ACI Server Introduction After installing and configuring ACI Server, you can take advantage of your Internet/Intranet capabilities to process Ascent Capture batches. This chapter covers the following topics: Downloading batch classes from the central site Creating and processing batches at a remote station Uploading batches to the central site Monitoring batch activity Batch class considerations Monitoring event log activity Getting Started with Ascent Capture Internet Server 5 49

58 Chapter 4 Downloading Batch Classes from the Central Site Once your system administrator has published batch classes from the Ascent Capture Administration module at the central site, you can download them to a remote processing station. If you are the system administrator and need more information about creating, updating, and publishing batch classes, refer to your Ascent Capture online help or to the following chapters in your Getting Started with Ascent Capture 5 guide: Chapter 3, The Basics The section Administration Module provides a detailed explanation of batch classes. Chapter 4, Learning Ascent Capture This chapter is a tutorial that walks you through the steps necessary to set up and publish a batch class. To ensure successful processing, administrators should also be aware of some other important issues that affect batch classes. These issues are outlined in the section Batch Class Considerations on page 58. Initiating the Download Process Batch classes can be downloaded from the central site whenever the remote station polls the central site, according to the scheduled polling times defined from the Central Administration page or the Client Configuration page. See the section Polling in Chapter 3. Batch classes can also be downloaded in two situations that differ from the regularly scheduled polling times: When a remote user clicks download classes from the navigation bar on the Manual Synchronization page. When a remote user clicks the Synchronize Now button located on the Remote Synchronization Agent dialog box. Both situations are explained in this section. Note If the Administration module is open at the central site and batch classes or administrative settings have changed, remote stations will not be able to download classes until the Administration module is closed. An error will display at the remote station indicating that the latest changes cannot be retrieved because exclusive access cannot be obtained. 50 Getting Started with Ascent Capture Internet Server 5

59 Using ACI Server! To download batch classes from the Manual Synchronization page 1 Start your browser and open the Manual Synchronization page. 2 From the navigation bar, click download classes. All published batch classes available from the central site will be downloaded to your remote station (which could take a few minutes if you are downloading for the first time, or if the administrator has republished batch classes at the central site). For each downloaded batch class, a message similar to Get file pubtypes \ mdb will be displayed in the status bar of your browser. When all batch classes are downloaded, the message Done will be displayed. Note If batch classes exist on the remote station, and this is the first time you attempt to download batch classes from your central site, a message will be displayed, reminding you that existing batch classes will be deleted and new batch classes will be administered by the central site. Click Yes to continue the download or No to cancel. Contact your central site administrator for more information.! To download batch classes from the Windows taskbar 1 From the Remote Synchronization Agent Windows taskbar icon, do one of the following: Double-click the icon Right-click the icon and select the Status option from the menu The Remote Synchronization Agent dialog box will be displayed, as shown in Figure 4-1. Figure 4-1. Remote Synchronization Agent Dialog Box Getting Started with Ascent Capture Internet Server 5 51

60 Chapter 4 2 Click Synchronize Now. The remote station will immediately upload any completed batches, and then poll the central site to check for published batch classes. All published batch classes available from the central site will be downloaded to your remote station (which could take a few minutes if you are downloading for the first time, or if the administrator has republished batch classes at the central site). For each downloaded batch class, a message similar to Get file pubtypes \ mdb will be displayed on the status line above the log. When the polling process is complete, the message Done will display briefly on the status line. 3 To close the dialog box, click Hide. Creating and Processing Batches at the Remote Station After downloading batch classes from the central site, you can create and process batches at the remote station. At the remote station, batches are routed through the Ascent Capture modules per their batch class definitions and per the remote site module selections made from the Central Administration page. See the section Ascent Capture Modules in Chapter 3. For more information about Ascent Capture batch processing, refer to your Getting Started with Ascent Capture 5 guide or the Ascent Capture online help. Uploading Batches to the Central Site Batches can be uploaded to the central site whenever the remote station polls the central site, according to the scheduled polling times defined from the Central Administration page or the Client Configuration page. See the section Configuring Polling Times in Chapter 3. Batches can also be uploaded in two situations that differ from the regularly scheduled polling times: When a remote user clicks upload batches from the navigation bar on the Manual Synchronization page. When a remote user clicks the Synchronize Now button located on the Remote Synchronization Agent dialog box. Both situations are explained in this section. 52 Getting Started with Ascent Capture Internet Server 5

61 Using ACI Server! To upload batches from the Manual Synchronization page 1 Start your browser and open the Manual Synchronization page. 2 From the navigation bar, click upload batches. All batches marked as Completed will be uploaded from the remote station to the central site. As the batches are uploaded, a Sending Batches message will display in the status bar of your browser. When all batches are uploaded, the message Done will display in the status bar.! To upload batches from the Windows taskbar icon 1 From the Remote Synchronization Agent Windows taskbar icon, do one of the following: Double-click the icon Right-click the icon and select the Status option from the menu The Remote Synchronization Agent dialog box will be displayed. 2 Click Synchronize Now. The remote station will immediately upload any completed batches, and then automatically poll the central site to check for published batch classes. All published batch classes available from the central site will be downloaded to your remote station (which could take a few minutes if the administrator has republished batch classes at the central site). For each downloaded batch class, a message similar to Get file pubtypes \ mdb will be displayed on the status line above the log. When polling is complete, the message Done will display briefly on the status line. 3 To close the dialog box, click Hide. Getting Started with Ascent Capture Internet Server 5 53

62 Chapter 4 Monitoring Batch Activity You can check the status of ACI Server batch polling activity by viewing the Remote Synchronization Agent status log, which is available from the Manual Synchronization page. The status log is also available from the Remote Synchronization Agent Windows taskbar icon (see the section Remote Synchronization Agent Windows Taskbar Icon in Chapter 3). Both ways to open the status log are explained in this section. The status log lists the most recent activity between remote stations and the central site. The log gives you information about batch classes downloaded to a remote station, batches uploaded to the central site, and other statuses. On the Manual Synchronization page, each status log entry is preceded by a colorcoded bullet, as follows: Green Success Messages Yellow Warning Messages Red Error Messages When you view the status log from the Remote Synchronization Agent Windows taskbar icon, the log format is the same, without the color-coding. To view the status log, do one of the following: Open the Manual Synchronization page. The status log will be displayed, as shown in Figure 4-2. Right-click the Remote Synchronization Agent Windows taskbar icon and select Status from the menu. The status log will be displayed, as shown in Figure 4-3. Double-click the Remote Synchronization Agent Windows taskbar icon. The status log will be displayed, as shown in Figure Getting Started with Ascent Capture Internet Server 5

63 Using ACI Server Figure 4-2. Status Log from Manual Synchronization Page Figure 4-3. Status Log from Remote Synchronization Agent Getting Started with Ascent Capture Internet Server 5 55

64 Chapter 4 Batch Class Considerations When using the ACI Server for Ascent Capture batch processing, the system administrator should be aware of the following information that relates to image folders, OCR dictionaries, user tracking, partial batch release, and database validation. Image Folders For your batch classes, you must specify the path to an image folder. If your IIS Web server and your Ascent Capture server are installed on different stations, you should use the Universal Naming Convention (UNC) format for this path. If you use an explicit drive letter in a non-unc format, that drive must be mapped to your IIS Web server. Problems will occur if you try to upload batches when the drive letter is not mapped. Note that mappings are not available unless someone is logged in on the server.! To specify the path to an image folder 1 When defining new batch classes, specify the path in UNC format to the desired image folder. You specify this folder on the Create Batch Class dialog box (General tab). Figure 4-4. UNC Path for Batch Class Image Folder 56 Getting Started with Ascent Capture Internet Server 5

65 Using ACI Server 2 For any existing batch classes, update the path to the image folder to UNC format. You edit this folder specification on the Batch Class Properties dialog box (General tab). For details on defining batch classes, refer to your Ascent Capture documentation or online help. Note If your image folder is located on an NTFS partition, the anonymous user that you specify for your ACIS virtual directory must have write permissions to that folder. Refer to the section Images Folder Permissions in Appendix C for details. OCR Dictionaries Ascent Capture allows you to specify OCR dictionaries from any folder on your station. Copies of the OCR dictionaries are automatically placed in an OcrDict folder located in your Ascent Capture installation folder. The first time batch classes are downloaded to your remote stations, the download process will create the OcrDict folder in your Ascent Capture installation folder on the remote stations. Then, it will copy all the OCR dictionaries to that folder. Thereafter, the download process will copy the OCR dictionaries from the central site and overwrite the ones at the remote stations. For details on OCR dictionaries, refer to your Ascent Capture documentation or online help. User Tracking User tracking statistics for completed and deleted batches at each remote site are collected and uploaded to the central site if the User Tracking feature is enabled in Ascent Capture at the central site. Once enabled, user tracking will begin the next time: A remote station automatically polls the central site A user at the remote station downloads batch classes from the Manual Synchronization page A user at the remote station clicks the Synchronize Now button located on the Remote Synchronization Agent dialog box. (The dialog box is accessed by double-clicking the Remote Synchronization Agent Windows taskbar icon.) Getting Started with Ascent Capture Internet Server 5 57

66 Chapter 4 Note that the merge utility does not need to be run at your remote sites. Statistics from your remote sites are automatically copied to the Stats.mdb file located at the central site. Note User statistics are uploaded for the current and previous month only. For example, if a batch takes longer than two months to process, the user tracking statistics for that batch will not be uploaded to the central site. For more information on the user tracking feature, see the Ascent Capture online help. Partial Batch Release Batches for which partial batch release is enabled are processed at the remote and central sites as follows: At the remote site: Batches are routed from Scan through all modules set to run at the remote site. Then, for any batch that contains errors, the rejected documents and pages are routed to Quality Control (Rescan) for repair at the remote site. Once repaired, the documents and pages are processed through the batch class workflow at the remote site starting with the first queue after Scan. When all documents and pages are successfully processed at all modules set to run at the remote site, the batch is marked Completed and is ready for uploading to the central site. Note that batches cannot be uploaded to the central site until all errors have been fixed. At the central site: Batches are routed from the first module set to run at the central site through Release. At Release, all error-free documents and pages are released, and any rejected documents and pages are routed to Quality Control (Rescan) for repair at the central site. Once repaired, the documents and pages are processed through the batch class workflow, starting with the first queue after Scan at the central site. Note that batches with errors are not sent back to the remote site for repair. 58 Getting Started with Ascent Capture Internet Server 5

67 Using ACI Server Database Validation Ascent Capture 5 supports a database validation feature, whereby database lookups can be used to fill data fields in Validation. To use this feature, database validation must be enabled for a batch class, and the appropriate database software and files must be available to your Validation modules. If your Validation module is set to run at remote sites, and database validation is enabled in the batch classes used by remote sites, you must set up the appropriate databases at all remote sites where Validation will run. If the database files are not accessible to the Validation module, the error Could not find file Database File Name will be generated when the Validation module is started at the remote site. Refer to your Ascent Capture documentation for more information about database validation. Note When batch classes for which database validation is enabled are downloaded to remote sites, no checking is performed to ensure that the appropriate databases are set up for Validation modules set to run at the remote sites. Getting Started with Ascent Capture Internet Server 5 59

68 Chapter 4 Monitoring Event Log Activity At a remote site, each time the Remote Synchronization Agent is started or stopped, an event is logged to the application log on that remote station (Windows 2000 or Windows NT only). You can view the application log using Event Viewer. For details about how to use Event Viewer, see your Microsoft documentation.! To display the application log on Windows Select Start Settings Control Panel. 2 Select Administrative Tools. 3 Select Event Viewer. 4 Select the application log from the Tree tab located in the left pane. 5 Double-click any line item in the log to see additional detail about the event.! To display the application log on Windows NT 1 Select Start Programs Administrative Tools (Common) Event Viewer. 2 Select Log Application to ensure you are viewing the application log. 3 Double-click any line item in the log to see additional detail about the event. 60 Getting Started with Ascent Capture Internet Server 5

69 Appendix A Glossary Anonymous access Allows remote access to a computer by using the IUSR_computername or guest account. Remote users can connect without a user name and password. The account has security restrictions that limit the type of Web content users can access. Ascent Capture Internet Server (ACI Server) module Module that adds remote scanning and processing capabilities to Ascent Capture. Ascent Capture remote station Workstation on which Ascent Capture is installed at a remote site. Ascent Capture station Workstation on which Ascent Capture is installed at the central site. If Ascent Capture is installed in a client/server configuration, this term refers to the client station. ASP pages Active Server Pages. A server-side scripting environment that runs ActiveX scripts and ActiveX components on a server. Browser See Web browser. Central site The site at which your central Ascent Capture installation is located. Getting Started with Ascent Capture Internet Server 5 61

70 Appendix A Client/Server configuration An Ascent Capture installation whereby the Ascent Capture database and other files are installed on a server station, and the Ascent Capture modules run on client stations. The server station and the client stations are connected via a LAN. The client stations share the database and files installed on the server. ACI Server does not support this type of Ascent Capture configuration for remote stations. Custom module A user-created Ascent Capture module that is registered and added to batch class workflows for specialized processing functions. Dongle See Hardware key. Download Process by which published batch classes and settings are transferred from the central site to a remote station. Hardware key HTML IIS A device that plugs into a computer s parallel port to prevent the unlicensed use of software. Hardware keys are required for running some of the Ascent Capture modules, and control the number of pages you can scan in a month. In addition, ACI Server requires a hardware key to be attached to the IIS Web server station. Hardware keys are sometimes called dongles. Hypertext Markup Language (HTML). A simple markup language used to create hypertext documents for use on the World Wide Web. See Microsoft Internet Information Server. IIS Web server This is the workstation on which the ACI Server software is installed. The station must be configured as an IIS Web server. The IIS Web server must have a virtual directory that points to the Ascent Capture installation on the same LAN. LAN access Local Area Network access. Access to a group of interconnected computers. 62 Getting Started with Ascent Capture Internet Server 5

71 Glossary Microsoft Internet Information Server (IIS) A network file and application server for the Microsoft Windows NT Server or Windows 2000 Server operating systems. It is the base component for building an Internet or Intranet server solution. Refer to your Microsoft documentation for details. Polling interval Polling refers to the ACI Server process of periodically checking for batches, batch classes, and user information to process. Polling interval refers to the amount of time between polling times. Proxy server A firewall component that manages Internet traffic to and from a local area network (LAN). Release Process by which completed batches are transferred from Ascent Capture to another application. Once released, the batches are not available to Ascent Capture. Batches can be released only from the Ascent Capture Release module installed at the central site. Remote site The site at which an Ascent Capture remote station is located. Remote station Workstation at a remote site on which Ascent Capture and the Remote Synchronization Agent are installed. Remote Synchronization Agent Remote station software used to synchronize Ascent Capture batch processing activity between the central site and the remote site. It includes software that runs in the browser and also a Windows taskbar application. Secure Sockets Layer (SSL) A secure communications channel to prevent interception of critical information over the World Wide Web. Getting Started with Ascent Capture Internet Server 5 63

72 Appendix A Standalone An Ascent Capture installation whereby the Ascent Capture database and all Ascent Capture modules run on one PC. With ACI Server, remote stations must be installed as Ascent Capture standalone stations. All Ascent Capture modules set to run at the remote site run from the standalone station. Synchronization Process by which batch classes and other settings at the central site are downloaded to remote stations. If completed batches exist at the remote station, the batches are uploaded to the central site. TCP/IP protocol Transmission Control Protocol/Internet Protocol. A protocol for communications between computers. Upload Process by which completed batches are transferred from the remote site to the central site. User profiles The Ascent Capture user profiles defined for users. They specify Ascent Capture user privileges, such as module access and batch class access. User profiles are defined from the Ascent Capture Administration module, which for ACI Server, must be run at the central site. Virtual directory A Web server uses virtual directories to map URLs to physical directories that are accessible from the Web server. Web browser A software application used to find and display Web pages and applications. Remote users access the ACI Server Web pages (such as the Installation page, Manual Synchronization page, and others) through a Web browser. 64 Getting Started with Ascent Capture Internet Server 5

73 Appendix B Custom Module Registration Introduction Ascent Capture allows you to create custom modules to perform unique functions suited to your business needs. A custom module is often registered using the Ascent Capture Administration module. With Ascent Capture Internet Server, the Administration module is disabled at all remote sites. This appendix describes how to register a custom module using the Custom Module Registration Utility. For details about creating, registering, and using custom modules with Ascent Capture, see the Ascent Capture 5 Advanced Features Guide. Registering a Custom Module If you plan on using a custom module at your remote stations, you must register the custom module at your central site and at each remote station after you install ACI Server. Then, you can add the custom module to the batch class workflow. To register the custom module at remote stations, the custom module executable and registration files must be provided for each remote station. Note The custom module must be registered at a remote site after the ACI Server Remote Synchronization Agent is installed, or the remote station will not be able to download classes from the central site. Getting Started with Ascent Capture Internet Server 5 65

74 Appendix B! To register a custom module 1 Copy the custom module executable (.exe) and registration (.acm) files to your Ascent Capture Bin directory. 2 Open an MS-DOS Prompt or Command Prompt window. To do so, follow the applicable directions below: Windows 98: Select Start Programs MS-DOS Prompt. Windows NT 4.0: Select Start Programs Command Prompt. Windows 2000: Select Start Programs Accessories Command Prompt. Windows Me: Select Start Programs Accessories MS-DOS Prompt. 3 Go to your Ascent Capture Bin directory. For example, if your Ascent Capture software is located in your Program Files folder, enter the following: cd C:\ Program Files \Ascent\Bin 4 Register your custom module by executing the Custom Module Registration Utility RegAscCM.exe. To do so, enter the following: RegAscCM.exe /f acmfilename /m modulename where: acmfilename is the name of your registration (.acm) file modulename is the name of your custom module Note If successful, the following message will be returned: Success (1002) : Module 'modulename' registered. 5 Type the following to close the MS-DOS Prompt or Command Prompt window: Exit 66 Getting Started with Ascent Capture Internet Server 5

75 Appendix C IIS Settings Introduction ACI Server requires certain IIS Web server property settings for your ACIS, Ascent, and Upload virtual directories. These settings are automatically set by the ACIS Configuration Wizard during the installation. If desired, you can enable additional settings. This appendix identifies the minimum IIS and NTFS security settings required by ACI Server. Refer to your Microsoft documentation for details on additional settings.! To display the ACI Server Web site properties on Windows 2000 Server 1 Run the Internet Information Services application from your IIS Web server station. To do so, select Start Programs Administrative Tools Internet Services Manager. 2 Expand the Internet Information Services tree to display your ACIS Web site. The ACIS Web site is located in the Default Web Site folder. 3 Right-click the applicable directory (ACIS, Ascent, or Upload) and select Properties.! To display the ACI Server Web site properties on Windows NT Server 1 Run the Microsoft Management Console from your IIS Web server station. To do so, select Start Programs Windows NT 4.0 Option Pack Microsoft Internet Information Server Internet Service Manager. 2 Expand the Internet Information Server tree to display your ACIS Web site. The ACIS Web site is located in the Default Web Site folder. 3 Right-click the applicable directory (ACIS, Ascent, or Upload) and select Properties. Getting Started with Ascent Capture Internet Server 5 67

76 Appendix C ACIS Required Properties The ACIS virtual directory stores the ACI Server Web pages and associated program files. On the ACIS Properties page, make sure the following settings are selected: Read access Ascent for Application name Windows 2000 Server: Scripts and Executables for Execute Permissions Windows NT Server: Execute (including script) for Permissions The ACIS Properties page will look similar to the following: Figure C-1. ACIS Virtual Directory Required Properties on Windows 2000 Server Note For Windows NT Server, the ACIS Configuration Wizard does not set the Run in separate memory space (isolated process) option. It is recommended that you set it in order to run your ACI Server application independently from other IIS Web server applications. For Windows 2000 Server, the High (Isolated) application protection set by default is recommended but not required. 68 Getting Started with Ascent Capture Internet Server 5

77 IIS Settings Ascent Required Properties The Ascent virtual directory points to your Ascent Capture root installation folder. It is used when downloading batch classes and their associated files. On the Ascent Properties page, make sure the following settings are selected: Read access Windows 2000 Server: None for Execute Permissions Windows NT Server: None for Permissions The Ascent Properties page will look similar to the following: Figure C-2. Ascent Virtual Directory Required Properties on Windows 2000 Server Getting Started with Ascent Capture Internet Server 5 69

78 Appendix C Ascent Capture and IIS Web Server on Different Computers If Ascent Capture is located on a different computer than the IIS Web server, the Network Directory property is displayed instead of the Local Path property. See Figure C-3. In this case, the user account assigned to connect to the Network Directory must have full control permissions. Ensure the user account meets one of the following criteria: If IIS is installed within a domain, ensure the user is a domain-wide account that has permissions on both the IIS Web server and the Ascent Capture server. Note that if IIS is installed within a domain, the domain name should be specified with the Username. If IIS is not installed within a domain, ensure the user exists on both the IIS Web server and the Ascent Capture server and has the same password.! To display the network directory user 1 Run the Microsoft Management Console. To do so, do one of the following: Windows 2000 Server: Select Start Programs Administrative Tools Internet Services Manager. Windows NT Server: Select Start Programs Windows NT 4.0 Option Pack Microsoft Internet Information Server Internet Service Manager. 2 Expand the Internet Information Server tree to display your ACIS Web site. The ACIS Web site is located in the Default Web Site folder. 3 Right-click the Ascent directory and select Properties. 70 Getting Started with Ascent Capture Internet Server 5

79 IIS Settings Figure C-3. Ascent Virtual Directory Network Directory Option on Windows 2000 Server 4 Click Connect As to display the user account assigned to connect to the Ascent Capture server. Note that if IIS is installed within a domain, the domain name should be specified with the Username. Figure C-4. Network Directory Security Credentials Dialog Box Getting Started with Ascent Capture Internet Server 5 71

80 Appendix C Upload Required Properties The Upload directory temporarily stores batches as they are uploaded to the central site. On the Upload Properties page, make sure the following settings are selected: Write access Windows 2000 Server: None for Execute Permissions Windows NT Server: None for Permissions Note The ACIS Configuration Wizard enables anonymous access with write permission for the Upload virtual directory. This allows completed batches to be uploaded to the central site without remote users having to log in to an account on the IIS Web server. Anonymous access is required to allow remote stations to automatically poll the central site. The Upload Properties page will look similar to the following: Figure C-5. Upload Virtual Directory Required Properties on Windows 2000 Server 72 Getting Started with Ascent Capture Internet Server 5

81 IIS Settings Anonymous User Account The anonymous user account is used as the logon account for remote users. Typically IUSR_computername (where computername is the name of your computer) is used as the anonymous user account. You may use another user account if desired, but be sure to consider the following when doing so: If IIS is installed on a domain controller, ensure the anonymous user account has permissions on the Ascent Capture server. By default, the anonymous user account will be a domain-wide account. If IIS is installed on a member server (rather than a domain controller), ensure the anonymous user account is a domain-wide account that has permissions on the IIS Web server and the Ascent Capture server. If IIS is not installed within a domain, ensure the anonymous user account exists on both the IIS Web server and the Ascent Capture server and has the same password. Note The user name specified for the anonymous user account must have Log on locally permission for the IIS Web server or be a member of a group that has this permission. To identify if your anonymous user account has Log on locally permission, refer to the applicable procedure below.! To display users with Log on locally rights on a Windows 2000 IIS Web Server 1 Select Start Programs Administrative Tools Local Security Policy. Note If your computer is a domain controller, you need to select Domain Controller Security Policy rather than the Local Security Policy. 2 Expand the tree to display Security Settings\Local Policies\User Rights Assignment. 3 Right-click the Log on locally right and select Security. 4 The users with Log on locally rights are specified in the Assigned To list. Getting Started with Ascent Capture Internet Server 5 73

82 Appendix C! To display users with Log on locally rights on a Windows NT IIS Web Server 1 Select Start Administrative Tools (Common) User Manager for Domains. 2 Select Policies User Rights. 3 Select Log on locally from the Right: drop-down list. 4 The users with Log on locally rights are specified in the Grant To: list. Allow IIS to Control Password Settings The ACIS Configuration Wizard enables or disables the Allow IIS to control password setting for all three ACI Server virtual directories (ACIS, Ascent, and Upload). Note that with Windows NT, this property is called Enable Automatic Password Synchronization. This setting determines if the anonymous user has network credentials to log in to another computer on the network. The Allow IIS to control password (Windows 2000 Server) or Enable Automatic Password Synchronization (Windows NT Server) setting should be enabled or disabled as follows: If the anonymous user specified is a local user and Ascent Capture is installed on the IIS Web server, the setting should be checked for all ACI Server virtual directories (ACIS, Ascent, and Upload). If the anonymous user specified is a local user and Ascent Capture is not installed on the IIS Web server, the setting should be cleared for all ACI Server virtual directories. If the anonymous user specified is a domain user (regardless of where Ascent Capture is installed), the setting should be cleared for all ACI Server virtual directories.! To display password settings 1 Run the Microsoft Management Console. To do so, do one of the following: Windows 2000 Server: Select Start Programs Administrative Tools Internet Services Manager. Windows NT Server: Select Start Programs Windows NT 4.0 Option Pack Microsoft Internet Information Server Internet Service Manager. 2 Expand the Internet Information Server tree to display your ACIS Web site. The ACIS Web site is located in the Default Web Site folder. 3 Right-click the applicable directory (ACIS, Ascent, or Upload) and select Properties. 74 Getting Started with Ascent Capture Internet Server 5

83 IIS Settings 4 Select the Directory Security tab. 5 Select Anonymous Access and Authentication Control Edit. The Authentication Methods dialog box will appear. 6 Do one of the following: Windows 2000 Server: Select Anonymous access Edit. Windows NT Server: Select Allow Anonymous Access Edit. The Anonymous User Account dialog box will appear. See Figure C-6 and Figure C-7. Figure C-6. Anonymous User Account Dialog Box on Windows 2000 Server Figure C-7. Anonymous User Account Dialog Box on Windows NT Server Getting Started with Ascent Capture Internet Server 5 75

84 Appendix C NTFS Security Settings If ACI Server and/or Ascent Capture are installed on NTFS partitions, ensure that the ACIS, Ascent, Upload, and Scripts folders (not virtual directories) have the minimum required permissions documented in this section. Note that these folders may be located on separate computers. This section also describes required permissions for the Common Files folder (located under the Program Files folder) and the System Variables TEMP folder if they are located on NTFS partitions. The Common Files folder and TEMP folder requirements only apply to the computer where ACI Server is installed. Note A reboot is required for NTFS security setting changes to take effect.! To display folder permissions on Windows 2000 Server 1 Run Windows Explorer. To do so, select Start Programs Accessories Windows Explorer. 2 Right-click the applicable folder. 3 Select Properties Security tab to display folder permissions.! To display folder permissions on Windows NT Server 1 Run Windows NT Explorer. To do so, select Start Programs Windows NT Explorer. 2 Right-click the applicable folder. 3 Select Properties Security tab. 4 Click Permissions to display the Directory Permissions dialog box. 76 Getting Started with Ascent Capture Internet Server 5

85 IIS Settings ACIS Folder Permissions Default location: C:\Inetpub\wwwroot\ACIS on the computer where ACI Server is installed The ACIS folder, if located on an NTFS partition, must have full control permissions for the following user: The anonymous user account used for the ACIS virtual directory (typically IUSR_computername, where computername is the name of your computer). The ACIS folder must have read and execute permissions for the following user: Windows 2000 Server: The Component Services user for the ACI Server application (typically IWAM_computername, where computername is the name of your computer) if you are running ACI Server as a High (Isolated) or Medium (Pooled) application process. To identify your Component Services user, refer to the procedure To display the Component Services user on Windows 2000 Server on page 83. Windows NT Server: The Transaction Server user for the ACI Server application (typically IWAM_computername, where computername is the name of your computer) if you are running ACI Server in a separate memory space (isolated process). To identify your Transaction Server user, refer to the procedure To display the Transaction Server user on Windows NT Server on page 84. Ascent Folder Permissions Default location: C:\Program Files\Ascent on the computer where Ascent Capture is installed The Ascent folder, if located on an NTFS partition, must have full control permissions for the following users: The anonymous user account used for the ACIS virtual directory (typically IUSR_computername, where computername is the name of your computer). The anonymous user account used for the Ascent virtual directory (typically IUSR_computername, where computername is the name of your computer). The user account assigned to connect to the Network Directory if Ascent Capture is located on a different computer than the IIS Web server. For more information, see the section Ascent Capture and IIS Web Server on Different Computers on page 71. Getting Started with Ascent Capture Internet Server 5 77

86 Appendix C Images Folder Permissions Default location: C:\Program Files\Ascent\Images on the computer where Ascent Capture is installed The Images folder provides a temporary storage location for Ascent Capture image files from the time they are captured by the Scan module until they are released to permanent storage by the Release module. You set this folder for each Ascent Capture batch class using the General tab available on the Create Batch Class or Batch Class Properties dialog box. The required permissions for the Images folder are usually correct if you use the default storage location. If you store your Ascent Capture images somewhere else, you will need to verify that the folder, if located on an NTFS partition, has write permissions for the following user: The anonymous user account used for the ACIS virtual directory (typically IUSR_computername, where computername is the name of your computer). Note If you use different image folders for different batch classes, you will need to set write permissions for each image folder that is located on an NTFS partition. Upload Folder Permissions Default location: C:\Inetpub\wwwroot\ACIS\Upload on the computer where ACI Server is installed The Upload folder, if located on an NTFS partition, must have full control permissions for the following users: The anonymous user account used for the ACIS virtual directory (typically IUSR_computername, where computername is the name of your computer). The anonymous user account used for the Upload virtual directory (typically IUSR_computername, where computername is the name of your computer). Scripts Folder Permissions Default location: C:\Inetpub\Scripts on the computer where ACI Server is installed If using Windows NT Server, the Scripts folder, if located on an NTFS partition, must have read and execute permissions for the following user: The anonymous user account used for the Scripts folder (typically IUSR_computername, where computername is the name of your computer). 78 Getting Started with Ascent Capture Internet Server 5

87 IIS Settings Common Files Permissions Default location: C:\Program Files\Common Files on the computer where ACI Server is installed The required permissions for the Common Files folder are usually correct by default. The Common Files folder, if located on an NTFS partition, must have full control permissions for the following users: The anonymous user account used for the ACIS virtual directory (typically IUSR_computername, where computername is the name of your computer). Windows 2000 Server: The Component Services user for the ACI Server application (typically IWAM_computername, where computername is the name of your computer) if you are running ACI Server as a High (Isolated) or Medium (Pooled) application process. To identify your Component Services user, refer to the procedure To display the Component Services user on Windows 2000 Server on page 83. Windows NT Server: The Transaction Server user for the ACI Server application (typically IWAM_computername, where computername is the name of your computer) if you are running ACI Server in a separate memory space (isolated process). To identify your Transaction Server user, refer to the procedure To display the Transaction Server user on Windows NT Server on page 84. System Variables TEMP Folder Permissions Default location: C:\Temp on the computer where ACI Server is installed The required permissions for the TEMP folder are usually correct by default. The TEMP folder location is specified using the Control Panel. The TEMP folder for your system variables, if located on an NTFS partition, must have full control permissions for the following users: The anonymous user account used for the ACIS virtual directory (typically IUSR_computername, where computername is the name of your computer). Windows 2000 Server: The Component Services user for the ACI Server application (typically IWAM_computername, where computername is the name of your computer) if you are running ACI Server as a High (Isolated) or Medium (Pooled) application process. To identify your Component Services user, refer to the procedure To display the Component Services user on Windows 2000 Server on page 83. Windows NT Server: The Transaction Server user for the ACI Server application (typically IWAM_computername, where computername is the name of your computer) if you are running ACI Server in a separate memory space Getting Started with Ascent Capture Internet Server 5 79

88 Appendix C (isolated process). To identify your Transaction Server user, refer to the procedure To display the Transaction Server user on Windows NT Server on page 84. Identifying Your Component Services or Transaction Server User Follow the procedures below to identify your Component Services user on Windows 2000 Server or the Transaction Server user on Windows NT Server.! To display the Component Services user on Windows 2000 Server 1 Select Start Programs Administrative Tools Component Services. 2 Expand the Component Services tree to display Console ROOT\Component Services\Computers\My Computer\COM+ Applications. 3 If using a High (Isolated) application process, right-click the IIS-{Default Web Site//ROOT/ACIS} and select Properties. If using a Medium (Pooled) application process, right-click IIS Out-Of- Process Pooled Applications and select Properties. Note If you are running ACI Server as a Medium (Pooled) or Low (IIS Process) application process, the IIS-{Default Web Site//ROOT/ACIS} will not exist. 4 The Component Services user is specified on the Identity tab. See Figure C Getting Started with Ascent Capture Internet Server 5

89 IIS Settings Figure C-8. IIS {Default Web Site//ROOT/ACIS} Properties Dialog Box! To display the Transaction Server user on Windows NT Server 1 Select Start Programs Windows NT 4.0 Option Pack Microsoft Transaction Server Transaction Server Explorer. 2 Expand the Microsoft Management Console tree to display Console Root\Microsoft Transaction Server\Computers\My Computer\Packages Installed. 3 Right-click the IIS-{Default Web Site//ROOT/ACIS} and select Properties. Note If ACI Server is not running in a separate memory space (isolated process), the IIS-{Default Web Site//ROOT/ACIS} will not exist. 4 The Transaction Server user is specified on the Identity tab. See Figure C-8. Getting Started with Ascent Capture Internet Server 5 81