Installation guide

If the Connector renames the file name passed to it by the Manager, it is the Connector’s responsibility to
publish that information to the Manager for tracking purposes. If the Connector does not publish the
renamed files, the filename or filenames generated by the Manager are displayed.
4.8.3 - Activity Tracking operation
The scan job activity is written to the database after the Connector sends the final document to its
destination successfully. By the time the Redirect form is displayed, the transaction is being written to the
database in the background. In case of an error sending the document using the Connector, since the
Redirect form is not displayed, the activity is not written to the database. This means that only successful
transactions and activity are being recorded.
When a Connector profile has Offline processing enabled, the final document creation and processing is
performed in the background (Error message or Redirect form status is not available).
In this case, the following scenario can happen:
n If the final document is created successfully, but could not be sent out to its destination using the
Connector, the activity is logged into the database with an error message returned by the Connector
along will all the additional information about the scan job.
n If the final document creation failed, then the activity is logged into the database with an error
message returned by the Manager along with all the additional information about the scan job.
n If the final document was created successfully and sent to its destination using the Connector, the
activity is logged into the database with a Success message along will all the additional information
about the scan job.
A part of the Activity Report has the data filled in by the Connector at run time. It is the Connectors
responsibility to fill this information using the Publishing Interface.
4.8.4 - Migrating Activity Tracking data
In case you want to use your already-existing Activity Tracking data on a newly-installed ShareScan version,
you can migrate the data by following the steps below:
1. Launch the ActivityTrackingReport.DataMigration.exe tool, located in the Server/Tools folder
of your ShareScan installation. The tool uses the current connection string from the registry, and uses
that to create a new SQL table for the exported data, which will be available on the newly installed
ShareScan Manager.
Enter an sa-level username/password combination on the UI of the tool.
You can use the following command line arguments for the tool:
n /ConnectTimeout (only set if your database is large-scale, and has exceedingly slow
connection)
n /DataSource (by default, taken from the registry)
n /InitialCatalog (by default, taken from the registry)