c1932321 PDF

IBM Datacap Taskmaster Capture
Version 8.0.1
Installation and Configuration Guide
GC19-3232-01
Version 8.0.1
GC19-3232-01
Note
Before using this information and the product it supports, read the information in “Notices” on page 1.
This edition applies to version 8, release 0 of IBM Datacap Taskmaster (product number 5725-C15) and to all
subsequent releases and modifications until otherwise indicated in new editions.
© Datacap Inc. 1994, 2011
Table of Contents
Chapter 1...................................................................................................... 7
Welcome .......................................................................................................................... 7
About this Guide.............................................................................................................. 7
Chapter 2...................................................................................................... 9
Introduction to IBM Datacap Taskmaster Capture 8.0.1 ............................................... 9
What is IBM Datacap Taskmaster Capture? .................................................................. 9
Overview of Taskmaster Architecture ............................................................................. 9
Overview of Taskmaster Components ........................................................................... 10
Locating Applications on a Network ............................................................................. 12
Chapter 3.................................................................................................... 13
Installation and Configuration Prerequisites ............................................................... 13
Configuration Assumptions ........................................................................................... 13
Taskmaster Client-Server Configuration ...................................................................... 13
Before You Begin........................................................................................................... 14
Make a Note of and Shut Down Taskmaster Software .................................................. 14
Backup and Uninstall Taskmaster Versions 7.1 and 7.1 SP1 ....................................... 15
Back Up Taskmaster Version 7.5, 7.5 SP1, 7.6, or 8.0 ................................................. 15
Ensure Domain/Windows Accounts Exist ..................................................................... 16
Ensure Scanner is Set Up and Works............................................................................ 16
Microsoft .NET Framework 3.5.1 ................................................................................. 17
Chapter 4.................................................................................................... 19
Install, Configure, and Run on Single Machine ............................................................ 19
Overview of Taskmaster Installation on Single Machine.............................................. 19
Installation Instructions for Single Machine................................................................. 20
Microsoft .NET Framework 3.5.1 ................................................................................. 20
Install Taskmaster Components on Single Machine ..................................................... 21
Using Taskmaster 1040EZ ............................................................................................ 23
Review Default Installation Results .............................................................................. 28
Taskmaster RV2............................................................................................................. 30
Taskmaster Web ............................................................................................................ 35
Copyright © 1994, 2011 Datacap Inc. Page 3

Internet Explorer ........................................................................................................... 37

Taskmaster Web Client 1040EZ Application ................................................................ 39
Rulerunner Quattro ....................................................................................................... 45
Chapter 5.................................................................................................... 53
Install, Configure, and Run on Client and Server......................................................... 53
Taskmaster Client-Server Configuration ...................................................................... 53
Overview of Taskmaster Installation on Client and Server .......................................... 54
Installation Instructions for Taskmaster Server............................................................ 56
Installation Instructions for Developer Workstation .................................................... 62
Copy APT Application to Taskmaster Server................................................................ 64
Complete Taskmaster Server Configuration ................................................................. 69
Run Taskmaster Client APT Application ...................................................................... 71
Review Default Installation Results .............................................................................. 82
Set Up Taskmaster APT to Process Your Invoice Images............................................. 84
APT Troubleshooting .................................................................................................... 86
Installation Instructions for User Workstation ............................................................. 88
Install and Configure Taskmaster RV2 ......................................................................... 93
Install and Configure Taskmaster Web ....................................................................... 108
Run Taskmaster Web Client APT Application ............................................................ 129
View RV2 Reports for Taskmaster Web APT .............................................................. 136
Install and Configure Rulerunner Quattro.................................................................. 137
Install and Configure Taskmaster Client Service ....................................................... 184
Run Datacap Studio Application................................................................................. 194
Install and Configure NENU....................................................................................... 195
Install and Configure Rulerunner as a Web Service................................................... 214
Configure Windows Authentication for Taskmaster ................................................... 231
Use the Fingerprint Maintenance Tool ....................................................................... 235
Chapter 6.................................................................................................. 237

Uninstall Taskmaster 8.0.1.......................................................................................... 237
Overview of Taskmaster 8.0.1 Uninstall Process ....................................................... 237
Ensure All Taskmaster Clients are Shut Down ........................................................... 237
Ensure All Taskmaster Web Sites and Services are Shut Down ................................. 238
Page 4 Copyright © 1994, 2011 Datacap Inc.

Ensure Taskmaster Server Service is Shut Down........................................................ 238

Create Backup Folders................................................................................................ 238
Backup Custom Applications ...................................................................................... 238
Backup Application Shortcuts ..................................................................................... 238
Uninstall IBM Datacap Taskmaster Capture 8.0.1..................................................... 239
Remove Accounts from Administrator and Backup Operator Groups........................ 239
Delete Registry Keys ................................................................................................... 239
Remove Web Sites and Virtual Folders....................................................................... 239
Reset Application Pool Process Model Identities ....................................................... 240
Remove Process Identity from Machine.Config File .................................................. 240
Delete Program Shortcuts ........................................................................................... 241
Delete Remaining Folders........................................................................................... 241
Appendix A .............................................................................................. 243

Single Machine Setup Checklist .................................................................................. 243
Single IIS 7 Machine Installation................................................................................ 243
Start Taskmaster Server on Single Machine ............................................................... 243
Run Taskmaster Client on Single Machine ................................................................. 244
Set Up RV2 on Single Machine ................................................................................... 244
Configure Taskmaster Web on Single Machine .......................................................... 245
Configure IE 7 and Run Taskmaster Web Client on Single Machine ......................... 245
Configure Single Thread Rulerunner Quattro ............................................................ 246
Run Taskmaster Client 1040EZ Tasks using Quattro ................................................. 248
Appendix B............................................................................................... 249

Client-Server Setup Checklist...................................................................................... 249
Server Setup................................................................................................................. 249
Developer Workstation Setup...................................................................................... 253
Datacap Application Copy Wizard ............................................................................. 253
Complete Server Configuration .................................................................................. 255
Run Taskmaster Client on DevWorkstation ................................................................ 256
Set Up Taskmaster APT to Process Your Invoice Images........................................... 257
End User Workstation and Permissions Setup............................................................ 259
Install and Configure RV2........................................................................................... 260

Install and Configure Taskmaster Web ....................................................................... 265

Configure and Test Remote Workstation .................................................................... 272
Install and Configure Rulerunner Quattro.................................................................. 275
Install and Configure Taskmaster Client Service ....................................................... 288
Install and Configure NENU....................................................................................... 291
Install and Configure Rulerunner as a Web Service................................................... 296
Configure Windows Authentication for Taskmaster ................................................... 302
Use Fingerprint Maintenance Tool............................................................................. 304
Appendix C .............................................................................................. 305

Taskmaster Installer Command Line Parameters....................................................... 305
InstallShield Parameters ............................................................................................. 305
Microsoft Windows Installer Parameters ................................................................... 305
Most Commonly Used Taskmaster Setup.exe Parameters .......................................... 305
Appendix D .............................................................................................. 309

Rulerunner Quattro Manager Reference .................................................................... 309
Rulerunner Quattro Manager How To........................................................................ 317
Troubleshooting Quattro............................................................................................. 321
Appendix E............................................................................................... 325

Fingerprint Maintenance Tool Reference ................................................................... 325
Index ......................................................................................................... 329

Chapter 1
Welcome
Welcome to IBM Datacap Taskmaster Capture 8.0.1 - and to the IBM Datacap Taskmaster
Capture 8.0.1 Installation and Configuration Guide.
This Guide provides you with the information you need to install and configure components of
IBM Datacap Taskmaster Capture in two configurations:
• Install, Configure, and Run on Single Machine
• Install, Configure, and Run on Client and Server
This Welcome chapter describes the contents of the IBM Datacap Taskmaster Capture 8.0.1
Installation and Configuration Guide.
NOTE
The most up to date version of this document is online at:
http://www.ibm.com/support/docview.wss?uid=swg27020850
About this Guide

The IBM Datacap Taskmaster Capture 8.0.1 Installation and Configuration Guide contains the
following chapters:
Chapter 1: Welcome
Chapter 1 describes the contents of this Guide.
Chapter 2: Introduction to IBM Datacap Taskmaster Capture 8.0.1

Chapter 2 provides an introduction to IBM Datacap Taskmaster Capture 8.0.1 capabilities and
architecture.
Chapter 3: Installation and Configuration Prerequisites

Chapter 3 describes what you need before you begin the installation of IBM Datacap
Taskmaster Capture 8.0.1 software. These prerequisites ensure that you can install, configure,
and run the IBM Datacap Taskmaster Capture components of an application either on a single
machine, or on multiple machines in a client-server network configuration.
Chapter 4: Install, Configure, and Run on Single Machine

Chapter 4 describes what you need to know to install the IBM Datacap Taskmaster Capture
software components on a single Microsoft Windows 7 machine, perform minimal
configuration, and run the IBM Datacap Taskmaster Capture software components "out of the
box." This configuration uses the Taskmaster 1040EZ sample application as the example so
you can see it process sample batches of documents. This information is provided to support
demonstration or proof of concept environments.

Chapter 5: Install, Configure, and Run on Client and Server

Chapter 5 describes what you need to know to install, configure, and run IBM Datacap
Taskmaster Capture 8.0.1 in a Microsoft Windows client-server environment for proof of
concept, development, or test purposes. It includes instructions that guide you through setting
up and running IBM Datacap Taskmaster Capture software components "out of the box" and
uses the separately licensed IBM Datacap Taskmaster Accounts Payable Capture application
as the example so you can see it process sample batches of documents.
Chapter 6: Uninstall IBM Datacap Taskmaster Capture 8.0.1

This chapter provides the information you need to uninstall IBM Datacap Taskmaster Capture
8.0.1 software.
Appendix A: Single Machine Setup Checklist

This Appendix provides a summary checklist of the account and configuration settings that are
required to install and run IBM Datacap Taskmaster Capture software components on a single
Windows 7 machine with a single Domain/Windows user who has administrator rights on the
machine.
Appendix B: Client-Server Setup Checklist

This Appendix provides a summary checklist of the account and configuration settings that are
required to install and run IBM Datacap Taskmaster Capture software components in a client-
server environment using separate Windows accounts for services, processes, and users.
Appendix C: Taskmaster Installer Command Line Parameters

This Appendix provides information about the most commonly used parameters available
when running the IBM Datacap Taskmaster Capture InstallShield Setup.exe from the
command line.
Appendix D: Rulerunner Quattro Manager

This Appendix provides information about Rulerunner Quattro Manager, the various settings
that can be used to control and fine-tune Rulerunner Quattro, as well as tips for troubleshooting
Rulerunner Quattro.
Appendix E: Fingerprint Maintenance Tool Reference

This Appendix provides reference information about the Fingerprint Maintenance Tool field
definitions, buttons, and settings file.

Chapter 2
Introduction to IBM Datacap Taskmaster Capture 8.0.1

This chapter provides an overview of IBM Datacap Taskmaster Capture 8.0.1 capabilities and
architecture.
What is IBM Datacap Taskmaster Capture?

IBM Datacap Taskmaster Capture 8.0.1 is a complete solution for document and data capture.
Taskmaster scans, classifies, recognizes, validates, verifies, and exports data and document
images quickly, accurately and cost-effectively.
By combining the best of breed recognition engines for OCR, ICR, OMR and barcodes with
libraries of hundreds of script-based actions, Taskmaster accurately captures data from any
type of structured, highly variable, or unstructured form.
Taskmaster captures machine print, hand print, bar codes, and check box data. Using
Taskmaster's flexible rules engine, data capture can be tailored to fit the most demanding
business requirements – and can be changed quickly when business needs change.
For indexing applications, Taskmaster streamlines the manual data entry of indexes by using
recognition to automatically identify the index values on each document and to automate the
document identification process.
Overview of Taskmaster Architecture

Taskmaster provides a flexible and scalable architecture that lets you distribute tasks across
machines according to the anticipated processing load.
At one end of the spectrum is the single machine configuration, where Taskmaster components
are installed on the same machine. This configuration is typically used for providing product
demonstrations, in a proof of concept environment, or during initial product evaluation.
At the other end of the spectrum is the client-server configuration, where the various
Taskmaster components are installed on dedicated machines (web servers, database servers,
etc.). This configuration can support hundreds of simultaneous users, and uses centralized
application management and shared databases.

And, spanning the center of the spectrum, are various hybrid configurations in which more two
or more Taskmaster component are installed on the same machine. You might, for example,
run Taskmaster Web, RV2, and Rulerunner running as a Web Service on the same web server.
Overview of Taskmaster Components

The main Taskmaster components are:
• Taskmaster Server runs as a Windows service and controls authentication, database
access, and batch processing. Only the Taskmaster Server can access the admin and
engine databases – all other components must access these databases through Taskmaster
Server. The Taskmaster Server installation component includes a restricted version of the
Taskmaster Application Manager. Typically, the main application settings file
(datacap.xml) is found on the Taskmaster Server.
• Taskmaster Client is used to run end-user tasks such as scanning and verification (also
known as the “thick client”). It also lets you configure an application's workflow and
perform administrative tasks such as setting up Taskmaster users. When verifying a batch,
verification rules run on the Taskmaster Client machine, unless the task is configured to
use the Web Rulerunner Service. The Taskmaster Client installation component includes a
restricted version of the Taskmaster Application Manager, as well as optional Datacap
Studio, DotEdit, and NENU subcomponents.

• Datacap Studio is the Taskmaster application development environment. When you

install the Datacap Studio subcomponent, it includes an unrestricted version of the
Taskmaster Application Manager, which lets you manage multi-machine distributed
environments by centralizing key Taskmaster configuration settings in shared files.
• Rulerunner Quattro runs as a Windows service and runs batch processing tasks that do
not require operator interaction, such as recognition and export. In a typical production
environment, Quattro is configured to detect new batches and run the recognition process
automatically. After verification and submission, Quattro detects that the batch is ready
for export and runs the export task automatically. The Rulerunner Quattro installation
component includes a restricted version of the Taskmaster Application Manager.
• Taskmaster Client Service runs as a Windows service and is the legacy background
processor for running batch processing tasks that do not require operator interaction. The
Taskmaster Client Service installation component includes a restricted version of the
Taskmaster Application Manager.
• NENU provides application monitoring and notification capabilities that let you automate
administrative functions such as resetting batches or archiving old batches. The NENU
installation component includes a restricted version of the Taskmaster Application
Manager.
• Taskmaster Web supports browser-based Taskmaster clients. The web client (also known
as the “thin client”) provides similar functionality to the Taskmaster Client but does not
require additional software installed on the workstation. When verifying a batch using the
web client, verification rules run on the Taskmaster Web machine, unless the application is
configured to use the Web Rulerunner Service. The Taskmaster Web installation
component includes a restricted version of the Taskmaster Application Manager.
• Web Rulerunner Service runs rules on behalf of Taskmaster clients (thick and thin). The
Web Rulerunner Service installation component includes a restricted version of the
Taskmaster Application Manager.
• RV2 is the reporting tool that displays real-time reports of Taskmaster activity. RV2 gets
usage statistics and other data from the Engine database. The RV2 installation component
includes a restricted version of the Taskmaster Application Manager.
Other Taskmaster components include:
• Application folder stores Taskmaster application files.
• Batches folder stores files generated during batch processing.
• Taskmaster databases - the three key application databases are:
Admin: Stores information on workflows, users, and groups.
Engine: Stores batch information and statistics.
Fingerprint: Stores page template data.
Additionally, Taskmaster applications can access external, non-Taskmaster databases during
processing (for looking up and validating Vendor IDs, Purchase Order Numbers, zip codes,
Customer IDs, etc.), and can export captured data and images to external systems and
databases, IBM repositories, and other vendors' repositories using standard actions and
separately licensed "connectors."

Locating Applications on a Network

The Taskmaster datacap.xml file (typically found in the shared Datacap folder on the
Taskmaster Server) contains information about the locations of the available Taskmaster
applications.
Each Taskmaster application, in turn, has its own application configuration file that identifies
the locations of the components used by that application. This application configuration file
(.app) includes details about the locations of its components (batches folder, input image
folder, databases, etc.).
The Taskmaster Application Manager is used to identify the location of the datacap.xml file
and to manage the contents of the application configuration files.
In the diagram below, App2's configuration file defines the location of the Taskmaster Server
hosting the application, as well as the locations of the application’s databases, batches folder,
and other components of the application.

Chapter 3
Installation and Configuration Prerequisites

This chapter provides the information you need before you begin the installation of IBM
Datacap Taskmaster Capture 8.0.1 software. These prerequisites ensure that you can install,
configure, and run the IBM Datacap Taskmaster Capture components of an application either
on a single machine, or on multiple machines in a client-server distributed network
configuration.
Configuration Assumptions
For information on hardware and operating system requirements for IBM Datacap Taskmaster
Capture software, see:
http://www.ibm.com/support/docview.wss?uid=swg27020397
To keep things simple, instructions are provided for two configurations:
• Chapter 4 Install, Configure, and Run on Single Machine - These instructions allow
you to install, configure, and run IBM Datacap Taskmaster Capture components on a
single Microsoft Windows 7 machine. This machine is referred to as the “Workstation.”
This configuration uses the Taskmaster 1040EZ sample application as the example so you
can see it process sample batches of documents. This information is provided to support
demonstration or proof of concept environments. The instructions assume your Windows
user account has administrator rights on the Workstation. For a checklist of the account
and configuration settings, see Appendix A: Single Machine Setup Checklist.
• Chapter 5 Install, Configure, and Run on Client and Server - These instructions allow
you to install, configure, and run IBM Datacap Taskmaster Capture 8.0.1 server and client
components in a client-server environment for proof of concept, development, or test
purposes. It includes instructions that guide you through setting up and running
Taskmaster software components "out of the box" and uses the separately licensed IBM
Datacap Taskmaster Accounts Payable Capture application as the example so you can see
it process sample batches of documents. The instructions assume your Windows user
account has administrator rights on every machine on which you will install Taskmaster.
For a checklist of the account and configuration settings, see Appendix B: Client-Server
Setup Checklist.
Taskmaster Client-Server Configuration

Taskmaster can be configured in many ways. The multiple machine configuration used
throughout the client-server examples provided in this Guide includes the following machines:
• Taskmaster Server (referred to as the "Server") hosts the Taskmaster Server, the main
application settings file (datacap.xml), the applications, batch files, and databases. For the
Server, these instructions cover Windows 2003, and Windows 2008.
• Taskmaster Web Server (referred to as the "WebServer") hosts Taskmaster Web and
RV2. For the WebServer, these instructions cover Windows 2003 and Windows 2008.

• Developer Workstation (referred to as the "DevWorkstation") hosts the complete

Taskmaster Client, including Datacap Studio, DotEdit, and NENU. These instructions
cover Windows XP and Window 7.
• End-user Workstation (referred to as the "Workstation") hosts the Taskmaster Client or
only the browser. For the Workstation, these instructions cover Windows XP and
Windows 7.
• Rulerunner Quattro Server (referred to as the "QServer") hosts the Rulerunner Quattro
Service that runs tasks that do not require human interaction. These instructions cover
Windows 2003 and Windows 2008.
• Taskmaster Client Service Server (referred to as the "TCSServer") hosts the Taskmaster
Client Service that runs tasks that do not require human interaction. These instructions
cover Windows 2003 and Windows 2008.
• Web Rulerunner Service Server (referred to ask the "RRServer") hosts Taskmaster
Rulerunner running as a web service. These instructions cover Windows 2003 and
Windows 2008.
These instructions also include information on the accounts and permissions needed for the
following types of users: Implementation/development personnel with administrative rights on
all machines, end users, and accounts for the various Taskmaster processes and services:
Taskmaster Server Service, Rulerunner Quattro Service, Taskmaster Client Service, NENU,
RV2, Rulerunner running as a web service, and Taskmaster Web.
Before You Begin

Before beginning the installation, ensure you have done the following:
• Make a note of and shut down pre-existing Taskmaster software
• Backup and uninstall Taskmaster Versions 7.1 and 7.1 SP1
• Backup Taskmaster Version 7.5, 7.5 SP1, 7.6, or 8.0
• Ensure scanner is set up and works
• Ensure domain accounts exist
• For Windows 7 and Windows 2008 machines, ensure Microsoft .NET Framework 3.5.1 is
installed
Make a Note of and Shut Down Taskmaster Software

Before beginning the installation of IBM Datacap Taskmaster Capture 8.0.1, we recommend
that you make a note of the Taskmaster software components running on each machine before
shutting it down. Regardless of whether all Taskmaster components are installed on a single
machine or the machine is part of a Taskmaster network configuration, you should shut down
the Taskmaster software in the following sequence:
1 Taskmaster Client software for all applications (including Taskmaster Client,
Taskmaster Web Client, Taskmaster Client Service, Rulerunner Quattro Service,
Datacap Studio, Batch Pilot, etc.)
2 Taskmaster Web and any Taskmaster web services (RV2, WRRS, Fingerprint Service,
etc.)

3 Taskmaster Server Service
Backup and Uninstall Taskmaster Versions 7.1 and 7.1 SP1

When either Taskmaster version 7.1 or version 7.1 SP1 exists on a machine on which you want
to install IBM Datacap Taskmaster Capture 8.0.1, you must correctly and completely uninstall
the earlier version before you install IBM Datacap Taskmaster Capture 8.0.1.
WARNING
Uninstalling Taskmaster version 7.1 or version 7.1 SP1 must be performed using the
Windows Add or Remove Programs tool in a specific sequence:
1 Uninstall Datacap Taskmaster
2 Reboot the machine
3 Uninstall Datacap CD
1 Before you begin, ensure you have shut down all software (in addition to the
Taskmaster software) on the machine.
2 Copy the entire shared Datacap folder, including your application’s process folder, to a
backup location.
3 From the Windows Start menu, select Settings, select Control Panel, and double-click
Add or Remove Programs. When the Add or Remove Programs window opens, scroll
down and select Datacap Taskmaster.
4 Click Change/Remove. The Preparing to Install window is displayed, followed by the
Welcome window.
5 Select the Remove option, then click Next. A Confirm Uninstall message box is
displayed.
6 Click OK. The message box closes and the Setup Status window displays a progress
bar for various removal and unregistration activities, followed by the InstallShield
Wizard Complete window. The Yes I want to restart my computer now option is
selected.
7 Click Finish. The window closes, and the machine reboots.
8 When the machine has restarted, log on again.
9 From the Windows Start menu, select Settings, select Control Panel, and double-click
Add or Remove Programs. When the Add or Remove Programs window opens, scroll
down and select Datacap CD.
10 Click Change/Remove. A message box prompts you to confirm you want to remove
Datacap from your computer.
11 Click Yes. The message box is closes and the Setup Status window displays a progress
bar for various removal and unregistration activities, followed by a message box
confirming that Datacap has been uninstalled successfully.
Back Up Taskmaster Version 7.5, 7.5 SP1, 7.6, or 8.0

When Taskmaster version 7.5, 7.5 SP1, 7.6, or 8.0 exists on a machine on which you will
install IBM Datacap Taskmaster Capture 8.0.1, there is no need to remove it before you install

IBM Datacap Taskmaster Capture 8.0.1 (as the 8.0.1 installation process will uninstall it
automatically). However, you should copy the entire shared Datacap folder, including your
application’s process folder, to a backup location. If your databases or batches folders, or any
other Taskmaster components are located separately, make a backup copy of every component.
This ensures you have a backup copy of your customized applications and all separately
purchased Datacap options.
Ensure Domain/Windows Accounts Exist

Single Machine
When installing IBM Datacap Taskmaster Capture components on a single Windows 7
machine, the Windows accounts you need are local users that are usually found on a Windows
workstation: the implementer's/developer's/your own Windows user ID, and the NETWORK
SERVICE and IUSR local users. At a minimum, the Windows User ID you use to log onto the
Workstation must have Administrator rights to the Workstation.
Client-Server Environment
When installing on one or more servers and a developer's workstation (referred to as the
"DevWorkstation"), all machines must be in the same domain, and the domain must also
include separate, individual Domain/Windows accounts for each of the various IBM
Datacap Taskmaster Capture 8.0.1 services, processes, and users.
The Domain/Windows accounts that must be set up include some or all of the following,
depending on which Taskmaster software components you are installing and configuring:
• Implementation/development personnel with administrative rights on all machines
• Individual end users (with more restricted rights)
• Services such as Taskmaster Server Service, Taskmaster Client Service, Rulerunner
Quattro Service
• Processes such as NENU, RV2, Taskmaster Web, and Rulerunner running as a web
service.
Details about the rights and permissions for each type of Windows account are included in
each set of instructions.
In addition, the Windows accounts used for the Taskmaster Windows services (Taskmaster
Server Service, Taskmaster Client Service, Rulerunner Quattro Service) must be granted the
Log on as a Service right on the primary domain controller.
IMPORTANT
In a client-server environment, all users, implementation/development personnel, services,
and processes must log on using the Domain/Windows accounts set up for Taskmaster.
Logging onto a machine using a local account rather than a Domain/Windows account
results in unexpected Taskmaster system behavior.
Ensure Scanner is Set Up and Works

Follow the manufacturer’s instructions to attach the scanner to the Workstation, and install and
configure the required scanner software. Be sure you can scan successfully using the scanner

using any image capture software product. If you cannot scan documents outside of IBM
Datacap Taskmaster Capture, you will not be able to scan documents using Taskmaster.
Note: A physical scanner is not required for running the IBM Datacap Taskmaster Capture
separately licensed or sample applications, as those applications can process the prescanned,
sample images included during installation.
Microsoft .NET Framework 3.5.1

When installing IBM Datacap Taskmaster Capture components on Microsoft Windows 7
Workstations or Microsoft Windows 2008 Servers, ensure the Microsoft .NET Framework
3.5.1 operating system feature has been turned on or added on the machine before you begin
installing Taskmaster.
On Windows 7:
1 From the Windows Start menu, select Control Panel. The Control Panel window opens.
2 Double-click Programs and Features. The Uninstall or change a program window
opens.
3 Select Turn Windows features on or off. The Windows Features dialog opens.
4 Select Microsoft .NET Framework 3.5.1 and click OK. A message window is
displayed.
5 Reboot the machine when prompted.
On Windows 2008:
1 From the Windows Start menu, select Control Panel, and on the Control Panel Home
window, select Administrative Tools, and then select Server Manager.
When UAC is on, the User Account Control window is displayed. Click Continue.
The Server Manager window opens.
2 In the Server Manager hierarchy pane, select Features. The Features currently installed
are displayed.
3 Click Add Features. The Add Features Wizard opens.
4 Select .NET Framework 3.5.1 Feature and click Next. The Confirm Installation
Selections window is displayed.
5 Click Install. The Installation Progress window is displayed, followed by the
Installation Results window.
6 Ensure the installation was successful, then click Close.


Chapter 4
Install, Configure, and Run on Single Machine

This chapter provides the information you need to install IBM Datacap Taskmaster Capture on
a single Windows 7 machine (referred to as the “Workstation”), perform a minimal amount of
configuration, and run IBM Datacap Taskmaster Capture software components "out of the
box," including:
• Taskmaster Server Service
• Taskmaster Client 1040EZ
• RV2
• Taskmaster Web
• Taskmaster Web Client 1040EZ
• Rulerunner Quattro (single thread)
The sections are sequenced deliberately, as some items in later sections depend on steps from
the previous sections having been completed successfully.
For a checklist of the account and configuration settings, see Appendix A: Single Machine
Setup Checklist.
Overview of Taskmaster Installation on Single Machine

You will install and configure IBM Datacap Taskmaster Capture components and run tasks in
the following sequence:
1 Ensure you have met the prerequisites detailed in Chapter 3 Installation and
Configuration Prerequisites, including ensuring Microsoft .NET Framework 3.5.1 is
installed.
2 Run the IBM Datacap Taskmaster Capture InstallShield Wizard, install the default IBM
Datacap Taskmaster Capture software components and any additional components you
have licensed on the Workstation and reboot the Workstation when prompted.
3 Run Taskmaster Client 1040EZ.
4 Configure RV2.
5 Configure Taskmaster Web.
6 Configure Internet Explorer.
7 Run Taskmaster Web Client 1040EZ.
8 Configure Rulerunner Quattro (single thread).
9 Run 1040EZ tasks using Taskmaster Client and Quattro.

Installation Instructions for Single Machine

This section provides the information you need to install all of the IBM Datacap Taskmaster
Capture software components on the Workstation when the Workstation is a Windows 7
machine.
Before proceeding, ensure you have met the prerequisites detailed in Chapter 3 Installation and
Configuration Prerequisites, including ensuring Microsoft .NET Framework 3.5.1 is installed.

On Windows 7:
opens.
displayed.
On Windows 2008:
are displayed.

Install Taskmaster Components on Single Machine

This procedure provides instructions on how to run the IBM Datacap Taskmaster Capture
InstallShield Wizard to install Taskmaster on a single machine (referred to as the
"Workstation"). The components you install include the main Taskmaster components as well
as the separately licensed applications for which you have a license, and the separately
licensed connectors for which you have a license.
WARNINGS
The steps for installing and configuring on more than one machine are significantly
different than the steps for installing on a single machine. For information on how to
install IBM Datacap Taskmaster Capture components on separate machines in a
client/server environment, see Chapter 5 Install, Configure, and Run on Client and
Server.
While the installation package (Setup.exe) can be located anywhere (for example, on an
accessible network drive, on the CD in the Workstation's CD/DVD drive), the
destination of the installed software must be on a physical hard drive of the machine
from which you run the Setup.exe.
Your initial Taskmaster software installation must be into the C:\Datacap folder on the
Workstation. If you do not use this installation path, the sample and foundation
applications will not function out of the box without additional changes.
These instructions apply to Windows 7.
1 Make the installation package available on your network, or insert the IBM Datacap
Taskmaster Capture CD in the Workstation’s CD/DVD drive. If the installation process
does not start automatically, or if the package is on the network, open Windows
Explorer, navigate to and double-click the Setup.exe.
When UAC is on, the User Account Control window opens. Click Yes.
The Select the language window opens.
2 Select the appropriate language, then click OK.
3 When additional, redistributable software is required, the InstallShield Wizard installs
it.
4 The InstallShield Wizard displays a Preparing to Install... window followed by the
InstallShield Wizard Welcome window.
5 Click Next. The Software License Agreement window opens.
6 Select the I accept the terms in the license agreement option, then click Next. The
Setup Type window is displayed with the Complete option selected.
7 Select the Custom option, then click Next. The Custom Setup window is displayed.
8 Expand the Taskmaster Client software component and include the separately licensed
applications for which you have a license, then expand the Connectors software
component and include the connectors for which you have a license.
9 Click Next. The Ready to Install the Program window is displayed.
10 Click Install. The Installation Wizard displays progress messages and a progress
indicator, and when complete, displays the InstallShield Wizard Complete window.

11 Click Finish. A prompt to reboot your machine is displayed.

12 Click Yes. The message box closes and the Workstation is rebooted.

Using Taskmaster 1040EZ

This section provides the information you need to run the IBM Datacap Taskmaster Capture
sample 1040EZ application “out of the box.” These instructions involve starting the
Taskmaster Server Service, starting the Taskmaster Client 1040EZ application, and running
the default 1040EZ tasks to process sample, pre-scanned images. The sample images are
provided so you can run using a “virtual scan” without having to hook up a real scanner to the
Workstation.
Overview of Taskmaster Client 1040EZ

The default shortcuts you run, and the sequence in which you run them using the Taskmaster
Client 1040EZ are as follows:
This shortcut Allows you to

Scan Process sample, pre-scanned images.
PageID Identify and assign page type to image.
Recognize Perform recognition and capture data on the page.
Verify/Fixup Perform data validation.
Export Complete processing of images and produce output.
Ensure or Set Location of Datacap.xml

This procedure provides instructions on how to ensure or set the location of the Taskmaster
application settings file using the Taskmaster Application Manager. In the examples used in
this Installation and Configuration Guide, the datacap.xml file containing the application
settings is found in the C:\Datacap folder.
1 From the Windows Start menu, select All Programs, select Datacap, select Taskmaster
Client, and select Taskmaster Application Manager.
On Windows 7 or Windows 2008, when UAC is on, the User Account Control window
is displayed. Click Yes.
The Taskmaster Application Manager window opens.
2 Click the Service tab to display it.
3 Change or ensure the path reflects the correct location of the datacap.xml file, for
example:
C:\Datacap\datacap.xml
4 Close Taskmaster Application Manager.
Start or Ensure Taskmaster Server Service is Started

All configurations of IBM Datacap Taskmaster Capture (all components installed on a single
Workstation or separate components installed on different machines) require that the
Taskmaster Server Service be running before you can successfully start the application.
This procedure provides instructions on how to start or ensure the Taskmaster Server Service is
started when the operating system is Windows 7.

1 From the Workstation's Windows Start menu, select All Programs, select Datacap,
select Taskmaster Server, and click Taskmaster Server Manager.
The Taskmaster Server Manager window opens.
2 When the Status:
Shows as Running, continue with the next step.
Shows as Stopped, click Start. A Starting Service message is displayed. The Status
changes to Running when the service is started.
3 Close the Taskmaster Server Manager window.
Start Taskmaster Client 1040EZ Application for the First Time

This procedure provides instructions on how to start the Taskmaster Client 1040EZ application
for the first time. Note that after the first time you log into the Taskmaster Client, it
remembers and displays what you entered the previous time.
select Applications, select 1040EZ, and click the 1040EZ Client icon. The Taskmaster
Client window opens, and a Station ID is missing in the profile message is displayed.
2 Click OK. The Please login window opens with your Windows User ID and the name
of your computer displayed.
3 Replace your Windows User ID with admin, enter admin as the password, replace your
computer name with the number 1, then click OK. The Taskmaster Client 1040EZ
main window opens with the Operations pane displayed.
Run Taskmaster Client 1040EZ Scan Task

This procedure provides instructions on how to start the Taskmaster Client 1040EZ Scan job
(this runs the VScan job) to process pre-scanned images.
1 On the Workstation, in the Operations pane, double-click the Scan shortcut. A Task
Monitor window opens and a Rulerunner window opens displaying a progress bar, then
they both close. A message box is displayed indicating the task has finished.
2 Click Stop. The message box closes and the Operations pane is redisplayed. When the
Scan task finishes successfully, 1040EZ has picked up the images from the
\1040EZ\images folder and created a batch which is a collection of document images to
be processed. Taskmaster has assigned a batch ID and created a uniquely-numbered
folder with the name of the batch ID in the \1040EZ\batches folder. This folder holds
all of the document image processing results for this batch of forms, including the
newly-created vscan.xml file.
3 To view information about the batch, in the Operations pane, click the View menu and
select Job Monitor to open the Job Monitor window.
4 To refresh the information displayed in the Job Monitor window, click the Job
Monitor's title bar and press F5. The Job, Task, and Status for this batch have been
updated, and are now Main Job.PageID and pending.
Run Taskmaster Client 1040EZ PageID Task

This procedure provides instructions on how to run the Taskmaster Client 1040EZ Page
Identification task.

You can run this task:

• In the Operations pane, double-click the PageID shortcut
• In the Job Monitor pane, double-click a batch with a pending PageID task
1 On the Workstation, in the Operations pane, double-click the PageID shortcut. A Task
2 Click Stop. The message box closes and the Operations pane is redisplayed.
3 When the PageID task finishes successfully, the images have been organized into
documents, copies (TIO) have been made of the original images, fingerprint (CCO) and
page XML files have been created, along with a PageID.xml file in the batch’s
uniquely-numbered folder in \1040EZ\batches.
updated, and are now Main Job.Recognize and pending.
Run Taskmaster Client 1040EZ Recognize Task

This procedure provides instructions on how to run the Taskmaster Client 1040EZ Recognition
task.
• In the Operations pane, double-click the Recognize shortcut
• In the Job Monitor pane, double-click a batch with a pending Recognize task
1 On the Workstation, in the Operations pane, double-click the Recognize shortcut. A
Task Monitor window opens and a Rulerunner window opens displaying a progress bar,
then they both close. A message box is displayed indicating the task has finished.
3 When the Recognize task finishes successfully, data from each image has been captured
and added to the page XML file along with character confidence values and, a
Recognize.xml file has been created in the batch’s uniquely-numbered folder in
\1040EZ\batches.
updated, and are now Main Job.Verify and pending.
Run Taskmaster Client 1040EZ Verify Task

This procedure provides instructions on how to run the Taskmaster Client 1040EZ Verify task.
• In the Operations pane, double-click the Verify/Fixup shortcut
• In the Job Monitor pane, double-click a batch with a pending Verify task
1 On the Workstation, in the Operations pane, double-click the Verify/Fixup shortcut. A
Task Monitor window opens and a Rulerunner window opens, then the Verify - Batch
Pilot window opens.

2 The following table describes some of the things you can do on the Verify window:
To Do This
Move to next field Press <F10>
containing low confidence
characters
Confirm data in low Press <Tab> (field changes to blue)
confidence field is correct
Move to next data field Press <Tab>
Move to next low Press <Alt+L>
confidence character
Clear all characters from Press <Alt+Z>
field
Run all validations for all Press <Alt+V>
fields on form and return
cursor to first problem on
form
Display the scanned image On the View menu, select Image View,
or press <Ctrl+Alt+I>
Display the batch tree On the View menu, select Batch Tree
or press <Ctrl+Alt+S>
Move the image Click and drag the image
Move to the previous Press <Ctrl+P>
document in the batch
Re-validate data on image Click Validate Return,
or press <F6>
Move to the next problem Press <Ctrl+N>
3 Use the keys and actions in the table above to correct, confirm, or change incorrect or
low confidence field values on each page in the batch.
4 When you have finished with the last document and press <Ctrl+N>, a message box is
displayed indicating No more problems have been found.
5 Click Yes to finish the batch. The message box closes and another message box is
displayed indicating the task has finished.
7 When the Verify task finishes successfully, page XML files have been updated (for
example, when low confidence characters have been changed during Verify), and a

Verify.xml file has been created in the batch’s uniquely-numbered folder found in
\1040EZ\batches.
updated, and are now Main Job.Export and pending.
Run Taskmaster Client 1040EZ Export Task

This procedure provides instructions on how to run the Taskmaster Client 1040EZ Export task.
• In the Operations pane, double-click the Export shortcut
• In the Job Monitor pane, double-click a batch with a pending export task
1 On the Workstation, in the Operations pane, double-click the Export shortcut. A Task
they both close. A message box is displayed indicating the Export task has finished.
3 When the Export task finishes successfully, the Export database has been updated,
XML files for each document and an Export XML file for the batch have been added to
the batch’s uniquely-numbered folder found in \1040EZ\batches.
updated, and are now Main Job.Export and Job done.
5 Exit the Taskmaster Client.

Review Default Installation Results

This section is optional. The instructions provided allow you to review the Taskmaster Client
groups, users, and stations installed by the default installation process and to become familiar
with the panels used to add new groups, users, and stations, and to assign application-specific
permissions.
View Taskmaster Client 1040EZ Groups, Users, Stations

When you perform the default IBM Datacap Taskmaster Capture installation and
configuration, some IBM Datacap Taskmaster Capture groups, users, passwords, and stations
are automatically set up for you in the 1040EZ sample application.
Start Taskmaster Client 1040EZ

This procedure provides instructions on how to start the Taskmaster Client 1040EZ
application. If you have logged into the Taskmaster Client before, the information you entered
previously is displayed.
select Applications, select 1040EZ, and click the 1040EZ Client icon. The Please login
window opens.
2 Ensure the User ID is admin, enter admin as the password, and ensure the Station is set
to 1, then click OK.
3 The 1040EZ main window opens with the Operations pane displayed.
View Taskmaster Client 1040EZ Groups

This procedure provides instructions on how to view the default user security group delivered
as part of the Taskmaster Client 1040EZ.
1 With the Taskmaster Client main window open, on the Settings menu, select Groups.
The IBM Datacap Taskmaster Capture Administrator dialog opens with the Groups tab
displayed on top, and the Groups listed in the left pane.
2 Select a group in the left pane.
3 In the right pane, completely expand the Privileges, Permissions, and Users branches to
view the options set for this group.
4 Do one of the following:
Click the Users tab and continue with step 2 in the View 1040EZ Taskmaster
Client Users procedure.
Click the Stations tab and continue with step 2 in the View 1040EZ Taskmaster
Client Stations procedure.
Click Done to close the IBM Datacap Taskmaster Capture Administrator dialog.
5 If you are finished viewing groups, users, or stations, close the Taskmaster Client
window. A confirmation message box is displayed. Click Yes to close the Taskmaster
Client window.
View Taskmaster Client 1040EZ Users

This procedure provides instructions on how to view the default user permissions delivered as
part of the Taskmaster Client 1040EZ.

1 With the Taskmaster Client main window open, on the Settings menu, select Users. The
IBM Datacap Taskmaster Capture Administrator dialog opens with the Users tab
displayed on top and the Users listed in the left pane.
2 Select a user in the left pane.
3 In the right pane, completely expand the Privileges, Permissions, and Groups branches
to view the options assigned to this user.
Click the Groups tab and continue with step 2 in the View 1040EZ Taskmaster
Client Groups procedure.
Click the Stations tab and continue with step 2 in the View 1040EZ Taskmaster
Client Stations procedure.
Client window.
View Taskmaster Client 1040EZ Stations

This procedure provides instructions on how to view the default station permissions delivered
as part of the Taskmaster Client 1040EZ.
1 With the Taskmaster Client main window open, on the Settings menu, select Stations.
The IBM Datacap Taskmaster Capture Administrator dialog opens with the Stations tab
displayed on top.
2 Select a station in the left pane.
3 In the right pane, completely expand the Permissions branches to view the specific
Tasks this station has permission to run.
Click the Groups tab and continue with step 2 in the View 1040EZ Taskmaster
Client Groups procedure.
Click the Users tab and continue with step 2 in the View 1040EZ Taskmaster
Client Users procedure.
Client window.

Taskmaster RV2
IBM Datacap Taskmaster Capture RV2 web application displays real-time reports of activity
related to your Taskmaster applications.
The following standard reports for monitoring batch status, station activity, and problem
batches are included with IBM Datacap Taskmaster Capture RV2 software component:
Report Name Description Data

Source
Problem Displays all queued batches that have aborted or queue table
Batches are offline, or have been running longer than two
hours.
Current Displays all queued batches that are not complete queue table
Batches or canceled.
Batch Aging Same as Current Batches except includes elapsed queue table
time since batch was started.
Current Displays the station IDs and IP addresses of all
Stations stations currently logged, plus the number of
batches processed by each station.
Station Activity Displays a bar chart showing the number of qstats table
batches completed by each station within the last
four hours.
Pending Tasks Displays a bar chart showing the number of queued queue table
batches with status pending or aborted.
Background Displays a bar chart for the last six days showing taskstats
Use Hourly the percentage of each hour spent processing by table
each station.
Use Daily the percentage of each day spent processing by table
each station.
Background Displays summary of all batches processed, taskstats
grouped by station ID. Includes aggregates for table
processing time, number of pages scanned, etc. for
each station.
Background Same as Background except starts and refreshes in taskstats
Summary collapsed view. table
Scan Displays a list of all scanned batches, grouped by scan2kst
operator. Includes aggregates for processing time, table
number of pages scanned, etc. for each operator.
Scan Summary Same as Scan except starts and refreshes in scan2kst
collapsed view. table


Source
Fixup Displays a list of all batches that have been through fixup2kst
Fixup, grouped by operator. Includes aggregates table
for processing time, number of pages rescanned,
inserted, etc. for each operator.
Fixup Same as Fixup except starts and refreshes in fixup2kst
Verify Displays all batches that are in or ready for de2kst
verification, grouped by operator. Includes table
aggregates for processing time, pages processed,
average documents per hour, etc. for each
operator.
Verify Same as Verify except starts and refreshes in de2kst
Batch Displays a list of all batches with status “Job queue and
Productivity done.” Includes number of pages scanned and total tmbatch
elapsed time for each batch from when batch was tables
started until completed. Also includes average
number of pages and average elapsed time per
batch.
Debug Displays a list of all batches in the debug table (for debug table
example, batches that were deleted manually).
Includes the batch status, status prior to being
moved to the debug table, etc.
Overview of RV2 Installation and Configuration

This section provides an overview of the steps required to install and configure the Taskmaster
RV2 reporting component.
Configuration Prerequisites.
In a single machine configuration, you must:
1 Ensure you have the required Microsoft Internet Information Services components
installed
2 Install RV2
3 Set up the RV2 web site
Ensure Required IIS Components are Installed (Windows 7)

This procedure provides instructions on how to ensure that the appropriate components have
been installed in Internet Information Services when the operating system is Windows 7.
1 From the Windows Start menu, select Control Panel, select Programs and Features. The
Programs and Features window opens with a Tasks pane on the left.

2 In the Tasks pane, select Turn Windows features on or off.

The Windows Features window opens and displays a list of features.
3 Expand Internet Information Services, expand Web Management Tools, and select or
ensure IIS Management Console is selected.
4 Scroll down and expand World Wide Web Services, expand Application Development
Features, and select or ensure both ASP and ASP.NET are selected (selecting these
options ensures other prerequisite features are selected).
5 Expand Common HTTP Features, and ensure Static Content is selected.
6 Click OK to save your changes. Windows applies any changes you have made, then
closes the Windows Features window.
7 Close the Programs and Features window.
Set Up RV2 Web Site (IIS 7)

This procedure provides instructions on how to set up the RV2 web site on Microsoft Internet
Information Services (IIS) 7 or 7.5.
1 From the Windows Start menu, select Control Panel, select Administrative Tools, and
select Internet Information Services Manager. The Internet Information Services (IIS)
Manager window opens.
2 In the Connections pane, expand the computer, expand Sites, right-click the Default
Web Site and choose Add Application. The Add Application window is displayed.
3 Set the Alias to RV2 and set the Physical path by entering or browsing to the
C:\Datacap\RV2 folder.
4 Click OK to close the Add Application dialog. The Internet Information Services (IIS)
Manager window is displayed.
5 In the Connections pane, select Application Pools. The Application Pools pane is
displayed.
6 In the Actions pane, select Set Application Pool Defaults. The Application Pool
Defaults window opens.
7 Ensure Enable 32-Bit Applications is set to True.
8 Ensure the Process Model Identity is set to your Windows account (which has
Administrative privileges on this machine).
9 Click OK. The Internet Information Services (IIS) Manager window is displayed.
10 Confirm all of the following are started: Web Server, Application Pool, and Default
Web Site.
Add RV2 Address as Trusted Site

This procedure provides instructions on how to add the RV2 address as a Trusted Site to
prevent Internet Explorer from blocking access.
1 Open Internet Explorer.
2 On the Tools menu, select Internet Options. The Internet Options dialog opens.
3 Click the Security tab to display it.

4 Select Trusted Sites, then click Sites. The Trusted Sites dialog opens.
5 When running Internet Explorer on the same machine as RV2, enter the default server
address (http://127.0.0.1) in the Add this website to the zone field, then click Add. The
URL is added to the bottom pane.
6 Click Close. The Internet Options dialog is redisplayed.
7 Click OK. The Internet Options dialog closes.
Log Onto RV2

When you log into RV2, the User ID you use on the login page is logged into all Taskmaster
applications for which that User ID is a valid Taskmaster user.
This procedure provides instructions on how to access and log into RV2 in a single machine
environment.
1 Open Internet Explorer, and connect to
http://127.0.0.1/RV2/Login.aspx
The RV2 login page is displayed.

2 Enter the appropriate Taskmaster Admin User ID, Password, and Station ID, then click
Login. The RV2 home page is displayed with the Taskmaster applications to which the
Taskmaster login User ID has access.
View Standard RV2 Report

This procedure provides instructions on how to view a standard RV2 report.
1 With the RV2 home page displayed, select the Batch Productivity report, select the
application, then click Run Report. The Batch Productivity report is displayed.
2 Click Reports to return to the RV2 home page.
Create an RV2 Report Filter

You can filter the data that is displayed in an RV2 report based on the values in one or more
fields. For example, if you want to view only activity related to a specific operator, you can
filter the data by operator name.
Each filter is associated with a single report, so the Select Filter list on the RV2 home page
displays only filters that are available for the report you have selected.
This procedure provides instructions on how to create a report filter.
1 With the RV2 home page displayed, select the report from the list on the left.
2 Click Manage Filters. Filter-related fields appear.
3 In the Add Filter field, enter a name for the new filter.
4 Click Add. Additional fields appear.
5 Set up the filter as follows:
In the first field, select the column name (for example, “Operator”)
In the second field, select the action (for example, “equal to”)
In the third field, enter the value (for example, “admin”)
6 To add another field, click Add Field and repeat the previous step.

7 Select Public (available to all users) or Private (available only to you).

8 Click Save.
9 If you want to run the report using the new filter, click Run Report. Otherwise, click
Reports to return to the RV2 home page.
Add Reports to the RV2 Dashboard

The RV2 dashboard view lets you view up to six reports simultaneously. The dashboard is
typically used for viewing chart-based reports.
This procedure provides instructions on how to add one or more reports to the RV2 dashboard.
You can add up to six reports.
1 With the RV2 home page displayed, click Dashboard. The Dashboard window is
displayed.
2 Select the report and the application name. If applicable, select a filter. The report is
displayed.
3 To add an additional report, click Add and repeat the previous step.
4 If you want the data on the reports to refresh automatically, click Refresh and select a
refresh interval.
Modify the RV2 Dashboard

Each report displayed on the dashboard can be resized, moved, or removed.
This procedure provides instructions on how to modify the dashboard by resizing, moving, or
removing a report.
displayed.
2 To resize a report, click the cross-hatched area at the bottom right corner and drag.
3 To move a report, click the dotted area at the top of the report and drag the report to a
different location.
4 To remove a report, click the report you want to remove, then click Remove.

Taskmaster Web
Taskmaster Web allows users to perform Taskmaster tasks from remote machines on which
only the Internet Explorer browser is installed.
This section provides the information you need to set up and run tasks using Taskmaster Web
and Internet Explorer.
Stop or Ensure Taskmaster Server Service is Stopped

This procedure provides instructions on how to stop or ensure the Taskmaster Server Service is
stopped when the operating system is Windows 7.
1 From the Workstation’s Windows Start menu, select Programs, select Datacap, select
Taskmaster Server, and click Taskmaster Server Manager.
2 When the Status:
Shows as Stopped, continue with the next step.
Shows as Running, click Stop. A Stopping Service message is displayed. The
Status changes to Stopped when the service is stopped.

been installed in Internet Information Services when the operating system is Windows 7.
1 From the Windows Start menu, select Control Panel, select Programs and Features. The
Programs and Features window opens with a Tasks pane on the left.
2 In the Tasks pane, select Turn Windows features on or off.
The Windows Features window opens and displays a list of features.
3 Expand Internet Information Services, expand Web Management Tools, and select or
ensure IIS Management Console is selected.
4 Scroll down and expand World Wide Web Services, expand Application Development
Features, and select or ensure both ASP and ASP.NET are selected (selecting these
options ensures other prerequisite features are selected).
5 Expand Common HTTP Features, and ensure Static Content is selected.
6 Click OK to save your changes. Windows applies any changes you have made, then
closes the Windows Features window.
7 Close the Programs and Features window.
Create Taskmaster Web Site

This procedure provides instructions on how to create the Taskmaster Web site using the
Taskmaster Web Server Configuration tool when the operating system is Windows 7.
select Support, select Web Configuration, then select Taskmaster Web Server

Configuration.
An information box is displayed.
2 When one or more of the items listed in the information box are Not Found, click OK,
then follow the instructions to Ensure Required IIS Components are Installed before
running the tool again.
3 When all of the items listed in the information box are Found, click OK. The
Taskmaster Web Server Configuration window opens. Note the Alias that is assigned,
as this is part of the URL you will use to test Internet Explorer's access to this site.
4 Click Configure. A Successfully Configured message is displayed.
5 Click OK, then click Exit. The Taskmaster Web site has been created.
6 To view the web site in IIS Manager, from the Windows Start menu, select Control
Panel, select Administrative Tools, then double-click Internet Information Services
(IIS) Manager. The Internet Information Services (IIS) Manager window opens.
7 Expand the computer, Sites, and the Default Web Site. The TaskRun folder and
tmweb.net site are displayed. If they are not displayed, right-click the Default Web Site
and select Refresh.
8 In the Connections pane, select the Default Web Site.
9 In the Actions pane, under Manage Web Site, click Restart.

Internet Explorer
This section provides the information you need to set up Internet Explorer.
Add TMWeb.net Address as Trusted Site

This procedure provides instructions on how to add the TMWeb.net address as a Trusted Site
to prevent Internet Explorer from blocking access.
5 When you are running Internet Explorer on the same machine as Taskmaster Web, enter
the default webserver address (http://localhost) in the Add this website to the zone field,
then click Add. The URL is added to the bottom pane.
Configure and Test Internet Explorer 6, 7 or 8 using Tool

This procedure provides instructions on how to run the Taskmaster Web Client Configuration
tool to set up Internet Explorer 6, 7 or 8 so you can use the Taskmaster Web Client for
processing. It also provides instructions on how to test your configuration of Internet Explorer.
NOTE
When the operating system of the machine on which you want to run Internet Explorer to
access Taskmaster Web is a 64-bit operating system, you must use the 32-bit version of
Internet Explorer to access Taskmaster Web.
select Support, select Web Configuration, then select Taskmaster Web Client
Configuration.
The Taskmaster Web Client Configuration window is displayed.
2 When you are running the Taskmaster Web Client Configuration tool on the same
machine as Taskmaster Web, use the default URL that is displayed
(http://localhost/tmweb.net).
4 Click OK, then click Exit.
5 Start Internet Explorer.
the URL for Taskmaster Web (http://localhost) followed by the tmweb.net virtual
directory and the test page (http://localhost/tmweb.net/ietest.aspx) then press <Enter>.
When UAC is on, the first time you access the test page, the User Access Control

window opens. Click Yes to download the Datacap TIFF Viewer, Thumbnails, and
DataEdit Controls. The IE Test page is displayed.
7 Click Test. The red Xs will change to green checkmarks when the test completes
successfully. If the Datacap TIFF Viewer does not download, switch to the 32-bit
version of Internet Explorer and repeat this procedure from step 1.

Taskmaster Web Client 1040EZ Application
Run Taskmaster Web Client 1040EZ Application

sample Taskmaster Web Client 1040EZ application “out of the box.” These instructions
involve starting the Taskmaster Server Service, starting the Taskmaster Web Client, running
the default browser-based tasks and the Taskmaster Client tasks to process pre-scanned
images.
Overview of Taskmaster Web Client 1040EZ

Web Client 1040EZ are as follows:

VScan Process sample, pre-scanned images
Upload Move scanned images to the Taskmaster Server Service for
further processing
Verify/FixUp Perform data validation
NOTE
To complete processing, the PageID, Recognition, and Export tasks must be run manually
from the Taskmaster Client 1040EZ (thick client).

2 When the Status:
Access Taskmaster Web Login Page and Login

This procedure provides instructions on how to login to the Taskmaster Web Client 1040EZ
application using Internet Explorer.

1 Open Internet Explorer, and enter the default IP address of the Taskmaster WebServer
followed by the alias you assigned to the website (http://localhost/tmweb.net). After a
pause, the IBM Datacap Taskmaster Capture Login window is displayed.
NOTE: You may have to turn off Internet Explorer’s popup blocker the first time you
display the Login page.
2 On the Taskmaster Web Login Page, enter the following:
Field Value
Application 1040EZ
User ID admin
Password admin
Station remote
3 Click Login. The Taskmaster Web Client 1040EZ main window opens with the
Operations pane and Available shortcuts displayed.
Run Taskmaster Web Client 1040EZ VScan Task

This procedure provides instructions on how to run the Taskmaster Web Client 1040EZ virtual
scan task.
1 In Internet Explorer, in the Operations pane, click the VScan shortcut. The Web Job
Scan page is displayed. The batch number assigned to this batch of documents is
located in the upper left of the page.
2 In the lower right of the page, if necessary change the Scan Into path – this path
indicates the location into which the pre-scanned images are temporarily placed, and
you must have write permission to this location.
3 Click Browse, navigate to the folder where the pre-scanned images are located
(C:\Datacap\1040EZ\images), and select one, then click Open. The Web Job Scan page
is redisplayed with the path to the Source folder.
4 Change the number in the Expected pages field, then click Scan. A window indicates
that scanning is taking place. The pages are scanned, images of the pages are displayed,
the batch-specific name of the folder and the filename assigned to the scanned images
are appended to the Scan Into path and an End of scan message is displayed.
5 Click OK. The message box closes.
6 The following table describes what you can do on the Web Job Scan dialog:
To Do This
Change sequence of pages Select either the image in the left pane, or
the name of the image in the right page
that you want to move, then click either
the MoveUp or MoveDown arrow
Delete all pages Click Remove All

To Do This
Delete a single page Select the image you want to delete, then
click Remove
Enlarge scanned images Click Zoom in
Shrink scanned images Click Zoom out
Rotate an image Click Rotate 900
Complete the Scan Task processing of Click Done
the batch
Cancel the Scan Task processing of the Click Cancel
batch; deletes batch and all batch data
from system
Put the batch on hold and end processing Click Hold
of the batch; batch remains available to
same user
7 After all pages have been scanned, click Done. A message box is displayed indicating
the Batch finished with a status of finished.
8 Click OK. A message box asks if you want to continue processing.
10 When the Scan task finishes successfully, the source images have been collected into a
batch and copied to the batch’s uniquely-numbered folder found in the Scan Into folder.
11 Click the Monitor tab to view information about the batch. To refresh the information
displayed, press F5. The Job, Task, and Status for this batch have been updated and are
now Web Demo, Upload, pending.
Run Taskmaster Web Client 1040EZ Upload Task

This procedure provides instructions on how to run the Taskmaster Web Client 1040EZ upload
task.
1 In Internet Explorer, in the Operations pane, click the Upload shortcut. The Upload
window opens and A transferring the batch to server window is displayed briefly, then
closes. A message box is displayed indicating the batch has finished.
4 When the Upload task finishes successfully, the scanned images have been moved to
the batch’s uniquely-numbered folder found in \Datacap\1040EZ\batches, and ivscan
and upload xml files have been created.
now Web Demo, PageID, pending.


window opens.
Run Taskmaster Client 1040EZ PageID Task

This procedure provides instructions on how to run the Taskmaster Client 1040EZ Page
Identification task.
• In the Operations pane, double-click the PageID shortcut
• In the Job Monitor pane, double-click a batch with a pending PageID task
1 On the Workstation, in the Operations pane, double-click the PageID shortcut. A Task
3 When the PageID task finishes successfully, the images have been organized into
page XML files have been created, along with a PageID.xml file in the batch’s
uniquely-numbered folder in \1040EZ\batches.
updated, and are now Main Job.Recognize and pending.
Run Taskmaster Client 1040EZ Recognize Task

This procedure provides instructions on how to run the Taskmaster Client 1040EZ Recognition
task.
• In the Operations pane, double-click the Recognize shortcut
• In the Job Monitor pane, double-click a batch with a pending Recognize task
1 On the Workstation, in the Operations pane, double-click the Recognize shortcut. A
then they both close. A message box is displayed indicating the task has finished.
3 When the Recognize task finishes successfully, data from each image has been captured
and added to the page XML file along with character confidence values and, a

Recognize.xml file has been created in the batch’s uniquely-numbered folder in

\1040EZ\batches.
updated, and are now Main Job.Verify and pending.
Run Taskmaster Web Client 1040EZ Verify/Fixup Task

This procedure provides instructions on how to run the Taskmaster Web Client 1040EZ
Verify/Fixup task.
1 In Internet Explorer, in the Operations pane, click the Verify/Fixup shortcut. The
verification panel opens with the first image displayed.
2 The following table describes some of the things you can do on the verification panel:
To Do This
Move to the next data field Press <Tab>
Display the next image in the batch (without Click Next
submitting or revalidating data)
Display the previous image in the batch Click Prev
(without submitting or revalidating data)
Put entire batch on hold Click Hold
View only fields with problematic data Select Problems only
Revalidate data after making corrections Click Verify
Complete processing of image and display next Click SuBmit
image
3 When you have finished with the last document and click SuBmit, a message box is
displayed indicating No more problems have been found. Click OK to finish the batch.
4 Click OK. The message box closes and another message box is displayed indicating the
task on the batch has finished with a status of finished.
6 Click No. The message box closes and the Operations pane is redisplayed.
\1040EZ\batches on the WinXPMachine on the Server.
now Web Demo, Export, pending.

Run Taskmaster Client 1040EZ Export Task

This procedure provides instructions on how to run the Taskmaster Client 1040EZ Export task.
• In the Operations pane, double-click the Export shortcut
• In the Job Monitor pane, double-click a batch with a pending export task
1 On the Workstation, in the Operations pane, double-click the Export shortcut. A Task
they both close. A message box is displayed indicating the Export task has finished.
3 When the Export task finishes successfully, the Export database has been updated,
XML files for each document and an Export XML file for the batch have been added to
the batch’s uniquely-numbered folder found in \1040EZ\batches.
updated, and are now Main Job.Export and Job done.
5 Exit the Taskmaster Client.

Rulerunner Quattro
Introduction to Rulerunner Quattro

Rulerunner Quattro (Quattro) is an IBM Datacap Taskmaster Capture component that runs
Datacap Studio application (RRS) tasks that are "background" tasks; that is, tasks that run
without any human interaction. Background tasks are typically vScan, recognition, image pre-
processing, validation, and export tasks.
Quattro uses virtualization to take advantage of multiprocessor systems. Each virtual
recognition machine (VRM) in a multi-threaded configuration of Quattro processes rules on a
batch of documents as if it were a standalone copy of Rulerunner on its own computer.
The ability to configure Quattro to run a single thread is included as part of the standard IBM
Datacap Taskmaster Capture licensing. Configuring Quattro to run multiple threads requires
additional licensing.
Multiple thread configurations of Quattro support simultaneous VRMs on a single
multiprocessor or multi-core equipped computer. Quattro completes your work faster by
taking full advantage of your hardware investment.
With Rulerunner Quattro you can:
• Complete your document processing work faster. Faster turn-around of documents such as
claims, contracts, tax returns and invoices improves responsiveness and shortens capture
cycle times.
• Reduce the number of physical computers dedicated to the capture process. One multi-core
computer can effectively replace and cost less than multiple single-processor computers,
thereby delivering a server-room/IT "friendly" solution.
• Reduce total cost of ownership by improving utilization of existing IT assets and IT staff
efficiency. The small hardware and software footprint of Quattro is less expensive than
alternative virtualization solutions.
Introduction to Single Thread Rulerunner Quattro
This portion of the Installation and Configuration Guide provides information on how to
configure Quattro on a machine where all IBM Datacap Taskmaster Capture components are
also installed. This information is included for demonstration purposes only, as this
configuration does not allow Quattro to take full advantage of the machine's multiple
processors. Do not use this configuration as your production configuration.
Rulerunner Quattro on Single Machine

This section provides the information you need to set up a single thread of Quattro to run
Taskmaster 1040EZ tasks and to monitor Quattro processing when all IBM Datacap
Taskmaster Capture components have been installed on a single machine.

The process is made up of the following steps:

1 Shut down IBM Datacap Taskmaster Capture software.
2 Configure Quattro account.
3 Configure Quattro to run Taskmaster 1040EZ tasks.
4 Create Taskmaster 1040EZ batches.
5 Start Quattro.
6 Monitor Quattro processing.

Before beginning the installation of Quattro on a standalone Workstation, we recommend
shutting down all other IBM Datacap Taskmaster Capture software on the machine in the
following sequence:
Taskmaster Web Client, Taskmaster Client Service, Datacap Studio, Batch Pilot, etc.)
etc.)
Configure Quattro Account

This section provides the information you need to ensure that the Workstation's local System
account (this account runs the Datacap Quattro Control Service (DQCS) and Rulerunner
Quattro) has the rights and permissions it needs. This includes: Adding the account to the
Workstation's Administrators group, and granting it the ability to log on as a service. You can
also ensure the DQCS starts up automatically when its host machine is restarted.
Add Quattro Account on Workstation

Add the Workstation's (local) System account to the Workstation's Administrators group so
that the account has local administrator rights on the machine.
Grant Quattro Log On as Service Right

This procedure provides instructions on how to ensure the System account used by Rulerunner
Quattro has been granted the Log On as a Service right on the Workstation machine (this
allows Rulerunner Quattro to run as a service).
1 From the Workstation's Windows Start menu, select Settings, select Control Panel,
select Administrative Tools, select Services.
The list of Services is displayed.
Right-click Datacap Rulerunner Quattro Service and select Properties. The Properties
dialog opens with the General tab displayed on top.
2 Click the Log On tab to display it.
3 Select or ensure the Local System account is selected (this indicates the System account
will run the service) and click Apply if you have made a change.
4 Click OK to close the Properties dialog.

5 Close the Services window.
Grant DQCS Log On as Service Right

This procedure provides instructions on how to ensure the System account used by DQCS
(which starts and stops Rulerunner Quattro) has been granted the Log On as a Service right on
the Workstation machine.
Right-click Datacap Quattro Control Service and select Properties. The Properties
3 Select or ensure the Local System account is selected (this indicates the System account
will run the service) and click Apply if you have made a change.
Configure DQCS Start Up Behavior

This optional procedure provides instructions on how to ensure the Datacap Quattro Control
Service (DQCS) starts up automatically when its host machine is restarted. When the DQCS is
started automatically and its Restart service if stopped setting is enabled, the DQCS will
automatically restart Quattro after a reboot.
Right-click Datacap Quattro Control Service and select Properties. The Properties
2 To start the DQCS automatically when the Workstation is rebooted, change the Startup
Type to Automatic, and click Apply to save your change.
Ensure or Set Location of Datacap.xml

This procedure provides instructions on how to ensure or set the location of the Taskmaster
application settings file using the Taskmaster Application Manager. In the examples used in
this Installation and Configuration Guide, the datacap.xml file containing the application
settings is found in the C:\Datacap folder.

example:
C:\Datacap\datacap.xml

2 When the Status:
Encrypt Taskmaster Login Password

When setting up Rulerunner Quattro to use Taskmaster Authentication, Quattro requires that
the password be encrypted.
This procedure provides instructions on how to use IBM Datacap Taskmaster Capture's
SitManager.exe to encrypt the password and create the encrypted string you need before you
begin configuring Quattro's IBM Datacap Taskmaster Capture login credentials.
1 On the Workstation, start Windows Explorer, navigate to and open the
C:\Datacap\support\Sit folder.
2 Double-click the SitManager.exe. The Sit Manager window opens.
3 Type in the password you want to encrypt (for example, the password for the IBM
Datacap Taskmaster Capture admin user) and click Encrypt. A string is displayed in
the Encrypted String field.
4 Click Test. A message box indicates the string was encrypted successfully.
5 Click OK to close the message box.
6 Highlight the encrypted string and copy it to your Windows clipboard (Ctrl+C) or to an
empty text file to save for later use.
7 Click Exit to close the Sit Manager window.
Configure Rulerunner Quattro to Run 1040EZ Tasks

This procedure provides instructions on how to use Rulerunner Quattro Manager to update
Rulerunner Quattro 1040EZ -specific settings reflect the PageID, Recognize, and Export tasks

that Quattro is to process on a single thread For more information on Rulerunner Quattro
Manager, see Appendix D Rulerunner Quattro Manager.
When you configure Quattro, your license determines the number of threads you can set up.
Follow the instructions in Encrypt Taskmaster Login Password to encrypt the password for the
Admin User ID before continuing with this procedure.
1 From the Workstation's Start menu, select All Programs, select Datacap, select
Taskmaster Client, and click Rulerunner Quattro Manager.
When UAC is on, the User Account Control window is displayed. Click Yes.
The Rulerunner Quattro Manager window opens.
2 If the Status displayed is Stopped, continue with the next step.
If the Status displayed is Running, click Stop. The status will change to Stopped after
batch processing is completed.
3 Click the Datacap Login tab to display it.
4 If not already selected, select the Taskmaster Authentication option to enable the login
credential fields and enter the appropriate Taskmaster User ID, paste in the encrypted
Password, and enter a Station ID of 2, then click Connect. A message indicates the
configuration file does not exist and identifies the path where the file will be created.
5 Click OK. The message box closes and the Connect button label changes to
Disconnect.
6 Click the Workflow:Job:Task tab to display it. The names of the available applications
are displayed in the left pane.
7 If the right pane displays thread0 with 1040EZ's PageID, Recognize, and Export tasks,
Quattro has already been set up to process these tasks - skip to step 15. If the right pane
is empty, continue with the next step.
8 In the left pane, expand the 1040EZ application, expand the Servers node, then select
the server, the Taskmaster Admin database and the Taskmaster Engine database. The
tree expands to display the 1040EZ workflow, jobs and tasks.
9 In the right pane, right-click, select Threads, then select Add Thread. A branch for
thread0 is created.
10 In the left pane, in the expanded tree under 1040EZ, under the Main Job, click in the
box to the left of PageID, click the PageID label (to highlight it in blue) and drag it onto
thread0 in the right pane. The thread expands and displays the server, job, and task
names.
11 Repeat (click the box, click and drag the label) to drag Recognize and Export onto
thread0 in the right pane. All three task names should be displayed under thread0.
12 Click Save to save your changes. A message indicates the configuration file does not
exist, and asks if you want to create it.
13 Click Yes. The message box closes.
14 Click Save again.
16 Click Disconnect. The button label changes to Connect.
17 Close the Rulerunner Quattro Manager window.

Confirm Quattro's 1040EZ Task Profiles in the Taskmaster Application Service

This procedure provides instructions on how to ensure the Taskmaster Application Service lists
the 1040EZ PageID, Recognize, and Export tasks that Quattro is to process.
select Taskmaster Client, and select Taskmaster Application Manager.
2 Select 1040EZ. Paths appear in the fields on the Application tab.
3 Click the Quattro tab to display it. This tab should display the PageID, Recognize, and
Export task profiles that Quattro is to process.
4 To remove a task profile, click the red X to the right of the profile name. A prompt is
displayed asking you to confirm you want to remove the task.
6 To add a task profile, click Add new Task. Two data entry fields appear.
7 Enter the name of the task (PageID )in the first field, and enter the name of the task
profile (PageID) in the second field, ensuring the spelling and case is accurate.
8 Repeat the previous two steps to add the Recognize and Export tasks.
Run Taskmaster Client 1040EZ Tasks using Quattro

This section provides the information you need to stop and restart the Taskmaster Server
Service, start Taskmaster Client 1040EZ, create Taskmaster Client batches, start Rulerunner
Quattro, and monitor Quattro as it picks up and processes each batch.

stopped when the operating system is Windows 7.
1 From the Workstation’s Windows Start menu, select Programs, select Datacap, select
Taskmaster Server, and click Taskmaster Server Manager.
2 When the Status:


2 When the Status:

window opens.
Run Taskmaster Client 1040EZ Scan Task

This procedure provides instructions on how to start the Taskmaster Client 1040EZ Scan job
(this runs the VScan job) to process pre-scanned images.
1 On the Workstation, in the Operations pane, double-click the Scan shortcut. A Task
Scan task finishes successfully, 1040EZ has picked up the images from the
\1040EZ\images folder and created a batch which is a collection of document images to
be processed. Taskmaster has assigned a batch ID and created a uniquely-numbered
folder with the name of the batch ID in the \1040EZ\batches folder. This folder holds
all of the document image processing results for this batch of forms, including the
newly-created vscan.xml file.
updated, and are now Main Job.PageID and pending.
5 When running this Scan task to queue up batches for Quattro, repeat these instructions
to create additional batches.

Start Quattro
When you start the Datacap Quattro Control Service it immediately attempts to start
Rulerunner Quattro.
IMPORTANT
When you are running Quattro on the same Workstation as the Taskmaster Client, exit from
the Taskmaster Client before starting Quattro.
This procedure provides instructions on how to start or ensure Quattro is started.
1 From the Workstation's Start menu, select All Programs, select Datacap, select
Taskmaster Client, and click Rulerunner Quattro Manager.
The Rulerunner Quattro Manager window opens with the Datacap Quattro tab
displayed on top.
2 If the Datacap Quattro Control Service Status displayed is Running, skip to the last step.
If the Status displayed is Stopped, continue with the next step.
3 Click Start. The Datacap Quattro Control Service status will change to Running.
Monitor Quattro Processing of 1040EZ on Single Machine

With the Workstation's Windows Explorer open and the application's Batches folder displayed,
select each uniquely-numbered batch folder and press <F5> periodically to refresh the view
and see the changes Quattro makes in the folder as it runs the configured tasks. Most
noticeable are the newly-generated .xml and .log files, and the updated image .xml files.
After Quattro has finished processing PageID and Recognize tasks for all of the batches, stop
it, then reopen Taskmaster Client, and open the Job Monitor pane. The batches will now show
Verify tasks with Status of pending.
Process each of the batches through Verify and ensure they show Export tasks with Status of
pending. Close Taskmaster Client and restart Quattro.
Use Windows Explorer to see the additional changes Quattro makes in each batch folder when
it runs each batch through the Export task.
For troubleshooting information, see Appendix D: Rulerunner Quattro Manager Reference, the
section titled Troubleshooting Quattro.

Chapter 5
Install, Configure, and Run on Client and Server

This chapter provides the information you need to install, configure, and run IBM Datacap
Taskmaster Capture 8.0.1 in a client-server environment for demonstration, proof of concept,
development, and test purposes. It also includes instructions that guide you through using the
separately licensed APT application so you can see it process sample batches of documents.
Following these instructions enables you to set up and run each of the IBM Datacap
Taskmaster Capture software components "out of the box," including:
• Taskmaster Server Service
• Datacap Studio Application Copy Wizard
• Taskmaster Client APT
• RV2
• Taskmaster Web
• Taskmaster Web Client APT
• Rulerunner Quattro
• Taskmaster Client Service
• Datacap Studio
• NENU
• Rulerunner running as a web service
• Running IBM Datacap Taskmaster Capture using Windows Authentication
• Fingerprint Maintenance Tool
For a checklist of the account and configuration settings, see Appendix B: Client-Server
Setup Checklist.
Taskmaster Client-Server Configuration

Taskmaster can be configured in many ways. The multiple machine configuration used
throughout the client-server examples provided in this Guide includes the following machines:
• Taskmaster Server (referred to as the "Server") hosts the Taskmaster Server, the main
application settings file (datacap.xml), the applications, batch files, and databases. For the
Server, these instructions cover Windows 2003, and Windows 2008.
• Taskmaster Web Server (referred to as the "WebServer") hosts Taskmaster Web and
RV2. For the WebServer, these instructions cover Windows 2003 and Windows 2008.

• Developer Workstation (referred to as the "DevWorkstation") hosts the complete

Taskmaster Client, including Datacap Studio, DotEdit, and NENU. These instructions
cover Windows XP and Window 7.
• End-user Workstation (referred to as the "Workstation") hosts the Taskmaster Client or
only the browser. For the Workstation, these instructions cover Windows XP and
Windows 7.
• Rulerunner Quattro Server (referred to as the "QServer") hosts the Rulerunner Quattro
Service that runs tasks that do not require human interaction. These instructions cover
Windows 2003 and Windows 2008.
• Taskmaster Client Service Server (referred to as the "TCSServer") hosts the Taskmaster
Client Service that runs tasks that do not require human interaction. These instructions
cover Windows 2003 and Windows 2008.
• Web Rulerunner Service Server (referred to ask the "RRServer") hosts Taskmaster
Rulerunner running as a web service. These instructions cover Windows 2003 and
Windows 2008.
These instructions also include information on the accounts and permissions needed for the
following types of users: Implementation/development personnel with administrative rights on
all machines, end users, and accounts for the various Taskmaster processes and services:
Taskmaster Server Service, Rulerunner Quattro Service, Taskmaster Client Service, NENU,
RV2, Rulerunner running as a web service, and Taskmaster Web.
Overview of Taskmaster Installation on Client and Server

The IBM Datacap Taskmaster Capture installation, configuration, and run processes are
performed in the following sequence (the separately licensed application, APT, is used as the
example throughout this client-server documentation):
2 Install the Taskmaster Server software component on the Server.
3 Configure Taskmaster on the Server.
4 Install the Taskmaster Client software component (Taskmaster Client, Datacap Studio,
DotScan, DotEdit, NENU, as well as the separately licensed applications and
connectors for which you have licenses) on the DevWorkstation.
5 Copy the APT application from the DevWorkstation to the Server.
6 Complete the Taskmaster Server configuration.
7 Run Taskmaster Client APT.
8 Set up Taskmaster APT to process your invoice images.
9 Install and configure the Taskmaster Client software component on an end user's
Workstation.
10 Install RV2 on WebServer.
11 Configure RV2 on WebServer.
12 View RV2 reports.

13 Install Taskmaster Web on WebServer.

14 Configure Taskmaster Web on WebServer.
15 Configure Internet Explorer on WebServer or DevWorkstation.
16 Run Taskmaster Web Client APT.
17 Install Rulerunner Quattro on QServer.
18 Configure Rulerunner Quattro to run APT tasks (both single thread and multi-thread).
19 Run APT tasks using Rulerunner Quattro and monitor processing.
20 Configure Rulerunner Quattro to run your application tasks.
21 Install Taskmaster Client Service on TCSServer.
22 Configure Taskmaster Client Service to run APT task.
23 Run APT task using Taskmaster Client Service and monitor processing.
24 Install NENU on DevWorkstation.
25 Set up NENU application or actions on DevWorkstation.
26 Run NENU actions.
27 Install Rulerunner on RRServer.
28 Configure Rulerunner to run as a web service.
29 Configure Rulerunner to run APT task.
30 Run APT task using Rulerunner running as a web service.
31 Configure IBM Datacap Taskmaster Capture to use Windows Authentication.
32 Use Fingerprint Maintenance Tool.

Installation Instructions for Taskmaster Server

This section provides the information you need to install the IBM Datacap Taskmaster Capture
Taskmaster Server component on the server (referred to as the "Server").
The Windows account you use when installing and configuring must have administrator rights
on every machine on which IBM Datacap Taskmaster Capture components are being installed.

On Windows 7:
opens.
displayed.
On Windows 2008:
are displayed.
Install Taskmaster Server Components on Server

InstallShield Wizard to install the Taskmaster Server component and the separately licensed
connectors for which you have a license.
These instructions apply to Windows 2003 and Windows 2008 Servers (referred to as
"Server").

WARNINGS
install on a single machine, see Chapter 4 Install, Configure, and Run on Single
Machine.
accessible network drive, in the machine's CD/DVD drive), the destination of the
installed software must be on a physical hard drive of the machine from which you run
the Setup.exe.
Your initial IBM Datacap Taskmaster Capture software installation must be into the
C:\Datacap folder. If you do not use this installation path, the sample and foundation
Taskmaster Capture CD in the Server’s CD/DVD drive. If the installation process does
not start automatically, or if the package is on the network, open Windows Explorer,
navigate to and double-click the Setup.exe.
On Windows 2008, when UAC is on, the User Account Control window opens. Click
Allow.
it.
On Windows 2003, if Microsoft .NET Framework 3.5 is installed during this step, a
reboot is required before the InstallShield Wizard can continue. Reboot the machine,
and the Wizard will continue.
5 Click Next. The License Agreement window opens.
6 Select the I accept the terms in the license agreement option and click Next. The Setup
Type window is displayed with the Complete option selected.
8 Exclude all components from the installation process except Taskmaster Server and the
separately licensed connectors for which you have a license.
12 Click Yes to reboot.
Configure Taskmaster on Server

This section provides the information you need to set up IBM Datacap Taskmaster Capture on
the Server. All of the IBM Datacap Taskmaster Capture components require the Taskmaster

Server Service to function, and the appropriate folder and security permissions must be
granted.
Create or Ensure Account Exists for Taskmaster Server Service

configuration, the Taskmaster Server Service uses the Local System account to log onto the
Server.
In a client-server environment, create or ensure a specific domain/Windows account exists for
the Taskmaster Server Service.
Grant Taskmaster Server Service Log On as a Service Right

This procedure provides instructions on how to ensure the domain account used by the
Taskmaster Server Service has been granted the Log On as a Service right on the Server, and
optionally, change the Service's start-up behavior when the Server is rebooted. These
instructions apply to Windows 2003 and Windows 2008.
1 From the Server's Windows Start menu, select Control Panel, select Administrative
Tools, and double-click Services.
Yes.
The Services window opens.
2 Right-click Datacap Taskmaster Server Service and select Properties. The Datacap
Taskmaster Server Service Properties dialog opens with the General tab displayed on
top.
3 If you want the Taskmaster Server Service to start automatically when the Server is
rebooted, change the Startup Type to Automatic and click Apply to save your change.
4 Click the Log On tab to display it, then select This account. The Browse button is
enabled.
5 Locate or enter the domain name, user name and password of the Windows account to
be used by Taskmaster Server Service, and click Apply. A message is displayed
confirming the account was granted the Log On as a Service right.
7 Click OK to close the Datacap Taskmaster Server Service Properties dialog.
Create or Ensure Accounts Exist for Developers and End Users

Ensure domain/Windows accounts exist for your Taskmaster developers and end users.
Share Datacap Folder and Set Sharing Permissions (Windows 2003)

This procedure provides instructions on how to set up the appropriate sharing permissions for
the C:\Datacap folder when the Server's operating system is Windows 2003.
1 On the Server, start Windows Explorer, navigate to and right-click the C:\Datacap
folder and select Sharing and Security. The Sharing tab is displayed.
2 Click Share this Folder and keep Datacap as the Share name.
3 Click Permissions. The Permissions for dialog is displayed.

4 Add the local ASP.NET Machine Account (Server\ASPNET) and the local Internet
Guest Account (Server\IUSR_SERVER) and set both to allow Full Control.
5 Add/ensure Domain/Windows User IDs of developers are set to allow Full Control.
6 Add/ensure Domain/Windows User ID of Taskmaster Server Service is set to allow Full
Control.
7 When Batches folders are staying on Server in C:\Datacap\Application path, add/ensure
Domain/Windows User IDs of Taskmaster end users are set to allow Full Control.
Share Datacap Folder and Set Sharing Permissions (Windows 2008)

the C:\Datacap folder when the Server's operating system is Windows 2008.
folder and select Properties. The Properties dialog opens with the General tab
displayed.
2 Click the Sharing tab to display it, then click Advanced Sharing.
The Advanced Sharing dialog opens.
3 Click Share this Folder and keep Datacap as the Share name.
5 Add NETWORK SERVICE and local IUSR and set both to allow Full Control.
6 Add/ensure Domain/Windows User IDs of developers are set to allow Full Control.
Control.
Set Up Security on Datacap Folder (Windows 2003)

This procedure provides instructions on how to set up the appropriate security for the
C:\Datacap folder when the Server's operating system is Windows 2003.
3 Add/ensure Domain/Windows User IDs of developers who can change existing
Taskmaster applications are set to allow Read & Execute (this developer cannot create
new applications).
4 Add/ensure Domain/Windows User IDs of developers who can create new Taskmaster
applications in the C:\Datacap folder are set to allow Full Control.
5 Add/ensure Domain/Windows User ID of Taskmaster Server Service is set to allow
Read & Execute.
Domain/Windows User IDs of Taskmaster end users are set to allow Read & Execute.

Set Up Security on Datacap Folder (Windows 2008)

C:\Datacap folder when the Server's operating system is Windows 2008.
displayed.
2 Click the Security tab to display it, then click Edit.
The Permissions for dialog opens.
3 Add/ensure Domain/Windows User IDs of developers who can change existing
Taskmaster applications are set to allow Read & Execute (this developer cannot create
new applications).
4 Add/ensure Domain/Windows User IDs of developers who can create new Taskmaster
applications in the C:\Datacap folder are set to allow Full Control.
5 Add/ensure Domain/Windows User ID of Taskmaster Server Service is set to allow
Read & Execute.
Set Up Security on Datacap\RRS (Windows 2003)

This procedure provides instructions on how to set up the appropriate security permissions for
the C:\Datacap\RRS folder on the Server when the Server's operating system is Windows
2003.
1 On the Server, start Windows Explorer, navigate to and right-click the C:\Datacap\RRS
3 Add the local ASP.NET Machine Account (Server\ASPNET) and local Internet Guest
Account (Server\IUSR_SERVER) and set both to allow Read & Execute.
Set Up Security on Datacap\RRS (Windows 2008)

the C:\Datacap\RRS folder on the Server when the Server's operating system is Windows
2008.
displayed.
2 Click the Security tab to display it, and click Edit.
3 Add NETWORK SERVICE and local IUSR and set both to allow Read & Execute.
Set Location of Datacap.xml

This procedure provides instructions on how to define the location of the Taskmaster
application settings using the Taskmaster Application Manager. In the examples used in this
Installation and Configuration Guide, the datacap.xml file containing the application settings is
found on the Taskmaster Server ("Server") in the C:\Datacap folder.

example:
\\Server\Datacap\datacap.xml

Installation Instructions for Developer Workstation

On Windows 7:
opens.
displayed.
On Windows 2008:
are displayed.

InstallShield Wizard on a developer's Workstation (referred to as the "DevWorkstation") to
install the Taskmaster Client software components. The components you install include:
Taskmaster Client and sample applications, the separately licensed applications for which you
have a license, Datacap Studio, DotScan, DotEdit, NENU, and the separately licensed
These instructions apply to Windows XP and Windows 7.
WARNINGS

Machine.
the Setup.exe.
On Windows 7, when UAC is on, the User Account Control window opens. Click Yes.
it.
On Windows XP, if Microsoft .NET Framework 3.5 is installed during this step, a
8 Exclude all features except Taskmaster Client, the separately licensed applications for
which you have a license, and the separately licensed connectors for which you have a
license.
11 Click Finish.
Install Scanner
Install a scanner, and ensure the scanner works outside of IBM Datacap Taskmaster Capture.
applications out of the box, as those applications can use the sample, prescanned images
included during installation.

Copy APT Application to Taskmaster Server
Overview of Copying APT to Taskmaster Server

This section provides the information you need to start Datacap Studio, start the Datacap
Studio Application Copy Wizard, and copy the APT foundation application from the
DevWorkstation to the Server so that the application can be accessed by other workstations
running the Taskmaster Client or Taskmaster Web Client, and by other services and processes.
The Windows account that you use to log on with (referred to earlier as the "developer"
Domain/Windows account when granting permissions on the Taskmaster Server) must have
been granted full control for both sharing and security permissions on the Datacap folder on
the Taskmaster Server.
NOTE
For clarity, the instructions in this section use the Taskmaster APT foundation application as
the example application, and refer to it by name.
In general we recommend that, when copying a foundation or sample application in order to

change it or customize it to your business needs, you rename it (instructions for renaming are
included in the instructions titled Copy APT Application to Taskmaster Server). Renaming
allows you to:
Avoid losing your customizations when upgrading to later versions of Taskmaster

(application folders with the names of Taskmaster applications may be
overwritten)
Better identify the business function the application provides for your users
Leave the foundation and sample applications intact so that if you encounter
issues with your customized version, you can use the original application for
troubleshooting to determine whether or how the feature works in the original
application as compared to your customized version
Leave the foundation and sample applications intact so you can use them as
models when building your own rulesets and tasks
Start Datacap Studio to Use Application Wizard

This procedure provides instructions on how to start Datacap Studio on the DevWorkstation
without opening an application.
1 From the DevWorkstation's Windows Start menu, select All Programs, select Datacap,
select Datacap Studio, and select Datacap Studio again.
On Windows 7, when UAC is on, the User Account Control window is displayed.
Click Yes.
The Select Application window opens.
2 Click Close. An empty Datacap Studio main window opens with the Rulemanager tab
displayed on top.

Set or Ensure Correct Datacap.xml File is in Use

When you install the Taskmaster Client software component on the DevWorkstation, the
Taskmaster application files are installed, and a datacap.xml file is placed in the C:\Datacap
folder. This default datacap.xml file contains entries for the Taskmaster applications and
allows Datacap Studio to "see" the applications.
This procedure provides instructions on how to ensure Datacap Studio is using the local
version of the datacap.xml file that contains an entry for the application that you want to copy
from the DevWorkstation to the Taskmaster Server.
1 On the DevWorkstation, with an empty Datacap Studio main window open, click the
Settings button in the upper right. The Settings window is displayed.
2 Click the DCapp tab to display it.
3 Set or ensure the path in the Main application management file field is set to the local
copy of the datacap.xml file, then click OK. The Settings window closes.
4 If you changed the path to the datacap.xml file, you must close and restart Datacap
Studio to begin using the newly-selected file.

This procedure provides instructions on how to copy the APT foundation application from the
DevWorkstation to the Server using the Datacap Studio Application Copy Wizard.
Note
Batches that exist in the source application on the DevWorkstation and their associated
records in the Engine database are not copied to the Server.
Application Wizard button in the upper right. The Application Wizard – Overview
window is displayed.
2 Click Next. The Application Wizard – Wizard Mode window is displayed.
3 Select the Copy an existing RRS application option, then click Next. The Application
Wizard – Copy an existing application window is displayed.
4 Enter or use the browse button and Browse For Folder window to navigate to and select
or create the following:
Field Description Example

Please select an The items in this dropdown list APT
application to are the applications that are listed
copy from the in the datacap.xml file that is in
list use. If the application you want to
copy is not displayed, follow the
instructions in Set or Ensure
Correct Datacap.xml File is in Use
to point to the correct datacap.xml
file.

Field Description Example

Root folder on Target folder on the Server under \\Server\Datacap
target system which the new application folder
will be created.
Datacap folder This path is used in the C:\Datacap
on Taskmaster Taskmaster Client shortcut to run
Client the Taskmaster Client software on
workstation the Workstation.
Taskmaster Location of the tmweb.net folder \\WebServer\Datacap\tmweb.n
Web folder on the Taskmaster Web Server. et
Leave blank if Taskmaster Web is
not set up yet, if it is set up, use
the correct WebServer name.
Rename Copy Indicates that you want the new N/A*
application to have a different
name than the original APT
application
New Name Name of the new application N/A*
* For clarity, the instructions in this section and throughout this Installation and
Configuration Guide use the Taskmaster APT foundation application as the example
application, and refer to it by name. In general we recommend that, when copying an
application, you rename it. When you provide a New Name, it cannot be a substring of
the original application, and can only be composed of alphabetic, numeric, and
underscore characters.
5 Click Next. The Application Wizard – Finish window is displayed.
6 Click Finish to begin the copying process. The wizard makes a copy of the APT
application in the new location on the Server, then performs search-and-replace
operations throughout the application to make all required changes. Messages and
progress bars are displayed, and when the process is complete, the Application Wizard
– Summary window is displayed with one or more of the following:
Warnings – Indicate the wizard encountered something unexpected, but could continue.
General – Lists the results completed successfully.
Errors – Indicate the wizard encountered a problem that must be corrected.
7 Click View Logs to open the appwiz.log file (found in the \\Server\Datacap\APT folder)
and search for "error" and "warning" and "not copied" to locate issues you need to
address. The appwiz.log contains a list of the changes to the application made by the
wizard, including:
Type of Change Information Logged
Rename Databases Displays Before and After values
Rename Files within Folders Displays Before and After values
Update Contents of Databases Displays messages identifying what was updated,
Displays Before and After values
Update Strings within Project Files Displays Before and After values

Type of Change Information Logged

Update Parameters in Rule Files When changed: displays Before and After values
(.rul) When not changed: displays Information Message
– you decide if it needs to be changed, and if so,
change it manually
Updates Fingerprint Database Displays Application.xml
Name
8 When the application copy is successful, a Taskmaster Client shortcut is created on the
DevWorkstation that runs the new application. The new application's Taskmaster
Client shortcut is also placed in the new application's folder on the Server.
9 Copy the newly-created Taskmaster Client shortcut to other end user Workstations
where the Taskmaster Client component has been installed and from which users will
run the application.
10 Exit from Datacap Studio.
Copy Datacap.xml from DevWorkstation to Taskmaster Server

This procedure provides instructions on how to copy the datacap.xml file from the
DevWorkstation to the Taskmaster Server during your initial setup. This datacap.xml file
contains information about the application you copied and the location of the application's files
on the Taskmaster Server.
NOTE
Once the datacap.xml file has been copied to the Taskmaster Server, update it following the
instructions in Update Datcap.xml on Taskmaster Server.
1 On the DevWorkstation, start Windows Explorer, navigate to, and open the C:\Datacap
folder.
2 On the DevWorkstation, start another instance of Windows Explorer, navigate to the
Taskmaster Server, and open \\Server\Datacap.
3 Copy the DevWorkstation's datacap.xml file and paste it into the \\Server\Datacap
folder.
Set Location of Taskmaster Server and Datacap.xml

This procedure provides instructions on how to define the location of the datacap.xml and
define the location of the Taskmaster Server for an application using the Taskmaster
Application Manager.
2 Select the application (such as APT, MClaims, NENU, or a newly-converted
application). Paths appear in the fields on the Application tab.

3 Ensure all workflows are reflected, and that all of the paths reflect the correct UNC
paths to the various files and databases using the Server's name rather than C:\.
4 Click the Taskmaster tab to display it.
5 Change the Server name/address to the name of the Taskmaster Server (without
backslashes).
7 Change or ensure the path reflects the correct location of the datacap.xml on the Server,
for example:

Complete Taskmaster Server Configuration

This section provides the information you need to complete the configuration of your
Taskmaster Server, including updating the datacap.xml file on the Taskmaster Server to reflect
the actual locations of those applications and setting up security on the folder containing the
newly-copied application.
Update Datacap.xml on Taskmaster Server

The datacap.xml file on the Taskmaster Server should only contain references to applications
that actually exist in the locations indicated in the file and that are being configured for use.
This procedure provides instructions for updating the file, including adding references to
additional applications that exist, deleting references to applications that do not exist in the
locations indicated in the file, or deleting references to applications that exist but have not been
configured for use.
NOTE
The Taskmaster Application Service is case-sensitive; when adding or changing entries in
the datacap.xml file, ensure the case matches the case of the UNC paths, folders and file
names.
1 Before you begin, identify the names and locations of the applications you want the
Taskmaster Application Service to be aware of.
2 Start Notepad, navigate to, and open the datacap.xml file on the Server. It contains lines
that look like this:
<datacap ver="8.0">
<app name="1040ez" ref="1040EZ"/>
<app name="Express" ref="Express"/>
<app name="Flex" ref="Flex"/>
<app name="Survey" ref="Survey"/>
<app name="APT" ref="\\TASKMASTERSERVER\Datacap\APT"/>
<app name="MClaims" ref="MClaims"/>
<app name="AppWizard" ref="DStudio\AppWizard"/>
</datacap>
3 To delete references to applications that do not exist or have not been configured for
use, delete the corresponding <app name= lines. For example, when the only application
on the Taskmaster Server is the APT application, delete all of the lines except the line
for the APT application so your end result looks like this:
<datacap ver="8.0">
</datacap>
4 To add references to applications that exist, add a line that reflects the name of the
application and the full UNC path to the application folder. For example, when adding
a line for the NENU application, your end result looks like this:
<datacap ver="8.0">

<app name="NENU" ref="\\TASKMASTERSERVER\Datacap\NENU"/>

</datacap>
5 Save and then close the datacap.xml file.
Set Up Security on Datacap\Application Folder (Windows 2003)

an application-specific folder for a newly-copied application when the Server's operating
system is Windows 2003.
Repeat these instructions for each C:\Datacap\Application folder - setting up these security
permissions at this level allows you to grant access to different applications to specific
developers and end users.
1 On the Server, start Windows Explorer, navigate to and right-click the
C:\Datacap\Application folder and select Sharing and Security. The Sharing tab is
displayed.
3 Add the local ASP.NET Machine Account (Server\ASPNET) and local Internet Guest
Account (Server\IUSR_SERVER) and set both to allow Full Control.
4 Add/ensure Domain/Windows User ID of developer is set to allow Full Control.
Control.
Set Up Security on Datacap\Application Folder (Windows 2008)

an application-specific folder for a newly-copied application when the Server's operating
Repeat these instructions for each C:\Datacap\Application folder on the Server - setting up
these security permissions at this level allows you to grant access to different applications to
specific developers and end users.
C:\Datacap\Application folder and select Properties. The Properties dialog opens with
the General tab displayed.
2 Click the Security tab to display it, and click Edit.
3 Add NETWORK SERVICE and local IUSR and set both to allow Full Control.
4 Add/ensure Domain/Windows User ID of developer is set to allow Full Control.
Control.
6 When Batches folders are staying on Server in the C:\Datacap\Application path,
add/ensure Domain/Windows User IDs of Taskmaster end users are set to allow Full
Control.

Run Taskmaster Client APT Application
Using Taskmaster APT

This section provides the information you need to process the sample, pre-scanned images
included with the IBM Datacap Taskmaster Capture foundation APT application. The sample
images consist of single and multi-page invoices and a separator page, provided so you can run
Taskmaster Client APT “out of the box” using a “virtual scan” without having to hook up a
real scanner to the Workstation.
Overview of Taskmaster APT

Taskmaster APT is delivered with different pre-configured “jobs.” A job is a collection of
tasks to perform and rules to run that process invoices. The default shortcuts you see when
you start APT allow you to start and run various job-task combinations.
APT’s jobs include:
• Demo
• Demo-Dot Matrix
• Demo-FlexID
• Demo-Multipage TIFF
• Main Job
• Main Job-Dot Matrix
• Web Demo
• Web Demo-Dot Matrix
• Web Main
• Web Main-Dot Matrix
Note that the Main Job and Main Job-Dot Matrix must be configured for use with your specific
scanners before they appear on the list of available jobs and before you can use them.
The Demo-FlexID job is used as the example in this documentation. When running the Demo-
FlexID job, the default shortcuts you run, and the sequence in which you run them using the
Taskmaster Client APT are as follows:
This shortcut Does this

Scan Allows you to select the Demo-FlexID job, and run the VScan
(virtual scan) task to bring the sample invoice images into APT.
FlexID Allows you to assign a page type to each of the images in your
batch.

This shortcut Does this

Background Starts the Batch Profiler task that performs many image
processing functions including: identification of pages, image
cleaning (e.g. despeckling), image rotation (if necessary), full
page character recognition, and more. It also attempts to
identify the invoice by comparing it to a library of known
invoices.
Verify Starts the Verify task that displays the sample invoice images
and the data that has been recognized in the Verify window so
you can ensure the data is complete and correct. When an
invoice is not a known invoice, the Verify window allows you
to identify the fields and data on it, and to save its fingerprint so
it will be recognized the next time.
Export (or Starts the Export task that completes processing of images,
Background) saves information about the invoices, and exports field data to
XML files for input into your Accounts Payable, document
imaging, or ERP system. (Depending on the available batches
and their current statuses, clicking the Background shortcut
will run either the Batch Profiler task or the Export task.)
Upload Used by remote users (using Taskmaster Web Client) to upload
batches to the Taskmaster Server.
Run Taskmaster Client APT Application

foundation APT application “out of the box.” These instructions involve starting the
Taskmaster Server Service, starting the Taskmaster Client APT application, and running the
default tasks to process sample, pre-scanned images.

started on the Taskmaster Server .
Server, and click Taskmaster Server Manager.
opens. Click Yes.
2 When the Status:
In a client-server environment:
If a Taskmaster Server Service error is displayed

See the section titled Grant Taskmaster Server Service Log On as a Service Right to re-
grant the service the log on as a service right.
Start Taskmaster Client APT for the First Time

This procedure provides instructions on how to start the Taskmaster Client APT application on
the DevWorkstation for the first time after copying the application to the Server and
completing the Server configuration.
When you have copied the APT application to the Server successfully, a Copy of APT Client
shortcut is created on your DevWorkstation desktop, and is added to your Windows Start
menu.
Note that after the first time you log into the Taskmaster Client, it remembers and displays
what you entered the previous time.
1 From the DevWorkstation's desktop, double-click the Copy of APT Client icon. The
Taskmaster Client window opens, and a Station ID is missing in the profile message is
displayed.
2 Click OK. If your Windows login credentials are used, a Login name and/or password
invalid message is displayed.
3 Click OK. The Please login window is displayed with your Window User ID and the
name of your computer displayed.
4 Replace your Windows User ID with admin, enter admin as the password, replace your
computer name with the number 1, then click OK. The Taskmaster Client APT main
window opens with the Operations pane displayed.
Run Taskmaster Client APT VScan Task (Scan Shortcut)

This procedure provides instructions on how to run the Taskmaster Client APT VScan task to
process pre-scanned images.
1 On the DevWorkstation, in the Operations pane, double-click the Scan shortcut, select
the Demo-FlexID job and click OK. A Task Monitor window opens and a Rulerunner
window opens displaying a progress bar, then they both close. A message box is
displayed indicating the task has finished.
VScan task finishes successfully, APT has picked up the images from the
\APT\images\Input folder and created a IBM Datacap Taskmaster Capture “batch,”
which is a collection of document images to be processed. Taskmaster has assigned a
batch ID and created a uniquely-numbered folder with the name of the batch ID in
\APT\batches. This folder holds all of the document image processing results for this
batch of invoices, including the newly-created rrsvscan.xml file.

Monitor's title bar and press F5. The Job.Task and Status for this batch have been
updated and are now Demo-FlexID.FlexID and pending.
Run Taskmaster APT FlexID Task

This procedure provides instructions on how to run the Taskmaster Client APT FlexID task.
1 On the DevWorkstation, in the Operations pane, double-click the FlexID shortcut.
After a moment, the FlexID window opens, displaying thumbnails of the images in the
batch on the left and a large version of the first image on the right.
The following table describes some of the things you can do on the FlexID window:
To Do this
Zoom in or out, or change size of Right-click on the image or thumbnail,
image or thumbnail point at Zoom, then select appropriate
command
Rotate thumbnail or image Right-click on the image or thumbnail and
select Rotate 90 - repeat if necessary
Add or remove scroll bars from image Right-click on the image or thumbnail and
when image is larger than display area select Scroll bars
Print currently selected image Right-click on the image or thumbnail and
select Print
Select Page Type Click the dropdown arrow and select the
Page Type
Set the first page of each invoice to Main,
set the document separator sheet to
DocSep, and set the second invoice page to
Trailing.
Change the sequence of images Press <Shift> then click the image you
want to move and drag it to the left or right
Add a blank separator page before the Click <Add
currently selected image
Add a blank separator page after the Click Add>
currently selected image
Make a duplicate copy of the currently Click Clone
selected image
Display the next row of images when Click Next
there are more than nine images in the
batch
Display the previous row of images Click Prev
when there are more than nine images
in the batch
Place the batch on hold Click Hold
Complete Page Type assignment Click Done

2 After assigning the Page Type to each image, click Done. A message box is displayed
indicating the task has finished.
FlexID task finishes successfully, a FlexID.xml file has been created (containing the
Page Types you assigned) in the batch's uniquely-numbered folder in \APT\batches.
updated and are now Demo-FlexID.Batch Profiler and pending.
Run Taskmaster Client APT Batch Profiler Task (Background Shortcut)

This procedure provides instructions on how to run the Taskmaster Client APT Batch Profiler
task.
1 On the DevWorkstation, in the Operations pane, double-click the Background shortcut.
A Task Monitor window opens and a Rulerunner window opens displaying a progress
bar, then they both close. This may take a few minutes, as Rulerunner is running a
number of processing-intensive modules, including PageID, ImageFix, CreateDocs,
Recognize, FindFingerprint, Locate, lookups, and others. When processing is complete,
a message box is displayed indicating the task has finished.
When the Batch Profiler task finishes successfully, the images have been organized into
page XML files have been created, along with a BatchProfiler.xml file in the batch's
uniquely-numbered folder in \APT\batches.
updated and are now Demo-FlexID.Verify and pending.
Run Taskmaster Client APT Verify Task (Verify Shortcut)

This procedure provides instructions on how to run the Taskmaster Client APT Verify task.
1 On the DevWorkstation, in the Operations pane, double-click the Verify shortcut. A
Task Monitor window opens and a Rulerunner window opens, then the Verify - Batch
Pilot window opens.
Note that for demonstration purposes only, all invoices are deliberately set to be
displayed in the Verify window. In a production environment, you decide whether
you want every invoice to be displayed to the Verify Operator, or only those invoices
where recognition results are low confidence and data validation rules are violated.
The Verify window displays the first invoice in the batch and the details for the first
line item on that invoice. The left side of the window displays fields, recognized data,
snippets, and a number of buttons, with invoice “header” information displayed on top,
and line item detail on the bottom. The right side of the window displays the scanned
invoice.

When there are errors or low confidence results, the cursor is placed in the first problem
field and the field is outlined in red. In addition, the background color of a data field
indicates:
• Blue: No data validation errors or low confidence recognition results
• Yellow: Low confidence recognition results (low confidence characters are
displayed in red)
• Red: Data validation error
When a field fails validation (red background), you must correct the data before you can
complete the batch. When the recognition results for a field are low confidence (yellow
background), you can either update the contents of the field and tab out (background
changes to blue), or ignore the low confidence condition and press Ctrl+Shift+N to go
to the next document in the batch.
2 The following table describes some of the things you can do using buttons and hot-key
combinations on the APT Verify window; for additional instructions on using the APT
Verify Window, see Verify Window.
To Do this
Move to next low confidence Press <Alt+L>
character
Fill empty field with data using Click Click in an empty data entry field, then
N Key do one of the following:
Point at the field value on the document
image and click it, or,
Click and drag the mouse to draw a
rectangular box around the existing field
data on the image, or,
Press and hold <Alt>, click and drag the
mouse to draw a rectangular box that
encompasses additional blank space (to
leave room for additional characters ), or,
Press and hold <Shift>, click a field that
has already been defined and drag the
mouse to extend the field.
Invoke validation rules for entire Press <Alt+V>
invoice
Delete the document that is currently Press <Alt+D>
displayed
Mark the document for review Press <F2>
Display the next document in the Press <Ctrl+Shift+N>
batch

To Do this
Display the previous document in the Press <Ctrl+Shift+P>
batch.
Move to the next problem document Press <Ctrl+N>
in the batch
Move to the previous problem Press <Ctrl+P>

Lookup and select vendor (either Enter at least the first character of the
when blank or when incorrect vendor vendor’s name and the Remittance_Zip,
is displayed) then click Lookup Vendor
Open the Purchase Order Line Click POLR
Reconciliation window to match or
review matched line items
Identify type of invoice Select from the Invoice Type dropdown
list
Refresh line item matching Click the button next to the PO Number
label
Display original version of scanned Click the TIO button to toggle to TIF
image (with lines, noise, etc.), display
cleaned up version of image (toggles
from TIO to TIF)
Create new fingerprint for this Click New
invoice
Display previous page of invoice, Click Page 1 of 1 < or >
display next page of invoice
Display contents of previous line Click Lineitem Prev or Next
item, display contents of next line
item
Add line before current (displayed) Click <Add or Add >
line, add line after current line
Delete current (displayed) line Click Del
Calculate missing numeric values Click Calculate Blank
using existing values and
automatically fill blank numeric
fields
For all detail lines, locate all field Click Find Details
values for all fields
View all detail lines (opens separate Click View Details
window)

To Do this
Display or hide the scanned image On the View menu, select Image View,
or press <Ctrl+Alt+I>
Move the image within the display Click and drag the image
frame
3 Using <Tab>, <Alt+L>, <Alt+V> and other keys described above, review and validate
each sample document. When the data has been validated, an End of Page Reached
message will be displayed.
4 Click Yes to go to the next document. When you have finished processing the last
invoice in the batch, a message box indicates that no additional problems were found.
5 Click OK to finish the batch. A message box is displayed indicating the task has
finished.
When the Verify task finishes successfully, page XML files have been updated (for
Verify.xml file has been created in the batch's uniquely-numbered folder in
\APT\batches.
updated and are now Demo-FlexID.Export and pending.
Run Taskmaster Client APT Export Task (Export Shortcut)

This procedure provides instructions on how to run the Taskmaster Client APT Export task.
1 On the DevWorkstation, in the Operations pane, double-click the Export shortcut. A
then they both close. A message box is displayed indicating that the Export task
finished.
When the Export task finishes successfully:
• Export outputs the field data to XML files. The XML files and the image files
are now ready to be input into a back-end application.
• An Export XML file has been added to the batch’s uniquely-numbered folder
found in \APT\batches.
• Export saves information about unknown invoices that were successfully
validated (creates new fingerprints) so that the next time Taskmaster APT “sees”
the same invoice, it can identify the vendor and extract the field data using a
process called Intellocate.
• If during Verify, you marked an invoice for review or rescan, or deleted an
invoice and you did not configure email notifications, the PDFs of the marked or
deleted images stay in the batch's uniquely-numbered folder in \APT\batches; the
images and information about the images are not exported. If you configured
Taskmaster APT to send email notifications when invoices are marked or

deleted, Export also sends the appropriate emails with the marked or deleted
image attached as a PDF file.
updated and are now Demo-FlexID.Export and Job Done.
4 Use Windows Explorer to navigate to and open the resulting PDFs (one for each
invoice), and you can open the Export.xml file to view the data captured from the
invoices.
APT Verify Window Instructions

These instructions cover situations that are likely to occur during processing of invoices.
Note
These instructions use the following terms:
• Matched/Unmatched - Taskmaster APT’s processing finds a fingerprint that it
thinks matches an invoice; this match may be correct or incorrect
• Known/Unknown - Taskmaster APT has or does not have the vendor in a
lookup database; Taskmaster APT has or does not have a fingerprint for the
invoice
Process Unknown Invoice for Known Vendor
This situation involves processing an unknown invoice for a known vendor. This can occur
when a vendor has changed the layout of their invoices so much so that APT does not identify
the invoice as belong to the vendor, or when an invoice is processed for a vendor who has just
recently been added to the lookup database.
Symptom(s)
When APT processes the unknown invoice, the Vendor Name is blank.
Instructions
Process the invoice as a unknown invoice: Enter the first few letters of the vendor’s name and
the vendor’s zip code, click Lookup Vendor, and populate the data fields using Click N Key,
Find Details, etc. and press <Alt+V> to validate, and ensure the invoice data passes all
validations. It is important to use Click N Key to populate the fields so that the data locations
on the images can be stored as part of the fingerprint.
Identify Detail Lines on Unknown Invoice
This situation involves identifying where the first line item is located or where each of the
fields in the line are located or what type of information they contain. This occurs on unknown
invoices.
Symptom(s)
When an unknown invoice is processed, the Lineitem counter displays 0(0) - line 0 of 0.
Instructions
Click the Add> button to add an empty line, use Click N Key to identify where each of the
fields are in the first line, then click Find Details to locate the remaining lines. When the
Lineitem counter displays an actual count, click View Details to review the data captured for

all of the lines in a separate window. Close the window, and press <Alt+V> to validate, and
ensure the invoice data passes all validations.
Process Multiple Unknown Invoices for Known Vendor in Single Batch
This situation involves processing multiple unknown invoices in a single batch for a known
vendor. This can occur when a vendor has changed the layout of their invoices, or when
previously unprocessed invoices are processed for a vendor who has just been added to the
lookup database.
Symptom(s)
When APT processes the first unknown invoice, the Vendor Name is blank.
Instructions
Process the invoice as a unknown invoice: Enter the first few letters of the vendor’s name and
the vendor’s zip code, click Lookup Vendor, and populate the data fields using Click N Key,
Find Details, etc. and press <Alt+V> to validate, and ensure the invoice data passes all
validations. It is important to use Click N Key to populate the fields so that the data locations
on the images can be stored as part of the fingerprint.
When the next invoice in that batch for that same vendor is displayed in the Verify window,
APT matches it to the earlier invoice that passed validation, and displays a Sticky Fingerprint
Available button above the Lookup Vendor button. Click the Sticky Fingerprint Available
button to locate and populate the fields automatically.
Handle Unknown Invoice when Vendor is Unknown
This situation involves handling an unknown invoice for an unknown vendor. This can occur
when your company is invoiced by a vendor before the vendor has been added to the lookup
database.
Symptom(s)
When APT processes the invoice, the Vendor Name is blank, and when you click Lookup
Vendor, the vendor is not listed.
Instructions
When Microsoft Outlook is installed on the Workstation and you updated the APT Settings.ini
file with real email addresses, you can do one of the following that will route the invoice to a
knowledge worker for handling:
• Mark the invoice for supervisor review - Press <F2>, enter relevant comments,
then click OK. When Microsoft Outlook is installed on the Workstation, this
invoice is not exported, rather, during the Export task, an email containing this
invoice image is sent to the email address specified by the Review= parameter
provided in the Settings.ini file.
• Delete the invoice from the batch - Press <Alt+D>. A message box is displayed,
asking you to confirm that you want to delete the document. Click Yes. When
Microsoft Outlook is installed on the Workstation, this invoice is not exported,
rather, during the Export task, an email containing this invoice image is sent to
the email address specified by the Delete= parameter provided in the Settings.ini
file.
Otherwise, when Microsoft Outlook is not installed on the Workstation, you can put the entire
batch on hold and alert a Supervisor of the problem:

On the File menu, select Quit Task and confirm you want to put the batch on hold.
Associate Vendor and Fingerprint
This situation involves correcting the association between a vendor and a fingerprint, and
correcting the data when APT has matched an invoice with the wrong fingerprint. This can
occur when two vendors use nearly identical invoice formats.
Symptom(s)
When APT processes the invoice, it displays the wrong vendor and the data fields are
populated with incorrect data.
Instructions
Enter the first few letters of the vendor’s name and the vendor’s zip code, click Lookup
Vendor, and select the correct vendor. Ensure all of the data fields are populated correctly
using Click N Key, Find Details, etc. and press <Alt+V> to validate. Then click the New
Fingerprint button. It is important to use Click N Key to populate the fields so that the data
locations on the images can be stored as part of the fingerprint.
Capture Fields on Rotated Image
This situation involves processing an invoice that you rotated.
Symptom(s)
Click N Key no longer works.
Instructions
Manually key the data into the fields from the image and press <Alt+V> to validate. Even
though the invoice passes all validations, a fingerprint is not automatically created by
Taskmaster APT, and the next invoice from that vendor is treated as an unknown invoice.

Review Default Installation Results

This section is optional. The instructions provided allow you to review the Taskmaster Client
groups, users, and stations installed by the default installation process and to become familiar
with the panels used to add new groups, users, and stations and assign application-specific
permissions.
View Taskmaster Client APT Groups, Users, Stations

configuration, some Taskmaster groups, users, passwords, and stations are automatically set up
for you in the APT foundation application.
Start Taskmaster Client APT

This procedure provides instructions on how to start the Taskmaster Client APT application. If
you have logged into the Taskmaster Client before, the information you entered previously is
displayed.
select Applications, select APT, and click the APT Client icon. The Please login dialog
opens.
3 The APT main window opens with the Operations pane displayed.
View Taskmaster Client APT Groups

This procedure provides instructions on how to view the default user security group delivered
as part of Taskmaster Client APT.
1 With the Taskmaster Client main window open, on the Settings menu, select Groups.
The Taskmaster Administrator dialog opens with the Groups tab displayed on top, and
the Groups listed in the left pane.
2 Select the Scanners group in the left pane.
3 In the right pane, completely expand the Privileges, Permissions, and Users branches to
view the options set for this group. For example, the "Scanners" group has been
granted permission to the iVScan and Upload tasks for the Web Demo, Web Demo
Dot-Matrix, Web Main, and Web Main Dot-Matrix jobs.
4 Then, do one of the following:
Click the Users tab and continue with step 2 in the View Taskmaster Client APT
Users procedure.
Click the Stations tab and continue with step 2 in the View Taskmaster Client
APT Stations procedure.
Click Done to close the Taskmaster Administrator dialog.
Client window.

View Taskmaster Client APT Users

This procedure provides instructions on how to view the default user permissions delivered as
part of Taskmaster Client APT.
1 With the Taskmaster Client main window open, on the Settings menu, select Users. The
Taskmaster Administrator dialog opens with the Users tab displayed on top and the
Users listed in the left pane.
2 Select the scan1 user in the left pane.
3 In the right pane, completely expand the Privileges, Permissions, and Groups branches
to view the options assigned to this user. For example, the "scan1" user is part of the
Scanners group, and has been granted the permissions that were granted to the group.
4 Then do one of the following:
Click the Stations tab and continue with step 2 in the View Taskmaster Client
APT Stations procedure.
Click the Groups tab and continue with step 2 in the View Taskmaster Client
APT Groups procedure.
Client window.
View Taskmaster Client APT Stations

This procedure provides instructions on how to view the default station permissions delivered
as part of Taskmaster Client APT.
1 With the Taskmaster Client main window open, on the Settings menu, select Stations.
The Taskmaster Administrator dialog opens with the Stations tab displayed on top.
2 Select the remote station in the left pane.
3 In the right pane, completely expand the Permissions branches to view the specific
Tasks this station has permission to run. For example, the "remote" station has been
granted permissions to run iVScan, Upload, and Verify tasks.
Click the Groups tab and continue with step 2 in the View Taskmaster Client
APT Groups procedure.
Click the Users tab and continue with step 2 in the View Taskmaster Client APT
Users procedure.
Client window.

Set Up Taskmaster APT to Process Your Invoice Images

You can easily test Taskmaster APT using your own invoice images. However, since APT
out-of-the-box cannot access your company's actual accounts payable or vendor database to
perform vendor lookups and validation, nor can it access your company's actual purchase order
database to match line items from your invoices to your purchase orders, the instructions in
this section allow you to simulate the vendor lookup and purchase order matching processing.
The steps to do this include:
1. Shut down all Taskmaster software
2. Back up, then delete the sample invoice images
3. Copy your images to the input folder
4. Add the vendors of those invoices to the Demo Vendor List (to simulate your
vendor lookup database)
5. Optional: Obtain purchase orders related to your invoice images and add purchase
order line item details to the simulated purchase order database
6. Run APT, and process each invoice
Shut Down Taskmaster Software

Before setting up APT to process your invoice images, we recommend that you shut down the
Taskmaster software components running on each machine. Regardless of whether all
Taskmaster components are installed on a single machine or the machine is part of a
Taskmaster network configuration, you should shut down the Taskmaster software in the
following sequence:
Taskmaster Web Client, Taskmaster Client Service, Rulerunner Quattro Service,
Datacap Studio, Batch Pilot, etc.)
etc.)
Back Up then Delete Sample Input Images

Open Windows Explorer, navigate to, and make a backup copy of the
\\Server\Datacap\APT\images\Input folder, then delete the sample images in the Input folder.
Copy Your Images to Input Folder

Copy your own invoice images to the \\Server\Datacap\APT\images\Input folder.
Add Your Vendors to the Demo Vendor List

Since APT out-of-the-box cannot access your company's actual accounts payable or vendor
database to perform vendor lookups and validation, Datacap provides a utility program that
simulates a database that contains vendor information.
This procedure provides instructions for adding your own vendors to this simulated database
so that you can process invoices from vendors other than those from the APT samples.

1 Open Windows Explorer, navigate to \\Server\Datacap\APT\dco_APT and double-click

the Add Vendor Demo.exe file. The Add Demo Vendor window opens.
2 If vendor information is displayed for a vendor in the upper part of the window, click
Clear.
3 For each of your vendors, enter a Vendor Name, a Vendor Zip code, and either enter a
Vendor Number or select the Generate Random option, then click Add. The vendor is
added to the Demo Vendors list.
4 Close the Add Demo Vendor window when you have added the vendors associated with
your invoice images.
Add Your PO Line Items to POTable

Since APT out-of-the-box cannot access your company's actual purchase order database to
match line items from your invoices to your purchase orders, if Microsoft Office Access
software is available, you can simulate your purchase order database by adding entries to a
purchase order table in the default Microsoft Access APTLook database.
Use either the actual purchase orders that are related to one or more of your invoice images, or
use the data on the invoice images to create the purchase order line item entries.
This procedure provides instructions for backing up and adding purchase order line items so
that APT's POLR feature can match line items from your invoices and purchase orders.
1 Open Windows Explorer, navigate to, and make a backup copy of the
\\Server\Datacap\APT\APTLook.mdb.
2 From the Windows Start menu, select All Programs, select Microsoft Office, and select
Microsoft Office Access. The Microsoft Access main window opens.
3 On the File menu, select Open, navigate to \\Server\Datacap\APT\APTLook.mdb, select
it, and click Open. The APTLook : Database window opens.
4 Double-click POTable to open it. The POTable: Table is displayed with default data.
5 On the Edit menu, point to Go To, then select Last. The row marker moves to the last
row in the table.
6 On the Edit menu, point to Go To, then select New Record. A row is added to the table.
7 For each line item, press the Tab key to move to the next column, and enter data in each
column (purchase order number, line item quantity, line item number, description of
item, and purchase order line number).
8 Repeat the previous two steps to add the purchase order line items on which you want
APT to perform matching.
9 On the File menu, select Save, then close the POTable window, the APTLook window,
and the Microsoft Access window.
Run Taskmaster APT

Follow the instructions in the section titled Using Taskmaster APT to process the images.

APT Troubleshooting
Permission Denied: 'Load Picture' Error

This situation involves inadequate permissions granted to users and to a graphic image that is
stored in the application's dco_ folder.
Symptom(s)
The user receives a "Permission denied: 'LoadPicture' Run-Time Error" while running the
Verify task in APT or Flex.
Instructions
Depending on the permissions your organization grants users, when a user is logged onto
Windows as a Restricted User and is running the Verify task in APT (or Flex), the user may
receive a "Permission denied: ‘Load Picture’ " error message.
Using Windows Explorer, navigate to and open the application's dco_ folder (usually on
Taskmaster Server). Right-click the fprintnew.bmp file, select Properties, and click the
Security tab. Add the user and grant the user Full Control to the fprintnew.bmp file.
Changes to Pre-Existing Zone Positions Are Ignored

This situation involves an invoice on which, when processed the first time, the field zones
were not set up properly. A subsequent attempt to make changes to the existing zones is
ignored.
Symptom(s)
When APT processes an invoice from a known vendor, it "misses" data or captures the wrong
data.
Instructions
When an invoice is processed for the first time, an incorrect fingerprint for the invoice can be
created. While APT supports adding missing fields to an existing fingerprint, it does not
support making changes to existing field positions.
To correct a fingerprint with incorrectly zoned fields, do the following:
• Identify the fingerprint's unique Fingerprint ID
• Delete the fingerprint
• Recreate the fingerprint
Identify Fingerprint ID Associated with Problem Invoice

When fields on an invoice have not been zoned correctly, data from the invoice will not be
captured when the invoice is displayed in the Verify window.
To identify the Fingerprint ID associated with the problem invoice, do the following:
1 With the invoice is displayed in the Verify window, make a note of the vendor's name
(displayed on the invoice) as well as the Batch ID and document number found in the
lower right portion of the status bar.
2 Using Windows Explorer, navigate to the application's Batches folder, and open the
folder that contains the batch.

3 Using a text editor such as Notepad, open the Verify.xml file.

4 Locate the portion of the file associated with the Batch ID and document number.
5 Locate the TemplateID tag and the Fingerprint ID.
6 Use the Fingerprint ID to identify and delete the fingerprint using the Fingerprint
Maintenance Tool.
Start Fingerprint Maintenance Tool

On the Taskmaster Server where the application files are located, open Windows Explorer and
navigate to the Datacap\Application\dco_Application folder (for example:
Datacap\APT\dco_APT) and double-click Fingerprint Maintenance Tool.exe. The Fingerprint
Maintenance Tool window opens.
The very first time the Fingerprint Maintenance Tool is run, a message is displayed indicating
a backup directory has been created.
Delete Fingerprint
To delete a fingerprint when you know the Fingerprint ID, do the following:
1 Start the Fingerprint Maintenance Tool.
2 Click the Show Statistics button to display information about all existing fingerprints.
3 Select the ID of the fingerprint that you want to delete.
4 Click the Delete Selected button.
Recreate the Fingerprint for the Invoice

Recreate the fingerprint associated with the invoice by re-scanning the invoice and creating all
of the zones for all of the fields, including line items. Then complete the process by exporting
the batch containing the invoice.

Installation Instructions for User Workstation

On Windows 7:
opens.
displayed.
On Windows 2008:
are displayed.
Installation Instructions for User Workstation

InstallShield Wizard on an end user's Workstation ("Workstation") to install the Taskmaster
Client ("thick client") software components. The components you install include the
Taskmaster Client sample applications, the separately licensed applications for which you have
a license, and the separately licensed connectors for which you have a license.
WARNINGS
Machine.

the Setup.exe.
it.
8 Exclude all features except Taskmaster Client, and the separately licensed connectors
for which you have a license.
9 Expand the Taskmaster Client software component and exclude the separately licensed
applications for which you do not have a license, and exclude the Datacap Studio,
DotScan, DotEdit, and NENU components.
12 Click Finish.
Set Up Sharing and Security Permissions for End Users

Each Taskmaster user must be granted sharing permissions and security permissions to a
number of Taskmaster folders.
This procedure provides instructions on how to grant the appropriate permissions to
Taskmaster end user accounts.

Set Up Sharing Permissions on Datacap Folder

Set Up Security on Datacap Folder
Set Up Security on Datacap\Application Folder
C:\Datacap\Application folder and select Sharing and Security. The Sharing tab is
displayed.
Copy Taskmaster Client APT Shortcut to Workstation

After an application has been successfully copied from one machine to another using the
Datacap Application Copy Wizard, a Taskmaster Client shortcut for that copied application is
placed in the application's folder on the target Server, as well as on the DevWorkstation from
which the application was copied.
Copy the Taskmaster Client shortcut to other end user Workstations where the Taskmaster
Client component has been installed and from which users will run the application.
Ensure Scanner is Set Up and Works

Follow the manufacturer’s instructions to attach the scanner to the Workstation, and install and
configure the required scanner software. Be sure you can scan successfully using the scanner
using any image capture software product. If you cannot scan documents outside of IBM
Datacap Taskmaster Capture, you will not be able to scan documents using Taskmaster.
separately licensed or sample applications, as those applications can process the prescanned,
sample images included during installation.
Set Up Taskmaster Application to Use Scanner

Install a scanner on the Workstation, and ensure the scanner works outside of IBM Datacap
Taskmaster Capture before starting these instructions to define the scanner to the Taskmaster
Client application.
This procedure provides instructions on how to define your scanner to a specific Taskmaster
Client application.

applications out-of-the-box, as these applications can use the prescanned sample images
included during installation.
1 On the Workstation, with the Taskmaster Client application main window displayed, on
the Settings menu, select Workflow. The IBM Datacap Taskmaster Capture
Administrator dialog opens with the Workflow tab displayed on top.
2 In the left pane, expand the workflow, and select one of the scan jobs to expand its
contents.
3 In the left pane, select the scan task. The task information in the right pane displays
information about the scan task.
4 In the right pane, click Setup. The Scan Setup – IBM Datacap Taskmaster Capture
window opens.
5 If a Scan flatbed message box appears, click Cancel. When the message box closes,
another message may appear that indicates a scanner is not currently selected.
6 Click OK. A blank Scan Setup window is displayed.
7 On the File menu, select Quit. The IBM Datacap Taskmaster Capture Administrator
dialog is redisplayed.
8 Click Setup again. The Scan Setup – IBM Datacap Taskmaster Capture window opens.
If the message indicating that a scanner is not currently selected appears, click OK.
9 Click OK. A filled-in Scan Setup window is displayed.
10 Click Select Scanner. A Loading Driver message box is briefly displayed, then the
Scanner Selection window opens.
11 Select the scanner you want to use, then click OK. The Configure Device Settings
window opens.
12 Click OK. Both windows close and the Scan Setup – IBM Datacap Taskmaster Capture
window is redisplayed.
13 Click Done. The Scan Setup – IBM Datacap Taskmaster Capture window closes.
14 Click Apply to save your scanner setup settings.
15 Click Done. The IBM Datacap Taskmaster Capture Administrator dialog window
closes.


example:

Install and Configure Taskmaster RV2
Taskmaster RV2
IBM Datacap Taskmaster Capture RV2 web application displays real-time reports of activity
related to your Taskmaster applications.
The following standard reports for monitoring batch status, station activity, and problem
batches are included with IBM Datacap Taskmaster Capture RV2 software component:

Source
Problem Displays all queued batches that have aborted or queue table
Batches are offline, or have been running longer than two
hours.
Current Displays all queued batches that are not complete queue table
Batches or canceled.
Batch Aging Same as Current Batches except includes elapsed queue table
time since batch was started.
Current Displays the station IDs and IP addresses of all
Stations stations currently logged, plus the number of
batches processed by each station.
Station Activity Displays a bar chart showing the number of qstats table
batches completed by each station within the last
four hours.
Pending Tasks Displays a bar chart showing the number of queued queue table
batches with status pending or aborted.
Use Hourly the percentage of each hour spent processing by table
each station.
Use Daily the percentage of each day spent processing by table
each station.
Background Displays summary of all batches processed, taskstats
grouped by station ID. Includes aggregates for table
processing time, number of pages scanned, etc. for
each station.
Background Same as Background except starts and refreshes in taskstats
Scan Displays a list of all scanned batches, grouped by scan2kst
operator. Includes aggregates for processing time, table
number of pages scanned, etc. for each operator.
Scan Summary Same as Scan except starts and refreshes in scan2kst
collapsed view. table


Source
Fixup Displays a list of all batches that have been through fixup2kst
Fixup, grouped by operator. Includes aggregates table
for processing time, number of pages rescanned,
inserted, etc. for each operator.
Fixup Same as Fixup except starts and refreshes in fixup2kst
Verify Displays all batches that are in or ready for de2kst
verification, grouped by operator. Includes table
aggregates for processing time, pages processed,
average documents per hour, etc. for each
operator.
Verify Same as Verify except starts and refreshes in de2kst
Batch Displays a list of all batches with status “Job queue and
Productivity done.” Includes number of pages scanned and total tmbatch
elapsed time for each batch from when batch was tables
started until completed. Also includes average
number of pages and average elapsed time per
batch.
Debug Displays a list of all batches in the debug table (for debug table
example, batches that were deleted manually).
Includes the batch status, status prior to being
moved to the debug table, etc.
Overview of RV2 Installation and Configuration

This section provides an overview of the steps required to install and configure the Taskmaster
RV2 reporting component.
In a client-server environment, you must:
1 Create or ensure an account exists for RV2
2 Ensure you have the required Microsoft Internet Information Services (IIS) components
installed
3 Set up various RV2 permissions
4 Install RV2 on the WebServer
5 Set up the RV2 web site
Create or Ensure Account Exists for RV2

Create or ensure a domain/Windows account exists for RV2.

Note
When Taskmaster Web, RV2 or Web Rulerunner Service (Rulerunner running as a web
service) are installed on the same WebServer, they must use the same domain/Windows
account.
Add RV2 Account to WebServer Administrators Group

The RV2 domain/Windows account must have administrative rights on the WebServer hosting
RV2.
Add the RV2 domain/Windows account to the WebServer's Administrators group so that the
account has local administrator rights on the machine.

stopped on the Server.
opens. Click Yes.
2 When the Status:
Install and Configure RV2 on Windows 2003 Web Server

This section provides the information you need to install and configure RV2 on a Windows
2003 web server (referred to as "WebServer").
Confirm IIS Configuration on Windows 2003 Server
Confirm that Internet Information Services (IIS) Manager was installed on your Windows
2003 WebServer.
The IBM Datacap Taskmaster Capture install package installs the Microsoft .NET Framework
when needed. If you run the Taskmaster InstallShield Wizard before installing IIS, the
ASP.NET application script maps may not point to the correct ASP.NET ISAPI version.
If you are not sure that IIS was installed prior to the Taskmaster installation, run Microsoft’s
ASP.NET IIS Registration Tool (aspnet_regiis.exe) with the installation parameter (-i).
Running the tool ensures the ASP.NET application script maps point to the appropriate
ASP.NET ISAPI version. For instructions on running the tool, see Run aspnet_regiis.exe. For
more information about the tool, search for “aspnet_regiis.exe” on the Microsoft website.
Run aspnet_regiis.exe
This procedure provides instructions on how to run Microsoft’s aspnet_regiis.exe to update the
ASP.NET application script maps to point to the appropriate ASP.NET ISAPI version.

1 From the Windows Start menu, select Run. The Run dialog opens.
2 In the Open field, type cmd, and click OK. A DOS command prompt window opens.
3 Locate the aspnet_regiis.exe (for example, from your C:\> prompt, type: dir
aspnet_regiis.exe /s)
4 Run the aspnet_regiis.exe with the -i parameter (for example:
C:\>C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i)
Progress messages are displayed indicating the start and completion of the installation.
5 When the installation has finished, exit/close the DOS window.
Set RV2 Sharing Permissions for Datacap Folder (Windows 2003)
This procedure provides instructions on how to set up the appropriate RV2 sharing permissions
for the C:\Datacap folder when the Taskmaster Server's operating system is Windows 2003.
2 The Datacap folder should already be shared.
4 Add the RV2 domain/Windows account and set to allow Read.
Set Up Security for RV2 on Datacap Folder (Windows 2003)
This procedure provides instructions on how to set up the appropriate RV2 security for the
C:\Datacap folder when the Taskmaster Server's operating system is Windows 2003.
3 Add/ensure the RV2 domain/Windows account is set to allow Read & Execute.
Update ASP.NET Process Identity in Machine.Config File (Windows 2003)
RV2 uses an IIS Process Model Identity to access IBM Datacap Taskmaster Capture.
Note
When RV2, Taskmaster Web, or Web Rulerunner Service (Rulerunner running as a web
service) are installed on the same web server, they must use the same domain/Windows
account.
This procedure provides instructions on how to update the machine.config file on the
WebServer when the operating system is Windows 2003.
1 On the WebServer, use Windows Explorer to navigate to and use a text editor such as
Notepad to open
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\CONFIG\machine.config
2 Locate the line that contains only <system.web> and the next line starting with
<processModel …
Caution
There are multiple occurrences of "<system.web>" in the machine.config file. Be sure

you locate the occurrence where "<system.web>" is the only text on the line, and that
the next line starts with "<processModel".
3 Add the following information to the <processModel line so that it reflects the RV2
domain/Windows account that you want to use:
<processModel autoConfig="true" enable="true"
userName="DOMAIN\RV2AccountName" password="RV2AccountPassword"/>
4 Save the changes to machine.config and close the file.
Grant RV2 Account Access to IIS Metabase (Windows 2003)
This procedure provides instructions on how to run Microsoft's ASP.NET IIS Registration
Tool (version 2 of .NET Framework) with the grant access parameter (-ga) to grant the RV2
domain/Windows account access to the IIS metabase and other directories used by ASP.NET
when the operating system is Windows 2003. For more information about the registration
tool, search for "aspnet_regiis.exe" on the Microsoft website.
1 On the WebServer, from the Windows Start menu, select Run. The Run dialog opens.
aspnet_regiis.exe /s).
4 Run the aspnet_regiis.exe with the -ga parameter followed by the domain name, a
backslash, then the RV2 account name;
for example (no line breaks):
C:\>C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -ga
DOMAIN\RV2AccountName
then press <ENTER>.
A "Start granting… access" message is displayed, followed by a "Finished granting…
access" message.
5 Close the DOS command prompt window.
Install RV2 on WebServer
InstallShield Wizard to install the RV2 component.
WARNINGS
Machine.
the Setup.exe.

These instructions apply to Windows 2003 and Windows 2008 Servers.

Taskmaster Capture CD in the WebServer’s CD/DVD drive. If the installation process
Allow.
it.
8 Exclude all components from the installation process except RV2.
11 Click Finish to close the Wizard.
example:


This procedure provides instructions on how to set up the RV2 website under IIS 6.0
1 On the WebServer's Windows Start menu, select Settings, select Control Panel, select
Administrative Tools, and double-click Internet Information Services to open the
Internet Information Services window.
2 Expand the computer on which you want to create the virtual directory, expand its Web
Sites folder, right-click the Default Web Site, and on the shortcut menu, select New,
then select Virtual Directory. The Welcome page of the Virtual Directory Creation
Wizard opens.
3 Click Next. The Virtual Directory Alias page is displayed.
4 Enter RV2 as the alias, then click Next. The Web Site Content Directory page is
displayed.
5 Enter the full path of or use the Browse button to navigate to and select the
C:\Datacap\RV2 folder, then click OK. The Web Site Content Directory page
reappears with the full path to the RV2 folder displayed.
6 Click Next. The Access Permissions page is displayed.
7 Select the Read, Run scripts, and Execute options, then click Next. The completion
page of the Virtual Directory Creation Wizard is displayed.
8 Click Finish. The Wizard closes and the new RV2 virtual directory is displayed in the
Set Other Parameters for RV2 Web Site (IIS 6)
This procedure provides instructions on how to set additional parameters required by or
relevant to RV2 in an IIS 6 environment.
1 From the Server's Windows Start menu, select Settings, select Control Panel, select
2 Expand the computer, the Web Sites folder, right-click the Default Web Site, and select
Properties from shortcut menu. The Properties dialog opens.
3 Click the Configuration button. The Application Configuration window opens.
4 Click the Options tab to display it.
5 Select the Enable session state option and set the Session timeout field in accordance
with your company's security policies.
6 Select the Enable parent paths option.
7 Click OK to close the Application Configuration window.
8 Click the Documents tab to display it.
9 If the default.aspx document is not displayed, add it and click Apply to save your
change.
10 Click the ASP.NET tab to display it.
11 Click the Edit Configuration button. The ASP.NET Configuration Settings window
opens with the General tab displayed on top.

12 Click the Application tab to display it.

13 Set the Request execution timeout field to at least 1200 seconds, then click Apply.
14 Click State Management tab to display it.
15 Set the Session timeout field in accordance with your company's security policies, then
click Apply.
16 Click OK to close the local Settings window.
17 Click OK to save and close the Properties dialog.


This section provides the information you need to install and configure RV2 on a Windows
2008 web server (referred to as "WebServer").
On Windows 7:
opens.
displayed.
On Windows 2008:
are displayed.
been installed in Internet Information Services when the Server’s operating system is Windows
2008.
1 From the WebServer's Windows Start menu, select Control Panel, and on the Control
Panel Home window, select Administrative Tools, and then select Server Manager. The
Server Manager window opens.
2 In the Server Manager hierarchy pane, expand Roles, and then select Web Server (IIS).
The Web Server (IIS) window opens.
3 In the Web Server (IIS) pane, under Common HTTP Features, ensure Static Content is
installed.

4 In the Web Server (IIS) pane, scroll down to the Role Services section, and under
Application Development, ensure the ASP.NET and ASP modules are installed.
5 In the Web Server (IIS) pane, scroll down to the Management Tools section and ensure
IIS Management Console is installed.
6 Close the Server Manager window.
Set RV2 Sharing Permissions for Datacap Folder (Windows 2008)
This procedure provides instructions on how to set up the appropriate RV2 sharing permissions
for the C:\Datacap folder when the Taskmaster Server's operating system is Windows 2008.
displayed.
5 Add the RV2 domain/Windows account and set to allow Read.
Set Up Security for RV2 on Datacap Folder (Windows 2008)
displayed.
3 Add/ensure the RV2 domain/Windows account is set to allow Read & Execute.
Install RV2 on WebServer
InstallShield Wizard to install the RV2 component.
WARNINGS
Machine.
the Setup.exe.

Allow.
it.
8 Exclude all components from the installation process except RV2.
example:


This procedure provides instructions on how to set up the RV2 web site on Microsoft Internet
Information Services (IIS) 7 or 7.5.
2 In the Connections pane, expand the computer, expand Sites, right-click the Default
Web Site and choose Add Application. The Add Application window is displayed.
3 Set the Alias to RV2 and set the Physical path by entering or browsing to the
C:\Datacap\RV2 folder.
4 Click OK to close the Add Application dialog. The Internet Information Services (IIS)
Manager window is displayed.
displayed.
8 Click the browse button to the right of the Process Model Identity. The Application
Pool Identity window opens.
9 Select Custom account and click Set. The Set Credentials window opens.
10 Enter the RV2 Windows account information (the same account that you added to the
WebServer's Administrators Group) in the format: accountname@domain.com, enter
the account's password twice, then click OK. The Credentials window closes and the
Application Pool Defaults window is displayed.
11 Click OK. The Internet Information Services (IIS) Manager window is displayed.
Web Site.

View RV2 Reports for Taskmaster Client APT

opens. Click Yes.
2 When the Status:
Add RV2 Address as Trusted Site
This procedure provides instructions on how to add the RV2 address as a Trusted Site to
prevent Internet Explorer from blocking access.
5 When running Internet Explorer on the same machine as RV2, enter the default server
address (http://127.0.0.1) in the Add this website to the zone field, then click Add. The
URL is added to the bottom pane.
When running Internet Explorer from a different machine, enter either the WebServer's
IP address or name (http://WebServer) in the Add this website to the zone field, then
click Add. The URL is added to the bottom pane
Log Onto RV2
This procedure provides instructions on how to access and log into RV2.


http://WebServer/RV2/Login.aspx

Create an RV2 Report Filter
You can filter the data that is displayed in an RV2 report based on the values in one or more
fields. For example, if you want to view only activity related to a specific operator, you can
filter the data by operator name.
Each filter is associated with a single report, so the Select Filter list on the RV2 home page
displays only filters that are available for the report you have selected.
This procedure provides instructions on how to create a report filter.
1 With the RV2 home page displayed, select the report from the list on the left.
2 Click Manage Filters. Filter-related fields appear.
3 In the Add Filter field, enter a name for the new filter.
4 Click Add. Additional fields appear.
5 Set up the filter as follows:
In the first field, select the column name (for example, “Operator”)
In the second field, select the action (for example, “equal to”)
In the third field, enter the value (for example, “admin”)
6 To add another field, click Add Field and repeat the previous step.
7 Select Public (available to all users) or Private (available only to you).
8 Click Save.
9 If you want to run the report using the new filter, click Run Report. Otherwise, click
Reports to return to the RV2 home page.
Add Reports to the RV2 Dashboard
The RV2 dashboard view lets you view up to six reports simultaneously. The dashboard is
typically used for viewing chart-based reports.
This procedure provides instructions on how to add one or more reports to the RV2 dashboard.
You can add up to six reports.
displayed.

2 Select the report and the application name. If applicable, select a filter. The report is
displayed.
3 To add an additional report, click Add and repeat the previous step.
4 If you want the data on the reports to refresh automatically, click Refresh and select a
refresh interval.
Modify the RV2 Dashboard
Each report displayed on the dashboard can be resized, moved, or removed.
This procedure provides instructions on how to modify the dashboard by resizing, moving, or
removing a report.
displayed.
2 To resize a report, click the cross-hatched area at the bottom right corner and drag.
3 To move a report, click the dotted area at the top of the report and drag the report to a
different location.
4 To remove a report, click the report you want to remove, then click Remove.

Install and Configure Taskmaster Web
Taskmaster Web
This section provides the information you need to set up and run tasks using Taskmaster Web
and Internet Explorer.
Overview of Taskmaster Web Installation and Configuration

This section provides an overview of the steps required to install and configure Taskmaster
Web.
Configuration Prerequisites, including ensuring Microsoft .NET Framework 3.5.1 is
installed on Windows 7 and Windows 2008 machines.
2 Create or ensure an account exists for Taskmaster Web
3 Ensure you have the required Microsoft Internet Information Services (IIS) components
installed
4 Set various Taskmaster Web permissions and settings
5 Install Taskmaster Web on the WebServer
6 Set up the Taskmaster web site
Create or Ensure Account Exists for Taskmaster Web

Create or ensure a domain/Windows account exists for Taskmaster Web.
Note
account.

Install and Configure Taskmaster Web on IIS 6 Web Server

IBM Datacap Taskmaster Capture Taskmaster Web allows users to perform Taskmaster tasks
from remote machines on which only the Internet Explorer browser is installed.
This section provides the information you need to install and configure Taskmaster Web on a
Windows 2003, IIS 6 server (referred to as "WebServer") so users can use the browser-based
Taskmaster Web Client for processing.
opens. Click Yes.
2 When the Status:
Set Taskmaster Web Sharing Permissions for Datacap Folder (Windows 2003)
This procedure provides instructions on how to set up the appropriate Taskmaster Web sharing
permissions for the C:\Datacap folder when the Taskmaster Server's operating system is
Windows 2003.
4 Add the Taskmaster Web domain/Windows account and set to allow Read.
Set Up Security for Taskmaster Web on Datacap Folder (Windows 2003)
This procedure provides instructions on how to set up the appropriate Taskmaster Web
security for the C:\Datacap folder when the Taskmaster Server's operating system is Windows
2003.
3 Add/ensure the Taskmaster Web domain/Windows account is set to allow Read &
Execute.
Add or Ensure Upload Limit Setting is Large Enough in web.config
Depending on the usual size of the images that will be uploaded from the Taskmaster Web
Client, you should adjust the upload limit setting found in the web.config file.

This procedure provides instructions on how to locate and change the setting in the web.config
file that affects upload speed.
1 On the WebServer, start Windows Explorer, navigate to and open the
C:\Datacap\tmweb.net folder, scroll down to the web.config file and open it in a text
editor such as Notepad.
2 Within the <system.web> element, locate or add the
<httpRuntime maxRequestLength="52428" />
element - this parameter is expressed in kilobytes.
3 Depending on the usual size of the images that are being uploaded, you can increase the
size, for example:
4 When you have made changes, save and close the file.
Add or Ensure File Transfer Limit Setting is Large Enough (Windows 2003)
Client to the WebServer, you should adjust the default File Transfer Limit setting found in the
METABASE.XML file that is on the WebServer.
This procedure provides instructions on how to locate and change the File Transfer Limit
setting in the METABASE.XML file when the WebServer’s operating system is Windows
2003.
1 Before editing the METABASE.XML file, enable the metabase edit-while-running
feature using IIS Manager on the WebServer, otherwise you will not be able to save
your changes. To do this: In IIS Manager, right-click the local computer, click
Properties, select the Enable Direct Metabase Edit option, click Apply, then click OK.
\windows\system32\inetsrv folder, scroll down to the metabase.xml file and open it in a
text editor such as Notepad.
3 Locate and change the value (expressed in bytes) for AspMaxRequestEntityAllowed=
for example, from 204800 to 10238976.
5 After saving your changes, disable/clear the Direct Metabase Edit option in IIS
Manager.
Install Taskmaster Web on WebServer
InstallShield Wizard to install the Taskmaster Web component.
WARNINGS
Machine.

the Setup.exe.
Allow.
it.
8 Exclude all components from the installation process except Taskmaster Web.
2003 WebServer.

Taskmaster Web uses an IIS Process Model Identity to access IBM Datacap Taskmaster
Capture.
Note
When RV2, Taskmaster Web, or Web Rulerunner Service are installed on the same web
server, they must use the same domain/Windows account.
WebServer hosting Taskmaster Web when the operating system is Windows 2003.
1 On the WebServer, use Windows Explorer to navigate to and use a text editor such as
Notepad to open
<processModel …
Caution
There are multiple occurrences of ""<system.web>" in the machine.config file. Be sure
3 Add the following information to the <processModel line so that it reflects the
Taskmaster Web domain/Windows account that you want to use:
userName="DOMAIN\TaskmasterWebAccountName"
password="TaskmasterWebAccountPassword"/>
Grant Taskmaster Web Account Access to IIS Metabase (Windows 2003)
Tool (version 2 of .NET Framework) with the grant access parameter (-ga) to grant the
Taskmaster Web domain/Windows account access to the IIS metabase and other directories
used by ASP.NET when the operating system is Windows 2003. For more information about
the registration tool, search for "aspnet_regiis.exe" on the Microsoft website.
1 On the WebServer, from the Windows Start menu, select Run. The Run dialog opens.

backslash, then the Taskmaster Web account name;
DOMAIN\TaskmasterWebAccountName
then press <ENTER>.
access" message.
Create and Share (Nested) Virtual Directory for Taskmaster Web (IIS 6)
These instructions assume you will create a virtual directory for Taskmaster Web nested within
the WebServer's Default Web Site when Taskmaster Web is installed in an IIS 6 environment.
This procedure provides instructions on how to create a virtual directory for the Taskmaster
Web site.
1 From the WebServer's Windows Start menu, select Settings, select Control Panel, select
Administrative Tools, and double-click Internet Information Services. The Internet
Information Services window opens.
Wizard opens.
4 Enter tmweb.net as the alias, then click Next. The Web Site Content Directory page is
displayed.
5 Enter the full path or use the Browse button to navigate to and select the
C:\Datacap\tmweb.net folder, then click OK. The Web Site Content Directory page
reappears with the full path to the tmweb.net folder displayed.
8 Click Finish. The Wizard closes and the new tmweb.net virtual directory is displayed in
the Internet Information Services window.
Set Other Parameters for (Nested) Taskmaster Web Site (IIS 6)
This procedure provides instructions on how to set additional parameters required by or
relevant to Taskmaster in an IIS 6 environment.

2 Expand the computer, the Web Sites folder and the Default Web Site, right-click the
tmweb.net web site, and select Properties from shortcut menu. The tmweb.net
Properties dialog opens with the Virtual Directory tab displayed on top.
5 Select the Enable session state option and set the Session timeout field in accordance
with your company's security policies.
6 Select the Enable parent paths option.
change.
13 Set the Request execution timeout field to at least 1200 seconds, then click Apply.
15 Set the Session timeout field in accordance with your company's security policies, then
click Apply.
16 Click OK to close the local Settings window.
17 Click OK to save and close the Properties dialog.
Set Web Site Isolation Mode (IIS 6)
This procedure provides instructions on how to set the service to run in IIS 5.0 Isolation Mode
in an IIS 6 environment.
1 With the Internet Information Services window open, expand the computer on which
you created the virtual directory, right-click Web Sites, and on the shortcut menu, select
Properties. The Web Site Properties dialog opens.
3 Select Isolation Mode: Run WWW Service in IIS 5.0 Isolation Mode, click Apply and
click Yes when you are prompted to restart IIS.
4 Click OK to close the Web Site Properties dialog.
Select Web Service Extensions (IIS 6)
This procedure provides instructions on how to allow Active Server Page extensions in an IIS
6 environment.
1 On the WebServer, with the Internet Information Services window open, expand the
computer on which you created the virtual directory, and select Web Service
Extensions. The Web Service Extension options are displayed in the right pane.

2 Select/ensure Active Server Pages, ASP.NET v2.0.50727, and Server Side includes are
Allowed.
3 Close the Internet Information Services window.
Set Up Web Sharing and Security Settings on TaskRun Folder (Windows 2003)
This procedure provides instructions on how to share the TaskRun processing folder on the
WebServer that is required by Taskmaster Web. This folder is where batches temporarily
reside while they are being processed.
1 On the WebServer, start Windows Explorer, navigate to C:\Datacap\TaskRun, right-
click the TaskRun folder, and select Properties from the shortcut menu. The TaskRun
Properties dialog opens with the General tab displayed on top.
2 Click the Web Sharing tab to display it.
3 Select or ensure Share on is set to Default Web Site.
4 Select the Share this folder option. The Edit Alias dialog opens displaying the folder
name in the Alias field.
5 In the Application permissions group box, select the None option, and in the Access
permissions group box, select Write in addition to the Read option, then click OK. The
Web Sharing tab reappears with TaskRun displayed as an alias.
6 Click Apply to save your changes.
8 Add the local ASPNET Machine Account (Server\ASPNET) and Internet Guest
Account (Server\IUSR_SERVER) and set both to allow Modify.
9 Click OK to close the TaskRun Properties dialog.
Set Up TaskRun Virtual Folder (Windows 2003)
This procedure provides instructions on how to set the appropriate IIS parameters for the
TaskRun virtual folder required by Taskmaster Web.
2 Expand the computer, the Web Sites folder and the Default Web Site. If the virtual
TaskRun folder is not displayed, refresh the window as many times as it takes for the
TaskRun folder to appear.
3 Right-click the TaskRun folder, select Properties from the shortcut menu. The TaskRun
Properties window opens with the Virtual Directory tab displayed on top.
4 Click the Remove button. The Application name field is protected, and the Remove
button label changes to Create.
change.
7 Click the Directory Security tab to display it.

8 Click the top Edit button to edit the Anonymous access and authentication control
settings. The Authentication Methods dialog opens.
9 Select the Enable anonymous access checkbox and clear the Integrated Windows
authentication checkbox, then click OK. The Authentication Methods dialog closes and
the Directory Security tab is redisplayed.
If the ASP.NET version displayed is version 2.0.5nnnn, continue with the next
step.
If the ASP.NET version displayed is blank but the field is active, click the
dropdown arrow, select the 2.0.5nnnn entry from the list, and continue to the next
step.
If the ASP.NET version displayed is blank or earlier than 2.0.5nnnn and you
cannot select the correct entry (the field is protected), you cannot continue with
this procedure. To recover, ensure that you installed IBM Datacap Taskmaster
Capture:
o If you did not, begin this process over again with the correct version of the IBM
Datacap Taskmaster Capture software.
o If you did, refer to Chapter 2 Installation and Configuration Prerequisites and
follow the instructions to Run aspnet_regiis.exe to update the ASP.NET
application script maps.
11 Click Apply to save any changes.
12 Click the HTTP Headers tab to display it.
13 Select the Enable Content Expiration option to activate the expiration fields.
14 Select the Expire Immediately option, then click Apply to save the change and then OK
to close the TaskRun Properties dialog. The Internet Information Services window is
redisplayed – the TaskRun folder's icon has changed.
Confirm Server.INI Points to TaskRun
This procedure provides instructions on how to ensure that the Server.ini file contains the
correct value for the setting that Taskmaster Web uses to locate the TaskRun folder.
1 On the WebServer, start Windows Explorer, navigate to and use a text editor such as
Notepad to open the C:\Datacap\tmweb.net\server.ini file.
2 The server.ini’s TempFolder= setting should be set to TempFolder=/TaskRun/ (folder
name is case-sensitive) and if it is not, change it, save it, and close the file.
Change SSL Setting in Server.INI
If you are using Secure Socket Layer to encrypt communications between Taskmaster Web
and Taskmaster Web Clients, this procedure provides instructions on how to change the value
of the SSL setting in the Server.ini file that controls Taskmaster Web's SSL behavior.
2 Change the server.ini’s UseSSL=0 setting to UseSSL=1, save it, and close the file.


example:

Restart Internet Information Services (IIS)
After you set the location of the datacap.xml file on a web server, restart Internet Information
Services (IIS).

Install and Configure Taskmaster Web on IIS 7 Web Server

This section provides the information you need to install and configure Taskmaster Web on a
Windows 2008, IIS 7 or 7.5 server (referred to as "WebServer") so you can use the browser-
based Taskmaster Web Client for processing.
opens. Click Yes.
2 When the Status:
On Windows 7:
opens.
displayed.
On Windows 2008:
are displayed.

2008.
installed.
Set Taskmaster Web Sharing Permissions for Datacap Folder (Windows 2008)
This procedure provides instructions on how to set up the appropriate Taskmaster Web sharing
permissions for the C:\Datacap folder when the Taskmaster Server's operating system is
Windows 2008.
displayed.
5 Add the Taskmaster Web domain/Windows account and set to allow Read.
Set Up Security for Taskmaster Web on Datacap Folder (Windows 2008)
displayed.


3 Add/ensure the Taskmaster Web domain/Windows account is set to allow Read &
Execute.
Add or Ensure Upload Limit Setting is Large Enough in web.config
Client, you should adjust the upload limit setting found in the web.config file.
This procedure provides instructions on how to locate and change the setting in the web.config
file that affects upload speed.
C:\Datacap\tmweb.net folder, scroll down to the web.config file and open it in a text
editor such as Notepad.
2 Within the <system.web> element, locate or add the
3 Depending on the usual size of the images that are being uploaded, you can increase the
size, for example:
Install Taskmaster Web on WebServer
InstallShield Wizard to install the Taskmaster Web component.
WARNINGS
Machine.
the Setup.exe.

Allow.
it.
8 Exclude all components from the installation process except Taskmaster Web.
Create Taskmaster Web Site
This procedure provides instructions on how to create the Taskmaster Web site using the
Taskmaster Web Server Configuration tool when the operating system is Windows 2008.
1 From the WebServer's Windows Start menu, select All Programs, select Datacap, select
Support, select Web Configuration, then select Taskmaster Web Server Configuration.
An information box is displayed.
2 When one or more of the items listed in the information box are Not Found, click OK,
then follow the instructions to Ensure Required IIS Components are Installed before
running the tool again.
3 When all of the items listed in the information box are Found, click OK. The
Taskmaster Web Server Configuration window opens. Note the Alias that is assigned,
as this is part of the URL you will use to test Internet Explorer's access to this site.
5 Click OK, then click Exit. The Taskmaster Web site has been created.
6 To view the web site in IIS Manager, from the Windows Start menu, select Control
Panel, select Administrative Tools, then double-click Internet Information Services
(IIS) Manager. The Internet Information Services (IIS) Manager window opens.
7 Expand the computer, Sites, and the Default Web Site. The TaskRun folder and
tmweb.net site are displayed. If they are not displayed, right-click the Default Web Site
and select Refresh.
8 In the Connections pane, select the Default Web Site.

9 In the Actions pane, under Manage Web Site, click Restart.

Set Taskmaster Web Application Pool Identity (IIS 7)
This procedure provides instructions on how to set the Application Pool Identity that
Taskmaster Web uses to access Taskmaster.
displayed.
7 Enter the Taskmaster Web Windows account information in the format:
accountname@domain.com, enter the account's password twice, then click OK. The
Credentials window closes and the Application Pool Identity window is displayed.
8 Click OK. The Application Pool Defaults window is displayed.
9 Click OK. The Internet Information Services window is displayed.
Web Site.
Set Up Web Sharing and Security Settings on TaskRun Folder (Windows 2008)
This procedure provides instructions on how to share the TaskRun processing folder on the
WebServer that is required by Taskmaster Web. This folder is where batches temporarily
reside while they are being processed.
1 On the WebServer, start Windows Explorer, navigate to C:\Datacap, right-click the
TaskRun folder, and select Properties from the shortcut menu. The TaskRun Properties
2 Click the Web Sharing tab to display it.
3 Select the Share this folder option. The Edit Alias dialog opens displaying the folder
name in the Alias field.
4 In the Application permissions group box, select the None option, and in the Access
permissions group box, select Write in addition to the Read option, then click OK. The
Web Sharing tab reappears with TaskRun displayed as an alias.
5 Click Apply to save your changes.
7 Add NETWORK SERVICE and local IUSR and set both to allow Modify.
8 Click OK to close the TaskRun Properties dialog.

Set IIS ASP Request Size Limit (Windows 2008)

Client to the WebServer, you should adjust the default Maximum Requesting Entity Body
Limit (maxRequestEntityAllowed).
This procedure provides instructions on how to locate and change the Maximum Requesting
Entity Body Limit when the operating system is Windows 2008.
Panel Home window, click System and Maintenance. The System and Maintenance
window opens.
2 Click Administrative Tools. The Administrative Tools window opens.
3 Double-click Internet Information Services.
When UAC is on, the User Account Control window opens. Click Continue.
The Internet Information Services (IIS) Manager window opens.
4 In the Connections pane, select the WebServer. The WebServer’s Home pane is
displayed.
5 In the Home pane, scroll down to the IIS area and double-click ASP.
If ASP is not displayed, ensure it was installed, then restart IIS and the ASP icon should
be displayed.
The ASP properties pane is displayed.
6 In the Behavior section, expand Limits Properties. Additional properties are displayed.
7 Locate Maximum Requesting Entity Body Limit (maxRequestEntityAllowed), change
the value (expressed in number of bytes) to reflect the appropriate size; for example,
from 200000 (200 kb) to 10238976 (10MB), then tab out. The Apply button in the
Actions pane is enabled.
8 In the Actions pane, click Apply. A message box indicates the change was saved.
9 Close the Internet Information Services (IIS) Manager window.
Confirm Server.INI Points to TaskRun
This procedure provides instructions on how to ensure that the Server.ini file contains the
correct value for the setting that Taskmaster Web uses to locate the TaskRun folder.
2 The server.ini’s TempFolder= setting should be set to TempFolder=/TaskRun/ (folder
name is case-sensitive) and if it is not, change it, save it, and close the file.
Change SSL Setting in Server.INI
If you are using Secure Socket Layer to encrypt communications between Taskmaster Web
and Taskmaster Web Clients, this procedure provides instructions on how to change the value
of the SSL setting in the Server.ini file that controls Taskmaster Web's SSL behavior.
2 Change the server.ini’s UseSSL=0 setting to UseSSL=1, save it, and close the file.


example:

Services (IIS).
opens. Click Yes.
2 When the Status:

Configure and Test Remote Workstation

This section provides the instructions you need to configure a "thin client" workstation, that is,
a remote workstation that uses Internet Explorer to access Taskmaster Web. You need to
know your Taskmaster Web URL before you can configure a remote workstation.
There are two ways to configure a remote workstation:
1 You can package the Taskmaster Web Client Configuration tool, then send the package
to the end user and have the end user run the tool to configure Internet Explorer.
To package the Taskmaster Web Client Configuration tool, follow the instructions in
Package the Client Configuration Tool.
To run the Client Configuration Tool, follow the instructions in Add TMWeb.net
Address as Trusted Site and Configure and Test internet Explorer 6, 7 or 8
2 The end user can configure Internet Explorer manually. Provide the end user with the
following instructions:
Configure Internet Explorer 6, 7 or 8 Manually
Test Internet Explorer
Package the Client Configuration Tool
This procedure provides instructions on how to package the Taskmaster Web Client
Configuration tool for use by an end user. The package you create allows an end user to
configure Internet Explorer on a remote workstation so it can access Taskmaster Web.
1 On any machine on which Taskmaster software is installed, open Windows Explorer,
navigate to and open the C:\Datacap\support\WebConfiguration folder.
2 Make a backup copy of the WebClientConfig.exe.config file.
3 With a text editor like Notepad, open the WebClientConfig.exe.config file.
4 Locate the line containing:
<value>http://localhost/tmweb.net</value>
and change "localhost" to the URL of your WebServer.

5 Save and close the WebClientConfig.exe.config file.
6 Send the following three files to your end user: WebClientConfig.exe.config,
Datacap.Config.dll, and WebClientConfig.exe along with the instructions in Add
TMWeb.net Address as Trusted Site and Configure and Test Internet Explorer 6, 7 or 8
This procedure provides instructions on how to add the TMWeb.net address as a Trusted Site
to prevent Internet Explorer from blocking access.
the default webserver address (http://localhost) in the Add this website to the zone field,


When you are running Internet Explorer from a different machine, enter either the
WebServer's IP address or name (http://WebServerName) in the Add this website to the
zone field, then click Add. The URL is added to the bottom pane
Configure and Test Internet Explorer 6, 7 or 8 using Tool
This procedure provides instructions on how to run the Taskmaster Web Client Configuration
tool to set up Internet Explorer 6, 7 or 8 so you can use the Taskmaster Web Client for
processing. It also provides instructions on how to test your configuration of Internet Explorer.
NOTE
When the operating system of the machine on which you want to run Internet Explorer to
access Taskmaster Web is a 64-bit operating system, you must use the 32-bit version of
Internet Explorer to access Taskmaster Web.
Additionally, on a Windows 2008 server, when the Internet Explorer Enhanced Security
Configuration for Users is ON, you cannot use Internet Explorer on the Server to access
Taskmaster Web, you must access Taskmaster Web from a different machine.
1 From the Windows Start menu, select All Programs, select Datacap, select Support,
select Web Configuration, then select Taskmaster Web Client Configuration.
The Taskmaster Web Client Configuration window is displayed.
2 When you are running the Taskmaster Web Client Configuration tool on the same
machine as Taskmaster Web, use the default URL that is displayed
(http://localhost/tmweb.net).
When you are running the Taskmaster Web Client Configuration tool from a machine
other than the machine on which Taskmaster Web is installed, enter or ensure the URL
is the WebServer's IP address or name (http://WebServerName/tmweb.net)
4 Click OK, then click Exit.
WebServer's IP address or name, followed by the tmweb.net virtual directory and the
test page (http://WebServerName/tmweb.net/ietest.aspx), then press <Enter>.

Configure Internet Explorer 6, 7 or 8 Manually

This procedure provides instructions on how to configure Internet Explorer 6, 7 or 8 manually
so it can communicate with Taskmaster Web. You must configure Internet Explorer on each
Workstation that will run Taskmaster Web Client.
1 Start Internet Explorer 6, 7 or 8 and display any web page.
5 Clear the Require server verification option.
the default server address (http://localhost) in the Add this website to the zone field,
WebServer's IP address or name (http://ServerName) in the Add this website to the
zone field, then click Add. The URL is added to the bottom pane.
8 On the Security tab, click the Custom level button. The Security Settings dialog
appears.
9 Scroll down until the ActiveX controls and plug-ins settings are displayed.
10 The following settings should be Enabled – if an option is not enabled, select its Enable
option :
Download signed ActiveX controls
Download unsigned ActiveX controls
Initialize and script ActiveX controls not marked as safe for scripting
11 Scroll down until the Miscellaneous setting are displayed.
12 Enable (or ensure it is enabled), the Include local directory path when uploading files to
a server option.
13 Click OK. A warning is displayed, asking you to confirm your changes.
14 Click Yes. The Internet Options dialog reappears with the Security tab on top.
15 Click OK to close the Internet Options dialog.
Test Internet Explorer
This procedure provides instructions on how to test your configuration of Internet Explorer 6,
7 or 8.
WebServer's IP address or name, followed by the tmweb.net virtual directory and the
test page (http://WebServerName/tmweb.net/ietest.aspx), then press <Enter>.


Run Taskmaster Web Client APT Application
Taskmaster Web Client APT Application

foundation Taskmaster Web Client APT application “out of the box.”
These instructions involve starting the Taskmaster Server Service, starting the Taskmaster
Web Client, and running the default browser-based tasks to process pre-scanned images.
Overview of Taskmaster Web Client APT

Web Client APT are as follows:

Scan Process sample, pre-scanned images.
Upload Move scanned images to the Taskmaster Server Service for
further processing
Verify Perform data validation.
NOTE
To complete processing, the APT Batch Profiler and Export tasks must be run manually
from the Taskmaster Client APT (thick client). In a client-server environment, the APT
Batch Profiler and Export tasks can be run automatically as background tasks by either the
Taskmaster Client Service or Rulerunner Quattro.

opens. Click Yes.
2 When the Status:

Access Taskmaster Web Login Page and Login

This procedure provides instructions on how to login to the Taskmaster Web Client APT
application using Internet Explorer.
1 Open Internet Explorer, and enter the IP address of the Taskmaster WebServer followed
by the alias for the website (for example: http://127.0.0.1/tmweb.net,
http://WebServerName/tmweb.net, or https://WebServerName/tmweb.net). After a
pause, the IBM Datacap Taskmaster Capture Login window is displayed.
NOTE: You may have to turn off Internet Explorer’s popup blocker the first time you
display the Login page.
2 On the Taskmaster Web Login Page, enter the following:
Field Value
Application APT
User ID admin
Password admin
Station remote
3 Click Login. The APT Taskmaster Web Client main window opens with the Operations
pane and Available shortcuts displayed.
Run Taskmaster Web Client APT Scan Task

This procedure provides instructions on how to run the Taskmaster Web Client APT virtual
scan task and begin processing the sample invoices.
1 In Internet Explorer, on the Operations tab, click the Scan shortcut. The list of available
jobs is displayed.
2 Click the Web Demo shortcut. The Web Demo Scan page is displayed. The batch
number assigned to this batch of documents is located in the upper left of the page. By
default, the Multiple files option is selected.
3 The Scan Into path in the lower right of the page indicates the location into which the
pre-scanned images are temporarily placed. If you do not have permission to write to
this location, change this path to one to which you can write.
4 Click Browse, navigate to the folder where the pre-scanned images are located - the
default location is in the application folder (\Datacap\APT\images\input), select the first
one, then click Open. The Web Demo Scan page is redisplayed with the path to the
Source folder.
5 If you don't want to process all of the sample invoices (five single-page invoices and
one two-page invoice), change the number in the Expected pages field to the number of
images (not documents) you want to process, then click Scan. A window indicates that
scanning is taking place. The pages are scanned, images of the pages are displayed, the
batch-specific name of the folder is appended to the Scan Into path and an End of scan
message is displayed.


7 The following table describes some of the things you can do on the Web Demo Scan
dialog:
To Do This
Change sequence of pages Select either the image in the left pane, or the
name of the image in the right page that you
want to move, then click either the MoveUp
or MoveDown arrow
Delete all pages Click Remove All
Delete a single page Select the image you want to delete, then click
Remove
Enlarge scanned images Click Zoom in
Shrink scanned images Click Zoom out
Rotate an image Click Rotate 900
Complete the Scan Task processing Click Done
of the batch
Cancel the Scan Task processing of Click Cancel
the batch; deletes batch and all batch
data from system
Put the batch on hold and end Click Hold
processing of the batch; batch
remains available to same user
8 After all images have been scanned, click Done. A message box is displayed indicating
the Batch finished with a status of finished.
11 When the Scan task finishes successfully, the source images have been collected into a
batch and copied to the batch’s uniquely-numbered folder found in the Scan Into folder.
now Web Demo, Upload, pending.
Run Taskmaster Web Client APT Upload Task

This procedure provides instructions on how to run the Taskmaster Web Client APT upload
task.
1 In Internet Explorer, on the Operations tab, click the Upload shortcut. The Upload
window opens and A transferring the batch to server message is displayed briefly, then
closes. A message box is displayed indicating the batch has finished with a status of
finished.


4 When the Upload task finishes successfully, the scanned images have been moved to
the batch’s uniquely-numbered folder found in \Datacap\APT\batches and ivscan and
upload xml files have been created.
now Web Demo, Batch Profiler, pending.
6 The next task, the APT Batch Profiler task, must be run manually from the Taskmaster
Client APT (thick client).

displayed.
opens.
Run Taskmaster Client APT Batch Profiler Task (Background Shortcut)

This procedure provides instructions on how to run the Taskmaster Client APT Batch Profiler
task.
1 On the DevWorkstation, in the Operations pane, double-click the Background shortcut.
A Task Monitor window opens and a Rulerunner window opens displaying a progress
bar, then they both close. This may take a few minutes, as Rulerunner is running a
number of processing-intensive modules, including PageID, ImageFix, CreateDocs,
Recognize, FindFingerprint, Locate, lookups, and others. When processing is complete,
a message box is displayed indicating the task has finished.
When the Batch Profiler task finishes successfully, the images have been organized into
page XML files have been created, along with a BatchProfiler.xml file in the batch's
uniquely-numbered folder in \APT\batches.
updated and are now Demo-FlexID.Verify and pending.

Run Taskmaster Web Client APT Verify Task

This procedure provides instructions on how to run the Taskmaster Web Client APT Verify
task.
1 In Internet Explorer, on the Operations tab, click the Verify shortcut. The verification
panel opens with the first image displayed.
2 The following table describes some of the things you can do on the verification panel:
To Do This
Move to the next low confidence Click Next LC
character
Lookup and select vendor (either Enter at least the first character of the
when blank or when incorrect vendor vendor's name and the Remittance_Zip,
is displayed) then click the Vendor link above the
Vendor Name snippet to open the lookup
window
Fill empty field with data using Click Click in the empty data entry field, then
N Key do one of the following:
Point at the field value on the image and
click it, or,
Click and drag the mouse to draw a
rectangular box around the existing field
data on the image
Complete processing of image and Click Submit
display next image
Mark the document for deletion, Select appropriate choice from Routing
rescanning, or review Instructions dropdown list
Display the first page of the next Click Next Page
document in the batch without
submitting or revalidating data
Display the first page of the previous Click Previous Page
document in the batch without
submitting or revalidating data
Display the first page, next page, Click Page No |<
previous page, or last page of the >
current document <
or >|
Display the details of the first line Click Lineitem |<
item, next line item, previous line >
item or last line item <
or >|

To Do This
For all detail lines, locate all field Click Find Details
values for all fields
Calculate missing numeric values Click Calculate Blank
using existing values and
automatically fill blank numeric
fields
Move to the next problem document Click Next Problem
in the batch
Move to the previous problem Click Previous Problem
Identify the type of invoice Select from Invoice Type dropdown list
Display snippet associated with a Select Disp snip
field
Create new fingerprint for this Select Yes from Add New Fingerprint
invoice dropdown list
Put entire batch on hold Click Hold
Override an error Select Override
Zoom in or out, resize the image Right-click on the image and select the
appropriate action
3 When you have finished with the last document and click Submit, a message box is
displayed indicating all documents are complete and you are prompted to finish the
batch.
4 Click OK. The message box closes and another message box is displayed indicating the
task on the batch has finished with a status of finished.
\Datacap\APT\batches.
now Web Demo, Export, pending.
9 The next and last task, the APT Export task, must be run manually from the Taskmaster
Client APT (thick client).
Run Taskmaster Client APT Export Task (Export Shortcut)

This procedure provides instructions on how to run the Taskmaster Client APT Export task.

1 On the DevWorkstation, in the Operations pane, double-click the Export shortcut. A

then they both close. A message box is displayed indicating that the Export task
finished.
When the Export task finishes successfully:
• Export outputs the field data to XML files. The XML files and the image files
are now ready to be input into a back-end application.
• An Export XML file has been added to the batch’s uniquely-numbered folder
found in \APT\batches.
• Export saves information about unknown invoices that were successfully
validated (creates new fingerprints) so that the next time Taskmaster APT “sees”
the same invoice, it can identify the vendor and extract the field data using a
process called Intellocate.
• If during Verify, you marked an invoice for review or rescan, or deleted an
invoice and you did not configure email notifications, the PDFs of the marked or
deleted images stay in the batch's uniquely-numbered folder in \APT\batches; the
images and information about the images are not exported. If you configured
Taskmaster APT to send email notifications when invoices are marked or
deleted, Export also sends the appropriate emails with the marked or deleted
image attached as a PDF file.
updated and are now Demo-FlexID.Export and Job Done.
4 Use Windows Explorer to navigate to and open the resulting PDFs (one for each
invoice), and you can open the Export.xml file to view the data captured from the
invoices.

View RV2 Reports for Taskmaster Web APT
Log Onto RV2

This procedure provides instructions on how to access and log into RV2.
http://WebServer/RV2/Login.aspx



Install and Configure Rulerunner Quattro
Introduction to Rulerunner Quattro

Quattro uses virtualization to take advantage of multiprocessor systems. Each virtual
recognition machine (VRM) in a multi-threaded configuration of Quattro processes rules on a
batch of documents as if it were a standalone copy of Rulerunner on its own computer.
Multiple thread configurations of Quattro support simultaneous VRMs on a single
multiprocessor or multi-core equipped computer. Quattro completes your work faster by
taking full advantage of your hardware investment.
With Rulerunner Quattro you can:
• Complete your document processing work faster. Faster turn-around of documents such as
claims, contracts, tax returns and invoices improves responsiveness and shortens capture
cycle times.
• Reduce the number of physical computers dedicated to the capture process. One multi-core
computer can effectively replace and cost less than multiple single-processor computers,
thereby delivering a server-room/IT "friendly" solution.
• Reduce total cost of ownership by improving utilization of existing IT assets and IT staff
efficiency. The small hardware and software footprint of Quattro is less expensive than
alternative virtualization solutions.
Quattro Configuration Assumptions
This portion of the Installation and Configuration Guide provides the information you need in
order to install, configure, and run Taskmaster tasks using Rulerunner Quattro (Quattro) in a
IBM Datacap Taskmaster Capture environment.
The instructions assume that all applications that you want Quattro to process have already
been installed, configured, and run successfully using Taskmaster Client. The instructions also
assume you have one or more separate servers (QServer) on which you will install Quattro.
Before you begin installing Rulerunner Quattro, ensure:
• You have a working IBM Datacap Taskmaster Capture 8.0.1 or later client/server
environment.
• At a minimum, ensure Taskmaster runs correctly in a client/server environment where the
application files are located on the Taskmaster Server and the application runs correctly from
a Workstation. This makes troubleshooting easier, and narrows down the sources of
potential problems.
• If you want Rulerunner Quattro to run tasks from two IBM Datacap Taskmaster Capture
applications, ensure you have a second working application with which you have processed
batches from start to finish successfully using Taskmaster Client.

• When installing on client and server machines, ensure you have administrator access to all
machines on which IBM Datacap Taskmaster Capture software is installed and to the
Windows 2003 or Windows 2008 server(s) on which you will install Rulerunner Quattro.
Overview of Quattro Installation in Client-Server Environment
This section provides an overview of the steps required to install and configure the Datacap
Quattro Control Service (DQCS) which starts and stops Rulerunner Quattro, and Rulerunner
Quattro (Quattro) on one or more servers (QServers) that are separate from the Taskmaster
Server (Server), as well as the steps required to configure Quattro to run tasks from a single or
multiple IBM Datacap Taskmaster Capture applications on multiple threads.
Depending on the way you want to authenticate Rulerunner Quattro, instructions are provided
for authenticating using either Taskmaster Authentication or Windows Authentication.
Multiple Servers
When installing Quattro on more than one server, repeat the instructions for each QServer (see
Install and Configure Rulerunner Quattro on Windows 2003 Server or Install and Configure
Rulerunner Quattro on Windows 2008 Server).
Multiple Applications
When configuring Quattro to run tasks from more than one application, repeat the instructions
for setting up an application in the section titled Configure Quattro to Run Your Applications.
Multiple Workflows
When configuring Quattro to run tasks from multiple workflows, configure each workflow as
if it is its own application using the instructions for setting up an application in the section
titled Configure Quattro to Run Your Applications.
The installation of Datacap Quattro Control Service and Rulerunner Quattro in a client-server
environment is made up of the following steps:
2 Ensure you can run all of your applications' tasks manually before beginning this
installation process.
3 Determine which IBM Datacap Taskmaster Capture tasks from which application(s)
you want Quattro to process.
4 Decide whether you want to use IBM Datacap Taskmaster Capture Authentication or
Windows Authentication, then create or ensure one Windows/domain account exists for
Quattro (a separate account for each instance of Quattro), and follow the setup steps for
your Taskmaster application(s) relevant to the type of authentication you have chosen.
5 Configure Quattro permissions on the Taskmaster Server.
6 Install Rulerunner Quattro on QServer.
7 Install all IBM Datacap Taskmaster Capture Options that are required by the tasks that
Quattro will run, on each QServer.
8 Set the location of the datacap.xml file, and update the Taskmaster Application Service
with the appropriate Task profile names.
9 Complete Quattro authentication setup.

10 Configure DQCS/Quattro account and permissions on QServer.

Configuring Rulerunner Quattro to process specific application tasks involves the following
steps:
1 Configure Quattro to run the appropriate applications and tasks.
2 Configure Quattro security permissions on application folders on Server.
3 Create batches with your application's Taskmaster Client.
4 Start DQCS/Quattro on QServer.
5 Monitor Quattro processing.
6 Set up Quattro restarts.
7 Restart previously-running IBM Datacap Taskmaster Capture software.

Configure Rulerunner Quattro Authentication

When you use Rulerunner Quattro to run IBM Datacap Taskmaster Capture tasks, each
instance of Quattro must be authenticated as a valid Taskmaster user. You can perform this
authentication using either Taskmaster Authentication or Windows Authentication.
Use Windows Authentication
Quattro can be authenticated using either Windows Authentication or Taskmaster
Authentication.
This section provides the information you need to prepare for having Quattro use Windows
Authentication. This includes:
• Create or ensure a domain exists that you can use for Taskmaster-related accounts
• Create or ensure a Taskmaster-specific Active Directory (AD) or Lightweight Directory
Access Protocol (LDAP or LLLDAP) security group exists for the domain
• Create or ensure a domain/Windows account exists for each instance of Quattro and all are
part of the Taskmaster-specific AD/LDAP security group
• Configure Taskmaster Server Service to use Windows Authentication
• Add a Group (for the AD/LDAP security group) and Station IDs (for each QServer) to your
Taskmaster application
• For LLLDAP, add a User, Group, and Station ID for each instance of Quattro
Later, after installing the service, you will ensure Quattro is configured to use Windows
Authentication and grant the Quattro domain/Windows account(s) sharing and security
permissions to the appropriate Datacap folders.
Create or Ensure Domain Exists (Quattro)
When using Windows Authentication, the Rulerunner Quattro must have access to a domain
controller.
Create or ensure a domain exists in which a Taskmaster-specific Active Directory (AD) or
Lightweight Directory Access Protocol (LDAP or LLLDAP) security group can be created.
Ensure you know the exact spelling of the domain, as you will need it when you configure
Taskmaster to use Windows Authentication.
Create or Ensure Security Group Exists (Quattro)
The Rulerunner Quattro domain/Windows account must be part of a Taskmaster-specific
Active Directory (AD) or Lightweight Directory Access Protocol (LDAP or LLLDAP)
security group when using Windows Authentication.
Create or ensure a Taskmaster-specific Active Directory (AD) or Lightweight Directory
Access Protocol (LDAP or LLLDAP) security group is part of the domain.
Ensure you know the exact spelling of the security group, as you will need it when you
configure Taskmaster to use Windows Authentication.
Create or Ensure Quattro Account Exists
Create or ensure a domain/Windows account exists for each instance of Rulerunner Quattro.
When you are using Windows Authentication, ensure the Quattro account(s) are part of the
Taskmaster-specific AD , LDAP, or LLLDAP security group.

When you are using Taskmaster Authentication, there is no requirement to add the Quattro
account(s) to a security group.
Configure Taskmaster to use Windows Authentication
Skip this procedure if Rulerunner Quattro is using Taskmaster Authentication to log into
Taskmaster.
This section provides the information you need to configure Taskmaster to use Windows
Authentication in a Quattro environment, including:
• Shut down other Taskmaster software
• Configure Taskmaster Server Service to use Windows Authentication
• Add a Group to the Taskmaster application that has the exact same name as the AD/LDAP
security group and domain
• Add one or more Stations to the Taskmaster application that have the same names as the
QServers hosting Rulerunner Quattro
• When using LLLDAP, also add a User to the Taskmaster application that has the same name
as the Quattro domain/Windows account
Make a Note of and Shut Down Taskmaster Client and Web Software
Before beginning the installation and configuration process, we recommend identifying the
machines on which Taskmaster Client or Taskmaster Web software is running (so you can start
it back up after installing Rulerunner Quattro successfully), and shutting down client and web
software on machines in the following sequence:
1 Taskmaster Client software (including Taskmaster Client, Taskmaster Web Client,
Taskmaster Client Service, Datacap Studio, Batch Pilot, etc.).
etc.).
Configure Taskmaster Server Service to use Windows Authentication
Taskmaster.
This procedure provides instructions on how to open the Taskmaster Server Manager,
configure Taskmaster Server Service to use Windows Authentication, and restart Taskmaster
Server Service.
1 From the Server's Windows Start menu, select All Programs, select Datacap, select
Taskmaster Server, and click Taskmaster Server Manager. The Taskmaster Server
2 When the Status:
4 Click Show advanced to display Advanced Settings. The button label changes to Hide
advanced.

5 In the Authentication system field, select the type of authentication you want to use.
The Authentication path template field is enabled, and the template string that is
displayed changes depending on your selection.
6 Enter the appropriate string in the Authentication path template field. For:
ADSI authentication, enter:
WinNT://<%domain%>/<%user%>
LDAP authentication, enter:
LDAP://<%domain%>.com
LLLDAP authentication, enter:
<%server%>:<%port%>/uid=<%user%>,dc=<%domain%>,dc=Com
then click Save.
8 Click Start to start Taskmaster Server Service. A Starting Service message is displayed.
The Status changes to Running when the service is started.
displayed.
opens.
Add Taskmaster Group to Application
This procedure provides instructions on how to add the required Taskmaster group to your
application for Quattro.
1 On the Workstation, with the application's main window open, on the Settings menu,
select Groups. The Taskmaster Administrator dialog opens with the Groups tab
displayed on top and the existing Groups listed in the left pane.
2 On the Groups tab, click Add, and enter a Group ID for the Rulerunner Quattro Service
that is a concatenation of:
--Your Taskmaster-specific security group name
--A dot
--The domain to which your Taskmaster-specific security group belongs.
For example, for a security group called TMUsers in the XYZ Company's domain, the
Taskmaster Group ID would be TMUsers.XYZ.
3 Click Apply. A message box indicates the new settings will apply after currently signed
on users log off and log back on again.
4 Click OK to close the message box. The Privileges, Permissions, and Users pane is
enabled.

5 Since you are using this group to grant privileges to Quattro, expand the Privileges
branch, expand the Client(s) branch, and select the Client(s) Taskmaster Sub privilege,
then click Apply. A message box indicates the new settings will apply after currently
signed on users log off and log back on again.
7 Since you are using this group to grant permissions to Quattro to process the APT Batch
Profiler and Export background tasks, expand the Permissions branch, select the Batch
Profiler and Export tasks in each job, then click Apply. A message box indicates the
new settings will apply after currently signed on users log off and log back on again.
Add Taskmaster Station to Application
This procedure provides instructions on how to add the required Taskmaster Station to your
IMPORTANT
Use the name of the QServer machine as the Station name. You must enter the QServer
machine name exactly as it has been identified to the Domain Controller (i.e. if the machine
name identified in the Domain Controller is in all capital letters, be sure to enter the machine
name here in all capitals).
and select Stations. The Taskmaster Administrator dialog opens with the Stations tab
displayed on top and the existing Stations listed in the left pane.
2 Click Add, and enter the name of the QServer machine (exactly as it has been identified
to the Domain Controller), then click Apply. A message box indicates the new settings
will apply after currently signed on users log off and log back on again.
4 Since you are using the QServer as the Station to run background jobs as Quattro,
expand the Permissions branch and select the Batch Profiler and Export tasks in each
job, then click Apply. A message box indicates the new settings will apply after
currently signed on users log off and log back on again.
6 Click the Advanced button to open the Virtual stations dialog box.
7 Set the Maximum number of virtual stations allowed to 99, then click OK. The Virtual
stations dialog box closes.
10 Click Done to close the Taskmaster Administrator dialog, then close your Taskmaster
application.

Add Taskmaster User to Application

This procedure provides instructions on how to add the required Taskmaster user to your
application for Quattro. This is applicable when you are using Taskmaster Authentication or
LLLDAP Windows Authentication.
select Users. The Taskmaster Administrator dialog opens with the Users tab displayed
on top and the existing Users listed in the left pane.
2 On the Users tab, click Add, and enter the User ID Rulerunner Quattro will use to log
into Taskmaster.
3 Click Set Password. The Change password for user window opens.
4 Enter the New password in both fields, and click OK.
enabled.
7 Since you are using this user to grant privileges to Quattro, expand the Privileges
9 Since you are using this user to grant permissions to Quattro to process Batch Profiler
and Export background tasks, expand the Permissions branch, select the Batch Profiler
and Export tasks in each job, then click Apply. A message box indicates the new
settings will apply after currently signed on users log off and log back on again.
11 Click Done. The Taskmaster Administrator dialog closes.

Use Taskmaster Authentication

Quattro can be authenticated using either Windows Authentication or Taskmaster
Authentication.
This section provides the information you need to prepare for having Quattro use Taskmaster
Authentication. This includes:
• Create or ensure a domain/Windows account exists for each instance of Quattro
• Add a User ID and Station ID to your Taskmaster application for each instance of Quattro
Later, after installing the service, you will configure Quattro to use Taskmaster Authentication
and will grant the Quattro domain/Windows account(s) sharing and security permissions to the
appropriate Datacap folders.
Create or Ensure Quattro Account Exists
Create or ensure a domain/Windows account exists for each instance of Rulerunner Quattro.
When you are using Windows Authentication, ensure the Quattro account(s) are part of the
Taskmaster-specific AD, LDAP, or LLLDAP security group.
When you are using Taskmaster Authentication, there is no requirement to add the Quattro
account(s) to a security group.
opens. Click Yes.
2 When the Status:
displayed.

opens.
Add Taskmaster User to Application
This procedure provides instructions on how to add the required Taskmaster user to your
application for Quattro. This is applicable when you are using Taskmaster Authentication or
LLLDAP Windows Authentication.
select Users. The Taskmaster Administrator dialog opens with the Users tab displayed
on top and the existing Users listed in the left pane.
2 On the Users tab, click Add, and enter the User ID Rulerunner Quattro will use to log
into Taskmaster.
3 Click Set Password. The Change password for user window opens.
4 Enter the New password in both fields, and click OK.
enabled.
7 Since you are using this user to grant privileges to Quattro, expand the Privileges
9 Since you are using this user to grant permissions to Quattro to process Batch Profiler
and Export background tasks, expand the Permissions branch, select the Batch Profiler
and Export tasks in each job, then click Apply. A message box indicates the new
11 Click Done. The Taskmaster Administrator dialog closes.
Add Taskmaster Station to Application
This procedure provides instructions on how to add the required Taskmaster Station to your
IMPORTANT
Use the name of the QServer machine as the Station name. You must enter the QServer
machine name exactly as it has been identified to the Domain Controller (i.e. if the machine
name identified in the Domain Controller is in all capital letters, be sure to enter the machine
name here in all capitals).

and select Stations. The Taskmaster Administrator dialog opens with the Stations tab
displayed on top and the existing Stations listed in the left pane.
2 Click Add, and enter the name of the QServer machine (exactly as it has been identified
to the Domain Controller), then click Apply. A message box indicates the new settings
4 Since you are using the QServer as the Station to run background jobs as Quattro,
expand the Permissions branch and select the Batch Profiler and Export tasks in each
job, then click Apply. A message box indicates the new settings will apply after
6 Click the Advanced button to open the Virtual stations dialog box.
7 Set the Maximum number of virtual stations allowed to 99, then click OK. The Virtual
stations dialog box closes.
10 Click Done to close the Taskmaster Administrator dialog, then close your Taskmaster
application.

Install and Configure Rulerunner Quattro on Windows 2003 Server

This section provides the information you need to install and configure the Datacap Quattro
Control Service and Rulerunner Quattro in an environment that already has IBM Datacap
Taskmaster Capture running successfully, where the Workstations ("DevWorkstation" or
"Workstation") and Taskmaster Server ("Server") are separate machines, and where you are
adding an additional server ("QServer") to host Quattro.
In this scenario:
• Windows 2003 Server hosts the Taskmaster Server, all application files, batch files, and
databases
• Windows 2003 QServer hosts Quattro
• Workstations host the thick client (Taskmaster Client software) and there is at least one
DevWorkstation on which the complete Taskmaster Client software component has been
installed
Before beginning the installation and configuration process, we recommend identifying which
Taskmaster software is running on each machine (so you can start it back up after installing
Rulerunner Quattro successfully), and shutting down all Taskmaster software on all machines
in the following sequence:
etc.).
3 Taskmaster Server Service.
Configure Quattro Permissions on Server (Windows 2003)
This section provides the information you need to set up sharing permissions and security on
the shared folder for the Rulerunner Quattro account(s) when the Taskmaster Server's
operating system is Windows 2003.
Set Sharing Permissions for Datacap Folder (Windows 2003)
the Rulerunner Quattro account(s) on the Taskmaster Server's shared C:\Datacap folder when
the Server's operating system is Windows 2003. Note that other accounts were already granted
sharing permissions during the installation and configuration of Taskmaster.
2 The folder should already be shared with the Share name of Datacap.
4 Add/ensure Domain/Windows User ID for Rulerunner Quattro is set to allow Full
Control.
5 Repeat the previous step for each Quattro account.

Set Up Security on Shared Folder (Windows 2003)

Rulerunner Quattro account(s) on the Taskmaster Server's shared C:\Datacap folder when the
Server's operating system is Windows 2003. Note that other accounts were already granted
security permissions during the installation and configuration of Taskmaster.
3 Add/ensure Domain/Windows User ID for Rulerunner Quattro is set to allow Read &
Execute.
Install Taskmaster Options on QServer
Each server (QServer) that is to host Rulerunner Quattro requires that the appropriate
Taskmaster Options be installed when Quattro runs tasks that use those options.
If the required Taskmaster Options have not yet been installed on each QServer, follow the
instructions provided with each option to install them.
Install Quattro on QServer (Windows 2003)
This procedure provides instructions on how to run the InstallShield Wizard to install the
Datacap Quattro Control Service and Rulerunner Quattro on a Windows 2003 Server
(QServer). The components you install include the Rulerunner (Quattro) component as well as
the separately licensed connectors for which you have a license.
If you have multiple QServers, repeat this process for each server.
1 Make the installation package available on your network, or insert the Taskmaster CD
in the machine's CD/DVD drive. If the installation process does not start automatically,
or if the package is on the network, open Windows Explorer, navigate to and double-
click the Setup.exe.
it.
8 Exclude all components from the installation process except Rulerunner, then expand
the Connectors software component and include the connectors for which you have a
license.


example:

Configure Quattro to Use Windows Authentication
Taskmaster.
This procedure provides instructions on how to set up Quattro so it uses Windows
Authentication to log into Taskmaster. Use this procedure to confirm that Windows
Authentication is in use, or to switch Quattro back to Windows Authentication after using
Taskmaster Authentication.
1 From the QServer's Start menu, select All Programs, select Datacap, select Taskmaster
Client, and click Rulerunner Quattro Manager. The Rulerunner Quattro Manager
window opens with the Datacap Quattro tab displayed on top.
2 Ensure the Datacap Quattro Control Service Status is Stopped.
If the Status displayed is Running, click Stop. The status will change to Stopped.
4 If the Windows Authentication option is not already selected, select it and click Save.
Configure Quattro to Use Taskmaster Authentication
Skip this section if Rulerunner Quattro is using Windows Authentication to log into
Taskmaster.
Configuring Quattro to use Taskmaster Authentication involves providing each instance of
Quattro with the Taskmaster User ID, Password, and Station ID to use when logging into

Taskmaster. Because Quattro stores the password in an encrypted form, first use the
SitManager.exe provided with Taskmaster to encrypt the password, then use the Rulerunner
Quattro Manager tool to set up Quattro's Taskmaster User ID, Password, and Station ID.
When setting up Quattro to use Taskmaster Authentication, Quattro requires that the password
be encrypted. Additionally, you may want to temporarily use Taskmaster Authentication to
make changes to Quattro's configuration which also requires an encrypted password.
This procedure provides instructions on how to use Taskmaster's SitManager.exe to create the
encrypted password string you need.
1 On the QServer, start Windows Explorer, navigate to and open the
3 Type in the password you want to encrypt (for example, the password for Quattro's User
ID) and click Encrypt. A string is displayed in the Encrypted String field.
Configure Quattro's Taskmaster Login Credentials
This procedure provides instructions on how to set up Rulerunner Quattro to use the
appropriate User ID, Password, and Station ID to log into Taskmaster when you are using
Taskmaster Authentication. This procedure assumes that you have encrypted the password
using Taskmaster's SitManager.exe and can paste the encrypted string during this procedure -
if not, follow the instructions in Encrypt Taskmaster Login Password before continuing with
this procedure.
Client, and click Rulerunner Quattro Manager.
Yes.
displayed on top.
4 Select the Taskmaster Authentication option, and enter Quattro's Taskmaster User ID,
the encrypted password, and Station ID, then click Save.

Configure Quattro Account and Permissions on QServer (Windows 2003)

This section provides the information you need to ensure that the domain/Windows account
used by each instance of DQCS/Quattro has the rights and permissions it needs on its host
(QServer). This includes: Providing the Quattro domain/Windows account with Administrator
privileges on its QServer, and granting that account the ability to log onto its QServer as a
service.
Add Quattro Account on QServer
If you have multiple QServers, set up a separate domain/Windows account for each QServer.
• Quattro's domain account must have administrative rights on its QServer. Add the Quattro
domain account to the QServer's Administrators group so that the account has local
administrator rights on the machine. This allows Quattro to access the Service Control
Manager to issue “stop service” requests when the Stop on Abort setting is enabled. This
also allows DQCS to access the Service Control Manager to issue scheduled stop and restart
requests.
• If your corporate policy restricts Administrators group privileges, or if your corporate policy
precludes granting administrator rights to the domain account, you must grant the account
permissions using DCOM Config.
On the QServer, in Administrative Tools > Component Services > Computers > My
Computer > DCOM Config, on the TaskMaster.RunTask Security tab, add and grant Local
Launch and Local Activation permissions to the domain account used by DQCS and
Quattro.
This procedure provides instructions on how to ensure the domain account used by an instance
of Quattro has been granted the Log On as a Service right on its QServer (this allows
Rulerunner Quattro to run as a service).
1 From the QServer's Windows Start menu, select Settings, select Control Panel, select
Administrative Tools, select Services, right-click Quattro and select Properties. The
3 Select This account, click the Browse button, select the Quattro domain account, enter
the domain account's password, and click Apply.
of DQCS (which starts and stops Rulerunner Quattro) has been granted the Log On as a
Service right on its QServer.
Administrative Tools, select Services, right-click Datacap Quattro Control Service and
select Properties. The Properties dialog opens with the General tab displayed on top.


the domain account's password, and click Apply. (This indicates the domain account
will run the DQCS which in turn runs Quattro.)
Service starts up automatically when its host machine is restarted. When the DQCS is started
automatically and its Restart service if stopped setting is enabled, the DQCS will automatically
restart Quattro after a reboot.
2 To start the DQCS automatically when the QServer is rebooted, change the Startup
Next Steps
After you have installed and configured Rulerunner Quattro in a working IBM Datacap
Taskmaster Capture environment, you are ready to configure Quattro to process one or more
tasks of an existing application.
• To configure Rulerunner Quattro to process tasks of an existing, working APT application,
continue with the section titled Configure and Run APT Tasks using Quattro.
• To configure Rulerunner Quattro to process tasks from one or more of your applications, use
the instructions in the section titled Configure Quattro to Run Your Applications.

Install and Configure Rulerunner Quattro on Windows 2008 Server

This section provides the information you need to install and configure the Datacap Quattro
Control Service and Rulerunner Quattro in an environment that already has IBM Datacap
Taskmaster Capture running successfully, where the Workstation and Server are separate
machines, and where you are adding one or more additional Servers (QServers) to host
Quattro.
In this scenario:
• Windows 2008 Server hosts the Taskmaster Server, all application files, batch files, and
databases
• Windows 2008 QServers host Quattro
• Workstations host the thick client (Taskmaster Client software) and there is at least one
DevWorkstation on which the complete Taskmaster Client software component has been
installed
Before beginning the installation and configuration process, we recommend identifying which
Taskmaster software is running on each machine (so you can start it back up after installing
Rulerunner Quattro successfully), and shutting down all Taskmaster software on all machines
in the following sequence:
etc.).
3 Taskmaster Server Service.
Configure Quattro Permissions on Server (Windows 2008)
This section provides the information you need to set up sharing permissions and security on
the shared folder for the Quattro account(s) when the Taskmaster Server's ("Server") operating
Set Sharing Permissions for Datacap Folder (Windows 2008)
the Rulerunner Quattro account(s) on the Taskmaster Server's shared C:\Datacap folder when
the Server's operating system is Windows 2008. Note that other accounts were already granted
folder and select Properties. The Datacap Properties dialog is displayed.
2 Click the Sharing tab to display it. The folder should already be shared with the Share
name of Datacap.

5 Add/ensure the Domain/Windows User ID of Quattro Service is set to allow Full

Control.
Set Up Security on Shared Folder (Windows 2008)
Rulerunner Quattro account(s) on the Taskmaster Server's shared C:\Datacap folder when the
operating system is Windows 2008. Note that other accounts were already granted security
permissions during the installation and configuration of Taskmaster.
folder and select Properties. The Properties dialog is displayed.
3 Add/ensure the Domain/Windows User ID of Quattro Service is set to allow Read &
Execute.
On Windows 7:
opens.
displayed.
On Windows 2008:
are displayed.

Install Taskmaster Options on QServer

Each server (QServer) that is to host Rulerunner Quattro requires that the appropriate
Taskmaster Options be installed when Quattro runs tasks that use those options.
If the required Taskmaster Options have not yet been installed on each QServer, follow the
Install Quattro on QServer (Windows 2008)
This procedure provides instructions on how to run the InstallShield Wizard to install the
Datacap Quattro Control Service and Rulerunner Quattro on a Rulerunner Quattro on a
Windows 2008 Server (QServer). The components you install include the Rulerunner
(Quattro) component as well as the separately licensed connectors for which you have a
license.
1 Make the Rulerunner Quattro installation package available on your network, or insert
the CD in the machine's CD/DVD drive. If the installation process does not start
automatically, or if the package is on the network, open Windows Explorer, navigate to
and double-click the Setup.exe.
it.
8 Exclude all components from the installation process except Rulerunner, then expand
the Connectors software component and include the connectors for which you have a
license.


example:

Taskmaster.
This procedure provides instructions on how to set up Quattro so it uses Windows
Authentication to log into Taskmaster. Use this procedure to confirm that Windows
Authentication is in use, or to switch Quattro back to Windows Authentication after using
Taskmaster Authentication.
4 If the Windows Authentication option is not already selected, select it and click Save.
Skip this section if Rulerunner Quattro is using Windows Authentication to log into
Taskmaster.
Configuring Quattro to use Taskmaster Authentication involves providing each instance of
Quattro with the Taskmaster User ID, Password, and Station ID to use when logging into
Taskmaster. Because Quattro stores the password in an encrypted form, first use the
SitManager.exe provided with Taskmaster to encrypt the password, then use the Rulerunner
Quattro Manager tool to set up Quattro's Taskmaster User ID, Password, and Station ID.


Configure Quattro's Taskmaster Login Credentials
This procedure provides instructions on how to set up Rulerunner Quattro to use the
appropriate User ID, Password, and Station ID to log into Taskmaster when you are using
Taskmaster Authentication. This procedure assumes that you have encrypted the password
using Taskmaster's SitManager.exe and can paste the encrypted string during this procedure -
if not, follow the instructions in Encrypt Taskmaster Login Password before continuing with
this procedure.
Yes.
displayed on top.
4 Select the Taskmaster Authentication option, and enter Quattro's Taskmaster User ID,
the encrypted password, and Station ID, then click Save.
Configure Quattro Account and Permissions on QServer (Windows 2008)
used by each instance of DQCS/Quattro has the rights and permissions it needs on its host
(QServer). This includes: Providing the Quattro domain/Windows account with Administrator
privileges on its QServer, and granting that account the ability to log onto the QServer as a
service.
Add Quattro Account on QServer
If you have multiple QServers, set up a separate domain/Windows account for each QServer.
• Quattro's domain account must have administrative rights on its QServer. Add the Quattro
domain account to the QServer's Administrators group so that the account has local
administrator rights on the machine. This allows Quattro to access the Service Control
Manager to issue “stop service” requests when the Stop on Abort setting is enabled. This
also allows DQCS to access the Service Control Manager to issue scheduled stop and restart
requests.

• If your corporate policy restricts Administrators group privileges, or if your corporate policy
precludes granting administrator rights to the domain account, you must grant the account
permissions using DCOM Config.
On the QServer, in Administrative Tools > Component Services > Computers > My
Computer > DCOM Config, on the TaskMaster.RunTask Security tab, add and grant Local
Launch and Local Activation permissions to the domain account used by DQCS and
Quattro.
of Quattro has been granted the Log On as a Service right on its QServer (this allows
Rulerunner Quattro to run as a service).
Administrative Tools, select Services, right-click Quattro and select Properties. The
the domain account's password, and click Apply.
of DQCS (which starts and stops Rulerunner Quattro) has been granted the Log On as a
Service right on its QServer.
the domain account's password, and click Apply. (This indicates the domain account
will run the DQCS which in turn runs Quattro.)
Service starts up automatically when its host machine is restarted. When the DQCS is started
automatically and its Restart service if stopped setting is enabled, the DQCS will automatically
restart Quattro after a reboot.

2 To start the DQCS automatically when the QServer is rebooted, change the Startup
Next Steps
After you have installed and configured Rulerunner Quattro in a working IBM Datacap
Taskmaster Capture environment, you are ready to configure Quattro to process one or more
tasks of an existing application.
• To configure Rulerunner Quattro to process tasks of an existing, working APT application,
continue with the section titled Configure and Run APT Tasks using Quattro.
• To configure Rulerunner Quattro to process tasks from one or more of your applications, use
the instructions in the section titled Configure Quattro to Run Your Applications.

Configure and Run APT Tasks using Quattro

This section provides the information you need to configure Rulerunner Quattro so Quattro
runs background tasks of an existing, working IBM Datacap Taskmaster Capture APT
application.
This section assumes you have a working version of the IBM Datacap Taskmaster Capture
APT foundation application, that you have followed the instructions in the section titled Install
and Configure Rulerunner Quattro on Windows 2003 Servers or Windows 2008 Servers in an
environment where the DevWorkstation, Server, and QServer are separate machines.
In this scenario:
• Server hosts the Taskmaster Server, all application files, batch files, and databases
• QServer hosts Rulerunner Quattro
• DevWorkstation hosts the complete Taskmaster Client software component (Taskmaster
Client, Datacap Studio, DotEdit, NENU)
For the Server and QServer, these instructions cover the Windows 2003 and Windows 2008
operating systems.
For the DevWorkstation, these instructions cover Windows 7.
Make a Note of and Shut Down Taskmaster Client and Web Software
Before beginning the installation and configuration process, we recommend identifying the
machines on which Taskmaster Client or Taskmaster Web software is running (so you can start
it back up after installing Rulerunner Quattro successfully), and shutting down client and web
software on machines in the following sequence:
etc.).
Set Up Security on Datacap\APT Folder
the Taskmaster Server's C:\Datacap\APT folder when the Server's operating system is
Windows 2003 or 2008. Note that other accounts were already granted security permissions
during the installation and configuration of Taskmaster.
1 On the Server, start Windows Explorer, navigate to and right-click the C:\Datacap\APT
folder and select Properties. The Properties dialog opens.
3 Add/ensure Domain/Windows User ID of Rulerunner Quattro is set to allow Full
Control.
Set Up Security on Datacap\RRS Folder
the Taskmaster Server's C:\Datacap\RRS folder when the Server's operating system is
during the installation and configuration of IBM Datacap Taskmaster Capture.

3 Add/ensure Domain/Windows User ID of the Rulerunner Quattro is set to allow Full
Control.
opens. Click Yes.
2 When the Status:
Obtain Task Profile Name
This procedure provides instructions on how to obtain the exact spelling of the task name and
the task profile's name. You need this information to update the Taskmaster Application
Service with the specific task profile or profiles that Quattro is to process.
select Taskmaster Client, log in, and open the application.
2 On the Settings menu, select Workflow. The Workflow tab is displayed.
3 Expand the job that contains the task, select the task, and make a note of the task name.
4 Click Setup. The task's Setup - Batch Profiler window opens with the task profile
highlighted.
5 Make a note of the task profile name.
6 On the File menu, select Quit to close the Setup window.
Configure Quattro's Task Profiles in the Taskmaster Application Service
the task profiles that Quattro should process.

Before you begin this task, you need to know which tasks and task profiles you want Quattro
to process, and you need the exact spelling of each task name and task profile name. Follow
the instructions in Obtain Task Profile Name before continuing with this procedure.
2 Select APT. Paths appear in the fields on the Application tab.
3 Ensure all paths are correct.
4 Click the Quattro tab to display it. This tab should only display the task profiles that
Quattro is to process.
8 Enter the name of the task in the first field, and enter the name of the task profile in the
second field, ensuring the spelling and case is the same as what was displayed in the
task's Setup - Batch Profiler window.
opens. Click Yes.
2 When the Status:

opens. Click Yes.

2 When the Status:

Configure Rulerunner Quattro to Run APT Tasks (Single thread)

Rulerunner Quattro APT-specific settings to reflect the appropriate Taskmaster Server,
application, and tasks that Quattro is to process on a single thread. When you configure
Quattro, your license determines the number of threads you can set up.
For more information on Rulerunner Quattro Manager, see Appendix D Rulerunner Quattro
Manager.
IMPORTANT
These instructions allow you to temporarily use Taskmaster Authentication and the default
Taskmaster Admin User ID and Password to make your configuration changes. Follow the
instructions in Encrypt Taskmaster Login Password to encrypt the password for the Admin
User ID before continuing with this procedure.
Disconnect.
7 If the right pane displays thread0 with APT's Demo job Batch Profiler and Export tasks,
Quattro has already been set up to process these tasks - skip to step 15. If the right pane
is empty, continue with the next step.
8 In the left pane, expand the APT application, expand the Servers node, then select the
server, the Taskmaster Admin database and the Taskmaster Engine database. The tree
expands to display the APT workflow, jobs and tasks.
thread0 is created.
10 In the left pane, in the expanded tree under APT, under the Demo job, click in the box
to the left of Batch Profiler, click the Batch Profiler label (to highlight it in blue) and
drag it onto thread0 in the right pane. The thread expands and displays the server, job,
and task names.
11 Repeat (click the box, click and drag the label) to drag the Demo job's Export task onto
thread0 in the right pane. The thread expands and displays the additional task name.

IMPORTANT
Complete the following steps to ensure Quattro's authentication credentials are set
properly.
17 When using:
• Windows Authentication - Select the Windows Authentication option
• Taskmaster Authentication - Select the Taskmaster Authentication option, enter
the User ID of Quattro's domain/Windows account, the encrypted version of
Quattro's password, and the name of the QServer as the Station ID
18 Click Save.

Configure Rulerunner Quattro to Run APT Tasks (Multi-thread)

Rulerunner Quattro APT-specific settings to reflect the appropriate Taskmaster Server,
application, threads and tasks that Quattro is to process. This configuration is a multi-thread
configuration. When you configure Quattro, your license determines the number of threads
you can set up.
In general, the number of threads should match the number of processors in the host machine;
for example, when Quattro is installed on a quad core server, enable four Quattro threads.
For more information on Rulerunner Quattro Manager, see Appendix D Rulerunner Quattro
Manager.
IMPORTANT
These instructions allow you to temporarily use Taskmaster Authentication and the default
Taskmaster Admin User ID and Password to make your configuration changes. Follow the
instructions in Encrypt Taskmaster Login Password to encrypt the password for the Admin
User ID before continuing with this procedure.
Disconnect.
7 If the right pane displays thread0 with APT's Demo job Batch Profiler task and thread1
with the Demo job Export task, Quattro has already been set up to process these tasks -
skip to step 16. If the right pane is empty, continue with the next step.
8 In the left pane, expand the APT application, expand the Servers node, then select the
server, the Taskmaster Admin database and the Taskmaster Engine database. The tree
expands to display the APT workflow, jobs and tasks.
thread0 is created.
10 Repeat the previous step to create the number of threads you need and to which you are
entitled. For the purposes of this example, create two threads.

11 In the left pane, in the expanded tree under APT, under the Demo job, click in the box
to the left of Batch Profiler, click the Batch Profiler label (to highlight it in blue) and
drag it onto thread0 in the right pane. The thread expands and displays the server, job,
and task names.
12 Repeat (click the box, click and drag the label) to drag the Demo job's Export task onto
thread1 in the right pane. The thread expands and displays the server, job, and task
names.
IMPORTANT
properly.
19 When using:
the User ID of Quattro's domain account, the encrypted version of Quattro's
password, and the name of the QServer as the Station ID
20 Click Save.
Run Taskmaster Client APT Tasks using Quattro
This section provides the information you need to stop and restart the Taskmaster Server
Service, start Taskmaster Client APT, create Taskmaster Client APT batches, start Rulerunner
Quattro, and monitor Quattro as it picks up and processes each batch.
Start Taskmaster Client Application
This procedure provides instructions on how to start the Taskmaster Client application. If you
have logged into the application's Taskmaster Client before, the information you entered
previously is displayed. If your Windows login information appears, replace it using the
information in this procedure.
select Applications, select the application you want to start and click its Client icon.
The Please login window opens.
2 Use the default Taskmaster Admin User ID, Password, and Station ID 1, then click OK.
The Taskmaster Client application's main window opens with the Operations pane
displayed.

Run Taskmaster Client APT Scan

This procedure provides instructions on running the Taskmaster Client APT Scan job to
process pre-scanned images. Use this procedure to start one or more at least four, ideally more
than four, batches so that when Quattro is running, batches are available for processing. there
are enough batches to engage all enabled threads.
1 With the DevWorkstation's Operations pane displayed, double-click the Scan shortcut,
select Demo, and click OK. A Task Monitor window opens and a Rulerunner window
opens displaying a progress bar, then they both close. A message box is displayed
indicating the task on the batch has finished with a status of finished.
2 Click Next Batch, then on the Select Job to start window, click OK. A Rulerunner
window opens displaying a progress bar, then they both close. A message box is
displayed indicating the task on the batch has finished with a status of finished.
3 Repeat step 2 to generate batches.
Start Quattro
Rulerunner Quattro.
displayed on top.
Monitor APT Batches during Quattro Processing
When you are running the Taskmaster Client APT application on a machine separate from the
QServer, there are a number of ways to monitor Quattro processing:
• In Taskmaster Client APT, open the Job Monitor pane and refresh the view periodically to
watch the changes to the batches' task and status
• In Windows Explorer, open the individual batch folders in APT\batches and refresh the
view periodically to watch the changes to the various files associated with each batch
• Turn on Quattro logging and review the logs
For troubleshooting information, see Appendix D: Rulerunner Quattro Manager, the section
titled Troubleshooting Quattro.
View Batches Processed by Quattro using Job Monitor
This procedure provides instructions on how to monitor Rulerunner Quattro's processing using
the Taskmaster Client Job Monitor pane.

1 On the Workstation, with the application’s main window open, on the View menu,
select Job Monitor. The Job Monitor pane opens with information about existing
batches displayed.
2 Press <F5> periodically to refresh the Job Monitor pane and see the changes to the
batch task and status as Quattro runs the task or tasks for each batch.
3 After Quattro has finished processing the Batch Profiler task for a batch, double-click
the batch in the Job Monitor pane to run the Taskmaster Client APT Verify task on that
batch.
4 After you have successfully completed the Verify task for a batch, it is ready for
Quattro to run the Export task.
5 Click the Job Monitor title bar, then press <F5> to refresh the pane.
6 After you have completed the Verify task for all of the pending batches, Quattro should
pick up and run them through the Export task.
7 Close the Job Monitor pane.
Set Up Quattro Restarts
When you are running Rulerunner Quattro in a production environment, Quattro should be
restarted periodically, typically every four hours, or as determined by experience. The option
that controls this behavior is the Restart Interval option on the Rulerunner Quattro Manager's
Advanced Settings tab.
Additionally, if you have configured Quattro to Stop on Abort (on the Rulerunner Quattro
Manager's Quattro Settings tab), it is a good idea to restart it automatically. The option that
controls this behavior is the Restart Service (or Restart Service if Stopped) option on the
This procedure assumes that you have encrypted the password associated with Quattro's User
ID using IBM Datacap Taskmaster Capture SitManager.exe and can paste the encrypted string

during this procedure - if not, follow the instructions in Encrypt Taskmaster Login Password
before continuing with this procedure.
This procedure provides instructions on how to ensure the Quattro restart options are
configured properly.
window opens.
2 If the Datacap Quattro Control Service Status displayed is Stopped, continue with the
next step.
credential fields.
5 Enter Quattro's User ID, paste in the encrypted Password, enter the appropriate Station
ID, then click Connect. The button label changes to Disconnect.
6 Click the Workflow:Job:Task tab to display it. APT is displayed in the left pane and
thread0 is displayed in the right pane.
7 On the Quattro Settings tab, select or ensure Stop on Abort is selected, then click Save.
8 On the Advanced Settings tab, select or ensure Restart Service is selected, and ensure
there is a value in the Restart Interval field (defaults to 14400 or four hours), then click
Save.
IMPORTANT
properly.
11 When using:
• IBM Datacap Taskmaster Capture Authentication - Select the IBM Datacap
Taskmaster Capture Authentication option, enter the User ID of Quattro's account,
the encrypted version of the password, and the name of the QServer as the Station
ID
12 Click Save.
13 If you want to start Quattro, click the Datacap Quattro tab, then click Start. The Status
changes to Running.
Restart Taskmaster Software
After successfully installing, configuring, and using Rulerunner Quattro to run additional
tasks, you can restart the IBM Datacap Taskmaster Capture software that was previously

running on other machines. Restart IBM Datacap Taskmaster Capture software on all
machines in the following sequence:
etc.)
Taskmaster Client Service, Datacap Studio, Batch Pilot, etc.)

Configure Quattro to Run Your Applications

This section provides the information you need to configure one or more instances of
Rulerunner Quattro to run background tasks from your own applications or workflows
(referred to here as MyApp1 and MyApp2).
This section assumes that you have:
• Working versions of your own IBM Datacap Taskmaster Capture applications, and that
you have manually run all of the tasks successfully
• Configured Taskmaster authentication by following the instructions in either Use
Windows Authentication or Use Taskmaster Authentication
• Installed Quattro following the instructions in Install and Configure Datacap Rulerunner
Quattro on Windows 2003 Servers or Windows 2008 Servers (depending on operating
system) in an environment where the Workstation(s), Server, and QServer(s) are separate
machines.
In this scenario:
• Server hosts the Taskmaster Server Service, the MyApp1 and MyApp2 application files,
batch files, and databases
• One or more QServers host Quattro
• One or more Workstations host Taskmaster Client software (MyApp1, MyApp2)
IMPORTANT
Datacap's standard actions, with the exception of "virtual scan" (vscan) actions, are "thread-
safe" meaning they can be used simultaneously in multiple threads in Quattro. Actions you
have changed or developed, or actions that Datacap sells separately as Options may not be
thread-safe. Tasks containing actions that are not known to be thread-safe should be
configured to run in only one thread. Generally VBScript code is thread-safe, but external
COM objects may not be. Scripting that accesses files or databases may not be thread-safe.
If Quattro fails when running a task in multiple threads, try configuring that task on a single
thread. When a task contains both thread-safe and non-thread-safe actions, you can split the
task into multiple tasks in order to isolate the non-thread-safe action so it can be run on a
single thread.
When you contact Support for help with such issues, be sure to mention any custom or
separately-purchased (option) actions in your applications.
Determine Which Taskmaster Tasks to Process

When you are ready to set up Rulerunner Quattro to run tasks from your own applications or
workflows, you will need to determine which tasks are suitable for Quattro processing.
Quattro runs Datacap Studio (RRS) application tasks that are “background” tasks; that is,
tasks that run without any human interaction. Background tasks are typically vScan,
recognition, image pre-processing, validation, and export tasks.
Be sure to take the following recommendations into consideration when determining what
tasks Quattro is to process:

• In each instance of Quattro, enable the same number of threads as there are processors in
the QServer; for example, when Quattro is installed on a quad core server, enable all four
Quattro threads.
• When using Quattro to process vScan tasks, an application's vScan task that looks in a
particular folder for the input files should run on only one computer at a time and should
be set up to run on a single thread. VScans running in two different applications looking
in two different input folders can run simultaneously without conflict.
• When using Quattro to process Export tasks, use only one thread for Export when the
Export process does one or more of the following:
Updates field positions in the Setup DCO at runtime (includes Intellocate)
Updates a Fingerprint database
Exports to a text file or Microsoft Access DB
Exports at the field or page level
When it is not possible to predict the effect of multiple threads exporting files at
the same time to a downstream system
• Tasks containing actions that are not known to be thread-safe should be configured to run
in only one thread within a Quattro instance.
Gather Required Task Information
Before you begin setting up Quattro, gather the following information - you need this
information to successfully configure Quattro:
• Identify whether you want to use Windows Authentication or Taskmaster Authentication
to allow Quattro access to Taskmaster.
• Identify the UNC server names of your QServer(s) and your Taskmaster Server ("Server").
• Identify the number of processors available on each QServer.
• For each of your applications, obtain the full UNC path and file names of the Admin and
Engine databases.
• For each of your applications or workflows, make a list that includes the following - be
sure to copy the names of these items exactly, as they are all case-sensitive, and Quattro
will not work if the names don't match.
The full path to and folder name of the application's/workflow's folder on the
Server.
Start up the Taskmaster Client, on the Settings menu, select Workflow and make
a list that includes the Application Name and the Workflow, Job, and Task name
of each background task that you want Quattro to process.
Next, select each Task in turn, click the Setup button, and add the Task's Profile
name to the list if it is different from the Task name.
Using database client software, open the application's Admin database, open the
dco table within the Admin database, and add the dco_id name for each workflow
to your list - the dco_id is usually identical to the name of the workflow as it
appears in the Taskmaster Client Administrator window.
• Taking into consideration the recommendations mentioned above and the number of
processors available on each QServer, identify which tasks from which workflows or

applications should run on which threads (the number of threads you can use are
determined by your license agreement).
opens. Click Yes.
2 When the Status:
Set Up Security on Datacap\MyApp Folders
the C:\Datacap\MyApp1 and MyApp2 folders on the Server when the Server's operating
system is Windows 2003 or 2008. Note that other accounts were already granted security
permissions during the installation and configuration of IBM Datacap Taskmaster Capture.
C:\Datacap\MyApp1 folder and select Properties. The Properties dialog opens.
Control.
4 Navigate to and right-click the C:\Datacap\MyApp2 folder and select Properties. The
Properties dialog opens.
Control.
Set Up Security on Datacap\RRS Folder
the Taskmaster Server's C:\Datacap\RRS folder when the Server's operating system is
during the installation and configuration of IBM Datacap Taskmaster Capture.
3 Add/ensure Domain/Windows User ID of the Rulerunner Quattro is set to allow Full
Control.


opens. Click Yes.
2 When the Status:
Obtain Task Profile Name
This procedure provides instructions on how to obtain the exact spelling of the task name and
the task profile's name. You need this information to update the Taskmaster Application
Service with the specific task profile or profiles that Quattro is to process.
select Taskmaster Client, log in, and open the application.
2 On the Settings menu, select Workflow. The Workflow tab is displayed.
3 Expand the job that contains the task, select the task, and make a note of the task name.
4 Click Setup. The task's Setup - Batch Profiler window opens with the task profile
highlighted.
5 Make a note of the task profile name.
6 On the File menu, select Quit to close the Setup window.
Configure Quattro's Task Profiles in the Taskmaster Application Service
the task profiles that Quattro should process.
Before you begin this task, you need to know which tasks and task profiles you want Quattro
to process, and you need the exact spelling of each task name and task profile name. Follow
the instructions in Obtain Task Profile Name before continuing with this procedure.

2 Select APT. Paths appear in the fields on the Application tab.

3 Ensure all paths are correct.
4 Click the Quattro tab to display it. This tab should only display the task profiles that
Quattro is to process.
8 Enter the name of the task in the first field, and enter the name of the task profile in the
second field, ensuring the spelling and case is the same as what was displayed in the
task's Setup - Batch Profiler window.
opens. Click Yes.
2 When the Status:
opens. Click Yes.
2 When the Status:

Connect to Application, Taskmaster Server, Database Combination
Before you can configure Quattro to run a task, you must connect to the specific combination
of application, Taskmaster Server, and databases for that task.
IMPORTANT
These instructions allow you to temporarily use Taskmaster Authentication and the
Taskmaster "admin" User ID and password to make your configuration changes. Follow the
instructions in Encrypt Taskmaster Login Password to encrypt the password for the
Taskmaster "admin" User ID before continuing with this procedure.
This procedure provides instructions on how to connect to the specific application, Taskmaster
Server and databases that relate to the task Quattro is to process.
window opens.
4 Select the Taskmaster Authentication option to enable the login credential fields.

5 Enter the Taskmaster admin User ID, paste in the encrypted Password, and enter a
Station ID of "2", then click Connect. The button label changes to Disconnect.
6 Click the Workflow:Job:Task tab to display it. Application names are displayed in the
left pane, threads are displayed in the right pane.
7 In the left pane, click in the checkbox to the left of the application you want to work
with. The application tree expands with the Server, Administrator and Engine
databases selected.
8 Continue with the instructions in Configure Quattro to Run a Task.
Configure Quattro to Run a Task
Once you have connected to an application, Taskmaster Server and database combination, you
can set up threads to run tasks in that combination.
This procedure provides instructions on how to set up a thread and configure Quattro to run a
task using that thread. In general, if you click in a checkbox
1 With the Rulerunner Quattro Manager - Workflow:Job:Task window open, right-click
in the right pane to display the context menu items:
Expand all - Expands the details of all existing threads
Collapse all - Collapses the details of all existing threads
Threads - Clear - Deletes all existing threads
Threads - Add Thread - Adds a new, empty thread
Remove - Deletes the selected thread
2 Right-click, point at Threads, then select Add Thread. A new thread is created in the
right pane.
3 Repeat the previous step to create the threads you need.
4 To configure the individual threads to run one or more tasks, do one or more of the
following:
To: Do this:
Configure a thread to run all In the left pane, click the checkbox to the left of the
tasks in a workflow workflow name, then click the workflow name (it is
highlighted in blue) and drag it onto a thread in the
right pane
tasks in a single job job name, then click the job name (it is highlighted in
blue) and drag it onto a thread in the right pane
Configure a thread to run In the left pane, click the checkbox to the left of each
two or more tasks from a task, then click the job (it is highlighted in blue) and
job drag it onto a thread in the right pane
Configure a thread to run a In the left pane, click the checkbox to the left of the
single task task, then click the task (it is highlighted in blue) and
drag it into a thread in the right pane
To configure a thread to run In the left pane, click the checkboxes to the left of
more than one job in the each job, then select the workflow (it is highlighted in

same application blue) and drag it onto a thread in the right pane
Remove a task from a In the right pane, right-click a task and select Remove
thread to delete it
Disable a thread In the right pane, click in the checkbox to the left of
the thread (the checkmark disappears), or right-click
the thread and select Remove to delete it entirely
Remove a thread In the right pane, right-click the thread and select
Remove
Remove all threads In the right pane, right-click, select Threads, then
select Clear
5 Click Save to save your changes.
6 To configure Quattro to run one or more tasks from a different application, Taskmaster
Server or database combination, continue with Disconnect and Reconnect to Different
Application Combination.
7 If you have completed your changes, click the Datacap Login tab to display it.
IMPORTANT
properly.
9 When using:
the User ID of Quattro's domain account, the encrypted version of the password,
and the name of the QServer as the Station ID
10 Click Save.
Disconnect and Reconnect to Different Application Combination
Once you have connected to an application, Taskmaster Server and database combination, and
configured Quattro to run one or more tasks from a single application, you must disconnect
from the application/Taskmaster Server/Admin and Engine database combination you are
working with before you can connect to a different application/Taskmaster Server/Admin and
Engine database combination.
There are two ways to disconnect and reconnect to a different application:
• After saving your changes, click the Datacap Login tab, click Disconnect - the button label
changes to Connect.
To connect to a different application, click the Connect button, then click the
Workflow:Job:Task tab, and select a different application, Taskmaster Server, Admin and
Engine databases. Continue with the instructions in Configure Quattro to Run a Task.
• After saving your changes, right-click the Engine database and select Disconnect, then
right-click the Taskmaster Server and select Disconnect. Check the status bar and ensure

you are disconnected from the Taskmaster Server and databases. Continue with the
instructions in Configure Quattro to Run a Task.
Once you have finished making your changes and have disconnected, ensure Quattro's
authentication credentials are correct (see the last steps in Configure Quattro to Run a Task).
Start Taskmaster Client Application
From a Workstation, start your Taskmaster Client application using your administrative User
ID, password and Station ID.
Run Application Tasks
Run your applications so that there are batches pending for Quattro to process.
Start Quattro
Rulerunner Quattro.
displayed on top.
Monitor Batches during Quattro Processing
Monitor your batches using the Taskmaster Job Monitor to watch batches change status as they
are processed by Quattro.
For troubleshooting information, see Appendix D: Rulerunner Quattro Manager, the section
titled Troubleshooting Quattro.
View Batches Processed by Quattro using Job Monitor
This procedure provides instructions on how to monitor Rulerunner Quattro's processing using
the Taskmaster Client Job Monitor pane.
1 On the Workstation, with the application’s main window open, on the View menu,
select Job Monitor. The Job Monitor pane opens with information about existing
batches displayed.
2 Press <F5> periodically to refresh the Job Monitor pane and see the changes to the
batch task and status as Quattro runs the task or tasks for each batch and then, when
more than one batch is available, run tasks for one or more batches at the same time.
3 After Quattro has finished processing the tasks for all of the batches, the batches will be
displayed with the name of the next task and a Status of pending.
4 Close the Job Monitor pane.


When you are running Rulerunner Quattro in a production environment, Quattro should be
restarted periodically, typically every four hours, or as determined by experience. The option
that controls this behavior is the Restart Interval option on the Rulerunner Quattro Manager's
Additionally, if you have configured Quattro to Stop on Abort (on the Rulerunner Quattro
Manager's Quattro Settings tab), it is a good idea to restart it automatically. The option that
controls this behavior is the Restart Service (or Restart Service if Stopped) option on the
This procedure assumes that you have encrypted the password associated with Quattro's User
ID using IBM Datacap Taskmaster Capture SitManager.exe and can paste the encrypted string
during this procedure - if not, follow the instructions in Encrypt Taskmaster Login Password
before continuing with this procedure.
This procedure provides instructions on how to ensure the Quattro restart options are
configured properly.
window opens.
next step.
credential fields.

5 Enter Quattro's User ID, paste in the encrypted Password, enter the appropriate Station
ID, then click Connect. The button label changes to Disconnect.
6 Click the Workflow:Job:Task tab to display it. APT is displayed in the left pane and
thread0 is displayed in the right pane.
7 On the Quattro Settings tab, select or ensure Stop on Abort is selected, then click Save.
8 On the Advanced Settings tab, select or ensure Restart Service is selected, and ensure
there is a value in the Restart Interval field (defaults to 14400 or four hours), then click
Save.
IMPORTANT
properly.
11 When using:
• IBM Datacap Taskmaster Capture Authentication - Select the IBM Datacap
Taskmaster Capture Authentication option, enter the User ID of Quattro's account,
the encrypted version of the password, and the name of the QServer as the Station
ID
12 Click Save.
13 If you want to start Quattro, click the Datacap Quattro tab, then click Start. The Status
changes to Running.
Restart Taskmaster Software
After successfully installing, configuring, and using Rulerunner Quattro to run additional
tasks, you can restart the IBM Datacap Taskmaster Capture software that was previously
running on other machines. Restart IBM Datacap Taskmaster Capture software on all
machines in the following sequence:
etc.)
Taskmaster Client Service, Datacap Studio, Batch Pilot, etc.)

Install and Configure Taskmaster Client Service

All IBM Datacap Taskmaster Capture’s Windows- or browser-based software tasks can be run
manually. In addition, the Taskmaster Client Service can be configured to run tasks that do not
require human intervention (background tasks) on a separate workstation or server. Depending
on what you want to accomplish, and on your current IBM Datacap Taskmaster Capture
application(s) and client-server environment, running the Taskmaster Client Service on a
separate machine may offer significant processing advantages.
This section provides the information you need to set up the Taskmaster Client Service on a
separate, unattended workstation or server (referred to as the "TCSServer") to run one
application's background tasks automatically.
Optional instructions are also provided to configure the Taskmaster Client Service to use
Windows Authentication rather than standard IBM Datacap Taskmaster Capture
Authentication.
This section assumes that you have a working IBM Datacap Taskmaster Capture client-server
environment with at least one Workstation and one Server.
Overview of Taskmaster Client Service Installation

To set up and use the Taskmaster Client Service to run background tasks, you must:
• Determine which IBM Datacap Taskmaster Capture application and tasks you want the
Taskmaster Client Service to process
• Ensure you have met the prerequisites detailed in Chapter 3 Installation and Configuration
Prerequisites
• Create a domain/Windows account for the Taskmaster Client Service
• Add the Taskmaster Client Service to the Taskmaster Client application as a user and
identify which tasks the Taskmaster Client Service is to run
• Configure Taskmaster Client Service permissions on the Taskmaster Server
• Install and configure the Taskmaster Client Service on the Taskmaster Client Service
Server (TCSServer)
• Test the Taskmaster Client Service
• Leave Taskmaster Client Service running
Determine Which Datacap Application to Process

Before you set up the Taskmaster Client Service, you need to determine which IBM Datacap
Taskmaster Capture application contains background tasks suitable for Taskmaster Client
Service processing. Typically, these will be Rulerunner and export tasks, but can be any tasks
that do not require human interaction.
Create or Ensure Account Exists for Taskmaster Client Service

Create or ensure a specific domain account exists for the Taskmaster Client Service.
If you are using Windows Authentication, ensure the Taskmaster Client Service account has
been added to the appropriate IBM Datacap Taskmaster Capture-specific AD/LDAP security
group or groups. For more information, see Configure Windows Authentication for
Taskmaster.


opens. Click Yes.
2 When the Status:
Add Group, User, and Station for Taskmaster Client Service

This procedure provides instructions on how to add a Taskmaster Client Service group, user,
and station to your IBM Datacap Taskmaster Capture application so the Taskmaster Client
Service group has the Permissions and Privileges it needs for processing.
If you are using Windows Authentication, see Configure Windows Authentication for
Taskmaster for information on naming this group.
1 On the DevWorkstation, with the application's main window open, on the Settings
menu, select Groups. The IBM Datacap Taskmaster Capture Administrator dialog
opens with the Groups tab displayed on top and the existing Groups listed in the left
pane.
2 Click Add, and enter a Group ID and description for the Taskmaster Client Service
Group, then click Apply. A message box indicates the new settings will apply after
enabled.
4 Expand the Privileges branch, expand the Client(s) item, select Taskmaster Sub (Client
Service), then click Apply. A message box indicates the new settings will apply after
5 Click OK to close the message box, and in the Permissions branch, clear the All option,
and select the background tasks within every job that you want the Taskmaster Client
Service to process (typically tasks like Batch Profiler and Export tasks, but can be any
tasks that do not require human interaction), then click Apply. A message box indicates
the new settings will apply after currently signed on users log off and log back on again.

6 If you are using Windows Authentication, skip to step 11, otherwise, click OK to close
the message box, then click the Users tab to display it.
7 Click Add, and enter the User ID of the Taskmaster Client Service domain account,
then click Set Password, and enter the password of the Taskmaster Client Service
domain account, and then click OK and Apply. A message box indicates the new
8 Click OK to close the message box. The Privileges, Permissions, and Groups pane is
enabled.
9 In the Privileges branch, expand the Client(s) item, select Taskmaster Sub (Client
Service), then click Apply. A message box indicates the new settings will apply after
10 Click OK to close the message box, then scroll down to the Groups branch, and, at a
minimum, add the user to the Taskmaster Client Service group, then click Apply. A
message box indicates the new settings will apply after currently signed on users log off
and log back on again.
11 Click OK to close the message box and click the Stations tab to display it.
12 Click Add, and enter a Station ID and description for the Taskmaster Client Service
station, then click Apply. A message box indicates the new settings will apply after
13 Click OK to close the message box, and in the Permissions branch, clear the All option,
and select the background tasks within every job that you want this station to process,
14 Click OK to close the message box, then click Done to close the IBM Datacap
Taskmaster Capture Administrator dialog.
Grant Taskmaster Client Service Log On as a Service Right

This procedure provides instructions on how to ensure the domain/Windows account used by
the Taskmaster Client Service has been granted the Log On as a Service right on the
TCSServer (this allows the service to log on automatically when the TCSServer is restarted).
1 From the TCSServer's Windows Start menu, select Settings, select Control Panel, select
Administrative Tools, select Services, right-click Datacap Taskmaster Client Service
and select Properties. The Properties dialog opens.
2 Click the Log On tab to display it, then select This account. The Browse button is
enabled.
3 Locate or enter the domain name, user name and password of the Taskmaster Client
Service, and click Apply. A message is displayed confirming the account was granted
the Log On as a Service right.
4 Click OK to close the message box and the Properties dialog.
Add Taskmaster Client Service Account on Taskmaster Client Service Machine

Add the Taskmaster Client Service domain account to the TCSServer’s Administrators group
so that the account has local administrator rights on the machine.

If your corporate policy restricts Administrators group privileges, or precludes granting

administrator rights to the Taskmaster Client Service, you must grant the Taskmaster Client
Service account a number of permissions using DCOM Config.
On the TCSServer, in Administrative Tools > Component Services > Computers > My
Computer > DCOM Config, change the following TaskMaster.RunTask properties on the
Security tab:
• Launch and Activation Permissions: Select Customize, click Edit, add the Taskmaster
Client Service account and allow Local Launch, Remote Launch, Local Activation,
Remote Activation.
• Access Permissions: Select Customize, click Edit, add the Taskmaster Client Service
account and allow Local Access and Remote Access.
• Configuration Permissions: Select Customize, click Edit, add the Taskmaster Client
Service account and allow Full Control.
Set Taskmaster Client Service Sharing Permissions for Datacap Folder (Windows 2003)
This procedure provides instructions on how to set up the appropriate Taskmaster Client
Service sharing permissions for the C:\Datacap folder when the Taskmaster Server's operating
system is Windows 2003. Note that other accounts were already granted sharing permissions
4 Add the Taskmaster Client Service domain/Windows account and set to allow Full
Control.
Set Taskmaster Client Service Sharing Permissions for Datacap Folder (Windows 2008)
Service sharing permissions for the C:\Datacap folder when the Taskmaster Server's operating
system is Windows 2008. Note that other accounts were already granted sharing permissions
displayed.
5 Add the Taskmaster Client Service domain/Windows account and set to allow Full
Control.

Set Taskmaster Client Service Security Permissions for Datacap Folder (Windows 2003)
Service security for the C:\Datacap folder when the Taskmaster Server's operating system is
Windows 2003. Note that other accounts were already granted security permissions during the
installation and configuration of Taskmaster.
3 Add/ensure the Taskmaster Client Service domain/Windows account is set to allow
Read & Execute.
Set Taskmaster Client Service Security Permissions for Datacap Folder (Windows 2008)
Service security permissions for the C:\Datacap folder when the Taskmaster Server's operating
system is Windows 2008. Note that other accounts were already granted security permissions
displayed.
2 Click the Security tab to display it, then click Edit
3 Add/ensure the Taskmaster Client Service domain/Windows account is set to allow
Read & Execute.
Set Taskmaster Client Service Security Permissions for Datacap\Application Folder

Service security permissions at the application level when the Taskmaster Server's operating
system is Windows 2003 or Windows 2008. Note that other accounts were already granted
Repeat these instructions for each C:\Datacap\Application folder on the Server - setting up
these security permissions at this level allows you to grant Taskmaster Client Service access to
specific applications.
C:\Datacap\Application folder and select Properties. The Properties dialog opens with
the General tab displayed.
3 Add/ensure the Taskmaster Client Service domain/Windows account is set to allow Full
Control.
Set Taskmaster Client Service Security Permissions for Datacap\RRS Folder

Service security permissions at the application level when the Taskmaster Server's operating
system is Windows 2003 or Windows 2008. Note that other accounts were already granted

Repeat these instructions for each C:\Datacap\RRS folder on the Server - setting up these
security permissions at this level allows you to grant Taskmaster Client Service access to
specific applications.
displayed.
3 Add/ensure the Taskmaster Client Service domain/Windows account is set to allow Full
Control.

On Windows 7:
opens.
displayed.
On Windows 2008:
are displayed.
Install Taskmaster Options on TCSServer

The server (TCSServer) that is to host the Taskmaster Client Service requires that the
appropriate Taskmaster Options be installed when the Taskmaster Client Service runs tasks
that use those options.

If the required Taskmaster Options have not yet been installed on the TCSServer, follow the
Install Taskmaster Client Service on TCSServer

InstallShield Wizard to install the Taskmaster Client Service component and the separately
These instructions apply to Windows 2003 and Windows 2008 Servers (referred to as
"TCSServer").
WARNINGS
Machine.
the Setup.exe.
1 Make the installation package available on your network, or insert the Taskmaster CD
in the TCSServer's CD/DVD drive. If the installation process does not start
automatically, or if the package is on the network, open Windows Explorer, navigate to
and double-click the Setup.exe.
Allow.
it.
8 Exclude all components from the installation process except Taskmaster Client Service
and the separately licensed connectors for which you have a license.

12 Click Yes to reboot.

example:
Configure Taskmaster Client Service

This procedure provides instructions on how to configure the Taskmaster Client Service on the
TCSServer so it processes background tasks for an application automatically.
1 From the TCSServer's Windows Start menu, select All Programs, select Datacap, select
Taskmaster Client and click Taskmaster Client Service Manager.
Yes.
The Taskmaster Client Service Manager window opens with the TM Sub tab displayed
on top.
2 Confirm that the Taskmaster Client Service is Stopped.
3 Click the Application tab to display it and select the Explanations option at the bottom
left to display more information.
4 From the drop-down list, select the application that contains the task that you want the
Taskmaster Client Service to process, then click Connect. The button label changes to
Disconnect, and the information is protected.
5 Click the Login tab to display it.
6 If you are using:
Taskmaster authentication, select the Taskmaster Authentication option, enter the
Taskmaster Client Service’s User ID, Password and Station ID, then click Login.
Windows Authentication, select the Windows Authentication option, enter the
Taskmaster Client Service’s Station ID, and then click Login.
The button label changes to Log off and the Login information is protected.

7 Click the Workflow:Job:Task tab to display it.

8 Expand the application's workflow, expand each of the Jobs within the workflow, then
select or ensure the tasks in each job that this Taskmaster Client Service is responsible
for running are selected. Choose only those tasks that do not require human
intervention. The tasks should be the same as the tasks you selected when you added
the Group, User, and Station for Taskmaster Client Service.
9 Click Save.
10 Click the Logging tab to display the System event log and Datacap log tabs.
11 If appropriate, change the logging settings on either or both tabs, and click Save.
12 Click the Application tab to display it, and click Disconnect. The button label changes
to Connect.
13 Click the TM Sub tab to display it, and click Start. The Status changes to Running.
14 Click Close to close the Taskmaster Client Service Manager window.
15 If you want the Taskmaster Client Service to start automatically when its host computer
is rebooted, from the Windows Start menu, select Settings, select Control Panel, select
Administrative Tools, and double-click Services to open the Services window.
16 Scroll down to the Datacap Taskmaster Client Service entry, select it, right-click, and
select Properties from the shortcut menu. The Properties dialog is displayed with the
General tab displayed on top.
17 Change the Startup Type to Automatic, click Apply to save your changes, then click OK
to close the Properties dialog.
Test Taskmaster Client Service by Running Application

The way to test whether you have set up the Taskmaster Client Service correctly for your
application is to start up your Taskmaster Client application and run the application's tasks
that should trigger the Taskmaster Client Service.
For example, if you have an application with Scan, PageID and Recognition tasks, and you
have set up the Taskmaster Client Service to automatically run the PageID and Recognition
tasks, running a scan job should automatically trigger the Page ID and Recognition tasks. If
results from these jobs show up in the application's Batches folder, you know you have set up
the Taskmaster Client Service correctly.
Test Taskmaster Client Service and View Processing

Another method for testing your set up of the Taskmaster Client Service allows you to start
and run the Taskmaster Client Service so that it displays processing dialogs as it processes
batches. Since only one instance of the Taskmaster Client Service can run on a machine at a
time, these instructions include stopping the service before starting it in display mode.

Stop or Ensure the Taskmaster Client Service is Stopped

This procedure provides instructions on how to stop or ensure the Taskmaster Client Service is
stopped on the TCSServer.
1 From the TCSServer's Windows Start menu, select Settings, select Control Panel, select
Administrative Tools, double-click Services, and scroll down to the Datacap
Taskmaster Client Service entry.
2 When the Status:
Is blank, the service is stopped. Continue with the next step.
Shows as Started, click Stop the Service. A Stopping Service message is
displayed. The Status changes to a blank when the service is stopped.
View Taskmaster Client Service Processing

This procedure provides instructions on how to start and run the Taskmaster Client Service so
that it displays processing dialogs as it processes batches.
1 From the TCSServer's Windows Start menu, select Run. The Run dialog opens.
2 Enter the following command line:
C:\Datacap\tmclient\tmsub.exe
then click OK to start the Taskmaster Client Service. After a brief delay, the
Taskmaster Client Service icon appears in your system tray.
3 When you run the application's Scan task, processing dialogs appear briefly as each
batch is processed.
4 Check the Batches and Export folders for results.
Stop Taskmaster Client Service when in Display Mode

This procedure provides instructions on how to stop the Taskmaster Client Service when it is
running in display mode.
1 On the TCSServer, right-click the Taskmaster Client Service icon in the system tray,
and from the shortcut menu, select Stop and Exit. A message box prompts you to
confirm that you want to stop the service.
2 Click Yes. The message box closes, the Taskmaster Client Service stops after it has
finished any current processing, and the icon is removed from your system tray.

Run Datacap Studio Application

This section provides the information you need to run the Datacap Studio application. These
instructions involve starting the Taskmaster Server Service, and starting Datacap Studio.

opens. Click Yes.
2 When the Status:
Start Up Datacap Studio

This procedure provides instructions on how to start up Datacap Studio.
The Select Applications window opens.
2 Select the application you want to work with, then click Next.
3 The Taskmaster Login window opens.
4 Enter a valid Taskmaster User ID, Password, and Station ID, then click Finish. The
Datacap Studio main window opens with the Rulemanager tab displayed on top.

Install and Configure NENU
Introduction to NENU
NENU (New Enhanced Notification Utility) is a Taskmaster software component that allows
you to set up batch monitoring, status notification, and automatic deletion of completed
batches. It can monitor the status of your Taskmaster applications and:
• Identify batches that meet certain criteria (for example, batches that aborted)
• Change the status of batches or their order in the job queue
• Delete batches or move them to another location
• Send email notifications or take other actions
For example, you can use NENU to locate batches that aborted, move them to another
Taskmaster application for exception processing, and report the results to a system
administrator via email.
You can run NENU in two modes:
• Manually using NENU Manager
• Automatically at scheduled times using the Windows Task Scheduler
NENU Components
NENU includes the following components:
• A library of actions for connecting to a Taskmaster application, querying the database for
batch information, modifying information within the database, moving or deleting batches,
and sending notifications. You can use these actions in rulesets within an existing
Taskmaster application, or you can create a new application specifically for batch
monitoring. For more information, see Summary of NENU Actions.
• The NENU Manager configuration utility for creating the required settings file and
executing NENU rulesets manually. For more information, see Run a Ruleset with NENU
Manager.
Uses for NENU
Here are a few examples of things you can do using NENU:
• Notify an administrator that something has gone wrong with a background server (for
example, a Quattro server)
• Correct a problem that comes up regularly and is usually fixed by, for example, resetting a
batch from aborted to pending
• Generate data for reporting with Datacap RV2 (for example, to take a snapshot of the
number of current users)
• Delete or archive old batches that have completed processing (replaces AutoDelete)
Determine Tasks to be Performed by NENU
Before you create your NENU application, determine the tasks you want NENU to perform.

About these Instructions

This section of the Installation & Configuration Guide describes how to set up NENU for
batch monitoring. It is intended for Taskmaster application developers and Taskmaster
administrators.
These instructions assume you are familiar with the following:
• Creating and modifying Taskmaster applications using Datacap Studio
• Executing Taskmaster applications using Taskmaster Client
• The basic structure of Taskmaster batches and how batches move through the various
stages in the Taskmaster workflow

Installation and Configuration of NENU

Overview of Installation of NENU in Client-Server Environment
This section provides an overview of the steps required to install and configure NENU, and to
set NENU up to monitor the Taskmaster APT application for batches that have aborted.
Information is also provided for using NENU to autodelete old batches.
1 Create or ensure an account exists for NENU.
2 Configure the Developer and NENU accounts' permissions on the DevWorkstation and
the Taskmaster Server.
3 Install NENU on the DevWorkstation.
4 Create a NENU application and NENU-specific ruleset using Datacap Studio.
5 Configure Windows Task Scheduler to run the NENU application.
Create or Ensure Account Exists for NENU
Create or ensure a domain/Windows account exists for NENU.
Configure Developer Account and Permissions on Taskmaster Server
In order for the developer to create a new NENU application on the Taskmaster Server, ensure
the developer has been granted sharing and security permissions on the Taskmaster Server by
following the instructions in the section titled Configure Taskmaster on Server.
Configure NENU Account and Permissions on Developer Workstation
On the machine on which the NENU process (NENU.exe) will be run, add the NENU
domain/Windows account to either the Administrators or Backup Operators group.
Set NENU Account Sharing Permissions for Datacap Folder (Windows 2003)
the NENU account on the Taskmaster Server's shared C:\Datacap folder when the Server's
operating system is Windows 2003. Note that other accounts were already granted sharing
2 The folder should already be shared with the Share name of Datacap.
4 Add/ensure Domain/Windows User ID for NENU is set to allow Full Control.
Set NENU Account Sharing Permissions for Datacap Folder (Windows 2008)
the Rulerunner Quattro account on the Taskmaster Server's shared C:\Datacap folder when the
Server's operating system is Windows 2008. Note that other accounts were already granted

2 Click the Sharing tab to display it. The folder should already be shared with the Share
name of Datacap.
5 Add/ensure the Domain/Windows User ID of NENU is set to allow Full Control.
Set NENU Account Security Permissions for Datacap Folder (Windows 2003)
This procedure provides instructions on how to set up the appropriate security for the NENU
account on the Taskmaster Server's shared C:\Datacap folder when the Server's operating
system is Windows 2003. Note that other accounts were already granted security permissions
3 Add/ensure Domain/Windows User ID for NENU is set to allow Read & Execute.
Set NENU Account Security Permissions for Datacap Folder (Windows 2008)
account on the Taskmaster Server's shared C:\Datacap folder when the operating system is
Windows 2008. Note that other accounts were already granted security permissions during the
installation and configuration of Taskmaster.
3 Add/ensure the Domain/Windows User ID of NENU is set to allow Read & Execute.
Set NENU Account Security Permissions for Datacap\RRS Folder
account on the Taskmaster Server's shared C:\Datacap\RRS folder when the Server's operating
system is Windows 2003 or 2008. Note that other accounts were already granted security
3 Add/ensure Domain/Windows User ID of NENU is set to allow Read & Execute.
InstallShield Wizard on a developer's Workstation (referred to as the "DevWorkstation") to
install the Taskmaster Client software components. The components you install include:
Taskmaster Client and sample applications, the separately licensed applications for which you
have a license, Datacap Studio, DotScan, DotEdit, NENU, and the separately licensed

WARNINGS
Machine.
the Setup.exe.
it.
8 Exclude all features except Taskmaster Client, the separately licensed applications for
which you have a license, and the separately licensed connectors for which you have a
license.
11 Click Finish.

Create NENU Application

opens. Click Yes.
2 When the Status:
Start Datacap Studio to Use Application Wizard
This procedure provides instructions on how to start Datacap Studio on the DevWorkstation
without opening an application.
On Windows 7, when UAC is on, the User Account Control window is displayed.
Click Yes.
The Select Application window opens.
2 Click Close. An empty Datacap Studio main window opens with the Rulemanager tab
displayed on top.
Create NENU Application using Datacap Studio
This procedure provides instructions on how to create a new NENU application using Datacap
Studio.
Application Wizard button in the upper right. The Application Wizard – Overview
window is displayed.
2 Click Next. The Application Wizard - Wizard Mode window is displayed.
3 Ensure the Create a new RRS application option is selected, then click Next. The
Application Wizard - New RRS application window is displayed.
4 Enter the following:

Application NENU This is the name of the application, and

Name becomes the name of the folder in which
the application is created.
Datacap C:\Datacap This is used to create the application
Folder shortcut to tmclient.exe.
Destination \\Server\Datacap This identifies where the application files
will be created.
5 Select Create application shortcuts for all users, then click Next. The Application
Wizard - Document Hierarchy window is displayed.
6 Click Next. The Application Wizard - Fingerprints window is displayed.
7 Click Next. The Application Wizard - Add sample images window is displayed.
8 Click Next. The Application Wizard - Finish window is displayed.
9 Click Finish to begin the creation process. The wizard displays a message indicating
the application is being created, then the Application Wizard - Summary window is
displayed with one or more of the following:
General – Lists the results completed successfully.
Warnings – Indicate the wizard encountered something unexpected, but could continue.
Errors – Indicate the wizard encountered a problem that must be corrected.
10 Click View Logs to open the log file appwiz.new.log) and search for any "error" and
"warning" messages.
11 Close log.
12 Click Close to close the Application Wizard.
Update Datacap.xml on Taskmaster Server
The datacap.xml file on the Taskmaster Server should only contain references to applications
that actually exist in the locations indicated in the file and that are being configured for use.
This procedure provides instructions for updating the file, including adding references to
additional applications that exist, deleting references to applications that do not exist in the
locations indicated in the file, or deleting references to applications that exist but have not been
configured for use.
NOTE
The Taskmaster Application Service is case-sensitive; when adding or changing entries in
the datacap.xml file, ensure the case matches the case of the UNC paths, folders and file
names.
1 Before you begin, identify the names and locations of the applications you want the
Taskmaster Application Service to be aware of.
2 From either the DevWorkstation or the Server, start Notepad, navigate to, and open the
datacap.xml file on the Server. It contains lines that look like this:
<datacap ver="8.0">
<app name="1040ez" ref="1040EZ"/>
<app name="Express" ref="Express"/>
<app name="Flex" ref="Flex"/>

<app name="Survey" ref="Survey"/>

<app name="MClaims" ref="MClaims"/>
<app name="AppWizard" ref="DStudio\AppWizard"/>
</datacap>
3 To delete references to applications that do not exist or have not been configured for
use, delete the corresponding <app name= lines. For example, when the only application
on the Taskmaster Server is the APT application, delete all of the lines except the line
for the APT application so your end result looks like this:
<datacap ver="8.0">
</datacap>
4 To add references to applications that exist, add a line that reflects the name of the
application and the full UNC path to the application folder. For example, when adding
a line for the NENU application, your end result looks like this:
<datacap ver="8.0">
<app name="NENU" ref="\\TASKMASTERSERVER\Datacap\NENU"/>
</datacap>
5 Save and then close the datacap.xml file.

Set Location of Taskmaster Server and Datacap.xml
This procedure provides instructions on how to define the location of the datacap.xml and
define the location of the Taskmaster Server for an application using the Taskmaster
Application Manager.
2 Select the application (such as APT, MClaims, NENU, or a newly-converted
application). Paths appear in the fields on the Application tab.
3 Ensure all workflows are reflected, and that all of the paths reflect the correct UNC
paths to the various files and databases using the Server's name rather than C:\.
5 Change the Server name/address to the name of the Taskmaster Server (without
backslashes).
7 Change or ensure the path reflects the correct location of the datacap.xml on the Server,
for example:

Set NENU Account Security Permissions for Datacap\NENU Application Folder

account on the Taskmaster Server's shared C:\Datacap\NENU Application folder when the
Server's operating system is Windows 2003 or 2008. Note that other accounts were already
granted security permissions during the installation and configuration of Taskmaster.
3 Add/ensure domain/Windows accounts of developers are set to allow Full Control.
4 Add/ensure domain/Windows account of Taskmaster Server Service is set to allow Full
Control.
5 Add/ensure domain/Windows account of NENU is set to allow Read & Execute.
Set NENU Account Security Permissions for Monitored Application Folder
account on the Taskmaster Server's application folder (for example C:\Datacap\APT) when the
Server's operating system is Windows 2003 or Windows 2008. Note that other accounts were
already granted security permissions during the installation and configuration of Taskmaster.
C:\Datacap\Application folder and select Properties. The Properties dialog opens.
3 When NENU is monitoring the application, add/ensure NENU's domain/Windows
account is set to allow Read & Execute.
4 When NENU is deleting batch folders or otherwise making changes to the application
(for example, changing a task status), add/ensure NENU's domain/Windows account is
set to allow Full Control.
opens. Click Yes.
2 When the Status:

Start Datacap Studio and Open NENU Application
1 On DevWorkstation, from Windows Start menu, select All Programs, select Datacap,
select Datacap Studio, then select Datacap Studio again.
The Select Applications - Applications window is displayed.
2 Select the NENU application, and click Next. The Select Applications - Taskmaster
Login window is displayed.
3 Enter the default Taskmaster Admin User ID, Password, and Station ID, then click
Finish. The Datacap Studio window opens with the Rulemanager tab displayed.
Delete All Rulesets in NENU Application
When you use the Datacap Studio Application Wizard to create a new RRS application, the
new application contains a default ruleset structure that can be deleted from a NENU
application that only performs monitoring of another application.
This procedure provides instructions for deleting default rulesets from an application created
using the Application Wizard.
1 With the new application open in Datacap Studio, click the top Ruleset (i.e. VScan).
2 Click Lock/Unlock ruleset. The blue open lock icon changes to orange and locked.
3 Click Remove object. A prompt to confirm the deletion is displayed.
4 Click Yes. A warning message is displayed indicating the Document Hierarchy
contains references to a (now) nonexistent ruleset.
5 Click OK. The message box closes and the top ruleset is selected.
6 Repeat steps 2 through 5 to delete all of the rulesets.
7 On the Document Hierarchy tab, click Lock DCO for editing. A warning message is
displayed indicating the Document Hierarchy contains references to nonexistent
rulesets, and prompts you to confirm the deletion of these references.
8 Click Yes. The blue open lock icon changes to orange and locked.
9 Click Save changes.
10 Click Unlock DCO. The orange locked icon changes to blue and unlocked.
Add NENU Actions to NENU Application
This procedure provides instructions that demonstrate how to create a simple ruleset to check
the status of batches within a specified application workflow and email the results to an
administrator.
1 On the Task Profiles tab, click Lock/Unlock task profiles to lock the task profiles list for
editing. The blue unlocked icon changes to orange and locked.
2 Click Add a new task profile to create a new task. A window opens.
3 Select Custom and enter a name for the new task (for example, “NENU”), then click
OK. The window closes and the task name is displayed in the Task Profiles tab.

4 Click Save changes to save the task profiles list.

5 On the Rulesets tab, right-click the workflow name and choose Add Ruleset. Ruleset1
is added.
6 Click the Ruleset1 label, and rename the new ruleset (for example, “NENU”).
7 On the Task Profiles tab, select the NENU task.
8 On the Rulesets tab, select the NENU ruleset and click Add ruleset to profile.
9 On the Task Profiles tab, click Save changes and then click Lock/Unlock task profiles to
unlock the task profiles list. The orange locked icon changes to blue and unlocked.
10 Within the new ruleset, select Function 1.
11 Click the Actions Library tab and expand the Nenu actions to display the available
actions.
12 Use the Add to function button to add each of the actions below to Function1:
SetUser
SetPassword
SetStation
SetApplication
SetupOpenApplication
QuerySetStatus
ProcessRunSqlQuery
LogSendEmail
13 In the Rulesets tab, select each of the actions requiring a parameter and enter the
parameter value in the Properties tab, then press <Enter>. The parameter value is
displayed in the action on the Rulesets tab. For example:
SetUser admin
SetPassword admin
SetStation 1
SetApplication APT
QuerySetStatus aborted
LogSendEmail <Enter your email address in the “addressTo” parameter>
NOTE
The LogSendEmail action takes multiple parameters but in most cases only the
“addressTo” parameter is required. To get information about the other parameters,
select LogSendEmail in the Actions Library tab and click the Display information about
an action or namespace button to view the embedded help.
14 On the Rulesets tab, click Save changes. Then click Lock/Unlock ruleset and choose
Publish ruleset. The orange locked icon changes to blue and unlocked.
15 On the Document Hierarchy tab, click Lock DCO for editing to lock the DCO for
editing. The blue unlocked icon changes to orange and locked.
16 Expand the top (batch) level of the DCO and, within the Open node, select (global).
17 On the Rulesets tab, select the NENU ruleset’s Rule 1 and then click Add to DCO.

18 On the Document Hierarchy tab, click Save changes and then click Unlock DCO to
unlock the DCO. The orange locked icon changes to blue and unlocked.
Run a Ruleset with NENU Manager
This procedure provides instructions on how to run a ruleset manually using NENU Manager.
Running NENU manually is useful when you are testing the ruleset before you set Windows
Scheduler up to run it automatically
select Taskmaster Client, and select NENU Manager.
The NENU Manager window opens.
2 Click Create. NENU Manager generates a default settings file.
3 To modify the default settings, click in the empty field to the right of the "lib" label,
then either select a value from the drop-down list, or enter a value. Modify the
following:
lib Select the name of the NENU application (the application containing the
NENU task profile).
tprofile Select the name of the NENU task profile.
action_log_level Select the logging level for action messages (0 provides maximum
information).
log_override Select True to create a new log file; False to append to the existing log
file.
log_reflush Select True to ensure all messages are written to the log even in the case
of an exception (slower but easier to debug).
service_log Select the logging level for service messages (0 provides maximum
information).
4 Ensure Place settings file in the batch directory is selected. This creates a subfolder
beneath the application’s Batches folder for the NENU working files.
5 Click Save to generate the settings file. The Settings.xml file is saved in the NENU
folder of the selected application’s “batches” folder.
6 Click Run Profile to test the task profile. A message confirms the task was completed
and instructs you to check the log file.
8 Using Windows Explorer, open the NENU folder under application’s “batches” folder
(for example, C:\Datacap\NENU\batches\NENU_NENU) and review the log file (for
example, nenu_rrs.log).
9 If you configured the NENU ruleset to send an email, check your email inbox for a
message that contains the contents of the NENU log.
Configure Windows Task Scheduler to Run Ruleset Automatically (Windows 2003)
This procedure provides instructions on how to set up a scheduled Windows task to execute
the NENU task profile you created, and the security options to set to ensure the task runs
successfully when the operating system is Windows 2003. You must use the Windows
Scheduler that is on the machine on which the NENU component (NENU.exe) is installed.

1 On the Start menu, select All Programs, select Accessories, select System Tools, then
select Scheduled Tasks.
2 Double-click Add Scheduled Task and click Next.
3 Click Browse, select C:\Datacap\tmclient\NENU.exe, and click Open.
4 Enter a name for the task (for example, NENU) and select when to perform the task (for
example, Daily). Then click Next.
5 Specify the other scheduling parameters and click Next.
6 Enter the username and password for an account with local administrator rights. Then
click Next.
7 In the Summary window, select Open advanced properties for this task when I click
Finish. Then click Finish.
8 In the Run field, append the path and filename for the NENU settings file in quotation
marks, for example:
"C:\Datacap\NENU\Batches\NENU_NENU\Settings.xml"
9 Click OK. The application is now set to run automatically at the time you specified.
Configure Windows Task Scheduler to Run Ruleset Automatically (Windows 7, Windows 2008)
This procedure provides instructions on how to set up a scheduled Windows task to execute
the NENU task profile you created, and the security options to set to ensure the task runs
successfully when the operating system is Windows 7 or Windows 2008. You must use the
Windows Scheduler that is on the machine on which the NENU component (NENU.exe) is
installed.
1 From the Start menu, select Control Panel, select Administrative Tools, then select Task
Scheduler.
2 Under Task Scheduler (Local), right-click Task Scheduler Library and choose New
Folder.
3 Enter Datacap and click OK to create a new folder for your Datacap scheduled tasks.
4 Expand the Task Scheduler Library and select the Datacap folder.
5 In the Actions panel, click Create Basic Task. The Create Basic Task Wizard opens.
6 In the Create a Basic Task dialog, enter a name for the task and click Next. The Task
Trigger dialog is displayed.
7 In the Task Trigger dialog, select Daily and click Next. The Daily dialog is displayed.
8 In the Daily dialog, enter the Start date and time, and click Next. The Action dialog is
displayed.
9 In the Action dialog, select Start a program and click Next. The Start a Program dialog
is displayed.
10 In the Program/script field, browse and select
C:\Datacap\tmclient\NENU.exe
then click Open. The browse window closes.

11 In the Add arguments field, enter the path and filename for the NENU settings file, for
example:

C:\Datacap\NENU\Batches\NENU_NENU\Settings.xml
12 Click Next. The Summary dialog is displayed.

13 In the Summary dialog, select Open the Properties dialog for this task when I click
Finish, and then click Finish. The NENU Properties dialog opens.
14 If the Properties window for the NENU task is not already open, double-click the task
name in the Task Scheduler Library. The Properties window opens with the General
tab displayed.
15 Under Security Options, identify the domain/Windows account currently associated
with the task. If it is not the correct account, click Change User or Group, and select
the NENU domain/Windows account.
16 Select the Run whether user is logged on or not option.
17 Select the Run with highest privileges option.
18 Click OK. The Task Scheduler window opens.
19 Ensure the NENU domain/Windows account is correct, enter the password, then click
OK. The Task Scheduler window closes.
20 Click OK to close the Properties window.
AutoDelete Batches with NENU

Earlier versions of Taskmaster included an AutoDelete utility to automatically delete unwanted
batches. This functionality is now available through NENU.
As users process batches, the Taskmaster application’s “batches” folder can become very
large. For many applications, a batch loses much of its value after the Export task copies the
verified data to an export file or database in another location. If you wish, you can create a
NENU ruleset to periodically purge old batches from the application’s “batches” folder and
remove the corresponding records from the application’s engine database.
This section shows how to create an AutoDelete ruleset to:
• Locate batches completed within a given timeframe (for example, more than five days
ago).
• Delete those batches from the application’s “batches” folder, or move them to an archive
folder.
• Delete the records relating to the deleted batches from the application’s engine database, or
move those records to a separate archive database.
• Generate a log file documenting the results of the process.
You can then schedule the AutoDelete ruleset to run automatically on a scheduled basis (for
more information, see Configure Windows Task Scheduler to Run Ruleset Automatically
(Windows 7, Windows 2008) and Configure Windows Task Scheduler to Run Ruleset
Automatically (Windows 2003)).
AutoDelete Process
When you run a batch through the application workflow, Taskmaster does the following:
• Updates the image files, page data, etc. in the application’s “batches” folder.
• Updates the batch status information in the application’s engine database

In order to delete old batches from the system, you must remove the information from the
“batches” folder and the engine database. Typically you will move the data to a backup
location:
• You can move the batch folders to any available local drive or network share using the
ProcessMoveBatches action. For an example, see Sample AutoDelete Ruleset.
• You must move the database information to another database with the same format as the
engine database. The easiest way to create the database is to create another Taskmaster
application. You can then move the records use the ProcessMoveDBRecords action. For
an example, see Sample AutoDelete Ruleset.
Sample AutoDelete Ruleset
The sample ruleset found below removes all batches that were completed more than five days
ago (the age is specified in seconds). It uses a separate Taskmaster application called
“BackupApp” as an archive repository for the batches and database records that are removed
from the production application (“APT” in this example).
Each of the actions in the sample AutoDelete ruleset is described in the following table. For
more information, see the section titled Summary of NENU Actions or the embedded help in
Datacap Studio.
AutoDelete
Rule1
Function1
SetApplication(“APT”) ; Set application to APT
SetUser(“admin”) ; Set username
SetPassword(“admin”) ; Set password
SetStation(“1”) ; Set station
SetupOpenApplication() ; Connect to APT application
QuerySetStatus(“Job done”) ; Locate batches with status “Job done”
QuerySetAge(“432000”, False) ; Locate batches completed more than 5 days
ago (age is specified in seconds)
ProcessRunSQLQuery() ; Execute query
ProcessMoveBatches(“G:\BackupApp\batches”) ; Move batch folders to backup location
ProcessMoveDBRecords(“BackupApp”, “”, “”, ; Move database records to backup application
“”, False, “admin”, “admin”, “1”, True) database
Summary of NENU Actions

NENU actions are divided into the following categories:
Category Description
Application Setup Used to obtain connections to the admin and engine databases for the
specified Taskmaster application
Query Setup Used to build the query string that is executed against the application
databases you connected to in application setup
Batch Processing Used to execute the SQL query and perform actions on the selected
database records and (optionally) the corresponding batches
Logging Used to write information to the NENU and Windows log files, and also to
send emails

Category Description
Reporting Used to write information to the report tables in the engine database for use
by Datacap RV2
Embedded help is available for all NENU actions from within Datacap Studio. To access the
embedded help, select an action in the Actions Library tab and click the information button.
Brief descriptions of the available actions are provided in the sections that follow. For detailed
information, including information about parameters, refer to the embedded help.
NENU Application Setup Actions
This table lists the application setup actions provided by NENU:
Action Description
SetApplication Specifies the name of the application used by
SetupOpenApplication.
SetUser Specifies username used by SetupOpenApplication.
SetPassword Specifies station ID used by SetupOpenApplication.
SetStation Specifies station ID used by SetupOpenApplication.
SetServer Specifies the name of the server used by SetupOpenApplication.
This is specified in the “name” attribute in the application’s
configuration file. This action is only required if the application
you are connecting to has multiple servers defined.
SetupDisconnectAll Closes the connections to all Taskmaster databases that were
opened by NENU actions. Some NENU actions close the
connection automatically after executing a query.
SetupOpenApplication Connects to an application using the information specified earlier
with SetApplication, SetUser, SetPassword, and SetStation.
SetupOpenApplicationEx Connects to the application specified by the first parameter using
the login information specified by the remaining parameters.
This provides an alternative to SetupOpenApplication.
NENU Query Setup Actions

Before you can execute a query against the application databases you must build a SQL query
string. As you execute the actions in this category, NENU appends the corresponding SQL
code to the current query string. For example, executing QuerySetStatus(“hold”) followed by
QuerySetOperator(“admin”) generates the following query string:
Select * FROM JobMonitor WHERE queue.qu_status IN ('hold') AND qstats.qs_op IN
('admin')
Action Description Table Column

Queried
QueryClear Clears the current query string.
QuerySetAge Specifies the batch age in the query queue qu_start or
string – returns batches started or qu_done
finished within the last x seconds,
or before or after a specific date.
QuerySetBranch Specifies a minimum number of queue qu_id and
child batches – returns batches with qu_parent
at least the number of children

Action Description Table Column

Queried
specified.
QuerySetDateRange Specifies a date range in the query queue qu_start or
string – returns batches started or qu_done
finished within the specified date
range.
QuerySetGeneric Specifies generic attribute value – queue or qstats -any-
the first parameter specifies the
column name and second parameter
specifies the desired value.
QuerySetJobID Specifies the job ID in the query queue qu_job
string.
QuerySetOperator Specifies the operator name in the qstats qs_op
query string.
QuerySetPriority Specifies the job priority name in queue qu_priority
the query string.
QuerySetSeparator Specifies the SQL date/time
separator used in the query string
SQL query. The default value is
‘#’.
QuerySetStation Specifies the station ID in the query qstats qs_station
string.
QuerySetStatus Specifies the task status in the queue qu_status
query string.
QuerySetTaskID Specifies the task ID in the query queue qu_task
string.
NENU Batch Processing Actions

The ProcessRunSqlQuery action executes the current query string and generates a recordset
containing information about all matching batches. For example, if you build a query using
QuerySetStatus(“hold”) and your query locates one batch with status “hold,” the returned
recordset will contain the following information aggregated from the tmbatch, qstats, and
queue tables:
<rs:data xmlns:rs="urn:schemas-microsoft-com:rowset"><z:row pb_adjustdocs="0"
pb_adjustpages="0" pb_batch="20100260.001"
pb_batchdir="C:\Datacap\APT\batches\20100260.001" pb_expectdocs="0" pb_expectpgs="8"
pb_headertable=" " pb_ndocs="0" pb_needMeet="0" pb_pagefile="rrsvscan.xml" pb_pages="8"
qs_elaps="8" qs_op="admin" qs_qid="3" qs_start="2010-09-17T07:35:26" qs_station="2"
qs_stop="2010-09-17T07:35:34" qs_taskid="VScan" qs_tsorder="0" qu_admDB="156"
qu_batch="20100260.001" qu_counter="0" qu_done="2010-09-17T07:35:34" qu_elaps="8"
qu_id="3" qu_job="Demo" qu_lock="none" qu_parent="0" qu_priority="5" qu_spawntype="0"
qu_start="2010-09-17T07:35:26" qu_status="hold" qu_task="VScan" qu_tsorder="0"
xmlns:z="#RowsetSchema" /></rs:data>
The other actions in the batch processing category let you manipulate the batches identified in
the query results recordset.
Action Description
ProcessChangeBatchStatus Changes the status attribute (qs_status) for each batch in
the returned recordset. The database connection is then
closed.

Action Description
ProcessChangeBatchStatusOrder Changes the status (qs_status) and order (qu_tsorder)
attributes for each batch in the returned recordset. The
database connection is then closed.
ProcessChangeBatchStatusTaskOrder Changes the status (qs_status), order (qu_tsorder), and
task (qu_task) attributes for each batch in the returned
recordset. The database connection is then closed.
ProcessClearAuditTable Deletes all records from the audit table in the application’s
admin database.
ProcessClearDebugTable Deletes all records from the debug table in the
application’s engine database.
ProcessDeleteBatches Deletes the folder specified by the batch attribute
(pb_batchdir) for each batch in the returned recordset.
ProcessMoveBatches Moves the folder specified by the batch attribute
(pb_batchdir) to a new location for each batch in the
returned recordset.
ProcessMoveDBRecords For each batch identified in the returned recordset, this
action moves the associated database records from queue,
qstats, and tmbatch to a different application database.
You can optionally delete the records from the source
database.
ProcessResetPendingOrNotify This is typically used to reset aborted batches and changes
the batch status to “pending,” but only for the maximum
number of times specified by parameter 1. For example, if
you specify ‘3,’ NENU will reset the batch status a
maximum of three times. After the third attempt it will
send an email to the specified recipient.
ProcessRunSqlQuery Executes the current query string.
NENU Logging Actions

During ruleset execution, NENU writes status messages to an internal log file as well as the
Rulerunner log file:
• The internal log file is maintained in memory and is used by the SendEmail action.
• The Rulerunner log file is located in the NENU folder beneath the application’s “batches”
folder. For example, if you have a ruleset called “NENU” in an application called
“NENU,” the log file is C:\Datacap\NENU\batches\NENU_NENU\nenu_rrs.log.
Additionally, you can use LogWriteEventLog to write messages to the Windows event log.
Action Description
LogClear Clears the internal log file (does not affect the Rulerunner
log file)
LogSendEmail Sends an e-mail with the internal log file to one or more
email recipients.
LogWriteEventLog Writes an information, warning, or error message to the
Datacap section of Windows event log.
LogWriteRecordSet Writes the returned recordset to the NENU log file (for an
example, see NENU Batch Processing Actions).
LogWriteSQLQuery Writes the current query string to the NENU log file.

NENU Reporting Actions

This table lists the reporting actions provided by NENU:
Action Description
ReportQueryTMUsage Writes a record for each user connected to the current
application to the application’s reportUsers table.
For example, if you used SetupOpenApplication to connect
to the APT application, ReportQueryTMUsage writes
information about current APT users to the reportUsers
table in the APT engine database.
ReportSetReportingTable Reserved for future use (do not use)
ReportSetUsageDBTable Reserved for future use (do not use)

Install and Configure Rulerunner as a Web Service

In addition to IBM Datacap Taskmaster Capture Rulerunner running locally, it can also be
configured to run as a web service on a completely separate server (referred to as “RRServer”).
Depending on what you want to accomplish and the configuration of your current IBM
Datacap Taskmaster Capture client-server environment, running Rulerunner as a web service
may or may not be advantageous.
Configure Rulerunner as a Web Service

This section provides the information you need to install and configure Rulerunner as a web
service on an Internet Information Services (IIS) server in an existing, working IBM Datacap
Taskmaster Capture environment. This section assumes you are installing Rulerunner as a web
service on a separate Server ("RRServer"); that is, the RRServer is not running other IBM
Datacap Taskmaster Capture components.
Overview of Rulerunner as a Web Service Installation

The installation and configuration process is made up of the following steps:
1 Ensure you have a working IBM Datacap Taskmaster Capture environment where you
have successfully processed batches through export and that your application works
with Rulerunner running locally.
2 Install the Web Rulerunner Service component on RRServer.
3 Configure Rulerunner as a web service.
4 Configure the IBM Datacap Taskmaster Capture application to use Rulerunner as a web
service.
5 Test the application using Rulerunner running as a web service.
Create or Ensure Account Exists for Rulerunner

Create or ensure a domain/Windows account exists for the Web Rulerunner Service and give it
the Log on as a service right.
Note
account.
Configure Rulerunner Permissions on Server

Set Rulerunner Account Sharing Permissions for Datacap Folder
Depending on the operating system of the Server that is hosting the Datacap folder, follow the
appropriate set of instructions in Configure Taskmaster on Server to set up the appropriate
sharing permissions for the C:\Datacap folder. Note that other accounts were already granted
Add/ensure Domain/Windows User ID of Rulerunner is set to allow Full Control.
Set Rulerunner Account Security Permissions for Datacap Folder
Depending on the operating system of the Server that is hosting the Datacap folder, follow the
appropriate set of instructions in Configure Taskmaster on Server to set up the appropriate

security for the C:\Datacap folder. Note that other accounts were already granted security
Add/ensure Domain/Windows User ID of Rulerunner is set to allow Read & Execute.
Set Rulerunner Account Security Permissions for Datacap\RRS Folder (Windows 2003)
the C:\Datacap\RRS folder on the Server that is hosting the Datacap folder when the Server’s
1 On the Server, start Windows Explorer, navigate to, right-click the C:\Datacap\RRS
folder, and select Sharing and Security. The Sharing tab is displayed.
3 Add/ensure local ASP.NET Machine Account (Server\ASPNET) and local Internet
Guest Account (Server\IUSR_SERVER) are both set to allow Full Control.
4 Add/ensure Domain/Windows User ID of Rulerunner is set to allow Full Control.
Set Rulerunner Account Security Permissions for Datacap\RRS Folder (Windows 2008)
the C:\Datacap\RRS folder on the Server that is hosting the Datacap folder when the Server’s
displayed.
The Permissions dialog opens.
3 Add/ensure NETWORK SERVICE and local IUSR are both set to allow Full Control.
Set Rulerunner Account Security Permissions for Batches Folder (Windows 2003)
C:\Datacap\Application\Batches folder on the Server that is hosting the Datacap folder when
the Server’s operating system is Windows 2003. Note that other accounts were already
1 On the Server, start Windows Explorer, navigate to, right-click the
C:\Datacap\Application\Batches folder (for example C:\Datacap\APT\Batches), and
select Properties. The Properties dialog opens with the General tab displayed.
Set Rulerunner Account Security Permissions for Batches Folder (Windows 2008)
C:\Datacap\Application\Batches folder on the Server that is hosting the Datacap folder when

the Server’s operating system is Windows 2008. Note that other accounts were already
1 On the Server, start Windows Explorer, navigate to, right-click the
C:\Datacap\Application\Batches folder (for example C:\Datacap\APT\Batches), and
select Properties. The Properties dialog opens with the General tab displayed.

Install and Configure Rulerunner on RRServer (Windows 2003)

Configure Rulerunner Account and Permissions on RRServer
used by Rulerunner has the rights and permissions it needs on its host (RRServer). This
includes: Providing the account with Administrator privileges on its RRServer, and granting
security rights to the WRRS folder.
Add Rulerunner Account on RRServer
Rulerunner's domain/Windows account must have administrative rights on its RRServer. Add
the Rulerunner account to the RRServer's Administrators group so that the account has local
administrator rights on the machine.
Web Rulerunner Service uses an IIS Process Model Identity to access IBM Datacap
Taskmaster Capture.
NOTE
When RV2, Taskmaster Web, or Web Rulerunner Service are installed on the same web
server, they must use the same domain/Windows account.
RRServer hosting Rulerunner as a web service when the operating system is Windows 2003.
1 On the RRServer, use Windows Explorer to navigate to and use a text editor such as
Notepad to open
<processModel …
CAUTION
There are multiple occurrences of "<system.web>" in the machine.config file. Be sure
3 Add the following information to the <processModel line so that it reflects information
for the Rulerunner domain/Windows account that you want to use:
userName="DOMAIN\RulerunnerAccountName"
password="RulerunnerAccountPassword"/>
Grant Rulerunner Access to IIS Metabase (Windows 2003)
On the Windows 2003 RRServer that will host Rulerunner as a web service, grant Rulerunner's
domain/Windows account access to the IIS metabase and other directories used by ASP.NET.
Tool (version 2 of .NET Framework) with the grant access parameter (-ga) to grant the
Rulerunner account access to the IIS metabase. For more information about the tool, search
for "aspnet_regiis.exe" on the Microsoft website.
1 On the RRServer, from the Windows Start menu, select Run. The Run dialog opens.

backslash, then the Rulerunner account name;
DOMAIN\RulerunnerAccountName
then press <ENTER>.
access" message.
Grant DCOProcessor Permissions to Rulerunner in DCOM Config (Windows 2003)
On the Windows 2003 RRServer that will host Rulerunner, in Administrative Tools >
Component Services > Computers > My Computer > DCOM Config > right-click
DCOProcessor, select Properties, then click the Security tab. Add and grant Local Launch and
Local Activation permissions to the Rulerunner account.
2003 WebServer.

Install Web Rulerunner Service on RRServer

InstallShield Wizard to install the Web Rulerunner Service component and the separately
These instructions apply to Windows 2003 and Windows 2008 servers (referred to as
"RRServer").
WARNINGS
Machine.
the Setup.exe.
Taskmaster Capture CD in the machine's CD/DVD drive. If the installation process
Yes.
it.
8 Exclude all components from the installation process except Rulerunner Web Service

11 Click Finish.
Set Up WRRS Folder Account Permissions for Rulerunner (Windows 2003)
This procedure provides instructions on how to set up the appropriate security for the \WRRS
folder on the RRServer when the RRServer’s operating system is Windows 2003.
1 On the RRServer, start Windows Explorer, navigate to, right-click the
C:\Datacap\WRRS folder, and select Sharing and Security . The Sharing tab is
displayed.
3 Add/ensure local ASP.NET Machine Account (Server\ASPNET) and local Internet
Guest Account (Server\IUSR_SERVER) are both set to allow Read & Execute.
Create and Share Virtual Directory for Rulerunner Running as Web Service (Windows 2003)
These instructions assume you will create a virtual directory for Rulerunner running as a web
service nested within the RRServer’s Default Web Site.
This procedure provides instructions on how to create a virtual directory for Rulerunner
running as a web service.
1 On the RRServer's Windows Start menu, select Settings, select Control Panel, select
Wizard opens.
4 Enter RRS as the alias, then click Next. The Web Site Content Directory page is
displayed.
5 Enter the full path of or use the Browse button to navigate to and select the
C:\Datacap\WRRS folder, then click OK. The Web Site Content Directory page
reappears with the full path to the WRRS folder displayed.
8 Click Finish. The Wizard closes and the new RRS virtual directory is displayed in the
9 Right-click RRS, select Properties from the shortcut menu. The RRS Properties window
is displayed with the Virtual Directory tab on top.
10 Click the ASP.NET tab to display it and confirm the ASP.NET version is 2.0.nnnnn. If
it is not, you cannot continue with this procedure. To recover, ensure that you installed
the correct version of IBM Datacap Taskmaster Capture:
If you did not, begin this entire process over again with the correct version of the
IBM Datacap Taskmaster Capture software.

If you did, follow the instructions to Run aspnet_regiis.exe to update the ASP.NET
application script maps.
11 Click OK to save the settings and close the RRS Properties window.
Set or Confirm Timeout Parameters for Rulerunner Running as Web Service (Windows 2003)
This procedure provides instructions on how to set or confirm the timeout parameters affecting
Rulerunner running as a web service.
1 From the RRServer’s Windows Start menu, select Settings, select Control Panel, select
2 Expand the computer, expand its Web Sites folder, expand its Default Web Site, right-
click the RRS virtual directory, and select Properties from the shortcut menu. The RRS
Properties dialog opens with the Virtual Directory tab displayed on top.
5 Select or ensure the Enable session state option is selected and the Session timeout field
is set to 20 minutes.
6 Select or ensure the Enable parent paths option is selected and the ASP Script timeout
field is set to 1200 seconds.
11 Select or ensure the Request execution timeout field is set to 1200 seconds, then click
Apply if you have made any changes.
13 Select or ensure the Session timeout field is set to 20 minutes, then click Apply if you
have made any changes.
14 OK to save, and click OK to close the RRS Properties dialog.
Set Web Site Isolation Mode for Rulerunner (Windows 2003)
This procedure provides instructions on how to set the service to run in IIS 5.0 Isolation Mode
on a Windows 2003 IIS 6 Server.
1 On the RRServer, with the Internet Information Services (IIS) Manager window open,
expand the computer on which you created the virtual directory, right-click Web Sites,
and on the shortcut menu, select Properties. The Web Site Properties dialog opens.
3 Select Isolation Mode: Run WWW Service in IIS 5.0 Isolation Mode, and click OK. A
message box related to restarting IIS is displayed.
4 Click Yes. The message box and Web Site Properties dialog close, and IIS is restarted.

Select Web Service Extensions for Rulerunner (Windows 2003)

This procedure provides instructions on how to allow the Active Server Page extensions on a
Windows 2003 IIS 6 Server.
1 On the RRServer, with the Internet Information Services (IIS) Manager window open,
expand the computer on which you created the virtual directory, and select Web Service
Extensions. The Web Service Extension options are displayed in the right pane.
2 Select/ensure Active Server Pages, ASP.NET v2.0.50727, and Server Side includes are
Allowed.
Test Access to Rulerunner
This procedure provides instructions on how to test that you have correctly configured
1 Open Internet Explorer, and enter the following: http://RRServerName/rrs/session.asmx
where:
ServerName is either the default IP address or URL of the RRServer
rrs is the alias you assigned to the WRRS folder
After a pause, a Session Web Service window is displayed.
2 Close the window.
example:

Services (IIS).

Install and Configure Rulerunner on RRServer (Windows 2008)

Configure Rulerunner Account and Permissions on RRServer
used by Rulerunner has the rights and permissions it needs on its host (RRServer). This
includes: Providing the account with Administrator privileges on its RRServer, and granting
security rights to the WRRS folder.
Add Rulerunner Account on RRServer
Rulerunner's domain/Windows account must have administrative rights on its RRServer. Add
the Rulerunner account to the RRServer's Administrators group so that the account has local
administrator rights on the machine.
On Windows 7:
opens.
displayed.
On Windows 2008:
are displayed.
2008.

installed.
Install Web Rulerunner Service on RRServer
InstallShield Wizard to install the Web Rulerunner Service component and the separately
These instructions apply to Windows 2003 and Windows 2008 servers (referred to as
"RRServer").
WARNINGS
Machine.
the Setup.exe.
Taskmaster Capture CD in the machine's CD/DVD drive. If the installation process
Yes.
it.

8 Exclude all components from the installation process except Rulerunner Web Service
11 Click Finish.
Set Up WRRS Folder Account Permissions for Rulerunner (Windows 2008)
This procedure provides instructions on how to set up the appropriate security for the \WRRS
folder on the RRServer when the RRServer’s operating system is Windows 2008.
1 On the RRServer, start Windows Explorer, navigate to, right-click the
C:\Datacap\WRRS folder, and select Properties . The Properties dialog opens with the
General tab displayed.
3 Add/ensure NETWORK SERVICE and IUSR are set to allow Read & Execute,
add/ensure Domain/Windows User ID of Rulerunner is set to allow Full Control.
4 Click Apply and then OK to save your changes and close the dialog.
Set IIS ASP Request Size Limit (Windows 2008)
Depending on the usual size of the images that will be processed, you should adjust the default
Maximum Requesting Entity Body Limit (maxRequestEntityAllowed).
This procedure provides instructions on how to locate and change the Maximum Requesting
Entity Body Limit when the operating system is Windows 2008.
1 From the RRServer's Windows Start menu, select Control Panel, and on the Control
window opens.
The Internet Information Services (IIS) Manager window opens.
4 In the Connections pane, select the RRServer. The Home pane is displayed.

5 In the Home pane, scroll down to the IIS area and double-click ASP.
If ASP is not displayed, ensure it was installed, then restart IIS and the ASP icon should
be displayed.
The ASP properties pane is displayed.
6 In the Behavior section, expand Limits Properties. Additional properties are displayed.
7 Locate Maximum Requesting Entity Body Limit (maxRequestEntityAllowed), change
the value (expressed in number of bytes) to reflect the appropriate size; for example,
from 200000 (200 kb) to 10238976 (10MB), then tab out. The Apply button in the
Actions pane is enabled.
8 In the Actions pane, click Apply. A message box indicates the change was saved.
9 Close the Internet Information Services (IIS) Manager window.
Create and Share Rulerunner Web Site (Windows 2008)
This procedure provides instructions on how to create the Rulerunner web site when Web
Rulerunner Service is installed in a Windows 2008 IIS 7 environment.
1 From the RRServer's Windows Start menu, select Control Panel, and on the Control
window opens.
The Internet Information Services (IIS) Manager window opens with a Connections
pane on the left.
4 In the Connections pane, expand the computer on which the web site will reside, and
expand Sites, right-click the Default Web Site, and select Add Application from
shortcut menu. The Add Application dialog opens.
5 Select or enter the following on the Add Application dialog:
Alias: RRS
Application pool: Classic .NET AppPool
Physical path: C:\Datacap\WRRS
and click OK to save your settings. The Add Application dialog closes.
displayed.
8 Select the Classic .NET AppPool and in the Actions pane, under Manage Application,
select Advanced Settings. The Advanced Settings dialog opens.

12 Enter Rulerunner's domain/Windows account information in the format:

accountname@domain.com, enter the account's password twice, then click OK. The
Credentials window closes and the Application Pool Defaults window is displayed.
13 In the Connections pane, click the Default Web Site, in the far right pane, expand
Manage Web Site, and click the Configure Limits… link. The Edit Web Site Limits
dialog opens.
14 Set the Connection Timeout field to 1200 (seconds), then click OK to save your change
and close the Edit Web Site Limits dialog.
15 In the Connections pane, click the Default Web Site, in the middle Default Web Site
Home pane, in the IIS section, double-click the HTTP Response Headers icon. The
HTTP Response Headers pane opens.
16 In the far right pane, click the Set Common Headers link. The Set Common HTTP
Response Headers dialog opens.
17 Select Expire Web content, select Immediately, then click OK to save your changes and
close the Set Common HTTP Response Headers dialog.
Web Site.
Test Access to Rulerunner
This procedure provides instructions on how to test that you have correctly configured
1 Open Internet Explorer, and enter the following: http://RRServerName/rrs/session.asmx
where:
ServerName is either the default IP address or URL of the RRServer
rrs is the alias you assigned to the WRRS folder
After a pause, a Session Web Service window is displayed.
2 Close the window.
example:


Services (IIS).

Configure Application to Use Rulerunner as a Web Service

opens. Click Yes.
2 When the Status:
displayed.
opens.
Configure Taskmaster Application to Use Rulerunner as a Web Service
This procedure provides instructions on how to configure a Windows-based Taskmaster Client
application to use Rulerunner running as a web service rather than the local Rulerunner. This
procedure uses the IBM Datacap Taskmaster Capture APT application as an example.
1 With APT’s main window open, on the Settings menu, select Workflow. The IBM
Datacap Taskmaster Capture Administrator dialog opens with the Workflow tab
displayed on top.
2 Select the Demo Job to expand it.
3 Select the Batch Profiler task, then click Setup. The Batch Profiler Setup - Batch Pilot
window opens.

4 Select the Rulerunner Web Service option, enter the URL to the RRS (for example:
http://RRServer/rrs), then click Test Connection. A Remote RRS Session Available
message is displayed in the status bar.
5 Click Done. A message is displayed identifying the changes made, and prompting you
to confirm the change.
6 Click Yes. The Batch Profiler- Batch Pilot window closes and the Taskmaster
Administrator dialog reappears.
7 Click Apply.
Test Taskmaster Application Using Rulerunner as a Web Service
Once you have set up at least one task in the Taskmaster Client application to use Rulerunner
running as a web service, create a batch and process it through that task. If the task completes
successfully, open the application’s batches folder, and open the log file associated with that
task. The log file should contain a “RRS is REMOTE” entry that confirms the task used

Configure Windows Authentication for Taskmaster

This section provides the information you need to configure IBM Datacap Taskmaster Capture
to use either Windows Active Directory (AD) or any Lightweight Directory Access Protocol
(LDAP or LLLDAP) provider rather than maintaining individual users in Taskmaster itself and
using IBM Datacap Taskmaster Capture authentication.
This section includes information related to your domain, IBM Datacap Taskmaster Capture-
specific AD/LDAP/LLLDAP security groups, domain/Windows accounts for IBM Datacap
Taskmaster Capture users, as well as configuring Taskmaster Server Service to use Windows
Authentication, adding a IBM Datacap Taskmaster Capture group to the application that has
the exact same name as the security group and domain, and updating all Taskmaster Client
icons to use Windows Authentication.
No changes are required to your Taskmaster Web Client as it always attempts to use Windows
Authentication first.
To set up Taskmaster Client Service using Windows Authentication, follow the instructions in
Configure Taskmaster Client Service.
Overview of Taskmaster Windows Authentication Processing

Taskmaster Client, Taskmaster Web Client, and Taskmaster Client Service support enterprise
management of users in groups using either native Active Directory (AD) or any Lightweight
Directory Access Protocol (LDAP or LLLDAP) provider. This feature replaces the “NT
Authentication” method provided in earlier versions of Taskmaster.
Once the components of Taskmaster have been configured to use Windows Authentication and
a user logs onto Windows with a Windows ID that exists in the AD/LDAP directory, when that
same user logs onto Taskmaster, Taskmaster attempts to locate the user in the AD/LDAP
directory.
If Taskmaster locates the user in the AD/LDAP directory, it retrieves a list of all of the domain
groups that this user belongs to, and attempts to find a Taskmaster Group that matches an
AD/LDAP Group.
If authentication fails, Taskmaster presents its standard login dialog and the user can log onto
Taskmaster using Taskmaster authentication (which uses entries in the Taskmaster
Administration database for user authentication).
If a match is found, the user is authenticated and granted the permissions and privileges
defined for the matching Taskmaster Group – limited by the permissions and privileges of the
Station in use.
When the user belongs to other AD/LDAP Groups that also have corresponding Taskmaster
groups, the user is granted the Taskmaster permissions and privileges of those groups as well.
Overview of Windows Authentication Configuration Process

The procedures in this section apply to IBM Datacap Taskmaster Capture 7.5 or later. The
configuration process includes the following steps:
1 Create Domain, Security Groups, Domain Accounts
2 Configure Taskmaster Server Service to use Windows Authentication
3 Add IBM Datacap Taskmaster Capture Group to Application

4 Update Authentication Parameter in Taskmaster Client Application Shortcut
Create or Ensure Domain Exists

Create or ensure a domain exists in which Taskmaster-specific Active Directory (AD) or
Lightweight Directory Access Protocol (LDAP or LLLDAP) security groups can be created.
Ensure you know the exact spelling of the domain, as you will need it when you configure
Taskmaster to use Windows Authentication.
Create or Ensure Security Group Exists

Create or ensure at least one Taskmaster-specific security group exists within the domain.
Depending on your Datacap applications, you can create separate groups to limit what your
Taskmaster users can do in Taskmaster.
Create or Ensure Accounts Exist and are Part of Security Group

Create or ensure a domain/Windows account exists for each Taskmaster Client user and,
optionally, for the Taskmaster Client Service, and ensure each account has been added to the
appropriate Taskmaster-specific security group or groups.

opens. Click Yes.
2 When the Status:
Configure Taskmaster Server Service to use Windows Authentication
This procedure provides instructions on how to configure Taskmaster Server Service to use
Windows Authentication.
1 With the Taskmaster Server Manager window open, click the Taskmaster tab to display
it.
2 Click Show advanced to display Advanced Settings. The button label changes to Hide
advanced.
3 In the Authentication system field, select the type of authentication you want to use.
The Authentication path template field is enabled, and the template string that is
displayed changes depending on your selection.
4 Enter the appropriate string in the Authentication path template field. For:


<%server%>:<%port%>/uid=<%user%>,dc=<%domain%>,dc=Com
then click Save.
6 Click Start to start Taskmaster Server Service. A Starting Service message is displayed.
The Status changes to Running when the service is started.
Add Taskmaster Group to Application

This procedure provides instructions on how to add a IBM Datacap Taskmaster Capture group
to your IBM Datacap Taskmaster Capture application to support your Windows Authentication
configuration.
select Groups. The IBM Datacap Taskmaster Capture Administrator dialog opens with
the Groups tab displayed on top and the existing Groups listed in the left pane.
2 Click Add, and enter a Group ID that is a concatenation of:
--Your IBM Datacap Taskmaster Capture-specific security group name
--A dot
--The domain to which your IBM Datacap Taskmaster Capture-specific security group
belongs.
For example, for a security group called TMUsers in the XYZ Company's domain, the
IBM Datacap Taskmaster Capture Group ID would be:
TMUsers.XYZ
enabled.
5 Since you are using this group to grant specific privileges to a specific group of
Taskmaster Client users for this application, expand the Privileges branch and select the
appropriate privileges, then click Apply. A message box indicates the new settings will
apply after currently signed on users log off and log back on again.
7 Since you are using this group to grant permissions to a specific group of Taskmaster
Client users for this application, expand the Permissions branch and select the
appropriate permissions, then click Apply. A message box indicates the new settings
9 Click Apply, and then Done. The IBM Datacap Taskmaster Capture Administrator
dialog closes.
10 Close the Taskmaster Client window. A message box prompts you to confirm you want
to quit.

11 Click Yes. Taskmaster Client shuts down.
Update Authentication Parameter in Taskmaster Client Application Shortcut

In order to use Windows Authentication whenever a user starts the Taskmaster Client using an
application shortcut, the shortcut's authentication parameter must be changed. Taskmaster
Client application shortcuts can be located on the desktop, in the Datacap folder of shortcuts
installed on the desktop, and in the Workstation’s Windows Start menu. When shortcuts are
first installed, they may or may not contain an authentication parameter.
This procedure provides instructions on how to change a Taskmaster Client shortcut so it
contains the authentication parameter that indicates Windows Authentication should be used.
1 Right-click the appropriate Taskmaster Client shortcut and select Properties. The
application’s Client properties dialog opens with the contents of the Target field
selected, for example:
C:\Datacap\tmclient\tmclient.exe -dcapp:APT –tma
2 Press <End> to move the cursor to the end of the Target field. There may or may not be
an authentication parameter (either -tma or -nta).
a) If an authentication parameter appears, change it to or ensure it is -nta
b) If no authentication parameter appears, after the application name, add a space, then
-nta
The Target field should look like this:
C:\Datacap\tmclient\tmclient.exe -dcapp:APT –nta
3 Click Apply, then OK to close the Client properties dialog.

Use the Fingerprint Maintenance Tool
Fingerprint Maintenance
The Fingerprint Maintenance Tool (FMT) allows you to keep information about your
fingerprints synchronized in all of the places fingerprint information is stored, including your
application's Fingerprint Database and fingerprint data files.
Start Fingerprint Maintenance Tool

On the Taskmaster Server where the application files are located, open Windows Explorer and
navigate to the Datacap\Application\dco_Application folder (for example:
Datacap\APT\dco_APT) and double-click Fingerprint Maintenance Tool.exe. The Fingerprint
Maintenance Tool window opens.
The very first time the Fingerprint Maintenance Tool is run, a message is displayed indicating
a backup directory has been created.
Locate and Delete Partial Fingerprints

Over time, partial fingerprints associated with documents that have not been completely
processed will accumulate, and should be deleted.
1. Start the Fingerprint Maintenance Tool
2. Click the Find Problems button to locate existing problems.
3. When entries with Xs are displayed, click the Select All button, then click the Delete
Selected button. The partial fingerprints are deleted.
4. Close the Fingerprint Maintenance Tool.
Delete Fingerprint
To delete a fingerprint when you know the Fingerprint ID, do the following:
1 Start the Fingerprint Maintenance Tool.
2 Click the Show Statistics button to display information about all existing fingerprints.
3 Select the ID of the fingerprint that you want to delete.
4 Click the Delete Selected button.
Export Selected Fingerprints

When you want to move fingerprints from one application environment to another (for
example, from Test to Production), you must first export the fingerprints from the source (ex.
Test) Fingerprint Database, and then import, or add, those fingerprints to the target (ex.
Production) Fingerprint Database.
1. Start the Fingerprint Maintenance Tool associated with the source application
environment.
2. Click the Show Statistics button to display information about the existing
fingerprints.
3. Highlight the fingerprints you want to export.
4. Click the Export Selected button. The Enter Identification Prefix window is
displayed.

5. Enter two alphabetic characters - these become the first two characters of the
exported fingerprint-related files - , then click OK. The window closes and the
exported files are placed in the application's \fingerprint\Fingerprint Export folder.
6. For instructions on adding these exported fingerprints to the target application
environment, see Add Selected Fingerprints.
Add Selected Fingerprints

When you want to move fingerprints from one application environment to another (for
example, from Test to Production), after you have exported the fingerprints from the source
(ex. Test) Fingerprint Database, you then import, or add, those fingerprints to the target (ex.
Production) Fingerprint Database.
1. Using Windows Explorer, copy the exported fingerprint-related files (TIFF, CCO,
XML) from the source application's \fingerprint\Fingerprint Export folder to the
target application environment's \fingerprint folder.
2. Start the Fingerprint Maintenance Tool associated with the target application
environment.
3. Click the Find FPXML Files button to locate fingerprints that are not in the target
application environment's Fingerprint database.
4. When one or more entries are displayed, click the Select All button, then click the
Add Selected button. The fingerprints are added to the target application
environment's Fingerprint database.
5. Close the Fingerprint Maintenance Tool.
Fingerprint Maintenance Tool Troubleshooting

FMT Backup Directory
This folder is found in the application's dco_ directory and contains the FMT.Log as well as
backup copies of the SetupDCO file that are created when running the Fingerprint
Maintenance Tool.
FMT.Log
This log contains processing details identifying the changes made and attempted by the
Fingerprint Maintenance Tool.

Chapter 6
Uninstall Taskmaster 8.0.1

This chapter provides the information you need to uninstall IBM Datacap Taskmaster Capture
8.0.1 software components.
Overview of Taskmaster 8.0.1 Uninstall Process

The procedures in this section apply to uninstalling IBM Datacap Taskmaster Capture 8.0.1.
Because the Taskmaster uninstall process removes only those files that the previous
Taskmaster installation process created, any files, settings, registry keys, administrative users,
web sites, process model identity changes, etc. that you altered or created in Taskmaster or that
were changed by Taskmaster processing, are not removed automatically by the uninstall
process, and will need to be removed manually.
If you will be installing a newer version of Taskmaster on the same machine in the same
location, customized applications that were untouched by the uninstall process will not be
changed by the later installation, but you must follow all applicable upgrade instructions (if
any) provided with the newer version of Taskmaster for your custom application.
The uninstall process is made up of the following steps:
• Ensure All Taskmaster Clients are Shut Down
• Ensure All Taskmaster Services are Shut Down
• Ensure Taskmaster Server Service is Shut Down
• Create Backup Folders
• Backup Custom Applications
• Backup Application Shortcuts
• Uninstall IBM Datacap Taskmaster Capture 8.0.1
• Remove Accounts from Administrator and Backup Operator Groups
• Delete Registry Keys
• Remove Web Sites and Virtual Folders
• Reset Application Pool Process Model Identities
• Remove Process Identity from Machine.Config File
• Delete Program Shortcuts
• Delete Remaining Folders
Ensure All Taskmaster Clients are Shut Down

Before you begin uninstalling, ensure that all Taskmaster Client and Taskmaster Web Client
end users and administrators on all workstations are logged off.

Also ensure that all developers have logged off and all background client processes have been
shut down, including Taskmaster Client Service, Quattro, Datacap Studio, NENU, RV2, Batch
Pilot, etc.
Ensure All Taskmaster Web Sites and Services are Shut Down
Before you begin uninstalling, ensure that you have stopped the Taskmaster Web site and any
other Taskmaster sites or web-based services (RV2, WRRS, Fingerprint Service, etc.)
Ensure Taskmaster Server Service is Shut Down

After you have ensured that no other Taskmaster software components are running, shut down
the Taskmaster Server Service.
Create Backup Folders

In Windows Explorer, navigate to a network location of your choice and create one or more
folders for storing the backup copy of your customized application folders and shortcuts.
Backup Custom Applications

This procedure provides instructions on how to make backups of folders that contain
customizations you want to keep. Repeat these instructions to make copies of every
customized application.
1 Using Windows Explorer on the Taskmaster Server, navigate to the C:\Datacap folder.
2 Copy the datacap.xml file to your backup folder.
3 Using Windows Explorer, navigate to C:\Datacap\<application name> folder.
4 Copy the <application name> folder to your backup folder.
5 If any other files associated with the custom application exist in other locations (for
example, your admin and engine databases are located on a database server), copy them
to your backup folder as well.
Backup Application Shortcuts

This procedure provides instructions on how to make backup copies of IBM Datacap
Taskmaster Capture shortcuts. Repeat these instructions to make copies of the shortcuts
associated with your customized applications.
For shortcuts located on the desktop:
1 Display your desktop, right-click the shortcut, and select Copy from the shortcut menu.
2 Using Windows Explorer, navigate to your backup folder and, if necessary, the
appropriate subfolder.
3 Right-click in the folder and select Paste Shortcut from the shortcut menu.
For shortcuts located only on the Start menu:
1 Using Windows Explorer, navigate to C:\Documents and Settings\All Users\Start
Menu\Programs, right click the Datacap folder and select Copy from the shortcut menu.

2 Using Windows Explorer, navigate to your backup folder and, if necessary, the
appropriate subfolder.
3 Right-click in the folder and select Paste Shortcut from the shortcut menu.
Uninstall IBM Datacap Taskmaster Capture 8.0.1

This procedure provides instructions on how to uninstall IBM Datacap Taskmaster Capture
8.0.1 using Windows.
1 From the Windows Start menu, select Settings, select Control Panel, select
Administrative Tools, and select Programs and Features. The Programs and Features
window opens with a list of the software installed on the machine.
2 Scroll down to IBM Datacap Taskmaster Capture 8.0.1 and click Uninstall . A message
box is displayed prompting you to confirm that you want to remove the software.
3 Click Yes. Windows displays a Preparing to Install... window,
An IBM Datacap Taskmaster Capture 8.0.1 window with a progress bar are displayed.
When the uninstall process is finished, a message box is displayed prompting you to
reboot your system.
4 Click Yes. The message box closes, and the machine reboots.
Remove Accounts from Administrator and Backup Operator Groups

A number of IBM Datacap Taskmaster Capture components required that domain/Windows
accounts be added to the machine's Administrator or Backup Operator Groups. Repeat this
procedure on each machine on which Taskmaster was installed.
Using Windows Administrative Tools > Computer Management > Local Users and Groups >
Groups, remove all Taskmaster-specific accounts from the Administrators and Backup
Operators groups.
Delete Registry Keys

Every machine on which IBM Datacap Taskmaster Capture components were installed
contains Taskmaster-specific registry keys that should be deleted. Repeat this procedure on
each machine on which Taskmaster was installed.
Using Windows Regedit, delete the Datacap registry keys:
On Windows XP and Windows 2003:
• \HKEY_LOCAL_MACHINE\SOFTWARE\Datacap
On Windows 7 or Windows 2008 (64 bit):
• \HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Datacap
Remove Web Sites and Virtual Folders

Machines on which Taskmaster Web, RV2, and Web Rulerunner Service (Rulerunner running
as a web service) were installed and configured, contain web sites and virtual folders that
should be deleted. Repeat this procedure on each web server machine on which Taskmaster
was installed.

Using Windows Administrative Tools > Internet Information Services (IIS) Manager, expand
the computer, expand Sites, right-click the web site or virtual folder, and select Remove from
the shortcut menu.
Reset Application Pool Process Model Identities

Windows 2008 servers on which Taskmaster Web, RV2, and Web Rulerunner Service
(Rulerunner running as a web service) were installed and configured, contain one or more
Application Pool Identities that should be deleted.
Using Windows Administrative Tools > Internet Information Services (IIS) Manager, expand
the computer, and in the Connections pane, select Application Pools. The Application Pools
are listed in the center pane.
For each Taskmaster-specific application pool, right-click the application pool and select
Remove from the shortcut menu.
To ensure the other application pools are not using a Taskmaster account as the Process Model
Identity, select the application pool, and in the Actions pane, click Set Application Pool
Defaults. The Application Pool Defaults window opens and the account that is being used is
displayed.
To change the Process Model Identity account, click in the account field to display the browse
button. Click the browse button. The Application Pool Identity window opens. Select a
different account, then click OK to close the Application Pool Identity window, and click OK
again to close the Application Pool Defaults window.
Remove Process Identity from Machine.Config File

The machine.config file was updated on Windows 2003 servers on which Taskmaster Web,
RV2, and Web Rulerunner Service (Rulerunner running as a web service) were installed. The
Taskmaster account information should be removed from this file. Repeat this procedure on
each Windows 2003 web server on which a Taskmaster component was installed.
1 Using Windows Explorer, navigate to and use a text editor such as Notepad to open
2 Locate the line containing only <system.web> and the next line starting with
<processModel … that contains information for the Taskmaster Windows account. It
will look something like this:
account<processModel autoConfig="true" enable="true"
userName="DOMAIN\TaskmasterAccountName" password="AccountPassword"/>
3 Remove the account information so the line looks like this:
account<processModel autoConfig="true"/>

Delete Program Shortcuts

Program shortcuts were created on every machine on which a Taskmaster component was
installed and should be deleted. Repeat this procedure on each machine on which a
Taskmaster component was installed.
Delete shortcuts located on the desktop.
Delete shortcuts located on the Start menu.
Delete Remaining Folders

This procedure provides instructions on how to locate and delete folders that were not removed
by the uninstall process.
1 Using Windows Explorer, navigate to and delete the C:\Datacap folder. If access is
denied, delete individual subfolders before deleting the C:\Datacap folder.
2 If you processed batches using the Taskmaster Web Client, a Scan Into folder was used
to temporarily hold images during scanning. If this folder was outside C:\Datacap,
navigate to and delete the folder.


Appendix A
Single Machine Setup Checklist

This appendix provides a summary of the account and configuration settings that are required
to run some of the IBM Datacap Taskmaster Capture 8.0.1 software components on a single
Windows 7 IIS 7 machine for demonstration or proof of concept purposes. This configuration
uses a single Domain/Windows account that has administrator rights on the machine.
Single IIS 7 Machine Installation

On Do This
Workstation Set Up Implementer's User ID
Add/ensure Domain/Windows User ID of implementer is in Workstation's
Administrator group to allow implementer to run InstallShield on
Workstation
Control Panel > Administrative Tools > Computer Management > Local
Users and Groups > Groups > Administrators
Workstation Ensure Microsoft .NET Framework 3.5.1 is Installed
Start > Control Panel > double-click Programs and Features
Select Turn Windows features on or off
Select Microsoft .NET Framework 3.5.1 and click OK
Reboot the machine when prompted
Workstation Run InstallShield Wizard on Workstation
Install all components, including separately licensed applications and
connectors to which you are entitled
Workstation Reboot
Start Taskmaster Server on Single Machine

On Do This
Workstation Start Taskmaster Server Service
Start > All Programs > Datacap > Taskmaster Server > Taskmaster Server
Manager > Start

Run Taskmaster Client on Single Machine

On Do This
Workstation Run Thick Client 1040EZ Application
Double-click the 1040EZ icon, and sign on as Taskmaster user "admin"
Run/test thick client and confirm each job in the workflow is processing
correctly
Exit Taskmaster Client
Workstation Review Default Installation (Users, Groups, Stations)
Double-click the 1040EZ icon, and sign on as Taskmaster user "admin"
Review default users, groups, stations
Set Up RV2 on Single Machine

On Do This
Workstation Ensure Required IIS Components are Installed
Start > All Programs > Control Panel > Programs and Features
Turn Windows features on or off
Expand Internet Information Services, expand Web Management Tools,
select IIS Management Console
Expand World Wide Web Services, expand Application Development
Features, select ASP and ASP.NET
Expand Common HTTP Features, select Static Content
Workstation Set Up RV2 Web Site
Start > All Programs > Control Panel > Administrative Tools >Internet
Information Services Manager
Right-click Default Web Site > Add Application
Alias: RV2
Physical path: C:\Datcap\RV2
Application Pools > Set Application Pool Defaults:
Enable 32-Bit Applications = True
Set Process Model Identity to Implementer's Windows Account
Ensure Web Server, Application Pool, Default Web Site are all started
Workstation Add RV2 Address as Trusted Site
Open IE > Tools > Internet Options > Security tab > Trusted Sites > Sites
>Add server address

On Do This
Workstation Log onto RV2, View Standard Report
http://127.0.0.1/RV2/Login.aspx
Select Batch Productivity report, select 1040EZ, click Run Report
Configure Taskmaster Web on Single Machine

On Do This
Workstation Stop Taskmaster Server Service
Manager > Stop
Workstation Ensure Required IIS Components are Installed
Start > All Programs > Control Panel > Programs and Features
Turn Windows features on or off
Expand Internet Information Services, expand Web Management Tools,
select IIS Management Console
Expand World Wide Web Services, expand Application Development
Features, select ASP and ASP.NET
Expand Common HTTP Features, select Static Content
Workstation Create Taskmaster Web Site
Start > All Programs > Datacap > Support > Web Configuration >
Taskmaster Web Server Configuration
Click Configure
Start > Control Panel > Administrative Tools > Internet Information
Services > Default Web Site > Actions pane > Manage Web Site > Restart
Configure IE 7 and Run Taskmaster Web Client on Single Machine

On Do This
Workstation Add TMWeb.net Address as Trusted Site
Open IE > Tools > Internet Options > Security tab > Trusted Sites > Sites
>Add server address
Workstation Configure and Test IE 7 32-Bit only
Start > All Programs > Datacap > Support > Web Configuration >
Taskmaster Web Client Configuration
Click Configure
Start IE > enter http://localhost/tmweb.net/ietest.aspx > Click Yes to
download
Click Test

On Do This
Manager > Start
Workstation Run Thin Client
Start IE, and enter the URL (http://127.0.0.1/tmweb.net )
Sign on as Taskmaster user "admin"
Run/test thin client using the images found in the application's process
folder, and confirm each job in the workflow is processing correctly (will
have to switch back to thick client to run some jobs)
Configure Single Thread Rulerunner Quattro

On Do This
Workstation Shut Down Taskmaster Software
Taskmaster Client software
Taskmaster Web and web services
Taskmaster Server Service
Workstation Add Quattro Account on Workstation
Add Workstation's local System account to Workstation's Administrators
Group
Workstation Grant Quattro Log On as a Service Right
Start > Settings > Control Panel > Admin Tools > Services
Right-click Datacap Rulerunner Quattro Service > Properties
Click Log On tab > select or ensure the Local System account is selected,
click Apply
Workstation Grant DQCS Log on as a Service Right
Right-click Datacap Quattro Control Service > Properties
Click Log On tab > select or ensure the Local System account is selected,
click Apply
Workstation Configure DQCS Start Up Behavior
Optional:
Right-click Datacap Rulerunner Quattro Control Service > Properties
Startup Type = Automatic > click Apply

On Do This
Workstation Set Location of Datacap.xml
Start > All Programs > Datacap > Taskmaster Client > Taskmaster
Application Manager
Click Service tab, change path to reflect the location where the datacap.xml
file resides (C:\Datacap\datacap.xml)
Manager > Start
Workstation Encrypt Taskmaster Login Password
Windows Explorer > open C:\Datacap\support\Sit
Double-click SitManager.exe > type in password, click Encrypt
Click Test, click OK
Highlight encrypted string and copy to clipboard or text file
Workstation Configure Quattro to Run 1040EZ Tasks
Start > All Programs > Datacap > Taskmaster Client > Rulerunner Quattro
Manager > Stop
Click Datacap Login > select Taskmaster Authentication and enter
credentials > click Connect > click OK
Click Workflow:Job:Task tab > expand 1040EZ, expand Servers node,
select server, select Admin and Engine databases
In right pane, right-click > select Threads > select Add Thread
In left pane, under 1040EZ, under Main Job > click the box next to PageID,
click PageID label and drag onto thread in right pane
Repeat for Recognize and Export tasks
Click Save, click Yes, click Save
Click Datacap Login tab, click Disconnect
Reset login credentials if not using Taskmaster Authentication
Workstation Confirm Quattro's 1040EZ Task Profiles in Taskmaster Application
Service
Application Manager
Select 1040EZ, click Quattro tab, ensure PageID, Recognize, and Export
task profiles are listed, delete any other profiles
Workstation Stop and Restart Taskmaster Server Service
Manager > Stop
After Service stops, click Start

Run Taskmaster Client 1040EZ Tasks using Quattro

On Do This
Workstation Start and Run 1040EZ
Start > All Programs > Datacap > Applications > 1040EZ
Log in
Double-click Scan shortcut
Click Stop
Repeat to create additional batches for Quattro to process, then exit from
1040EZ
Workstation Start Quattro
Manager > Start
Workstation Monitor Quattro Processing using Windows Explorer
Open 1040EZ \batches folder, open each batch folder and press <F5>
periodically to see additional files.
Stop Quattro
Manager > Stop
Workstation Run 1040EZ Verify
Start > All Programs > Datacap > Applications > 1040EZ
Log in
Double-click Verify shortcut, verify all batches, then exit
Workstation Start Quattro
Manager > Start
Workstation Monitor Quattro Processing using Windows Explorer
Open 1040EZ \batches folder, open each batch folder and press <F5>
periodically

Appendix B
Client-Server Setup Checklist

This appendix provides a summary of the account and configuration settings that are required
to run IBM Datacap Taskmaster Capture 8.0.1 software components in a client-server
environment for demonstration, proof of concept, development and test purposes. This
configuration uses a number of Domain/Windows accounts. The implementer must have an
account that has administrator rights on every machine on which Taskmaster is to be installed.
Server Setup
Install Taskmaster Server on Server

On Do This
Server Set Up Implementer's User ID
Add/ensure Domain/Windows User ID of implementer is in Administrators
group on every machine to allow implementer to run InstallShield
Server Ensure Microsoft .NET Framework 3.5.1 is Installed
Start > Control Panel > Administrative Tools > Server Manager > Programs
and Features
In the Server Manager hierarchy pane, select Features
Click Add Features
Select .NET Framework 3.5.1 Feature, click Next
Click Install
Server Run InstallShield Wizard - Windows 2003, Windows 2008
Install Taskmaster Server component and separately licensed connectors to
which you are entitled
Server Reboot

Configure Taskmaster on Server

On Do This
Server Ensure Domain/Windows Account Exists for Taskmaster Server Service
Ensure Domain/Windows account exists for Taskmaster Server Service
Grant Taskmaster Server Service Log On as a Service Right
Control Panel > (System and Maintenance) > Admin Tools > Services > right-
click Datacap Taskmaster Server Service > Properties > Log On tab
Select This Account and enter domain name, user name and password of the
Taskmaster Server Service User you just set up, click Apply, returns message
that user granted Log On as a Service right
To start Taskmaster Server Service automatically on reboot
Control Panel > (System and Maintenance) > Admin Tools > Services > Right-
click Datacap Taskmaster Server Service > Properties > General tab > select
Startup Type of Automatic
Server Ensure Domain/Windows Accounts Exist for End Users
Server Share Datacap Folder and Set Sharing Permissions (Windows 2003)
Right-click C:\Datacap folder and select Sharing and Security
Click Sharing tab, click Share this Folder (as Datacap)
Click Permissions button
1 Add local ASP.NET Machine Account (Server\ASPNET) and local Internet
Guest Account (Server\IUSR_SERVER) and set both to allow Full Control
2 Add/ensure Domain/Windows User IDs of developers are set to allow Full
Control
3 Add/ensure Domain/Windows User ID of Taskmaster Server Service is set to
allow Full Control
4 When Batches folders are staying on Server in C:\Datacap\Application path,
add/ensure Domain/Windows User IDs of Taskmaster end users are set to
allow Full Control

On Do This
Server Share Datacap Folder and Set Up Sharing Permissions (Windows 2008)
Right-click C:\Datacap folder and select Properties
Click Sharing tab, click Advanced Sharing
Click Share this Folder (as Datacap)
1 Add NETWORK SERVICE and local IUSR and allow Full Control
Control
allow Full Control
allow Full Control
Server Set Up Security on Shared Folder (Windows 2003)
Click Security tab
1 Add/ensure Domain/Windows User IDs of developers who can change
existing Taskmaster applications are set to allow Read & Execute (this
developer cannot create new applications)
2 Add/ensure Domain/Windows User IDs of developers who can create new
Taskmaster applications in the C:\Datacap folder are set to allow Full Control
allow Read & Execute

On Do This
Server Set Up Security on Shared Folder (Windows 2008)
Click Security tab
1 Add/ensure Domain/Windows User IDs of developers who can change
existing Taskmaster applications are set to allow Read & Execute (this
developer cannot create new applications)
2 Add/ensure Domain/Windows User IDs of developers who can create new
Taskmaster applications in the C:\Datacap folder are set to allow Full Control
Server Set Up Security on Datacap\RRS (Windows 2003)
Right-click C:\Datacap\RRS folder and select Sharing and Security
Click Security tab
Add local ASP.NET Machine Account (Server\ASPNET) and local Internet
Guest Account (Server\IUSR_SERVER) and set both to allow Read & Execute
Server Set Up Security on Datacap\RRS (Windows 2008)
Right-click C:\Datacap\RRS folder and select Properties
Click Security tab
Add NETWORK SERVICE and local IUSR and allow Read & Execute
Server Set Location of Datacap.xml
Start > All Programs > Datacap > Taskmaster Client > Taskmaster Application
Manager
Click Service tab, change path to reflect the location where the datacap.xml file
will reside (\\Server\Datacap\datacap.xml)

Developer Workstation Setup
Install Taskmaster Client on DevWorkstation

On Do This
DevWorkstation Ensure Microsoft .NET Framework 3.5.1 is Installed (Windows 7)
DevWorkstation Run InstallShield Wizard (Windows XP, Windows 7)
Install Taskmaster Client components, including separately licensed
applications, and connectors to which you are entitled
DevWorkstation Optional: Install Scanner
Ensure scanner works outside of Taskmaster
Datacap Application Copy Wizard

On Do This
DevWorkstation Start Datacap Studio to Use Application Wizard
Start > All Programs > Datacap > Datacap Studio > Datacap Studio > Close
DevWorkstation Ensure Correct Datacap.xml File is in Use
In Datacap Studio, click Settings button
Click DCapp tab
Set path to local datacap.xml > OK
Close and restart Datacap Studio
DevWorkstation Copy APT Application to Taskmaster Server
Click Application Wizard button > Next > Copy an existing RRS
application > Next >
Application: APT
Root folder on target system: \\Server\Datacap
Datacap folder on workstation: C:\Datacap
Taskmaster Web folder on WebServer: leave blank or use
\\WebServer\Datacap\tmweb.net
Rename Copy: Not applicable
New Name: Not applicable
Click Next > Finish

On Do This
DevWorkstation Click View Logs to open log (found in \\Server\Datacap\APT) and search
for errors and warnings that you need to fix
DevWorkstation Copy Datacap.xml from DevWorkstation to Taskmaster Server
Windows Explorer > C:\Datacap
Windows Explorer > \\Server\Datacap
Copy datacap.xml file from C:\Datacap to \\Server\Datacap
DevWorkstation Set Location of Taskmaster Server and Datacap.xml
Application Manager
Select APT - Ensure correct paths reflected on Application tab
Click Taskmaster tab > Change Server name/address to correct Taskmaster
Server
Click Service tab > Ensure path reflects location of datacap.xml on
Taskmaster Server

Complete Server Configuration
Update Datacap.xml on Server

On Do This
Server Update Datacap.xml
Make a list of the applications that exist and their locations on Server
Open \\Server\Datacap\datacap.xml in Notepad
Edit contents of datacap.xml to reflect only those applications that exist and
have been configured for use
Set Security Permissions

On Do This
Server Set Up Security on Datacap\Application Folder (Windows 2003)
Right-click c:\Datacap\Application folder and select Sharing and Security
On Security tab
1 Add local ASP.NET Machine Account (Server\ASPNET) and local Internet
Guest Account (Server\IUSR_SERVER) and set to allow Full Control
Control
allow Full Control
allow Full Control
Server Set Up Security on Datacap\Application Folder (Windows 2008)
Right-click c:\Datacap\Application folder and select Properties
On Security tab
1 Add NETWORK SERVICE and local IUSR and set to allow Full Control
Control
allow Full Control
allow Full Control

Run Taskmaster Client on DevWorkstation

On Do This
Server Start Taskmaster Server Service
Manager > Start
DevWorkstation Test Thick Client Application
Log into Windows as end user
Start the application by clicking the Taskmaster Client shortcut that points
to the application files on the Server and sign on as Taskmaster user
"admin"
Run/test thick client and confirm each job in the workflow is processing
correctly
Exit client
DevWorkstation Optional: Review Default Installation (Users, Groups, Stations)

Set Up Taskmaster APT to Process Your Invoice Images

On Do This
Various Shut Down Taskmaster Software
Shut down the Taskmaster software in the following sequence:
Taskmaster Client software for all applications (including Taskmaster
Client, Taskmaster Web Client, Taskmaster Client Service, Rulerunner
Quattro Service, Datacap Studio, Batch Pilot, etc.)
Taskmaster Web and any Taskmaster web services (RV2, WRRS,
Fingerprint Service, etc.)
Server Back Up then Delete Sample Input Images
In Windows Explorer, navigate to, and make a backup copy of the
\\Server\Datacap\APT\images\Input folder
Delete the sample images in the Input folder
Server Copy Your Images to Input Folder
Copy your own invoice images to the \\Server\Datacap\APT\images\Input
folder
Server Add Your Vendors to the Demo Vendor List
Open Windows Explorer, navigate to \\Server\Datacap\APT\dco_APT
Double-click the Add Vendor Demo.exe file
If vendor information is displayed for a vendor in the upper part of the
window, click Clear
For each vendor, enter a Vendor Name, a Vendor Zip code, and either enter
a Vendor Number or select the Generate Random option, then click Add
Close the Add Demo Vendor window when you have added the vendors
associated with your invoice images

On Do This
Server Add Your PO Line Items to POTable
Open Windows Explorer, navigate to, and make a backup copy of the
\\Server\Datacap\APT\APTLook.mdb
From the Windows Start menu, select All Programs, select Microsoft
Office, and select Microsoft Office Access
On the File menu, select Open, navigate to
\\Server\Datacap\APT\APTLook.mdb, select it, and click Open
Double-click POTable to open it
On the Edit menu, point to Go To, then select Last
On the Edit menu, point to Go To, then select New Record
For each line item, press the Tab key to move to the next column, and
enter data in each column (purchase order number, line item quantity, line
item number, description of item, and purchase order line number)
Repeat the previous two steps to add the purchase order line items on
which you want APT to perform matching
On the File menu, select Save, then close the POTable window, the
APTLook window, and the Microsoft Access window
DevWorkstation Run Taskmaster APT
Process your invoice images

End User Workstation and Permissions Setup

On Do This
Workstation Ensure Microsoft .NET Framework 3.5.1 is Installed (Windows 7)
Workstation Run InstallShield Wizard (Windows XP, Windows 7)
Install the Taskmaster Client component - exclude Datacap Studio, DotEdit,
and NENU components, include separately licensed applications, and
Server Set Up Sharing Permissions on Datacap Folder
Add/ensure Domain/Windows User IDs of Taskmaster end users are set to
allow Full Control
Server Set Up Security on Datacap Folder
Server Set Up Security on Datacap\Application Folder
allow Full Control
Workstation Copy Taskmaster Client Shortcut to Workstation
Copy shortcut from either the DevWorkstation or Server to the Workstation
Workstation Optional: Install Scanner
Ensure scanner works outside of Taskmaster, set up application to use scanner
Workstation Set Location of Datacap.xml
Manager
Click Service tab > Ensure path reflects location of datacap.xml on Taskmaster
Server

Install and Configure RV2

On Do This
Server Ensure Domain/Windows Account Exists for RV2
When Taskmaster Web, RV2, or Web Rulerunner Service are installed on the
same WebServer, they must use the same domain/Windows account.
Ensure Domain/Windows account exists for RV2
Server Stop Taskmaster Server Service
Manager > Stop
WebServer Add RV2 Account to WebServer Administrators Group
WebServer Confirm IIS Configuration (Windows 2003)
Server Set RV2 Sharing Permissions for Datacap Folder (Windows 2003)
Add RV2 account set to allow Read
Server Set Up Security for RV2 on Datacap Folder (Windows 2003)
Click Security tab
Add RV2 account set to allow Read & Execute
WebServer Update ASP.NET Process Identity in Machine.Config File (Windows
2003)
Using Notepad, open
c:\windows\microsoft.net\framework\v2.0.50727\config\machine.config
Change <processModel autoConfig="true"> to reflect RV2 account user
name and password
WebServer Grant RV2 Account Access to IIS Metabase (Windows 2003)
Run c:\windows\microsoft.net\framework\v2.0.50727\aspnet_regiis.exe -ga
for Domain\RV2AccountName
WebServer Install RV2 on WebServer (Windows 2003)
Install only RV2 component

On Do This
WebServer Set Location of Datacap.xml
Application Manager
file will reside (\\Server\Datacap\datacap.xml)
WebServer Set Up RV2 Web Site (IIS 6)
Right-click Default Web Site > New > Virtual Directory
Alias: RV2
Physical path: C:\Datcap\RV2
Access Permissions: Read, Run scripts, and Execute
WebServer Set Other Parameters for RV2 Web Site (IIS 6)
Start > All Programs > Control Panel > Administrative Tools > IIS > expand
computer, expand Web Sites, right-click Default Web Site > Properties
Click Configuration button > Application Configuration > Options tab >
Select Enable session state, set Timeout, select Enable parent paths
Documents tab > add/ensure default.aspx is displayed
ASP.NET tab > click Edit Configuration button > General tab
Application tab > Request execution timeout > 1200
State Management tab > set Session timeout

On Do This
Server Ensure Domain/Windows Account Exists for RV2
When Taskmaster Web, RV2, or Web Rulerunner Service are installed on
the same WebServer, they must use the same domain/Windows account.
Ensure Domain/Windows account exists for RV2
Manager > Stop

On Do This
WebServer Ensure Microsoft .NET Framework 3.5.1 is Installed
and Features
Click Add Features
Click Install
WebServer Ensure Required IIS Components are Installed
Start > All Programs > Control Panel > Administrative Tools > Server
Manager
Expand Roles, select Web Server (IIS)
In Web Server (IIS) pane:
Under Common HTTP Features, ensure Static Content is installed
Scroll down to Role Services, under Application Development ensure
ASP.NET and ASP modules are installed
Scroll down further to Management Tools, ensure IIS Management Console
is installed
Server Set RV2 Sharing Permissions for Datacap Folder (Windows 2008)
Right-click C:\Datacap folder and select Sharing and select Advanced
Sharing
Should be shared (as Datacap)
Add RV2 account set to allow Read
Server Set Up Security for RV2 on Datacap Folder (Windows 2008)
Click Security tab
Add RV2 account set to allow Read & Execute
WebServer Install RV2 on WebServer (Windows 2003)
Install only RV2 component
Application Manager

On Do This
WebServer Set Up RV2 Web Site (IIS 7)
Connections pane > Expand the Server > expand Sites
Right-click Default Web Site, select Add Application... and select or enter
the following on the Add Application dialog:
Alias: RV2
Physical path: C:\Datacap\RV2
Connections pane, select Application Pools > in Actions pane, select Set
Application Pool Defaults
Ensure Enable 32-Bit Applications, set to True
Click browse button to right of Process Model Identity, select Custom
account, click Set and enter RV2 Windows account information, click OK
Ensure Web Server, Application Pool and Default Web Site are all started
View RV2 Reports for APT

On Do This
Start > All Programs > Datacap > Taskmaster Server > Taskmaster
Server Manager > Start
DevWorkstation Add RV2 Address as Trusted Site
Open IE > Tools > Internet Options > Security tab > Trusted Sites >
Sites > Add server address
DevWorkstation Log onto RV2, View Standard Report
http://ServerName/RV2/Login.aspx
Select Batch Productivity report, select APT, click Run Report
DevWorkstation Create RV2 Report Filter
On home page, select report
Click Manage Filters
Enter name for new filter, click Add
Select column name, select action, enter value
Click Add Field to add another field
Select Public or Private
Click Save
Click Run Report

On Do This
DevWorkstation Add Reports to RV2 Dashboard
On home page, click Dashboard
Select report and application name, select filter
Click Add to add another report
Click Refresh and select a refresh interval

Install and Configure Taskmaster Web
Configure Taskmaster Web on Windows 2003, IIS 6 Server

On Do This
Server Ensure Domain/Windows Account Exists for Taskmaster Web
Ensure domain/Windows account exists for Taskmaster Web
Manager > Stop
Server Set Taskmaster Web Sharing Permissions for Datacap Folder (Windows
2003)
Add Taskmaster Web account set to allow Read
Server Set Up Security for Taskmaster Web on Datacap Folder (Windows 2003)
Click Security tab
Add Taskmaster Web account set to allow Read & Execute
WebServer Add or Ensure Upload Limit Setting is Large Enough in web.config
Navigate to and open the C:\Datacap\tmweb.net folder, open web.config file in a
text editor such as Notepad
Within the <system.web> element, locate or add the
Depending on the usual size of the images that are being uploaded, you can
increase the size, for example:

On Do This
WebServer Add or Ensure File Transfer Limit Setting is Large Enough
Enable metabase edit-while-running.
On the Server, in Windows Explorer, navigate to and open the
\windows\system32\inetsvr folder, scroll down to the metabase.xml file and open
it in a text editor such as Notepad.
Locate and change the value for AspMaxRequestEntityAllowed= from 204800
to 10238976 (or larger)
When you have made changes, save and close the file.
Disable metabase edit-while-running.
WebServer Install Taskmaster Web on WebServer (Windows 2003)
Install only Taskmaster Web component
WebServer Confirm IIS Configuration (Windows 2003)
WebServer Update ASP.NET Process Identity in Machine.Config File (Windows 2003)
Using Notepad, open
c:\windows\microsoft.net\framework\v2.0.50727\config\machine.config
Change <processModel autoConfig="true"> to reflect Taskmaster Web account
user name and password
WebServer Grant Taskmaster Web Account Access to IIS Metabase (Windows 2003)
Run c:\windows\microsoft.net\framework\v2.0.50727\aspnet_regiis.exe -ga for
Domain\TaskmasterWebAccountName
WebServer Create and Share (Nested) Virtual Directory for Taskmaster Web
Start > Settings > Control Panel > Admin Tools > IIS > expand computer >
expand Web Sites folder > right-click Default Web Site and select New >
Virtual Directory
Alias: tmweb.net
Web Site Content directory: c:\Datacap\tmweb.net folder
Access Permissions: Read, Run scripts, Execute

On Do This
WebServer Set Other Parameters for (Nested) Taskmaster Web Site
Start > Settings > Control Panel > Admin Tools > IIS > expand computer,
expand Web Sites, expand Default Web Site, right-click tmweb.net web site >
Properties
Virtual Directory tab > click Configuration button > Application Configuration
> Options tab > Select Enable session state, set Timeout, select Enable parent
paths
ASP.NET tab > click Edit Global Configuration button > General tab
State Management tab > Session timeout = 20
State Management tab > set Session timeout
WebServer Set Web Site Isolation Mode
Admin Tools > IIS > expand computer > Right-click Web Sites >Web Site
Properties > Service tab, select WWW Isolation Mode: Run Service in IIS 5.0
Isolation Mode.
WebServer Select Web Service Extensions
Admin Tools > IIS > expand computer > click Web Service Extensions
Select/ensure Active Server Pages, ASP.NET v2.0.50727, and Server Side
Includes are Allowed.
WebServer Set Up Web Sharing and Security Settings on TaskRun Folder
In Windows Explorer, navigate to and right-click c:\Datacap\TaskRun folder,
select Properties
Web Sharing tab > Default Web Site , Share this folder >
Alias = TaskRun
Application Permissions = None, and Access Permissions Write and Read
Security tab > Add local ASP.NET Machine Account (Server\ASPNET) and
local Internet Guest Account (Server\IUSR_SERVER) and set both to allow
Modify

On Do This
WebServer Set Up TaskRun Virtual Folder
Admin Tools > IIS > right-click TaskRun folder >Properties
Virtual Directory tab > click Remove
Directory Security tab > top Edit button > Authentication Methods > Select
Anonymous access, clear Integrated Windows authentication, OK
ASP.NET tab > confirm version
HTTP Headers tab > Select Enable Content Expiration, select Expire
Immediately, click Apply
WebServer Confirm Server.INI File Points to TaskRun
Using Notepad, open c:\Datacaptmweb.net\server.ini and ensure
TempFolder=/TaskRun/
WebServer Change Secure Socket Layer Setting in Server.INI
If using web site SSL, also do the following:
Using Notepad, open c:\Datacap\tmweb.net\server.ini and ensure
UseSSL=1
Manager
WebServer Restart IIS
Manager > Start
Configure Taskmaster Web on Windows 2008 IIS 7 Server

On Do This
Server Ensure Domain/Windows Account Exists for Taskmaster Web
Ensure domain/Windows account exists for Taskmaster Web
Manager > Stop

On Do This
WebServer Ensure Microsoft .NET Framework 3.5.1 is Installed
and Features
Click Add Features
Click Install
WebServer Ensure Required IIS Components are Installed
Manager
Scroll down further to Management Tools, ensure IIS Management Console is
installed
Server Set Taskmaster Web Sharing Permissions for Datacap Folder (Windows
2008)
Should already be shared (as Datacap)
Add Taskmaster Web account set to allow Read
Server Set Up Security for Taskmaster Web on Datacap Folder (Windows 2008)
Click Security tab
Add Taskmaster Web account set to allow Read & Execute
WebServer Add or Ensure Upload Limit Setting is Large Enough in web.config
Open C:\Datacap\tmweb.net folder, open web.config file in Notepad
Within the <system.web> element, locate or add the
Increase size to reflect usual size of images, for example:

On Do This
WebServer Install Taskmaster Web on WebServer (Windows 2008)
Install only Taskmaster Web component
WebServer Create Taskmaster Web Site
Start > All Programs > Datacap > Support > Web Configuration > Taskmaster
Web Server Configuration
Click Configure
Start > Control Panel > Admin Tools > IIS
Expand computer > Sites > Default Web Site > in Connections pane, select
Default Web Site > in Actions pane, under Manage Web Site > click Restart
WebServer Set Taskmaster Web Application Pool Identity
Connections pane, select Application Pools > in Actions pane, select Set
Application Pool Defaults
Ensure Enable 32-Bit Applications, set to True
Click browse button to right of Process Model Identity, select Custom account,
click Set and enter Taskmaster Web Windows account information, click OK
Ensure Web Server, Application Pool and Default Web Site are all started
WebServer Set Up Web Sharing and Security Settings on TaskRun Folder
In Windows Explorer, navigate to and right-click c:\Datacap\TaskRun folder,
select Properties
Web Sharing tab > Default Web Site , Share this folder > Alias = TaskRun
Application Permissions = None, and Access Permissions Write and Read
Security tab > Add NETWORK SERVICE and local IUSR and set both to allow
Modify
WebServer Set IIS ASP Request Size Limit
Admin Tools > Internet Information Services (IIS) Manager
Connections pane > Select the WebServer, in Home pane, scroll down to the
IIS area and double-click ASP
ASP properties pane > Behavior section, expand Limits Properties.
Locate Maximum Requesting Entity Body Limit (maxRequestEntityAllowed),
increase value (increase size)
Click Apply
WebServer Confirm Server.INI File Points to TaskRun
TempFolder=/TaskRun/

On Do This
WebServer Change Secure Socket Layer Setting in Server.INI
If using web site SSL, also do the following:
UseSSL=1
Manager
WebServer Restart IIS
Manager > Start

Configure and Test Remote Workstation
Package the Client Configuration Tool

On Do This
Any machine Package the Client Configuration Tool
with
Open C:\Datacap\support\WebConfiguration folder
Taskmaster
installed Make backup copy of WebClientConfig.exe.config file
Open WebClientConfig.exe.config file and change server name in:
<value>http://localhost/tmweb.net</value>
Save and close .config file
Send WebClientConfig.exe.config, Datacap.Config.dll, and
WebClientConfig.exe to user with instructions to Add TMWEb.net Address as
Trusted Site, and Configure and Test Internet Explorer 6, 7 or 8.

On Do This
Workstation Add TMWeb.net Address as Trusted Site
Start IE > Tools > Internet Options > Security tab > Select Trusted sites >
Click Sites button > Trusted sites dialog
On Trusted sites dialog, clear Require server verification, and add either the
default IP address of the Taskmaster WebServer (http://127.0.0.1) or the URL
of the WebServer as it is defined in your network's DNS
(http://WebServerName or https://WebServerName), click OK.
Click OK to close Security settings dialog and Internet Options window
Configure and Test IE 6, 7 or 8 using Tool

You can use the Taskmaster Web Client Configuration tool if you have access to the
appropriate files. For more information on packaging the files, see Package the Client
Configuration Tool.
On Do This
On 64-bit operating system, you must use 32-bit version of IE. On Windows
2008, when Internet Explorer Enhanced Security Configuration for Users is
ON, access Taskmaster Web from a different machine.
Workstation Configure IE 6, 7 or 8
Double-click the WebClientConfig.exe file
Enter or ensure the URL is the WebServer's IP address or name
(http://WebServerName/tmweb.net)
Click Configure

On Do This
Workstation Test IE
Start IE, enter the appropriate WebServer URL and test page
(http://127.0.0.7/tmweb.net/ietest.aspx,
http://WebServerName/tmweb.net/ietest.aspx, or
https://WebServerName/tmweb.net/ietest.aspx).
Click Yes to download Datacap TIFF Viewer, Thumbnails, and DataEdit
Controls
Click Test - red Xs change to green checkmarks
Configure and Test IE 6, 7 or 8 Manually

If you do not have access to the Taskmaster Web Client Configuration tool, you can configure
Internet Explorer manually.
On Do This
Workstation Configure IE 6, 7 or 8 on Workstation
Start Internet Explorer
Tools > Internet Options > Security tab
Select Trusted sites > Click Sites button
On Trusted sites dialog, clear Require server verification, and add either the
default IP address of the Taskmaster Server (http://127.0.0.1) or the URL of the
WebServer as it is defined in your network's DNS (http://WebServerName or
https://WebServerName)
Security tab > Click Custom level button > Security settings dialog - Trusted
Sites Zone:
Enable: Download signed ActiveX controls
Enable: Download unsigned ActiveX controls
Enable: Initialize and script ActiveX controls not marked as safe
for scripting
Scroll down to Miscellaneous settings > Enable Include local directory path
when uploading files to a server
Close IE
Workstation Test IE
Start IE, enter the appropriate WebServer URL and test page
(http://127.0.0.7/tmweb.net/ietest.aspx,
http://WebServerName/tmweb.net/ietest.aspx, or
https://WebServerName/tmweb.net/ietest.aspx).
Click Yes to download Datacap TIFF Viewer, Thumbnails, and DataEdit
Controls
Click Test - red Xs change to green checkmarks

Run Taskmaster Web Client Application

On Do This
Manager > Start
Workstation Run Web Client
Start IE, and enter the appropriate WebServer URL
(http://127.0.0.7/tmweb.net, http://WebServerName/tmweb.net, or
https://WebServerName/tmweb.net).
Sign on as Taskmaster user "admin" and Station "remote"
Run/test thin client using the images on the WebServer in the application's
images folder, and confirm each job in the workflow is processing correctly
(you will have to switch back to thick client to run some jobs)

Install and Configure Rulerunner Quattro
Configure Type of Quattro Authentication

Quattro can use either Windows Authentication or Taskmaster Authentication.

On Do This
Server Create/ensure domain exists in which Taskmaster-specific
AD/LDAP/LLLDAP security groups can be created
Server Create/ensure AD/LDAP/LLLDAP security group exists
Server Create/ensure Quattro Account Exists and is part of security group
Various Shut Down Taskmaster Client and Web Software
Server Configure Taskmaster Server Service to use Windows Authentication
Manager > Stop
Taskmaster tab > click Show Advanced, enter authentication string
Click Save
Service tab > click Start
DevWorkstation Add Taskmaster Group to Application
Start Taskmaster Client Application as Admin
Settings > Groups
Click Add, and enter a Group ID that is a concatenation of:
--A dot
--The domain to which your Taskmaster-specific security group
belongs
Click Apply, then OK
Expand Privileges, select appropriate privileges, click Apply, then OK
Expand Permissions, select appropriate permissions, click Apply, click OK,
click Apply, click Done

On Do This
DevWorkstation Add Taskmaster Station to Application
Settings > Station
Click Add, enter name of QServer machine, click Apply, click OK
Expand Permissions, select appropriate permissions, click Apply, click OK
Click Advanced button, set Maximum number of virtual stations to 99, click
OK, click Apply, click OK, click Done
DevWorkstation Add Taskmaster User to Application (LLLDAP or Taskmaster
Authentication only)
Settings > Users
Click Add, and enter Quattro User ID
Click Set Password, enter password, click OK
Click Apply, click OK
Expand Privileges, expand Client(s) branch, select Client(s) Taskmaster Sub
privilege, click Apply, click OK
click Done
Configure Taskmaster Authentication for Taskmaster

On Do This
Server Create/ensure Quattro Account Exists
Manager > Start
DevWorkstation Add Taskmaster User to Application (LLLDAP or Taskmaster
Authentication only)
Settings > Users
Click Add, and enter Quattro User ID
Click Set Password, enter password, click OK
Click Apply, click OK
Expand Privileges, expand Client(s) branch, select Client(s) Taskmaster Sub
privilege, click Apply, click OK
click Done

On Do This
DevWorkstation Add Taskmaster Station to Application
Settings > Station
Click Add, enter name of QServer machine, click Apply, click OK
Expand Permissions, select appropriate permissions, click Apply, click OK
Click Advanced button, set Maximum number of virtual stations to 99, click
OK, click Apply, click OK, click Done
Install and Configure Quattro on Windows 2003 Server

On Do This
All Shut Down Taskmaster Software on all machines
Server Set Sharing Permissions for Datacap Folder
Click Sharing tab, click Permissions button
Add/ensure Domain/Windows account for Quattro set to allow Full Control
Click Security tab
Add/ensure Domain/Windows account for Quattro set to allow Read & Execute
QServer Install Taskmaster Options on QServer
QServer Install Quattro on QServer
Install Rulerunner (Quattro) component and separately licensed connectors to
QServer Set Location of Datacap.xml
Manager


On Do This
QServer Configure Quattro to Use Windows Authentication
Manager > Stop
Click Datacap Login tab > select Windows Authentication > Save

On Do This
QServer Encrypt Taskmaster Login Password
QServer Configure Quattro's Taskmaster Login Credentials
Manager > Stop
Click Datacap Login tab > select Taskmaster Authentication > Enter Quattro's
Taskmaster User ID, encrypted password, Station ID > click Save
Configure Quattro Account and Permissions on QServer

On Do This
QServer Add Quattro Account on QServer
Add Quattro account to QServer's Administrators Group or grant permissions
using DCOM Config: TaskMaster.RunTask, add and grant Local Launch and
Local Activation permissions
QServer Grant Quattro Log on as a Service Right
Click Log On tab > select This account > click Browse > select Quattro
account, enter password > click Apply
QServer Grant DQCS Log on as a Service Right

On Do This
QServer Configure DQCS Start Up Behavior
Optional:
Install and Configure Quattro on Windows 2008 Server

On Do This
All Shut Down Taskmaster Software on all machines
Server Set Sharing Permissions for Datacap Folder
Click Permissions
Click Security tab
Add/ensure Domain/Windows account for Quattro set to allow Read & Execute
QServer Ensure Microsoft .NET Framework 3.5.1 is Installed
and Features
Click Add Features
Click Install
QServer Install Taskmaster Options on QServer
QServer Install Quattro on QServer
Install Rulerunner (Quattro) component and separately licensed connectors to

On Do This
QServer Set Location of Datacap.xml
Manager

On Do This
QServer Configure Quattro to Use Windows Authentication
Manager > Stop
Click Datacap Login tab > select Windows Authentication > Save

On Do This
QServer Configure Quattro's Taskmaster Login Credentials
Manager > Stop
Click Datacap Login tab > select Taskmaster Authentication > Enter Quattro's
Taskmaster User ID, encrypted password, Station ID > click Save
Configure Quattro Account and Permissions on QServer

On Do This
QServer Add Quattro Account on QServer
Add Quattro account to QServer's Administrators Group or grant permissions
using DCOM Config: TaskMaster.RunTask, add and grant Local Launch and
Local Activation permissions
QServer Grant Quattro Log on as a Service Right

On Do This
QServer Grant DQCS Log on as a Service Right
QServer Configure DQCS Start Up Behavior
Optional:
Configure and Run APT Tasks using Quattro

On Do This
Various Shut Down Taskmaster Client and Web Software
Server Set Up Security on Datacap\APT Folder
Right-click c:\Datacap\APT folder and select Properties
Click Security tab
Server Set Up Security on Datacap\RRS Folder
Right-click c:\Datacap\RRS folder and select Properties
Click Security tab
Manager > Start
DevWorkstation Obtain Task Profile Name
Open Taskmaster Client application
Settings > Workflow > expand job > select task > make note of task name
Click Setup > make note of task profile name

On Do This
DevWorkstation Configure Task Profile in Taskmaster Application Service
Application Manager
Select application > ensure paths are correct
Click Quattro tab > ensure task profiles and task names match values
obtained from Taskmaster Client; add task profiles if necessary, delete task
profiles Quattro will not process
DevWorkstation Stop and Restart Taskmaster Server Service
Manager > Stop
Taskmaster Server Manager > Start
QServer Configure Quattro to Run APT Tasks (Single thread)
Manager > Stop
Click Workflow:Job:Task tab > expand APT, expand Servers node, select
server, select Admin and Engine databases
In left pane, under APT, under Demo > click the box next to Batch Profiler
and click and drag Batch Profiler onto thread0 in right pane
Repeat for Export task

On Do This
QServer Configure Quattro to Run APT Tasks (Multi-thread)
Manager > Stop
Click Workflow:Job:Task tab > expand APT, expand Servers node, select
server, select Admin and Engine databases
In right pane, right-click > select Threads > select Add Thread, repeat to
create multiple threads
In left pane, under APT, under Demo > click the box next to Batch Profiler
and click and drag Batch Profiler onto thread0 in right pane
In left pane, under APT, under Demo > click the box next to Export and
click and drag Export onto thread1 in right pane
Repeat for other APT tasks
Run Taskmaster Client APT Tasks using Quattro

On Do This
DevWorkstation Start and Run APT Batch Profiler
Start > All Programs > Datacap > Applications > APT
Log in
Double-click Scan shortcut, select Demo, click OK
Repeat to create additional batches for Quattro to process
QServer Start Quattro
Manager > Start
DevWorkstation View Batches Processed by Quattro using Job Monitor
From APT Operations pane, on the View menu > Job Monitor
Click Job Monitor window, press <F5> periodically to refresh view and see
changes to batch task and status as Quattro runs task for batch.
DevWorkstation Run APT Verify
Double-click Verify shortcut and process batch.
DevWorkstation Refresh Job Monitor View
Click Job Monitor window, press <F5> periodically to refresh view and see
changes to batch task and status as Quattro runs task for batch.


On Do This
QServer Set Up Quattro Restarts
Manager > Stop
Click Datacap Login tab > select Taskmaster Authentication > enter credentials
and click Connect
Click Workflow:Job:Task tab
On Quattro Settings tab, select Stop on Abort, click Save
On Advanced Settings tab, select Restart Service, click Save
Click Datacap Login tab > click Disconnect
Various Restart Taskmaster Software
Configure Quattro to Run Your Applications

On Do This
Various Ensure the following before starting:
Ensure you have working versions of your Taskmaster applications and that
you have successfully run all tasks manually
Configure your Taskmaster application to use either Windows or
Taskmaster authentication
Install Quattro on either a Windows 2003 or Windows 2008 server (includes
granting permissions to Quattro and DQCS on Server)
Determine which Taskmaster tasks to process, and gather required task
information
Various Shut Down Taskmaster Software

On Do This
Server Set Up Security on Datacap\MyApp1 Folder
Right-click c:\Datacap\MyApp1 folder and select Properties
Click Security tab
Server Set Up Security on Datacap\RRS Folder
Right-click c:\Datacap\RRS folder and select Properties
Click Security tab
Manager > Start
DevWorkstation Obtain Task Profile Name
Open Taskmaster Client application
Settings > Workflow > expand job > select task > make note of task name
Click Setup > make note of task profile name
DevWorkstation Configure Task Profile in Taskmaster Application Service
Application Manager
Select application > ensure paths are correct
Click Quattro tab > ensure task profiles and task names match values
obtained from Taskmaster Client; add task profiles if necessary, delete task
profiles Quattro will not process
DevWorkstation Stop and Restart Taskmaster Server Service
Manager > Stop
Taskmaster Server Manager > Start

On Do This
QServer Connect to Application, Taskmaster Server, Database Combination
Manager > Stop
Click Workflow:Job:Task tab > click the box to the left of MyApp1 to
expand tree
QServer Configure Quattro to Run a Task
Repeat to add additional threads
In left pane, under MyApp1, click the box next to the node, then click and
drag the node onto the thread in right pane
Click Save
QServer Disconnect and Reconnect to Different Application Combination
Either:
After saving your changes, click Datacap Login tab, click Disconnect, then
click Connect, click the Workflow:Job:Task tab and select a different
application, server, database combination
or
After saving your changes, right-click the Engine database and select
Disconnect, the right-click the Taskmaster Server and select Disconnect.
Check the status bar and ensure you are disconnected from the Taskmaster
Server and the databases. Then select a different application, server,
database combination.
QServer Reset Quattro Login Credentials
QServer Run Myapp1 Tasks and Monitor Quattro

On Do This

On Do This
QServer Set Up Quattro Restarts
Manager > Stop
Click Datacap Login tab > select Taskmaster Authentication > enter credentials
and click Connect
Click Workflow:Job:Task tab
On Quattro Settings tab, select Stop on Abort, click Save
On Advanced Settings tab, select Restart Service, click Save
Click Datacap Login tab > click Disconnect
Various Restart Taskmaster Software


On Do This
Server Ensure Domain/Windows User Account Exists for Taskmaster Client
Service
(OPTIONAL - skip if not using Windows Authentication)
For instructions, see Configure Windows Authentication for Taskmaster
Manager > Start
DevWorkstation Add Group, User, Station for Taskmaster Client Service to Application
Start the application and log in
Settings > Groups tab > click Add, add Group for Taskmaster Client Service
(see the Configure Windows Authentication for Taskmaster section for
instructions on naming this group), and assign Privileges, Permissions
Click Users tab > click Add, add User for Taskmaster Client Service and
assign Privileges, and add to Group
Click Stations tab > click Add, add Station for Taskmaster Client Service,
and assign Permissions
TCSServer Grant Taskmaster Client Service Log On as a Service Right
Control Panel > (System and Maintenance) > Admin Tools > Services >
right-click Datacap Taskmaster Client Service > Properties > Log On tab
Select This Account and enter domain name, user name and password of the
Taskmaster Client Service User, click Apply, returns message that user
granted Log On as a Service right
TCSServer Add Taskmaster Client Service Account on TCSServer
Add Taskmaster Client Service Account to TCSServer’s Administrators
group, or grant Taskmaster Client Service account permissions using
DCOM Config:
Admin Tools > Component Services > DCOM Config > change
TaskMaster.RunTask properties on the Security tab:
Launch and Activate: Add Taskmaster Client Service account and allow
Local Launch, Remote Launch, Local Activation, Remote Activation
Access Permissions: Add Taskmaster Client Service account and allow
Local Access, Remote Access
Configuration Permissions: Add Taskmaster Client Service account and
allow Full Control

On Do This
Server Set Taskmaster Client Service Sharing Permissions for Datacap Folder
(Windows 2003)
Click Permissions, add Taskmaster Client Service account and set to allow
Full Control
Server Set Taskmaster Client Service Sharing Permissions for Datacap Folder
(Windows 2008)
Click Sharing tab, click Advanced Sharing, click Permissions, add
Taskmaster Client Service account and set to allow Full Control
Server Set Taskmaster Client Service Security Permissions for Datacap Folder
(Windows 2003)
Right-click c:\Datacap folder and select Sharing and Security
Click Security tab, add Taskmaster Client Service account and set to allow
Read & Execute
Server Set Taskmaster Client Service Security Permissions for Datacap Folder
(Windows 2008)
Right-click c:\Datacap folder and select Properties
Read & Execute
Server Set Taskmaster Client Service Security Permissions for
Datacap\Application Folder
Right-click c:\Datacap\Application and select Properties
Full Control
Server Set Taskmaster Client Service Security on Datacap\RRS Folder
Right-click c:\Datacap\Application and select Properties
Full Control
TCSServer Ensure Microsoft .NET Framework 3.5.1 is Installed (Windows 2008)
and Features
Click Add Features
Click Install

On Do This
TCSServer Run InstallShield Wizard - Windows 2003, Windows 2008
Install Taskmaster Client Service component and separately licensed
TCSServer Install Taskmaster Options on TCSServer
TCSServer Set Location of Datacap.xml
Application Manager
TCSServer Reboot
Configure and Run Taskmaster Client Service

On Do This
TCSServer Configure Taskmaster Client Service
Start > All Programs > Datacap > Taskmaster Client > Taskmaster Client
Service Manager > TM Sub > Confirm Taskmaster Client Service is
Stopped
Click Application tab > select application > click Connect
Click Login tab and select appropriate authentication method and enter info,
click Login
Click Workflow:Job:Task tab > Expand workflow, expand jobs, select tasks
in each job that this Taskmaster Client Service is to run, click Save
Click Logging tab > Change settings if appropriate, click Save
Click Application tab > click Disconnect
Click TM Sub tab > click Start
Click Close
Start > Settings > Control Panel > Admin Tools > double-click Services
Scroll down to Datacap Taskmaster Client Service, right-click > Properties
General tab > Change Startup Type to Automatic, click Apply, click OK
DevWorkstation Test Taskmaster Client Service by Running Application
Start and run application tasks that should trigger the Taskmaster Client
Service


On Do This
Server Create/ensure NENU account exists
Server Ensure developer has been granted sharing and security permissions on the
Server
DevWorkstation Add NENU account to the Administrators or Backup Operators group
Server Set NENU Account Sharing Permissions for Datacap Folder (Windows
2003)
Click Sharing tab, click Permissions button
Add/ensure Domain/Windows account for NENU set to allow Full Control
Server Set NENU Account Sharing Permissions for Datacap Folder (Windows
2008)
Server Set NENU Account Security Permissions for Datacap Folder
(Windows 2003)
Click Security tab
Add/ensure Domain/Windows account for NENU set to allow Read &
Execute
Server Set NENU Account Security Permissions for Datacap Folder
(Windows 2008)
Click Security tab
Execute
Server Set NENU Account Security Permissions for Datacap\RRS Folder
Click Security tab
Execute

On Do This
DevWorkstation Run InstallShield Wizard
Install complete Taskmaster Client component
Create NENU Application

On Do This
Manager > Start
DevWorkstation Start Datacap Studio to Use Application Wizard
Start > All Programs > Datacap > Datacap Studio > Datacap Studio >
Close
DevWorkstation Create NENU Application using Datacap Studio
With Datacap Studio open, click Application Wizard button, click Next
Select Create a new RRS application, click Next, enter:
Application Name: NENU
Datacap Folder: C:\Datacap
Destination: \\Server\Datacap
Select Create application shortcuts for all users, click Next
Click Next, click Next, click Next, click Finish
Click View Logs to ensure no error or warning messages
Click Close
Server Update Datacap.xml on Taskmaster Server
Open datacap.xml on Server and add reference to NENU application
DevWorkstation Set Location of Taskmaster Server and Datacap.xml
Application Manager
Select application and ensure all paths are correct
Click Taskmaster tab, change Server name to name of Taskmaster Server
Click Service tab, ensure path reflects correct location of datacap.xml
Server Set NENU Account Security Permissions for Datacap\NENU
Application Folder
Click Security tab

On Do This
Server Set NENU Account Security Permissions for Monitored Application
Folder
Right-click C:\Datacap\Application folder and select Properties
Click Security tab
Manager > Start
DevWorkstation Start Datacap Studio and Open NENU Application
Start > All Programs > Datacap > Datacap Studio > Datacap Studio >
Select NENU Application and log in
DevWorkstation Delete All Rulesets in NENU Application
Click top Ruleset, click Lock/Unlock ruleset, click Remove object, click
Yes, Click OK.
Repeat to delete all rulesets
On Document Hierarchy tab, click Loc DCO for editing, click Yes, click
Save changes, click Unlock DCO.
DevWorkstation Add NENU Actions to NENU Application
Task Profiles tab > click Lock/Unlock task profiles, click Add
Select Custom and enter name for new task (NENU), click OK
Click Save changes
Rulesets tab > right-click workflow name, select Add Ruleset
Click new Ruleset label and rename (NENU)
Task Profiles tab > select task (NENU)
Rulesets tab > select ruleset (NENU), click Add ruleset to profile
Task Profiles tab > click Save changes, click Lock/Unlock task profiles
Rulesets tab > select Function 1, click Actions Library tab and expand
NENU actions
Use Add to function to add actions to Function 1
Click each action in Rulesets tab and enter appropriate parameter value
Rulesets tab > click Save changes, click Lock/Unlock ruleset, select
Publish ruleset
Document Hierarchy tab > click Lock DCO for editing, expand top level of
DCO and within Open node select global.
Rulesets tab > select NENU ruleset's Rule 1 > click Add to DCO
Document Hierarchy tab > click Save changes, click Unlock DCO

On Do This
DevWorkstation Run Ruleset with NENU Manager
Start > All Programs > Datacap > Taskmaster Client > NENU Manager
Click Create, click in empty field to right of lib, then either select or enter a
value and modify all the fields in the table
Select Place settings file in the batch directory, click Save
Click Run Profile, click OK
On Server, open NENU folder under application's batches folder and
review log file
Configure Windows Task Scheduler to Run NENU Ruleset Automatically (Windows

2003)
On Do This
DevWorkstation Start > All Programs > Accessories > System Tools > Scheduled Tasks
Double-click Add Scheduled Task, click Next
Click Browse > select C:\Datacap\tmclient\NENU.exe and click Open
Enter name for task, select when to perform task, click Next
Specify other scheduling parameters, click Next
Enter NENU user name and password for the NENU account you added to
the Administrators or Backup Operators group, click Next
Select Open advanced properties for this task when I click Finish
Click Finish
In Run field, append path and filename for NENU settings file in quotation
marks, for example:
"C:\Datacap\NENU\Batches\NENU_NENU\Settings.xml"
Click OK

Configure Windows Task Scheduler to Run NENU Ruleset Automatically (Windows 7

and Windows 2008)
On Do This
DevWorkstation Start > Control Panel > Administrative Tools > Task Scheduler
Under Task Scheduler (Local), right-click Task Scheduler Library, select
New Folder
Enter Datacap > click OK to create new folder
Expand Task Scheduler Library > select Datacap folder
Actions panel > click Create Basic Task
Enter name for task > click Next
Select Daily > click Next
Enter Start date and time > click Next
Select Start a program > click Next
Browse and select C:\Datacap\tmclient\NENU.exe
Click Open
In Add arguments field, enter path and filename for NENU settings file in
quotation marks, for example:
"C:\Datacap\NENU\Batches\NENU_NENU\Settings.xml" > click Next
Select Open the Properties dialog for this task when I click Finish > click
Finish
Open properties window for the NENU task
Under Security Options ensure the domain/Windows account is the correct
account, if not, click Change User or Group, and select the NENU
domain/Windows account
Select the Run whether user is logged on or not option
Select the Run with highest privileges option
Click OK
Ensure NENU domain/Windows account is correct, enter password, click
OK
Click OK

Install and Configure Rulerunner as a Web Service

Note: “Rulerunner running as a Web Service” or "Web Rulerunner Service" is referred to here
as “Rulerunner account”
On Do This
Server Ensure Domain/Windows User Account exists for Rulerunner account
with Log on as a service right
Ensure Domain/Windows account exists for Rulerunner account
Server Set Rulerunner Account Sharing Permissions for Datacap Folder
Add/ensure Domain/Windows Rulerunner account is set to allow Full Control
Server Set Rulerunner Account Security Permissions on Datacap Folder
Add/ensure Domain/Windows Rulerunner account is set to allow Read &
Execute
Server Set Rulerunner Account Security Permissions for Datacap\RRS Folder
(Windows 2003)
Add/ensure local ASP.NET Machine Account (Server\ASPNET) and local
Internet Guest Account (Server\IUSR_SERVER) are set to allow Full Control
Server Set Rulerunner Account Security Permissions for Datacap\RRS Folder
(Windows 2008)
Add/ensure NETWORK SERVICE and local IUSR are set to allow Full
Control
Server Set Rulerunner Account Security Permissions for Batches Folder
Configure Rulerunner Account and Permissions on RRServer (Windows 2003)

On Do This
RRServer Add Rulerunner Account on RRServer
Add the Rulerunner account to the RRServer's Administrators group

On Do This
RRServer Update ASP.NET Process Identity in Machine.Config File
Windows Explorer > navigate to and use Notepad to edit:
c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\CONFIG\machine.conf
ig
Locate <system.web> and <processModel…
Add Rulerunner account information to
userName="MYDOMAIN\RulerunnerAccountName"
password="RulerunnerAccountPassword"/>
Save and close file
RRServer Grant Rulerunner Access to IIS Metabase
Start > Run
Type cmd, click OK.
Locate the aspnet_regiis.exe and run with -ga parameter followed by the domain name,
a backslash, then the Rulerunner account name;
DOMAIN\RulerunnerAccountName
then press <ENTER>.
Close the DOS command window
RRServer Grant DCOProcessor Permissions in DCOM Config
Admin Tools > Component Services > DCOM Config > DCOProcessor, add and grant
Local Launch and Local Activation permissions to the Rulerunner account.
RRServer Confirm IIS Configuration (Windows 2003)
RRServer Run InstallShield Wizard
Install the Rulerunner Web Service component and separately licensed connectors to
which you are entitled.
RRServer Set Up WRRS Folder Permissions
Right-click c:\Datacap\WRRS and select Sharing and Security
Security tab > Add local ASP.NET Machine Account (Server\ASPNET) and
local Internet Guest Account (Server\IUSR_SERVER) are set to allow Read &
Execute

On Do This
RRServer Create and Share Virtual Directory for Rulerunner
expand Web Sites folder > right-click Default Web Site and select New >
Virtual Directory > Alias: RRS
Web Site Content directory: C:\Datacap\WRRS folder
Access Permissions: Read, Run scripts, Execute > click Finish
Right-click RRS > Properties
ASP.NET tab > confirm version is 2.0.nnnnn
RRServer Set Timeout Parameters for Rulerunner
expand Web Sites folder > expand Default Web Site and right-click RRS >
Properties
Virtual Directory tab > click Configuration button > Application Configuration
> Options tab > Select Enable session state, Timeout = 20, select Enable parent
paths, Default ASP Language = VBScript, ASP Script timeout = 1200
State Management tab > Session timeout = 20
RRServer Set Web Site Isolation Mode
right-click Web Sites > Web Site Properties > Service tab, select WWW
Isolation Mode: Run Service in IIS 5.0 Isolation Mode
RRServer Select Web Service Extensions
click Web Service Extensions
Select/ensure Active Server Pages, ASP.NET v2.0.50727, and Server Side
Includes are Allowed.
Any Test Access to Rulerunner
Open Internet Explorer, enter: http://RRServerName/rrs/session.asmx
RRServer Set Location of Datacap.xml
Manager
RRServer Restart IIS

On Do This
Manager > Start
Configure Rulerunner Account and Permissions on RRServer (Windows 2008)

On Do This
RRServer Add Rulerunner Account on RRServer
Add the Rulerunner account to the RRServer's Administrators group
RRServer Ensure Microsoft .NET Framework 3.5.1 is Installed (Windows 2008)
and Features
Click Add Features
Click Install
RRServer Ensure Required IIS Components are Installed
Manager
Scroll down further to Management Tools, ensure IIS Management Console is
installed
RRServer Run InstallShield Wizard
Install the Rulerunner Web Service component and separately licensed connectors to
which you are entitled.
RRServer Set Up WRRS Folder Permissions
Right-click c:\Datacap\WRRS and select Properties
Security tab > Add NETWORK SERVICE and IUSR and set to allow Read &
Execute

On Do This
RRServer Set IIS ASP Request Size Limit
Admin Tools > Internet Information Services (IIS) Manager
Connections pane > Select the Server, in Server’s Home pane, scroll down to
the IIS area and double-click ASP
ASP properties pane > Behavior section, expand Limits Properties.
Locate Maximum Requesting Entity Body Limit (maxRequestEntityAllowed),
increase value (increase size)
Click Apply
RRServer Create and Share Rulerunner Web Site
Start > Control Panel > System and Maintenance > Admin Tools > IIS >
expand computer > expand Web Sites folder > right-click Default Web Site
and select Add Application > Alias: RRS
Application pool: Classic.NET AppPool
Physical path: C:\Datacap\WRRS
Click OK
In Connections pane, select Application Pools
In Actions pane, select Set Application Pool Defaults
Select Classic.NET AppPool, in Actions pane, under Manage Application,
select Advanced Settings
Ensure Enable 32-Bit Applications = True
Click browse to right of Process Model Identity, select Custom account, click
Set
Enter Rulerunner account credentials, click OK
In Connections pane, click Default Web Site
In far right pane, expand Manage Web Site, click Configure Limits
Set Connection Timeout field, click OK
In Connections pane, click Default Web Site, in middle pane, in IIS section,
double-click the HTTP Response Headers icon
In far right pane, click Set Common Headers, select Expire Web content, select
Immediately, click OK
Confirm Web Server, Application Pool, and Default Web Site are all started
Any Test Access to Rulerunner
Open Internet Explorer, enter: http://RRServerName/rrs/session.asmx

On Do This
RRServer Set Location of Datacap.xml
Manager
RRServer Restart IIS
Manager > Start
Configure Application to Use Rulerunner as a Web Service

On Do This
DevWorkstation Configure Taskmaster Application to Use Rulerunner as a Web
Service
Start Taskmaster Client application and log in
Settings > Workflow > select Main Job > select Recognize task, click
Setup
Recognize Setup - Batch Pilot window > select the Rulerunner Web
Service option, click Done.
Click Apply.
DevWorkstation Test Taskmaster Application Using Rulerunner as a Web Service
Create a batch and process it through the (Recognize) task.
Open application’s batches folder, open log file associated with task, look
for “RRS is REMOTE” entry.


On Do This
Server Create/ensure domain exists in which Taskmaster-specific
AD/LDAP/LLLDAP security groups can be created
Server Create/ensure AD/LDAP/LLLDAP security group exists
Server Create/ensure Taskmaster users and services accounts exist and are part of
security group
Manager > Stop
Taskmaster tab > click Show Advanced, enter authentication string:
<%server%>:<%port%>/uid=<%user%>,dc=<%domain%>,dc
=Com
Click Save
Service tab > click Start
DevWorkstation Add Taskmaster Group to Application
Settings > Groups
Click Add, and enter a Group ID that is a concatenation of:
--A dot
--The domain to which your Taskmaster-specific security group
belongs
Click Apply, then OK
Expand Privileges, select appropriate privileges, click Apply, then OK
Expand Permissions, select appropriate permissions, click Apply, click
OK, click Apply, click Done

On Do This
Workstation Update Authentication Parameter in Taskmaster Client Application
Shortcut
Right-click application shortcut > Properties
Press <End> to move cursor to end of Target field, then ensure last
parameter in line is -nta, click Apply, click OK

Use Fingerprint Maintenance Tool

On Do This
Server Start Fingerprint Maintenance Tool
Windows Explorer > Datacap\Application\dco_Application folder
Double-click Fingerprint Maintenance Tool
Server Locate and Delete Partial Fingerprints
Click Find Problems
Click Select All
Click Delete Selected

Appendix C
Taskmaster Installer Command Line Parameters

This Appendix provides information about the most commonly used parameters available
when running the IBM Datacap Taskmaster Capture InstallShield Setup.exe from the
command line.
Other parameters that are available are the standard InstallShield parameters and standard
Microsoft Windows Installer parameters.
InstallShield Parameters
To view the InstallShield parameters:
2 Click the Browse button, navigate to the folder containing the IBM Datacap Taskmaster
Capture InstallShield Setup.exe, select it, and click Open. The Browse window closes
and the full path to the Setup.exe is displayed in the Run dialog.
3 After Setup.exe, add a space and /? (for example: c:\SP1\setup.exe /?), then click OK.
The InstallShield parameters are displayed.
4 Click OK to close the InstallShield message box.
Microsoft Windows Installer Parameters

To view Microsoft’s Windows Installer parameters:
2 Click the Browse button, navigate to the folder containing the Microsoft Windows
Installer program msiexec.exe, select it and click Open. The Browse window closes
and the full path to the msiexec.exe is displayed in the Run dialog.
3 After msiexec.exe, add a space and /? (for example:
C:\WINDOWS\system32\msiexec.exe /?), then click OK. The Windows Installer
parameters are displayed.
4 Click OK to close the Windows Installer message box.
Most Commonly Used Taskmaster Setup.exe Parameters

The following table covers the command lines that are most commonly used when installing
IBM Datacap Taskmaster Capture.
IMPORTANT NOTES
When these commands are run, they must be run as Administrator.
When installing components individually (Server, Web, Client), you must also install
the 'LAP' and 'Shared' components, otherwise the individual component will not
function properly.

Name/value pairs (for example INSTALLDIR=\"<path>\" and

ADDDEFAULT=LAP,Shared,Server) are case-sensitive: Name is all capitals, values
are upper/lower case as shown.
Replace <path> with full path (for example C:\Datacap).
Replace <filename> with name to assign to log file (for example: InstallLog).
To Do This Use This Command Line
Silent Install: Quiet mode, setup.exe /S /V"/quiet"
no user interaction
Silent Install: Quiet mode, setup.exe /S /V"/quiet INSTALLDIR=\"<path>\""
different location
Silent Install: Unattended setup.exe /S /V"/passive"
mode - progress bar only
Silent Install: Unattended setup.exe /S /V"/passive INSTALLDIR=\"<path>\""
mode, different location
Create Install Log setup.exe /V"/log <path>\<filename>.txt"
Disable Auto Reboot after setup.exe /V"/norestart”
Install Finishes
Install Taskmaster Server setup.exe /S /V"/passive ADDDEFAULT=LAP,Shared,Server"
only
Install Taskmaster Client setup.exe /S /V"/passive ADDDEFAULT=LAP,Shared,Client"
only
Install Taskmaster Web setup.exe /S /V"/passive ADDDEFAULT=LAP,Shared,Web"
only
Install Taskmaster Server & setup.exe /S /V"/passive ADDDEFAULT=LAP,Shared,Server,Web"
Taskmaster Web
Install Taskmaster Client & setup.exe /S /V"/passive ADDDEFAULT=LAP,Shared,Client,APT"
Accounts Payable Capture
Application
Install Taskmaster Client & setup.exe /S /V"/passive ADDDEFAULT=LAP,Shared,Client,MClaims"
Medical Claims Capture
Application
Install Taskmaster Client & setup.exe /S
Documentation /V"/passive ADDDEFAULT=LAP,Shared,Client,Docs"
Install Taskmaster Client & setup.exe /S /V"/passive ADDDEFAULT=LAP,Shared,Client,DStudio
Datacap Studio DSACTION=3"
Install Taskmaster Client & setup.exe /S /V"/passive ADDDEFAULT=LAP,Shared,Client,DotScan"
DotScan
Install Taskmaster Client & setup.exe /S /V"/passive ADDDEFAULT=LAP,Shared,Client,DotEdit"
DotEdit
Install Taskmaster Client & setup.exe /S /V"/passive ADDDEFAULT=LAP,Shared,Client,NENU"
NENU (Notification)
Install Taskmaster Client setup.exe /S /V"/passive ADDDEFAULT=LAP,Shared,ClientService"
Service

To Do This Use This Command Line

Install Rulerunner setup.exe /S /V"/passive ADDDEFAULT=LAP,Shared,Rulerunner"
(Rulerunner Quattro &
Fingerprint Service)
Install Taskmaster Web setup.exe /S /V"/passive ADDDEFAULT=LAP,Shared,WRRS"
Rulerunner Service
Install RV2 (Report setup.exe /S /V"/passive ADDDEFAULT=LAP,Shared,RV2"
Viewer)
Install eMail Input (eMail setup.exe /S /V"/passive ADDDEFAULT=LAP,Shared,eMail"
& eDoc)
Install Fax Input setup.exe /S /V"/passive ADDDEFAULT=LAP,Shared,Fax"
Install Connector for EMC setup.exe /S /V"/passive ADDDEFAULT=LAP,Shared,Documentum"
Documentum
Install Connector for setup.exe /S /V"/passive ADDDEFAULT=LAP,Shared,SharePoint"
Microsoft SharePoint
Install Connector for setup.exe /S /V"/passive ADDDEFAULT=LAP,Shared,Livelink"
OpenText Livelink
Install Developer Kit setup.exe /S /V"/passive ADDDEFAULT=LAP,Shared,DevKit"
Install Documentation setup.exe /S /V"/passive ADDDEFAULT=LAP,Shared,Docs"


Appendix D
Rulerunner Quattro Manager Reference
Rulerunner Quattro Manager

The Rulerunner Quattro Manager program allows you to update settings that determine how
Quattro functions, which applications, workflows, and tasks are processed by Quattro, as well
as the behavior of the Datacap Quattro Control Service that restarts Quattro. This
configuration program is installed when the Quattro software component is installed.
To start the Rulerunner Quattro Manager:
From the Windows Start menu, select Programs, select Datacap, select Taskmaster Client, and
click Rulerunner Quattro Manager. The Rulerunner Quattro Manager window opens with the
Datacap Quattro tab displayed on top.
This window is made up of the following tabs:
• Datacap Quattro tab
• Datacap Login tab
• Workflow:Job:Task tab with the Quattro Settings tab, the Advanced Settings tab and Node
Settings.
• Logging tab with the System Event Log tab, Quattro Log tab, and RRS Log tab.
Datacap Quattro Tab

This tab displays the name and current status of the Datacap Quattro Control Service, along
with Start and Stop buttons that allow you to change the status of the Control Service. When
you stop the Datacap Quattro Control Service, it stops Quattro after current processing
completes.
The Save and Close buttons are displayed on every tab:
• Use the Save button to save your changes to the Datacap Quattro Control Service and
Rulerunner Quattro settings.
• Use the Close button to close the Rulerunner Quattro window. The Close button only
closes the window; it does not start or stop either the Datacap Quattro Control Service or
the Datacap Rulerunner Quattro Service.
Datacap Login Tab

The fields on this tab are used for two different purposes:
• Identifying the authentication method to use when you want to make changes to the
Rulerunner Quattro and Datacap Quattro Control Service settings
• Identifying the authentication method Quattro uses when running Taskmaster tasks
Each time you make changes to the Quattro settings, before you exit, ensure you have set and
saved the settings that reflect the login credentials Quattro is to use the next time it's started.

Field or Button Explanation

Connect/ Disconnect When you are making changes to Quattro settings:
button
Select the authentication method, when using Taskmaster
Authentication enter login information, click Connect then make
changes on Workflow:Job:Task or Logging tabs. After completing
changes, click Disconnect.
When you are finished setting up Quattro and have disconnected,
ensure the authentication method is set properly for Quattro to use the
next time it is started.
Taskmaster Indicates you are using Taskmaster's Authentication to make changes
Authentication to Quattro settings.
or Also indicates Quattro is to be authenticated using Taskmaster's
Authentication when running tasks.
Taskmaster
Authentication. The login information you enter must be for a valid Taskmaster user.
Credentials used to
login to Taskmaster.
Windows Indicates you are using Windows Authentication to make changes to
Authentication Quattro settings (the login ID you used to log onto the QServer must
also be a valid Taskmaster user ID).
or
Also indicates Quattro is to be authenticated using Windows
Windows
Authentication when running tasks.
Authentication.
Credentials used to
login to Taskmaster.
User ID Identifies the User ID used by Quattro to log into Taskmaster.
When Taskmaster Authentication is being used, this value is used by
Quattro to log into Taskmaster.
Password Identifies the Password used by Quattro to log into Taskmaster.
Password must be encrypted using SitManager.exe.
Station ID Identifies the name of the machine hosting Quattro.
NOTE: Enter the name of the QServer machine exactly as it has been
identified to the Domain Controller (i.e. if the machine name
identified in the Domain Controller is in all capital letters, be sure to
enter the machine name here in all capitals).
Domain Displays the Domain name associated with the User ID. Only
displayed when Windows Authentication is selected.

Workflow:Job:Task Tab
The settings on this tab allow you to configure the applications and tasks that Quattro is to
process, as well as to set up how Quattro performs the processing. Changes you make on this
tab affect Quattro and Datacap Quattro Control Service.
This tab is organized into four panes, with the lower left pane split into two tabs. After you
have connected to the Datacap Application Service (on the Datacap login tab), additional data
is displayed in the upper panes:
• The upper left pane displays information from the Taskmaster Application Service about
the applications that are available; and, once you have connected to a specific application,
Taskmaster Server, and application database combination, additional information is
displayed about the workflows, jobs, and tasks that are available.
• The upper right pane allows you to create and configure the tasks that each Quattro thread
is to process.
• The lower left pane is split into two tabs of settings (Quattro Settings and Advanced
Settings) that define overall behavior (how Quattro and DQCS behave).
• The lower right pane displays the settings related to the node that is currently selected in
either of the upper panes.
Application Information from the Taskmaster Application Service

After you connect to the Taskmaster Application Service using the Connect button on the
Datacap Login tab, when you click the Workflow:Job:Task tab, the upper left pane displays the
list of applications the Taskmaster Application Service is aware of (stored in the datacap.xml
file). The status message indicates that you are not connected to the Taskmaster Server, that
you are not logged into Taskmaster databases, but that you are connected to the Taskmaster
Application Service.
Once you are connected to the Taskmaster Application Service, you do the following:
1 Connect to a specific application, Taskmaster Server, Administrator and Engine
database combination
2 Configure Quattro to run a job task on a thread
3 Disconnect from a combination and reconnect to a different application combination
Workflow:Job:Task – Threads
After you connect to the Taskmaster Application Service using the Connect button on the
Datacap Login tab, when you click the Workflow:Job:Task tab, the upper left pane displays the
list of applications the Taskmaster Application Service is aware of (stored in the datacap.xml
file). The status message indicates that you are not connected to the Taskmaster Server, that
you are not logged into Taskmaster databases, but that you are connected to the Taskmaster
Application Service.
Once you are connected to the Taskmaster Application Service, you do the following:
1 Connect to a specific application, Taskmaster Server, Administrator and Engine
database combination
2 Configure Quattro to run a job task on a thread
3 Disconnect from a combination and reconnect to a different application combination

Workflow:Job:Task - Quattro Settings Tab

The settings displayed on the Quattro Settings Tab apply to all tasks Quattro has been
configured to process.
Setting Explanation
Write to Debug Controls whether Quattro writes to the debug table in the
application’s Engine database:
or
Cleared - off
Write to Debug. Log
Selected - on
queuing activity in
debug table. Defaults to Cleared.
Mixed Queuing Controls how a batch is selected to run within a particular application.
or Cleared - (Sequential queuing) Quattro selects the oldest pending
batch from each of the selected tasks, one after the other. The first
Mixed Queuing.
batch is selected from the first task, the second batch is selected from
Batches are selected
the second task, etc. Sequential, or "round robin," queuing is
based on priority and
typically required when Quattro runs batch creation tasks like Vscan.
time stamp.
NOTE: When multiple applications are set to run in a single thread,
Quattro runs one task from the first application, then moves to the
next application and runs one task, etc. In other words, multiple
applications are always processed 'sequentially' in round robin order.
Batch selection within the application is as described above.
Selected - (Mixed queuing) Quattro sends the list of tasks to run
within the application to Taskmaster Server. Taskmaster Server
selects the oldest, highest priority batch pending for any of these tasks
and tells Quattro to run that batch.
Defaults to Selected.
Stop on Abort Controls whether Quattro stops all processing on all threads when a
task aborts:
or
Cleared - Quattro does not stop
Stop on Abort. Stop
Selected - Quattro does stop
the service if a task
aborts. Defaults to Selected. Use when cascading failures occur in order to
help identify the circumstances causing the failures.
Thread Timeout Controls how long the Datacap Quattro Control Service waits before
shutting down all Quattro threads.
Defaults to 900 seconds.
Sleep For Sets the amount of time in seconds Quattro waits before it roams.
Defaults to 10 seconds.

Setting Explanation
Settings File Identifies the full UNC path to the Quattro.xml file that contains
information about which applications, servers, databases, and tasks
or
each thread is to process. The default location is on the QServer in
Path to settings file. the \Datacap\tmclient folder.
Use the Browse button to navigate to the folder that contains the
Quattro.xml file.
Workflow:Job:Task - Advanced Settings Tab

The settings displayed on the Advanced Settings Tab apply to all tasks Quattro has been
configured to process.
Setting Explanation
Restart Service. Specifies whether DQCS automatically restarts the controlled service
when it is stopped:
or
0 - Does not automatically restart service
Restart service if 1 - Automatically restarts service
stopped.
You can use this setting to restart Quattro whenever it stops for
whatever reason, including when you have set Quattro to Stop on
Abort.
Defaults to 0.
Restart Interval Specifies, in seconds, the interval at which the controlled service is
stopped and restarted.
Defaults to 14400 seconds (4 hours).
State Change Delay Specifies, in seconds, the delay before the DQCS starts the stopped
service or attempts to stop the running service.
Defaults to 1.
Service Timeout Specifies, in seconds, the amount of time after which DQCS
considers the controlled service “hung.” Note: This only produces
an error message in the log.
0 - infinite
Defaults to 1800 (30 minutes).
Workflow:Job:Task - Node Settings (lower right)

The settings displayed in the Node Settings (lower right) apply to the node that is currently
selected, and the settings vary depending on whether the node is selected in the left pane or the
right, and the level or type of node that is selected.

System Event Log Tab

The slider on this tab allows you to adjust the level of detail written to the Windows System
Event log.
Field or Control Explanation
Messaging Level Controls the level of Quattro-related processing detail written to the
(slider) Windows System Event Log:
Critical only - Log Thread and Service start/stop messages and error
messages to Event Log
Serious and critical - Log Thread and Service start/stop messages,
and error and warning messages to Event Log
Info, critical and serious - Log all messages to Event Log (error,
warning, informational). Note: this setting writes the same level of
detail to the Event Log as is written to the thread logs (quattro#.log)
Defaults to Serious and critical.
Logging – Quattro Log Tab

The settings on this tab allow you to adjust the type and amount of detail written to the
Quattro.log and thread-specific log files.
Number of Controls the level of detail written to the main Quattro log
Messages (slider) (quattro.log). From left to right, None to All (referred to here as
positions 0 to 9) where:
0 No messages are logged
1-3 Logs warnings and exceptions
4-6 Logs information, warnings and exceptions
7-9 Logs the maximum amount of detail
Defaults to 5.
Common Buffer Writes details that can be viewed using the Taskmaster Client Log
Viewer.
or
Cleared – Do not write to buffer
Write to common
Selected – Writes to buffer
buffer for log
viewer. Defaults to Cleared.
Output To Controls whether Quattro log files (quattro.log, and the thread logs
(checkbox) quattro0.log through quattro3.log) are created.
Cleared – Do not create log files
Selected – Create log files
Defaults to Cleared.
Output To (path) Identifies the full path to the folder where Quattro log files are
written.
Defaults to C:\Datacap\


Overwrite Log Controls whether data is appended to existing Quattro log files or
whether the log files are overwritten each time Quattro is started.
or
Cleared – Append data to existing log files
Overwrite Log.
Selected – Overwrite log files each time Quattro is started
Overwrites existing
log files. Defaults to Selected.
Reflush Buffer Controls at what point the messages are written to the logs:
or Cleared – Buffer messages (for speed)
Selected – Force each message out to file in case of crash (slower)
Reflush buffer on
and flush the buffer after each line
each message.
Logging – RRS Log Tab

The settings on this tab allow you to adjust the type and amount of detail written to the
Rulerunner Service log.
Service Log Controls the level of detail written to the RRS log. From left to right,
None to All (referred to here as positions 0 to 5) where::
(slider)
0 = No log at all from RRS
1 = Interbatch errors log, Batch errors log
2 = Interbatch errors log. Batch errors log, Batch essential log
3 = Interbatch errors log , Batch errors log, Batch essential log,
Action parameters
4 = Interbatch errors log, Interbatch essential log, Batch errors log,
Batch essential log, Action parameters
5 = Full RRS log: Interbatch errors log, Interbatch essential log,
Batch errors log, Batch essential log, Action parameters, Detail
interbatch AND batch log
Defaults to 1.
Batch Log Controls the creation of the RRS log (taskname_rrs.log) in the batch
folder:
Cleared - Do not create log file
Selected - Create log file
Log Application ID Controls whether Quattro's application ID is included in the RRS log:
Cleared - Do not include
Selected - Include


Log Override Controls whether logging overwrites or appends to the log when
Quattro is restarted:
Cleared - Append data to existing log file
Selected - Overwrite log file each time Quattro is started
Log Reflush Controls at what point the messages are written to the log:
Cleared - Buffer messages (for speed)
Selected - Force each message out to file in case of crash (slower)
and flush the buffer after each line
Log Severity Indicates whether the value associated with the message severity is
written to the log:
Cleared - Message severity level is not written to log
Selected - Message severity level is written to log
Log Threadproc Controls whether the thread ID is included in the RRS log:
Cleared - Thread ID is not written to log
Selected - Thread ID is written to log
Log Time Controls whether a date time stamp is included in the RRS log:
Cleared - Date time stamp is not written to log
Selected - Date time stamp is written to log
Log Time Controls whether the time difference between log entries is included
Difference in the RRS action log:
Cleared - Time difference is not written to log
Selected - Time difference is written to log
Action Log Level Controls the severity level of messages logged when actions are run;
(slider) messages with a severity level lower than this number are excluded
from the log. From left to right, None to All (referred to here as
positions 0 to 5):
0 is none
5 is All (maximum).
Defaults to 5.

Rulerunner Quattro Manager How To

Connect to Application, Taskmaster Server, Database Combination

Before you can configure Quattro to run a task, you must connect to the specific combination
of application, Taskmaster Server, and databases for that task.
IMPORTANT
These instructions allow you to temporarily use Taskmaster Authentication and the
Taskmaster "admin" User ID and password to make your configuration changes. Follow the
instructions in Encrypt Taskmaster Login Password to encrypt the password for the
Taskmaster "admin" User ID before continuing with this procedure.
This procedure provides instructions on how to connect to the specific application, Taskmaster
Server and databases that relate to the task Quattro is to process.
window opens.
4 Select the Taskmaster Authentication option to enable the login credential fields.
5 Enter the Taskmaster admin User ID, paste in the encrypted Password, and enter a
Station ID of "2", then click Connect. The button label changes to Disconnect.
6 Click the Workflow:Job:Task tab to display it. Application names are displayed in the
left pane, threads are displayed in the right pane.

7 In the left pane, click in the checkbox to the left of the application you want to work
with. The application tree expands with the Server, Administrator and Engine
databases selected.
8 Continue with the instructions in Configure Quattro to Run a Task.
Configure Quattro to Run a Task

Once you have connected to an application, Taskmaster Server and database combination, you
can set up threads to run tasks in that combination.
This procedure provides instructions on how to set up a thread and configure Quattro to run a
task using that thread. In general, if you click in a checkbox
1 With the Rulerunner Quattro Manager - Workflow:Job:Task window open, right-click
in the right pane to display the context menu items:
Expand all - Expands the details of all existing threads
Collapse all - Collapses the details of all existing threads
Threads - Clear - Deletes all existing threads
Threads - Add Thread - Adds a new, empty thread
Remove - Deletes the selected thread
2 Right-click, point at Threads, then select Add Thread. A new thread is created in the
right pane.
3 Repeat the previous step to create the threads you need.
4 To configure the individual threads to run one or more tasks, do one or more of the
following:
To: Do this:
tasks in a workflow workflow name, then click the workflow name (it is
highlighted in blue) and drag it onto a thread in the
right pane
tasks in a single job job name, then click the job name (it is highlighted in
blue) and drag it onto a thread in the right pane
Configure a thread to run In the left pane, click the checkbox to the left of each
two or more tasks from a task, then click the job (it is highlighted in blue) and
job drag it onto a thread in the right pane
Configure a thread to run a In the left pane, click the checkbox to the left of the
single task task, then click the task (it is highlighted in blue) and
drag it into a thread in the right pane
To configure a thread to run In the left pane, click the checkboxes to the left of
more than one job in the each job, then select the workflow (it is highlighted in
same application blue) and drag it onto a thread in the right pane
Remove a task from a In the right pane, right-click a task and select Remove
thread to delete it

To: Do this:
Disable a thread In the right pane, click in the checkbox to the left of
the thread (the checkmark disappears), or right-click
the thread and select Remove to delete it entirely
Remove a thread In the right pane, right-click the thread and select
Remove
Remove all threads In the right pane, right-click, select Threads, then
select Clear
5 Click Save to save your changes.
6 To configure Quattro to run one or more tasks from a different application, Taskmaster
Server or database combination, continue with Disconnect and Reconnect to Different
Application Combination.
7 If you have completed your changes, click the Datacap Login tab to display it.
IMPORTANT
properly.
9 When using:
10 Click Save.
Disconnect and Reconnect to Different Application Combination

Once you have connected to an application, Taskmaster Server and database combination, and
configured Quattro to run one or more tasks from a single application, you must disconnect
from the application/Taskmaster Server/Admin and Engine database combination you are
working with before you can connect to a different application/Taskmaster Server/Admin and
Engine database combination.
There are two ways to disconnect and reconnect to a different application:
• After saving your changes, click the Datacap Login tab, click Disconnect - the button label
changes to Connect.
To connect to a different application, click the Connect button, then click the
Workflow:Job:Task tab, and select a different application, Taskmaster Server, Admin and
Engine databases. Continue with the instructions in Configure Quattro to Run a Task.
• After saving your changes, right-click the Engine database and select Disconnect, then
right-click the Taskmaster Server and select Disconnect. Check the status bar and ensure
you are disconnected from the Taskmaster Server and databases. Continue with the
instructions in Configure Quattro to Run a Task.

Once you have finished making your changes and have disconnected, ensure Quattro's
authentication credentials are correct (see the last steps in Configure Quattro to Run a Task).

Troubleshooting Quattro
This section contains information on steps to take when troubleshooting Rulerunner Quattro.
First Things to Check

Make sure that Taskmaster 8.0.1 or later has been installed on all of the machines.
Ensure you can run a batch manually using the Taskmaster Client on a Workstation. If you
cannot manually run batches through the tasks that Quattro is to process, your application
setup needs to be corrected. Use other sections of this Installation and Configuration Guide to
review your installation and configuration of the application and to get it working.
If you are able to run a batch manually through the tasks that Quattro is to process, your
application is set up properly and you need to perform Quattro-specific troubleshooting.
Follow the instructions to View Windows Event Viewer Logs, to stop Rulerunner Quattro,
enable logging, restart Quattro, and to check the logs for errors.
If Quattro starts then stops immediately and the logs indicate Quattro can’t connect to
Taskmaster Server Service:
• If there is a firewall enabled on the Server hosting Taskmaster Server Service, ensure that
TCP/IP port 2402 has been opened.
• When using Windows Authentication, check with your System Administrator to make
sure you selected the correct Windows Authentication template.
View Event Viewer Logs on QServer

This procedure provides instructions on how to open the Event Viewer Application and
System Logs on the QServer hosting Quattro.
1 From the QServer’s Windows Start menu, select Settings, select Control Panel, select
Administrative Tools, select Event Viewer, then in the navigation pane, select
Application. Entries for individual events are displayed in the details pane.
2 Press F5 or choose Action/Refresh to ensure you are seeing all recent messages.
3 Locate the first (bottom-most) event from the latest “run” of Quattro and double-click
the entry to view the event’s properties.
If present, ignore the message about “The description for Event ID ( 0 ) in Source …
cannot be found…. The following information is part of the event:” The information
following this text is relevant.
The first event should say “Service Started.” Subsequent events should indicate the
individual threads have each started. There are three initialization attempts with
intervals of two, four, and eight seconds apart and errors are logged if they occur.
Any warning or error events indicate a problem, the first warning or error is typically
the most significant.
4 Select System. Entries for individual events are displayed in the details pane.
5 Double-click an entry to view the event’s properties. Messages should indicate
Rulerunner Quattro was able to log on.
Any warning or error events indicate a problem, the first warning or error is typically
the most significant.

Stop or Ensure Quattro Service is Stopped

This procedure provides instructions on how to stop or ensure the Rulerunner Quattro is
stopped. If you attempt to stop Quattro while it is processing one or more job tasks, the
service will complete its current work before shutting down.
Client, and click Rulerunner Quattro Service. The Rulerunner Quattro Service window
opens with the Datacap Quattro tab displayed on top.
next step.
If the Status displayed is Running, click Stop. The status will change to Stopped once
Quattro has completed its processing.
3 Close the Rulerunner Quattro Service window.
Enable Quattro Processing Logging

Quattro processing logs can be created on both the QServer hosting Quattro and task-specific
logs can be created on the Server hosting Taskmaster and the application files.
Be sure there is ample disk space (10GB or more) on each server for storing these logs, and
remember to change the level of detail written to the logs or to turn them off once you no
longer need them.
This procedure provides instructions on how to enable Quattro logging on the server hosting
Quattro and how to enable task-specific logging on the Server hosting Taskmaster and the
application files.
4 Select the Windows Authentication option (this will work because the changes you are
making do not involve logging into Taskmaster), and click Connect. The label on the
Connect button changes to Disconnect.
5 Click the Logging tab to display it.
6 Click the System Event Log tab to display it, and move the Messaging level slider to
Info, critical and serious, then click Save.
7 Click the Quattro Log tab to display it, and move the Number of messages slider to All.
8 Ensure the Output to option is selected; change or make a note of the path in the Output
to field (this is where the logs will be created - you will need this information later).
9 Make changes to other options as desired, then click Save.
10 Click the RRS Log tab to display it, move the sliders to All for The level of detail
written to the RRS logs slider and the Severity level of messages logged, and ensure the
Batch Log option is selected. Make changes to other options as desired, then click
Save.


IMPORTANT
Complete the following steps to ensure Rulerunner Quattro's authentication
credentials are set properly.
13 When using:
14 Click Save.
Start Quattro
Rulerunner Quattro.
IMPORTANT
When you are running Quattro on the same Workstation as the Taskmaster Client, exit from
the Taskmaster Client before starting Quattro.
displayed on top.
View Quattro Processing Logs

Once you have enabled logging and restarted Rulerunner Quattro, Quattro should attempt to
process batches and will write to the logs.
This procedure provides instructions on how to view the various Quattro logs and provides
information on what to look for in the logs.
1 On the QServer, start Windows Explorer, navigate to and open the folder in which the
logs were created (the folder is defined using the Rulerunner Quattro Manager in the
Output to field on the Quattro Log tab; the default is C:\Datacap. For more information
on Rulerunner Quattro Manager, see Appendix D.
2 Using a text editor such as Notepad, open the Quattro.log and look for errors.

3 Using a text editor such as Notepad, open the Quattro thread log. Look for the
messages beginning EstablishConnection. A successful log would be similar to this:
EstablishConnection: Connecting to application [APT].
EstablishConnection: GetServer returned [127.0.0.1].
EstablishConnection: Connecting to TM Server [127.0.0.1:2402].
EstablishConnection: Connecting to Admin DB
[PROVIDER=MSACCESS;DSN=C:\Datacap\APT\APTAdm.mdb;].
EstablishConnection: Connecting to Engine DB
[PROVIDER=MSACCESS;DSN=C:\Datacap\APT\APTEng.mdb;].
EstablishConnection: TM Login [admin station=1].
EstablishConnection: Login successful.
4 Error conditions can include one or more of the following:

If connecting to Taskmaster Server fails, then the Taskmaster Server Service is
not responsive or a network failure occurred.
If connecting to the application’s Admin or Engine database fails, use the
Taskmaster Application Manager to ensure the paths to the databases are correct.
If Quattro fails to log into the Taskmaster Server, do the following:
o Ensure the Rulerunner Quattro is set up properly by reviewing the Quattro-
related instructions in Install and Configure Quattro on Windows 2003
Servers or Windows 2008 Servers (depending on operating system).
o Ensure the Quattro domain account has been added to the correct AD/LDAP
group, and, in your Taskmaster application, that you have set up a matching
group with a name that ends in the complete domain name (e.g. XYZ.com,
NOT just XYZ).
5 On the Server, start Windows Explorer, navigate to and open the application’s batches
folder (default is C:\Datacap\Application\Batches).
6 Using a text editor such as Notepad, open the taskname_rrs.log (pageid_rrs.log,
recognize_rrs.log, etc.) and look for errors.
During processing, when Quattro fails to run a batch from a particular application, there
is a delay interval before the next attempt, and Quattro doubles the delay each time
from 2 to 64 seconds.

Appendix E
Fingerprint Maintenance Tool Reference

The Fingerprint Maintenance Tool (FMT) allows you to keep information about your
fingerprints synchronized in all of the places fingerprint information is stored, including your
application's Fingerprint Database and fingerprint data files.
Fingerprint Maintenance Tool Field Definitions

Backup Directory
Displays the full path to the folder that contains backup copies of the fingerprint XML files
made when fingerprints are added to an application. If this folder does not exist, it is created
when the Fingerprint Maintenance executable is started.
CCO
An X in this column indicates the CCO file associated with this fingerprint is missing from the
application's Fingerprint Directory.
Database
An X in this column indicates the entry associated with this fingerprint is missing from the
application's Fingerprint Database.
Date Added
Displays the date the fingerprint was either created in or added to this application from
another.
Document Hierarchy
Displays the full path and filename of the application's Setup DCO.
Fingerprint Database
Displays connection string information related to the application's Fingerprint Database.
Fingerprint Directory
Displays the full path to the directory in which the fingerprint-related files (TIFF, CCO, XML)
are stored.
FPXML
An X in this column indicates the XML file associated with this fingerprint is missing from the
Fingerprint Directory.
Hits/Month
This is an estimate of how many times per month the fingerprint will be matched. This
estimate is based on the age of the fingerprint and the number of times the fingerprint has
actually been matched to date. This is calculated by first calculating the age of the fingerprint
(in months) by the number of times it has been matched.

For example, if a fingerprint is one month old (30 days) and has been matched once, the
Hits/Month value is 1.0000. If the fingerprint is two months old (60 days) and has been
matched once, the Hits/Month value is 0.5000.
Last Hit
Displays the date on which the fingerprint was last matched.
TIFF
An X in this column indicates the TIF file associated with this fingerprint is missing from the
Fingerprint Directory.
Total Hits
Indicates the number of times the fingerprint has been matched since it was created.
Fingerprint Maintenance Tool Buttons

Add Selected Button
Adds the selected fingerprints to the application's Fingerprint database and setup DCO, and
copies the associated TIFF and CCO files into the application's Fingerprint folder.
Delete Selected Button
Deletes the selected fingerprint, including the TIFF, CCO, and fingerprint XML files, and the
associated entry in the Fingerprint database.
Export Selected Button
Exports copies of the selected fingerprints, including the TIFF, CCO, and fingerprint XML
files, to the application's \fingerprint\Fingerprint Export folder.
Find FPXML Files Button
Finds any fingerprint XML files that are located in the application's \fingerprint folder.
Find Problems Button
Displays all fingerprints for which one or more components are missing from the Fingerprint
Directory, such as the TIFF, CCO, or fingerprint XML files, or when the entry for the
fingerprint in the application's Fingerprint database is missing.
Select All Button
Selects all displayed fingerprints.
Show Statistics Button
Displays all existing fingerprints and statistics related to each.
Fingerprint Maintenance Tool Configuration Settings File

Settings.INI File
This file contains three sections that contain definitions required by the Fingerprint
Maintenance Tool:
• Database Section
• Paths Section
• FMT Section

Database Section
Contains the connection strings to one or more databases used by the Fingerprint Maintenance
Tool, including:
• FingerprintDatabase Setting
FingerprintDatabase Setting
Defines the connection string to the Fingerprint database used by the Fingerprint Maintenance
Tool.
Example:
FingerprintDatabase=Provider=Microsoft.Jet.OLEDB.4.0;Data
Source=C:\Datacap\apt\process\APTFingerprint.mdb;Persist Security Info=False
Paths Section
Contains path information required by the Fingerprint Maintenance Tool to locate the
following:
Fingerprint Directory
Fingerprint Backup Directory
SetupDCO
FingerprintDirectory Setting
Defines the path to the application's folder that contains the application's fingerprint files
(TIFF, CCO, or fingerprint XML files).
Example:
FingerprintDirectory=c:\datacap\apt\Fingerprint
FingerprintBackupDirectory Setting
Defines the path to the folder that contains backup copies of the fingerprint XML files made
when fingerprints are added to an application. If this folder does not exist, it is created when
the Fingerprint Maintenance executable is started.
Example:
FingerprintBackupDirectory=c:\datacap\apt\Fingerprint Backup
SetupDCO Setting
Defines the path to the application's Setup DCO file.
Example:
SetupDCO=c:\datacap\apt\process\apt.xml


Index
A Backup Directory................................................. 325
About these Instructions.......................................196 Before You Begin .................................................. 14
About this Guide ......................................................7 C

Access Taskmaster Web Login Page and Login39, 130 Capture Fields on Rotated Image........................... 81
Add Group User and Station for Taskmaster CCO..................................................................... 325
Client Service .......................................................185 Change SSL Setting in Server.INI ............... 116, 123
Add NENU Actions to NENU Application..........204 Changes to Pre-Existing Zone Positions Are
Add or Ensure File Transfer Limit Setting is Large Ignored................................................................... 86
Enough Windows 2003 ........................................110 Client-Server Setup Checklist.............................. 248
Add or Ensure Upload Limit Setting is Large Complete Server Configuration ........................... 254
Enough in web.config...................................109, 120
Complete Taskmaster Server Configuration .......... 69
Add Quattro Account on QServer ................152, 158
Configuration Assumptions ................................... 13
Add Quattro Account on Workstation....................46
Configure and Run APT Tasks using Quattro161, 280
Add Reports to the RV2 Dashboard ...............34, 106
Configure and Run Taskmaster Client Service .... 289
Add Rulerunner Account on RRServer ........217, 223
Configure and Test IE 6 7 or 8 Manually ........... 272
Add RV2 Account to WebServer Administrators
Group .....................................................................95 Configure and Test IE 6 7 or 8 using Tool.......... 271
Add RV2 Address as Trusted Site..................32, 105 Configure and Test Internet Explorer 6 7 or 8
using Tool...................................................... 37, 126
Add Selected Button.............................................326
Configure and Test Remote Workstation............. 125
Add Selected Fingerprints to Fingerprint Database236
Configure Application to Use Rulerunner as a Web
Add Taskmaster Client Service Account on Service ......................................................... 229, 300
Taskmaster Client Service Machine .....................186
Configure Datacap Rulerunner Quattro
Add Taskmaster Group to Application.........142, 233 Authentication ..................................................... 140
Add Taskmaster Station to Application........143, 146 Configure Developer Account and Permissions on
Add Taskmaster User to Application ...........144, 146 Taskmaster Server ............................................... 197
Add TMWeb.net Address as Trusted Site37, 125, 271 Configure DQCS Start Up Behavior...... 47, 153, 159
Add Your PO Line Items to POTable.....................85 Configure IE 7 and Run Taskmaster Web Client on
Add Your Vendors to the Demo Vendor List.........84 Single Machine .................................................... 244
APT Troubleshooting .............................................86 Configure Internet Explorer 6 7 or 8 Manually... 127
APT Verify Window Instructions...........................79 Configure NENU Account and Permissions on

Developer Workstation........................................ 197
Associate Vendor and Fingerprint..........................81
Configure Quattro Account ................................... 46
AutoDelete Batches with NENU..........................208
Configure Quattro Account and Permissions on
AutoDelete Process ..............................................208 QServer........................................................ 277, 279
B Configure Quattro Account and Permissions on
QServer Windows 2003....................................... 152
Back Up Taskmaster Version 7.5 7.5 SP1 7.6 or
8.0...........................................................................15 Configure Quattro Account and Permissions on
QServer Windows 2008....................................... 158
Back Up then Delete Sample Input Images ............84
Configure Quattro Permissions on Server Windows
Backup and Uninstall Taskmaster Versions 7.1 and
2003 ..................................................................... 148
7.1 SP1 ...................................................................15
Configure Quattro Permissions on Server Windows
Backup Application Shortcuts ..............................238
2008 ..................................................................... 154
Backup Custom Applications ...............................238

Configure Quattro s Task Profiles in the Configure Windows Task Scheduler to Run
Taskmaster Application Service...................162, 176 Ruleset Automatically Windows 2003 ................ 206
Configure Quattro to Run a Task .................179, 318 Configure Windows Task Scheduler to Run
Configure Quattro to Run Your Applications173, 283 Ruleset Automatically Windows 7
Windows 2008..................................................... 207
Configure Quattro to Use Taskmaster
Authentication .............................. 150, 157, 277, 279 Confirm IIS Configuration on Windows 2003
Server..................................................... 95, 111, 218
Configure Quattro to Use Windows
Authentication .............................. 150, 157, 277, 279 Confirm Quattro s 1040EZ Task Profiles in the
Taskmaster Application Service ............................ 50
Configure Quattros Taskmaster Login
Credentials....................................................151, 158 Confirm Server.INI Points to TaskRun........ 116, 123
Configure Rulerunner Account and Permissions on Connect to Application Taskmaster Server

RRServer ......................................................217, 223 Database Combination................................. 178, 317
Configure Rulerunner Account and Permissions on Copy APT Application to Taskmaster Server........ 64
RRServer Windows 2003 .....................................295 Copy APT Application to Taskmaster Server........ 65
Configure Rulerunner Account and Permissions on Copy APT Application to Taskmaster Server...... 252
RRServer Windows 2008 .....................................298 Copy Datacap.xml From DevWorkstation to
Configure Rulerunner as a Web Service ..............214 Taskmaster Server ................................................. 67
Configure Rulerunner Permissions on Server ......214 Copy Taskmaster Client APT Shortcut to
Configure Rulerunner Quattro to Run 1040EZ Workstation ........................................................... 90
Tasks ......................................................................48 Copy Your Images to Input Folder ........................ 84
Configure Rulerunner Quattro to Run APT Tasks Create an RV2 Report Filter .......................... 33, 106
Multi-thread..........................................................167 Create and Share Nested Virtual Directory for
Configure Rulerunner Quattro to Run APT Tasks Taskmaster Web IIS 6 ......................................... 113
Single thread.........................................................165 Create and Share Rulerunner Web Site Windows
Configure Single Thread Rulerunner Quattro ......245 2008 ..................................................................... 226
Configure Taskmaster Application to Use Create and Share Virtual Directory for Rulerunner
Rulerunner as a Web Service ...............................229 Running as Web Service Windows 2003............. 220
Configure Taskmaster Authentication for Create Backup Folders......................................... 238
Taskmaster ...........................................................275 Create NENU Application ........................... 200, 291
Configure Taskmaster Client Service...................191 Create NENU Application using Datacap Studio 200
Configure Taskmaster on Server ....................57, 249 Create or Ensure Account Exists for NENU........ 197
Configure Taskmaster Server Service to use Create or Ensure Account Exists for Rulerunner . 214
Windows Authentication ..............................141, 232
Create or Ensure Account Exists for Taskmaster
Configure Taskmaster to use Windows Client Service ...................................................... 184
Authentication ......................................................141
Create or Ensure Account Exists for Taskmaster
Configure Taskmaster Web on Single Machine ...244 Server Service........................................................ 58
Configure Taskmaster Web on Windows 2003 IIS Create or Ensure Accounts Exist and are Part of
6.0 Server .............................................................264 Security Group..................................................... 232
Configure Taskmaster Web on Windows 2008 IIS Create or Ensure Accounts Exist for Developers
7 Server ................................................................267 and End Users........................................................ 58
Configure Type of Quattro Authentication...........274 Create or Ensure AD LDAP Security Group Exists
Configure Windows Authentication for Quattro................................................................. 140
Taskmaster ...........................................231, 274, 301 Create or Ensure AD/LDAP Security Group
Configure Windows Task Scheduler to Run NENU Exists ................................................................... 232
Ruleset Automatically Windows 2003 .................293 Create or Ensure an Account Exists for Taskmaster
Configure Windows Task Scheduler to Run NENU Web ..................................................................... 108
Ruleset Automatically Windows 7 and Windows Create or Ensure an RV2 Windows Account Exists94
2008......................................................................294
Create or Ensure Domain Exists .......................... 232

Create or Ensure Domain Exists Quattro..............140 F

Create or Ensure Quattro Account Exists .....140, 145 Find FPXML Files Button ................................... 326
Create Taskmaster Web Site ..........................35, 121 Find Problems Button .......................................... 326
D Fingerprint Database............................................ 325
Database ...............................................................325 Fingerprint Directory ........................................... 325
Database Section ..................................................327 Fingerprint Maintenance...................................... 235
Datacap Application Copy Wizard.......................252 Fingerprint Maintenance Tool Buttons ................ 326
Datacap Login Tab ...............................................309 Fingerprint Maintenance Tool Configuration
Datacap Quattro Tab ............................................309 Settings File ......................................................... 326
Datacap Studio .......................................................10 Fingerprint Maintenance Tool Field Definitions . 325
Date Added...........................................................325 Fingerprint Maintenance Tool Reference ............ 325
Delete All Rulesets in NENU Application ...........204 Fingerprint Maintenance Tool Troubleshooting .. 236
Delete Fingerprint ..........................................87, 235 FingerprintBackupDirectory Setting.................... 327
Delete Program Shortcuts.....................................241 FingerprintDatabase Setting ................................ 327
Delete Registry Keys............................................239 FingerprintDirectory ............................................ 327
Delete Remaining Folders ....................................241 First Things to Check........................................... 321
Delete Selected Button .........................................326 FMT Backup Directory........................................ 236
Determine Tasks to be Performed by NENU .......195 FMT.Log ............................................................. 236
Determine Which Datacap Application to FPXML................................................................ 325

Process .................................................................184 G
Determine Which Taskmaster Tasks to Process...173 Grant DCOProcessor Permissions to Rulerunner in
Developer Workstation Setup...............................252 DCOM Config Windows 2003 ............................ 218
Disconnect and Reconnect to Different Application Grant DQCS Log On as Service Right .. 47, 152, 159
Combination.................................................180, 319 Grant Quattro Log On as Service Right. 46, 152, 159
Document Hierarchy ............................................325 Grant Rulerunner Access to IIS Metabase
Domain/Windows Accounts...................................16 Windows 2003..................................................... 217
E Grant RV2 Account Access to IIS Metabase
Windows 2003............................................... 97, 112
Enable Quattro Processing Logging .....................322
Grant Taskmaster Client Service Log On as a
Encrypt Taskmaster Login Service Right ....................................................... 186
Password ........ 48, 151, 157, 164, 170, 178, 182, 317
Grant Taskmaster Server Service Log On as a
End User Workstation and Permissions Setup .....258 Service Right ......................................................... 58
Ensure All Taskmaster Clients are Shut Down.....237 H
Ensure All Taskmaster Web Sites and Services are
Shut Down............................................................238 Handle Unknown Invoice when Vendor is
Unknown ............................................................... 80
Ensure or Set Location of Datacap.xml ............23, 47
Hits/Month........................................................... 325
Ensure Required IIS Components are Installed
Windows 2008......................................101, 119, 223 I
Ensure Required IIS Components are Installed Identify Detail Lines on Unknown Invoice............ 79
Windows 7 .......................................................31, 35 Identify Fingerprint ID Associated with Problem
Ensure Scanner is Set Up and Works ...............16, 90 Invoice ................................................................... 86
Ensure Taskmaster Server Service is Shut Down.238 Install Configure and Run on Client and Server .. 53
Export Selected Button.........................................326 Install Configure and Run on Single Machine ..... 19
Export Selected Fingerprints ................................235 Install and Configure Datacap Rulerunner Quattro
on Windows 2003 Server..................................... 148

Install and Configure Datacap Rulerunner Quattro Installation Instructions for Taskmaster Server ..... 56
on Windows 2008 Server .....................................154 Installation Instructions for User Workstation ....... 88
Install and Configure NENU ........................195, 290 InstallShield Parameters ...................................... 305
Install and Configure Quattro on Windows 2003 Internet Explorer.................................................... 37
Server ...................................................................276
Introduction to Datacap Rulerunner Quattro.......... 45
Install and Configure Quattro on Windows 2008
Server ...................................................................278 Introduction to IBM Datacap Taskmaster Capture
8.0.1 ......................................................................... 9
Install and Configure Rulerunner as a Web
Service..................................................................214 Introduction to NENU ......................................... 195
Install and Configure Rulerunner as a Web Introduction to Rulerunner Quattro...................... 137
Service..................................................................295 Introduction to Single Thread Rulerunner
Install and Configure Rulerunner on Quattro................................................................... 45
RRServer ......................................................217, 223 L
Install and Configure Rulerunner Quattro ............137
Last Hit ................................................................ 326
Install and Configure RV2 on Windows 2003
Locate and Delete Partial Fingerprints................. 235
Web Server.....................................................95, 259
Locating Applications on a Network ..................... 12
Install and Configure RV2 on Windows 2008
Web Server...................................................101, 260 Log Onto RV2 ....................................... 33, 105, 136
Install and Configure Taskmaster Client Logging – Quattro Log Tab ................................. 314
Service..........................................................184, 287 Logging – RRS Log Tab...................................... 315
Install and Configure Taskmaster RV2 ..................93 Logging – System Event Log Tab ....................... 314
Install and Configure Taskmaster Web ................108 M
Install and Configure Taskmaster Web on IIS 6
Make a Note of and Shut Down Taskmaster
Server ...................................................................109
Client and Web Software............................. 141, 161
Install and Configure Taskmaster Web on IIS 7
Make a Note of and Shut Down Taskmaster
Server ...................................................................118
Software............................................14, 46, 148, 154
Install Instructions for Developer Workstation.....198
Install Quattro on QServer Windows 2003...........149 ................ 17, 20, 56, 62, 88, 101, 118, 155, 189, 223
Install Quattro on QServer Windows 2008...........156 Microsoft Windows Installer Parameters............. 305
Install RV2 on WebServer..............................97, 102 Modify the RV2 Dashboard........................... 34, 107
Install Scanner ........................................................63 Monitor APT Batches during Quattro Processing 169
Install Taskmaster Client on DevWorkstation......252 Monitor Batches during Quattro Processing ........ 181
Install Taskmaster Client Service on TCSServer..190 Monitor Quattro Processing of 1040EZ on Single
Install Taskmaster Components on Single Machine ................................................................. 52
Machine..................................................................21 Most Commonly Used Taskmaster Setup.exe
Install Taskmaster Options on QServer ........149, 156 Parameters ........................................................... 305
Install Taskmaster Options on TCSServer............189 N
Install Taskmaster Server Components on Server ..56 NENU .................................................................... 10
Install Taskmaster Server on Server .....................248 NENU Application Setup Actions ....................... 210
Install Taskmaster Web on WebServer ........110, 120 NENU Batch Processing Actions ........................ 211
Install Web Rulerunner Service on NENU Components ............................................. 195
RRServer ......................................................219, 224
NENU Logging Actions ...................................... 212
Installation and Configuration of NENU..............197
NENU Query Setup Actions................................ 210
Installation and Configuration Prerequisites...........13
NENU Reporting Actions.................................... 213
Installation Instructions for Developer
Next Steps.................................................... 153, 160
Workstation ............................................................62
Installation Instructions for Single Machine...........20

O Remove Web Sites and Virtual Folders ............... 239
Obtain Task Profile Name ............................162, 176 Reset Application Pool Process Model Identities 240
Overview of Copying APT to Taskmaster Server ..64 Restart Internet Information

Services IIS...................................117, 124, 222, 228
Overview of Installation of NENU in
Client-Server Environment...................................197 Restart Taskmaster Software ....................... 171, 183
Overview of Quattro Installation in Client-Server Review Default Installation Results................. 28, 82

Environment.........................................................138 Rulerunner Quattro .......................................... 10, 45
Overview of Rulerunner as a Web Service Rulerunner Quattro Manager ............................... 309
Installation............................................................214 Rulerunner Quattro Manager Reference .............. 309
Overview of RV2 Installation and Rulerunner Quattro on Single Machine ................. 45
Configuration ...................................................31, 94
Run a Ruleset with NENU Manager.................... 206
Overview of Taskmaster 8.0.1 Uninstall
Process .................................................................237 Run Application Tasks ........................................ 181
Overview of Taskmaster APT ................................71 Run Application Tasks using Quattro.................. 181
Overview of Taskmaster Architecture......................9 Run aspnet_regiis.exe ............................ 95, 112, 218
Overview of Taskmaster Client 1040EZ ................23 Run Datacap Studio Application ......................... 194
Overview of Taskmaster Client Service Run Taskmaster APT............................................. 85
Installation............................................................184 Run Taskmaster APT FlexID Task........................ 74
Overview of Taskmaster Components....................10 Run Taskmaster Client 1040EZ Export Task .. 27, 44
Overview of Taskmaster Installation on Client Run Taskmaster Client 1040EZ PageID Task . 24, 42
and Server...............................................................54
Run Taskmaster Client 1040EZ Recognize
Overview of Taskmaster Installation on Single Task ................................................................. 25, 42
Machine..................................................................19
Run Taskmaster Client 1040EZ Scan Task ..... 24, 51
Overview of Taskmaster Web Client 1040EZ........39
Run Taskmaster Client 1040EZ Tasks using
Overview of Taskmaster Web Client APT ...........129 Quattro........................................................... 50, 247
Overview of Taskmaster Web Installation and Run Taskmaster Client 1040EZ Verify Task......... 25
Configuration .......................................................108
Run Taskmaster Client APT Application ........ 71, 72
Overview of Taskmaster Windows Authentication
Run Taskmaster Client APT Batch Profiler
Processing ............................................................231
Task Background Shortcut............................. 75, 132
Overview of Windows Authentication
Run Taskmaster Client APT Export Task
Configuration Process ..........................................231
Export Shortcut.............................................. 78, 134
P Run Taskmaster Client APT Scan ....................... 169
Package the Client Configuration Tool ........125, 271 Run Taskmaster Client APT Tasks using
Paths Section ........................................................327 Quattro......................................................... 168, 282
Permission Denied Load Picture Error .................86 Run Taskmaster Client APT Verify Task
Verify Shortcut ...................................................... 75
Process Multiple Unknown Invoices for Known
Vendor in Single Batch ..........................................80 Run Taskmaster Client APT VScan Task Scan
Shortcut.................................................................. 73
Process Unknown Invoice for Known Vendor .......79
Run Taskmaster Client on DevWorkstation ........ 255
Q
Run Taskmaster Client on Single Machine.......... 243
Quattro Configuration Assumptions.....................137
Run Taskmaster Web Client 1040EZ
R Application ............................................................ 39
Recreate the Fingerprint for the Invoice .................87 Run Taskmaster Web Client 1040EZ
Upload Task........................................................... 41
Remove Accounts from Administrator and
Backup Operator Groups......................................239 Run Taskmaster Web Client 1040EZ
Verify/Fixup Task.................................................. 43
Remove Process Identity from Machine.Config
File .......................................................................240

Run Taskmaster Web Client 1040EZ Set Rulerunner Account Security Permissions for
VScan Task ............................................................40 Datacap\RRS Folder Windows 2003 ................... 215
Run Taskmaster Web Client Application .............273 Set Rulerunner Account Security Permissions for
Run Taskmaster Web Client APT Application.....129 Datacap\RRS Folder Windows 2008 ................... 215
Run Taskmaster Web Client APT Scan Task.......130 Set Rulerunner Account Sharing Permissions for
Datacap Folder..................................................... 214
Run Taskmaster Web Client APT Upload Task ...131
Set RV2 Sharing Permissions for Datacap Folder
Run Taskmaster Web Client APT Verify Task ....133 Windows 2003....................................................... 96
RV2 ........................................................................10 Set RV2 Sharing Permissions for Datacap Folder
S Windows 2008..................................................... 102
Set Security Permissions...................................... 254
Sample AutoDelete Ruleset..................................209
Set Sharing Permissions for Datacap Folder
Select All Button ..................................................326
Windows 2003..................................................... 148
Select Web Service Extensions for Rulerunner
Set Sharing Permissions for Datacap Folder
Windows 2003......................................................222
Windows 2008..................................................... 154
Select Web Service Extensions IIS 6....................114
Set Taskmaster Client Service Security
Server Setup .........................................................248 Permissions for Datacap Folder Windows 2003 .. 188
Set IIS ASP Request Size Limit Set Taskmaster Client Service Security
Windows 2008..............................................123, 225 Permissions for Datacap Folder Windows 2008 .. 188
Set Location of Datacap.xml Set Taskmaster Client Service Security
.....60, 91, 98, 103, 117, 124, 150, 156, 191, 222, 227 Permissions for Datacap\Application Folder ....... 188
Set Location of Taskmaster Server and Set Taskmaster Client Service Security
Datacap.xml ...................................................67, 202 Permissions for Datacap\RRS Folder .................. 188
Set NENU Account Security Permissions for Set Taskmaster Client Service Sharing Permissions
Datacap Folder Windows 2003 ............................198 for Datacap Folder Windows 2003 ...................... 187
Set NENU Account Security Permissions for Set Taskmaster Web Application Pool
Datacap Folder Windows 2008 ............................198 Identity IIS 7........................................................ 122
Set NENU Account Security Permissions for Set Taskmaster Web Sharing Permissions for
Datacap\NENU Application Folder......................203 Datacap Folder Windows 2003............................ 109
Set NENU Account Security Permissions for Set Taskmaster Web Sharing Permissions for
Datacap\RRS Folder.............................................198 Datacap Folder Windows 2008............................ 119
Set NENU Account Security Permissions for Set Up Datacap Folder Sharing for Taskmaster
Monitored Application Folder..............................203 Client Service Windows 2008 ............................. 187
Set NENU Account Sharing Permissions for Set Up Quattro Restarts ................170, 182, 283, 285
Datacap Folder Windows 2003 ............................197
Set Up RV2 on Single Machine........................... 243
Set NENU Account Sharing Permissions for
Set Up RV2 Web Site IIS 6 ................................... 99
Datacap Folder Windows 2008 ............................197
Set Up RV2 Web Site IIS 7 ........................... 32, 104
Set or Confirm Timeout Parameters for Rulerunner
Running as Web Service Windows 2003 .............221 Set Up Security for RV2 on Datacap Folder
Windows 2003....................................................... 96
Set or Ensure Correct Datacap.xml File is in Use ..65
Set Up Security for RV2 on Datacap Folder
Set Other Parameters for Nested Taskmaster Web
Windows 2008..................................................... 102
Site IIS 6...............................................................113
Set Up Security for Taskmaster Web on
Set Other Parameters for RV2 Web Site IIS 6........99
Datacap Folder Windows 2003............................ 109
Set Rulerunner Account Security Permissions for
Set Up Security for Taskmaster Web on
Batches Folder Windows 2003.............................215
Datacap Folder Windows 2008............................ 119
Batches Folder Windows 2008.............................215
Windows 2003....................................................... 59
Datacap Folder .....................................................214
Windows 2008....................................................... 60

Set Up Security on Datacap\Application Start or Ensure Taskmaster Server Service

Folder Windows 2003 ............................................70 is Started ....... 23, 39, 48, 50, 72, 105, 124, 129, 145,
Set Up Security on Datacap\Application 162, 163, 176, 177, 185, 194, 200, 203, 229, 232
Folder Windows 2008 ............................................70 Start Quattro ...................................52, 169, 181, 323
Set Up Security on Datacap\APT Folder..............161 Start Taskmaster Client 1040EZ................ 28, 42, 51
Set Up Security on Datacap\MyApp Folders .......175 Start Taskmaster Client 1040EZ Application for
Set Up Security on Datacap\RRS Folder......161, 175 the First Time......................................................... 24
Set Up Security on Datacap\RRS Start Taskmaster Client Application ............ 168, 181
Windows 2003........................................................60 Start Taskmaster Client
Set Up Security on Datacap\RRS APT ........................................82, 132, 142, 145, 229
Windows 2008........................................................60 Start Taskmaster Client APT for the First Time .... 73
Set Up Security on Shared Folder Start Taskmaster Server on Single Machine ........ 242
Windows 2003......................................................149 Start Up Datacap Studio ...................................... 194
Set Up Security on Shared Folder Stop or Ensure Quattro Service is Stopped .......... 322
Windows 2008......................................................155
Stop or Ensure Taskmaster Server Service is
Set Up Sharing and Security Permissions for Stopped ............................................................ 35, 50
End Users ...............................................................89
Stop or Ensure the Taskmaster Client Service is
Set Up Taskmaster Application to Use Scanner .....90 Stopped ................................................................ 193
Set Up Taskmaster APT to Process Your Stop or Ensure the Taskmaster Server Service is
Invoice Images ...............................................84, 256 Stopped ...........................95, 109, 118, 163, 175, 177
Set Up TaskRun Virtual Folder Windows 2003 ...115 Stop the Taskmaster Client Service when in
Set Up Web Sharing and Security Settings on Display Mode ...................................................... 193
TaskRun Folder Windows 2003 ...........................115 Summary of NENU Actions ................................ 209
Set Up Web Sharing and Security Settings on
T
TaskRun Folder Windows 2008 ...........................122
Set Up WRRS Folder Account Permissions for Taskmaster Client .................................................. 10
Rulerunner Windows 2003...................................220 Taskmaster Client Service ..................................... 10
Set Up WRRS Folder Account Permissions for Taskmaster Client-Server Configuration ......... 13, 53
Rulerunner Windows 2008...................................225
Taskmaster Installer Command Line Parameters. 305
Set Web Site Isolation Mode for Rulerunner
Taskmaster RV2 .............................................. 30, 93
Windows 2003......................................................221
Taskmaster Server ................................................. 10
Set Web Site Isolation Mode IIS 6 .......................114
Taskmaster Web ...................................... 10, 35, 108
Settings.INI File ...................................................326
Taskmaster Web Client 1040EZ Application ........ 39
SetupDCO Setting ................................................327
Taskmaster Web Client APT Application............ 129
Share Datacap Folder and Set Sharing Permissions
Windows 2003........................................................58 Test Access to Rulerunner ........................... 222, 227
Share Datacap Folder and Set Sharing Permissions Test Internet Explorer .......................................... 127
Windows 2008........................................................59 Test Taskmaster Application Using Rulerunner
Show Statistics Button..........................................326 as a Web Service.................................................. 230
Shut Down Taskmaster Software ...........................84 Test Taskmaster Client Service and View
Processing............................................................ 192
Single IIS 7 Machine Installation .........................242
Test Taskmaster Client Service by Running
Single Machine Setup Checklist...........................242
Application .......................................................... 192
Start Datacap Studio and Open NENU
TIF ....................................................................... 326
Application...........................................................204
TIFF .................................................................. 326
Start Datacap Studio to Use Application
Wizard............................................................64, 200 Total Hits ............................................................. 326
Start Fingerprint Maintenance Tool ...............87, 235 Troubleshooting Quattro...................................... 321

U View Standard RV2 Report ................... 33, 106, 136
Uninstall Taskmaster 8.0.1 ...................................237 View Taskmaster Client 1040EZ Groups .............. 28
Update ASP.NET Process Identity in View Taskmaster Client 1040EZ Groups Users
Machine.Config File Stations .................................................................. 28
Windows 2003........................................96, 112, 217 View Taskmaster Client 1040EZ Stations ............. 29
Update Authentication Parameter in Taskmaster View Taskmaster Client 1040EZ Users................. 28
Client Application Shortcut..................................234 View Taskmaster Client APT Groups ................... 82
Update Datacap.xml on Server.............................254 View Taskmaster Client APT Groups Users
Update Datacap.xml on Taskmaster Server....69, 201 Stations .................................................................. 82
Use Fingerprint Maintenance Tool.......................303 View Taskmaster Client APT Stations .................. 83
Use Taskmaster Authentication............................145 View Taskmaster Client APT Users ...................... 83
Use the Fingerprint Maintenance Tool .................235 View Taskmaster Client Service Processing........ 193
Use Windows Authentication...............................140 W
Uses for NENU ....................................................195 Web Rulerunner Service........................................ 10
Using Taskmaster 1040EZ .....................................23 Welcome.................................................................. 7
Using Taskmaster APT ..........................................71 What is IBM Datacap Taskmaster Capture? ............ 9
V Workflow Job Task - Advanced Settings Tab ..... 313
View Batches Processed by Quattro Workflow Job Task – Application Information
using Job Monitor.........................................169, 181 from the Taskmaster Application Service............ 311
View Event Viewer Logs on QServer ..................321 Workflow Job Task - Node Settings lower right.. 313
View Quattro Processing Logs .............................323 Workflow Job Task - Quattro Settings Tab ......... 312
View RV2 Reports for APT .................................262 Workflow Job Task – Threads............................. 311
View RV2 Reports for Taskmaster Client APT ...105 Workflow Job Task Tab ...................................... 311
View RV2 Reports for Taskmaster Web APT......136

Notices
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in
other countries. Consult your local IBM representative for information on the
products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
be used instead. However, it is the user's responsibility to evaluate and verify the
operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not grant you
any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing

IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact the IBM
Intellectual Property Department in your country or send inquiries, in writing, to:
Intellectual Property Licensing

Legal and Intellectual Property Law
IBM Japan Ltd.
1623-14, Shimotsuruma, Yamato-shi
Kanagawa 242-8502 Japan
The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law: INTERNATIONAL
BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS"
WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR
PURPOSE. Some states do not allow disclaimer of express or implied warranties in
certain transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors.

Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the publication. IBM may make improvements
and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for
convenience only and do not in any manner serve as an endorsement of those Web
sites. The materials at those Web sites are not part of the materials for this IBM
product and use of those Web sites is at your own risk.
1
IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose
of enabling: (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of the
information which has been exchanged, should contact:
IBM Corporation
Office 4360
One Rogers Street
Cambridge, MA 02142
U.S.A.
Such information may be available, subject to appropriate terms and conditions,

including in some cases, payment of a fee.
The licensed program described in this document and all licensed material
available for it are provided by IBM under terms of the IBM Customer Agreement,
IBM International Program License Agreement or any equivalent agreement
between us.
BalloonWindows, portions are Copyright (c) 2002-2003 Peter Rilling
Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of
International Business Machines Corporation, registered in many jurisdictions
worldwide. Other product and service names might be trademarks of IBM or other
companies. A current list of IBM trademarks is available on the Web at
http://www.ibm.com/legal/copytrade.shtml
Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered
trademarks or trademarks of Adobe Systems Incorporated in the United States,
and/or other countries.
Microsoft and Windows are trademarks of Microsoft Corporation in the United

States, other countries, or both.
Other product and service names might be trademarks of IBM or other companies.
2 Installation and Configuration Guide

Program Number: 5725-C15
Printed in USA
GC19-3232-01

c1932321 PDF

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

c1932321 PDF

Caricato da

Copyright:

Formati disponibili

IBM Datacap Taskmaster Capture

Installation and Configuration Guide

Installation and Configuration Guide

Copyright © 1994, 2011 Datacap Inc. Page 3

Internet Explorer ........................................................................................................... 37

Chapter 6.................................................................................................. 237

Page 4 Copyright © 1994, 2011 Datacap Inc.

Ensure Taskmaster Server Service is Shut Down........................................................ 238

Appendix A .............................................................................................. 243

Appendix B............................................................................................... 249

Copyright © 1994, 2011 Datacap Inc. Page 5

Install and Configure Taskmaster Web ....................................................................... 265

Appendix C .............................................................................................. 305

Appendix D .............................................................................................. 309

Appendix E............................................................................................... 325

Index ......................................................................................................... 329

Page 6 Copyright © 1994, 2011 Datacap Inc.

About this Guide

Chapter 2: Introduction to IBM Datacap Taskmaster Capture 8.0.1

Chapter 3: Installation and Configuration Prerequisites

Chapter 4: Install, Configure, and Run on Single Machine

Copyright © 1994, 2011 Datacap Inc. Page 7

Chapter 5: Install, Configure, and Run on Client and Server

Chapter 6: Uninstall IBM Datacap Taskmaster Capture 8.0.1

Appendix A: Single Machine Setup Checklist

Appendix B: Client-Server Setup Checklist

Appendix C: Taskmaster Installer Command Line Parameters

Appendix D: Rulerunner Quattro Manager

Appendix E: Fingerprint Maintenance Tool Reference

Page 8 Copyright © 1994, 2011 Datacap Inc.

Introduction to IBM Datacap Taskmaster Capture 8.0.1

What is IBM Datacap Taskmaster Capture?

Overview of Taskmaster Architecture

Copyright © 1994, 2011 Datacap Inc. Page 9

Overview of Taskmaster Components

Page 10 Copyright © 1994, 2011 Datacap Inc.

• Datacap Studio is the Taskmaster application development environment. When you

Copyright © 1994, 2011 Datacap Inc. Page 11

Locating Applications on a Network

Page 12 Copyright © 1994, 2011 Datacap Inc.

Installation and Configuration Prerequisites

Taskmaster Client-Server Configuration

Copyright © 1994, 2011 Datacap Inc. Page 13

• Developer Workstation (referred to as the "DevWorkstation") hosts the complete

Before You Begin

Make a Note of and Shut Down Taskmaster Software

Page 14 Copyright © 1994, 2011 Datacap Inc.

3 Taskmaster Server Service

Backup and Uninstall Taskmaster Versions 7.1 and 7.1 SP1

Back Up Taskmaster Version 7.5, 7.5 SP1, 7.6, or 8.0

Copyright © 1994, 2011 Datacap Inc. Page 15

Ensure Domain/Windows Accounts Exist

Ensure Scanner is Set Up and Works

Page 16 Copyright © 1994, 2011 Datacap Inc.

Microsoft .NET Framework 3.5.1

Copyright © 1994, 2011 Datacap Inc. Page 17

Page 18 Copyright © 1994, 2011 Datacap Inc.

Install, Configure, and Run on Single Machine

Overview of Taskmaster Installation on Single Machine

Copyright © 1994, 2011 Datacap Inc. Page 19

Installation Instructions for Single Machine

Microsoft .NET Framework 3.5.1

Page 20 Copyright © 1994, 2011 Datacap Inc.