After you install the Taskmaster Web Client
upload service, you must specify which application to use when you
upload batches.
You must also specify the user password for that application
and configure these settings on every scanning client where you installed
the
Taskmaster Web Client
upload service.
Tip: You must configure your applications
regardless of the method that you use to upload batches:
- Uploading batches by using Taskmaster Web
- Uploading batches by using a strict upload
- Uploading batches by using FastDoc
To configure applications to use the Web Client upload
service
- From the Datacap/Taskmaster folder,
open the dc2Run.exe.config file in a text editor.
- For the setting name parameter, enter the name of the application
that you will use to upload the batch files. For example,
if you are uploading batch files to the FastApp application, enter FastApp.
<setting name="Application" serializeAs="String">
<value>FastApp</value>
</setting>
- Set the user password that is used to authenticate the Taskmaster application.
- In Taskmaster Application
Manager, open the application that you are uploading the batches to,
such as FastApp.
- From the Custom Values tab, enter
the Value name dc2run.User in the Advanced
Values section. The value for User must be
the Taskmaster user
and must be the same user in the dc2Run.exe.config file.
The username is case sensitive. For example, if the
user is admin, the name must be dc2run.admin. In
the case of a domain user, for example DEVAD002\ScanUpload,
the name must be dc2run.DEVAD002\ScanUpload.
- In Value field, enter the user
password. For example, enter admin. The value name 1: in the Advanced values section must match
the user that is specified in the dc2Run.exe.config file.
- Click Add Now.
- From the dc2Run.exe.config file, configure
the following settings:
- dc2Run_localhost_utility
- Change the value of the URL value to reflect the IP address or
UNC name of the Taskmaster Web Server and path to utility.asmx.
<setting name="dc2Run_localhost_utility" serializeAs="String">
<value>http://localhost/tmweb.net/Task/utility.asmx</value>
</setting>
- http
- Change this setting to https if you are
using SSL. This change is made in the master copy of the configuration
file.
<setting name="dc2Run_localhost_utility" serializeAs="String">
<value>http://localhost/tmweb.net/Task/utility.asmx</value>
</setting>
- Application
- The name of the application to be processed by the Datacap Taskmaster Web Client Service. This change is made in the master copy of the configuration
file.
<setting name="Application" serializeAs="String">
<value>TravelDocs</value>
</setting>
- User
- The Taskmaster User for this application. This
change is made in the scan station-specific copy of the configuration
file.
<setting name="User" serializeAs="String">
<value>admin</value>
</setting>
Tip: You can also specify a domain
user. For example, <value>DEVAD002\ScanUpload</value>.
- Station
- The Taskmaster Station
ID of the User. This change is made in the scan station-specific copy
of the configuration file.
<setting name="Station" serializeAs="String">
<value>remote</value>
</setting>
- ShortcutIndex
- The btn_ButtonNumber value for the upload task. This change is
made in the master copy of the configuration file.
<setting name="ShortcutIndex" serializeAs="String">
<value>3</value>
</setting>
To determine the appropriate
ShortcutIndex value
to use:
- On the Taskmaster Server,
open Windows Explorer and
navigate to the Admin database for the application, which is typically
in the application \process folder.
- Use the appropriate database Client software to open the Admin
database.
- Open the Buttons table, find the upload task in the btn_ButtonName
column, and find the number for the upload task in the btn_ButtonNumber
column.
- Delay
- The amount of time for the service to wait after finishing a successful
upload and beginning the next upload. The value is in milliseconds.
This change is made in the master copy of the configuration file.
<setting name="Delay" serializeAs="String">
<value>3000</value>
</setting>
- RetryDelay
- The amount of time for the service to wait between attempts to
complete an upload. The value is in milliseconds. This change is made
in the master copy of the configuration file.
<setting name="RetryDelay" serializeAs="String">
<value>15000</value>
</setting>
- WorkTimes
- Defines the StartTime and StopTime pairs in which the service
is to run. Each Start and Stop pair is defined by using a 24 hour
clock or 12 hour clock. You can use a mix of both types of clocks.
Define as many pairs as you need. Within a pair, be sure the StartTime
is earlier than the StopTime, for example:
- <value>15:02-15:04</value>: An interval
defined by using the 24-hour clock
- <value>3:05 PM-3:07 PM</value>: An
interval defined by using the 12-hour clock
- <value>15:58-16:00;4:06 PM-4:08 PM</value>:
An interval defined by using the 24-hour clock followed by an interval
defined by using the 12-hour clock. To run the service around the
clock, use: <value>0:00-23:59</value>.
<setting name="WorkTimes" serializeAs="String">
<value>14:25-14:27;2:29 PM-2:29 PM</value>
</setting>
Important: The default StartTime
and StopTime value is 15:00-15:00. Be sure that you change the default
to an appropriate value for your environment.
- StrictUpload
- Defines how the batch files are uploaded. Change the value based
on the uploading method:
- FDPathMask
- This value is based on how you upload batches. Clear the FDPathMask
setting when you upload batches with Taskmaster Web or if
you are uploading batches that are created locally by using Taskmaster DotScan, Rulerunner, or FastDoc. You must set the
FDPathMask setting when you upload offline batches by using FastDoc.
<setting name="FDPathMask" serializeAs="String">
<value>c:\\datacap\FastDoc\batches\*\*\finished.xml</value>
</setting>
- Save and close the dc2Run.exe.config file.