Move files in batch for default local volumes

Default local volumes are temporary local volumes that allow files to be stored locally before they are automatically transferred to the final destination volume. This functionality is also known as store and forward. By default, the store and forward functionality moves files from the local volume one at a time using the fmstranslator Dispatcher translator. You can use the store_and_forward Dispatcher translator to upload files in batch. This is useful in situations when an FMS volume does not exist on the LAN with the remote user. In these situations, the closer the initial volume is to the user uploading the file, the faster the upload. Perform the following steps to configure moving files in batch for default local volumes: Procedure Install and configure the translator. Choose Enterprise Knowledge Foundation > Dispatcher Server. Then, in the Select Translators panel, select the StoreAndForward translator. If you have questions about setup, see the instructions in the \Module\Translators\store_and_forward\Readme.txt file. In the rich client, set the TC_Store_and_Forward preference to true. To set the preference, choose Edit > Options to open the Options dialog box, and then use the Search tab in the dialog box to locate the preference. Set the FMS_SAF_Batch_Transfer_Enabled preference to true. This switches the transfer mode from moving files one at a time (using the fmstranslator translator) to moving files in batches (using the store_and_forward translator). In the Organization application, choose Edit→User Setting to set the local volume for the user in the User Settings dialog box. Optionally, to view the files in local volumes to be moved to default volumes, run the move_volume_files utility with the -listaf argument. Run the store_and_forward translator in the Dispatcher Admin Client as a repeating job. This translator in turn runs the move_volume_files utility with the -transferaf argument, which queries the database for the user files in local volumes and transfers them to their respective default volumes. It also automatically schedules a task to clean up the files from the local volumes. You can also run the move_volume_files utility as a cron job or as a scheduled task using process_move_file_volumes as a .sh or .bat script, respectively. Note If you choose to use the Dispatcher Admin Client to schedule repeating jobs, ensure that the module service is started by an OS user who is a member of the dba group. This is mandatory because the -transferaf argument of the move_volume_files utility must have DBA privileges with bypass authority to commit the database records belonging to different users. However, if you use the cron job to schedule repeating jobs, you do not have this restriction. After the translator setup is complete, verify the translator installation: Create datasets in the local volume using the rich client. Import files into the datasets. Verify the files are created under the local volume. Schedule the repeating store_and_forward translation job using the Admin Client. After the translation is complete, verify that the files are moved to the default volume.