Tungsten Capture Network Server
Tungsten Capture Network Server (TCNS) adds Internet and Intranet processing capabilities to Tungsten Capture.
With this capability, Tungsten Capture remote stations can be connected to a central site through the Internet (or Intranet) to assist in the production document and data capture process. Batches can be scanned and processed at the remote site, and then uploaded to the central site for further processing and export.
TCNS eliminates the common and costly practice of shipping documents from remote offices or a central site for processing. It supports remote scanning and processing of documents through the Internet or Intranet.
With TCNS, documents can be scanned inexpensively at remote stations and then automatically uploaded to the central site, securely and reliably.
Integration with Tungsten Capture
Options for configuring and using TCNS are available from the Tungsten Capture Administration and Batch Manager modules.
Centralized Administration
The Tungsten Capture system administrator can centrally manage configuration information, station licenses, schedules for uploading batches, and batch class definitions for all remote sites by creating and assigning remote site profiles to remote sites.
You can specify the default behavior for assigning remote site profiles to new remote sites. This behavior is automatically used when a new remote site synchronizes with the Tungsten Capture Network the first time. For example, if there is a remote site profile with a name matching a remote site, you can set a policy in which the remote site automatically receives the matching remote site profile.
Centralized License Management
Tungsten Capture supports a centralized license management scheme that requires a software license or hardware key (optional) on the Tungsten Capture Network (in a client/server installation) and standalone stations (in standalone installations) at the central site. No licensing is required for Tungsten Capture Network remote site stations.
Tungsten Capture Network also requires Tungsten Capture Network volume licenses. However, all licensing is managed at the central site.
For more information about the Tungsten Capture options purchased for your company, contact your system administrator or Tungsten Automation Certified Solution Provider.
For more information on central site license management and licensing, contact your system administrator.
Data Security
With Tungsten Capture Network, remote stations do not have to be connected to the central Tungsten Capture server while processing batches. You can set your remote stations to connect with your central site and then synchronize with your central site at predetermined intervals or on demand.
Offline Capability
With Tungsten Capture Network, remote stations do not have to be connected to the central Tungsten Capture server while processing batches. You can set remote stations to connect and synchronize with your central site at predetermined intervals, or on demand.
Remote Site Profile Support
Use Tungsten Capture Network to create remote site profiles. Remote site profiles are groups of settings that you assign to one or more remote sites.
An important feature is that you can exclusively specify where in the Tungsten Capture workflow the remote site routes batches to the central site.
Batch Class Assignment
Tungsten Capture Network allows you to control which batch classes are visible to specific remote sites. This is provided through remote site profiles.
Event Logging
Tungsten Capture Network maintains a comprehensive log of polling activity and other events. Logs are maintained at both the central site and the remote sites.
Site Switching Capability
With Tungsten Capture Network, you can easily switch Web servers or central sites, if necessary.
The major Tungsten Capture Network features are described here.
Remote Synchronization Capability
Through the Remote Synchronization Agent (RSA), you can easily synchronize with the central site on a defined schedule or on demand. Synchronization allows you to download batch classes and upload completed batches to the central site at the same time.
Assign Web Server Port Number
If you do not want to use the standard TCN Web Server ports, you can assign alternate ports. By default, all HTTP communications use port 80, and all SSL communications use port 443.
Web Cache Affinity
If you have cache folders in multiple locations, a TCN Service "prefers" to use its local cache older (if there is one) rather than the other caches, provided other factors (such as priority) are equal. This "cache affinity" reduces network overhead and may increase performance.