Automated synchronization

This applies to stand-alone installations of the Batch Manager and Rest Services, and to all installations of Web Services.

The file must be named bootstrap.config, and it must be placed in a SharedFiles\Default directory within the Batch Manager, Rest Services, or Web Services application directory.

This example shows the structure of the bootstrap file:

<?xml version="1.0" encoding="utf-8"?>
<BootStrapConfiguration>
  <FileSystem>
    <FileManagers>
      <FileManager Type="Hansen.Core.FileManagement.IpsNetworkShareFileManager, Core" 
          SyncOnAppStart="true" IsRootDir="false">
        <Dependencies>
          <Dependency Id="rootPath" Value="path_to_local_enhancement_dir" />
          <Dependency Id="cachePath" Value="path_to_local_enhancement_dir" />
          <Dependency Id="remotePath" Value="path_to_ips_enhancement_dir" />
        </Dependencies>
      </FileManager>
    </FileManagers>
  </FileSystem>
</BootStrapConfiguration>

Replace the paths in the example with the actual values from your network. For example, the remote path might be something like \\O&RServer\O&RPath\Enhancement. The user under which the w3wp process is running must have Read access to this directory.

The application must be restarted and must then receive a request before the sync will occur.

If you also want to synchronize config files, set the IsRootDir attribute on the FileManager element to "true" and set the root path, cache path, and remote path to the roots of the respective Infor Operations and Regulations application directories.

This will sync all agency config files in the Config directory, such as Hansen8_Agency_en-US_changes.config, as well as syncing the Enhancement directory. The File Manager will only synchronize the specified files, so the rest of the application directory is ignored.