Setting

Definition

Job is active

Check this box to cause the backup job to become active.  When the ESI Secure File Transfer Client pulls its schedule from the MIE, it will only include records that have this box checked.

Transfer is owned by

The name of the user that "owns" this file transfer definition.  When the client pulls its schedule from the MIE, it will only include records that match the user whose credentials have been entered into the client.  It is important that the credentials used to log the client into the MIE match the value placed in this setting.

Type of database

Choose Access or SQL Server.  This determines the type of database where the local backup will be kept.

NOTE: SQL Server is the recommended backup database.  Access, although supported, is not handled as robustly as the backup to SQL server.  Access support is also dependent on Microsoft's jet engine DLL, which Microsoft no longer includes in their newer operating systems.  When choosing where to backup your data, SQL server is the better choice.

Name of your Access database

If you choose Access, this setting will be displayed.  Enter the full path and name for your Access database.  Make sure the path exists on your local computer (either a local path or a shared network path) and that you have write privileges.  Also make sure your database name ends in .MDB.

Example: C:\data\MIE.mdb

Name of your local SQL connection

This is the name, spelled exactly, of the SQL connection you created locally in the SFT client in order to connect to the SQL server and database.  This is the name you gave the connection, and the spelling must match exactly.  The SFT client will use that connection information that you set up locally in order to connect to the SQL server where the backup will be managed.

MIE tables to back up in your local  database

Choose the MIE tables that you want included in your local backup copy.  The SFT client will keep your local tables synchronized with the data on the MIE.

Date to begin automatic transfers

When the client pulls its schedule from the MIE, it will only include records that contain a date value in this setting that has passed.  The time base for this setting is the MIE.

Date to stop automatic transfers

When the client pulls its schedule from the MIE, it will only include records that contain a data value in this setting that is still in the future.  The time base for this setting is the MIE.

Run transfer every

This specifies the frequency with which to run the file transfer.  If it has been at least this much time since the last file transfer attempt, or if no attempt has ever been made, a file transfer will be attempted once the client pulls its schedule.

Run on <day of week>

When checked, the SFT client will run this job on that day of the week.  If not checked, even if it is time to run the job again, the SFT client will wait until a day of the week that has been checked before running the job.  

Do not run start  / end (ESI only)

These two fields specify a window of time (within the day) between which the job cannot run.  This allows keeping database-intensive jobs from running within working hours, for instance.  These fields are only visible to ESI.

How to notify

Always will cause the SFT client to email the job's owner with the results of every transfer attempt. Never will turn such notification off.