Cost Recovery settings

The following table describes the settings available for the Cost Recovery Service.

Setting	Description
Configured	Enables all settings for the service. Select the Yes check box to make all settings configurable.
Port number	Enters port number. The port number must match the TCP port configured for the cost recovery device. The default port is 9325. If you change the Port field, the Manager is automatically restarted after saving your settings.
Show Lock Button	Shows Lock Button at the client if you select the Yes check box. This button allows you to lock the terminal from any screen during a session. This option is only available for ScanStation devices.
Protocols	Selects the protocol. This version of the service supports cost recovery terminals that were configured to work with previous versions of the eCopyCost Recovery Service. Auto detect (v1, v2): Select this option if your terminal is configured to work with earlier versions of the Cost Recovery Service. Unicode/XML (v3): Select this option if your terminal is configured to use version 3 of the Cost Recovery Service. Unicode/XML (v3.5): Select this option if your terminal is configured to use the latest version of the Cost Recovery Service (recommended). All devices controlled by a Manager must use the same protocol.
Field separator	Specify field separator used in Cost Recovery activity logging.
Encryption	Encryption settings must be used if a password is included.
Type	The encryption type for Cost Recovery: None: Passes credentials to ShareScan without encryption. TripleDES: Enables you to encrypt the information from the application supplying the credentials to ShareScan. You can do this by creating an encryption key that you store on the computer where the Manager is running and on the Cost Recovery device.
Path	Set the path for the encryption key. Specifies a path to the storage destination for the encryption key on the device where the Manager is running.
Key	Generates a new key. Generates the encryption key and stores it in the eCopyCRSKey.txt file. You must manually copy this file to the Cost Recovery device. If you regenerate the key, you must copy the new key to the Cost Recovery device. All devices that use Cost Recovery Service and are managed by the same Manager must use the same encryption key. After generating a key for the first device, when you configure subsequent devices, you must select the same path you selected for the first device. ShareScan automatically recognizes the key file that is already in the storage destination.
Activity log	Includes the standard eCopyShareScan user activity log information. If Cost Recovery logging is turned on and you change protocol version in any direction, use a new log file name and extension. If you want to use the same name and extension, you must archive the old logs to a safe location and delete the original ones.
Configure	Track Cost Recovery using activity logging. Enables all settings for the service. Select the Yes check box to enable configuration options.
Location	Root folder for all Cost Recovery logs. The default location is %programdata%\Tungsten\ShareScan\costrecovery.log or %programdata%\Tungsten\ShareScan\costrecovery.xml.
Maximum Log Size (10-5000)	Maximum file size in kB. Maximum log size is 5000 kB.
File overflow type	Activity log file types. Enables file overflow for Cost Recovery, if appropriate: Rolling filenames: ShareScan001, ShareScan002, and so on. Overwrite oldest events: New events will overwrite the oldest events in the log.
Extended fields	Allows extended fields in Cost Recovery activity logging. Select the Yes check box to enable this feature.
Device specific activity	Allows separate Cost Recovery activity logging for each specific device. Select the Yes check box to enable this feature.
Enable for all Devices	Enables settings for all devices.
Enabled	Select the Yes check box to enable the service for all devices.

If the key is re-generated, the eCopyCRSKey.txt file must be copied to the Cost Recovery terminal again. If a key mismatch occurs, the data is not decrypted correctly.