IDM Agent FileRepository Configuration Example

To specify files to upload and the destination directory for file downloads for Axeda IDM Agents, you cannot browse the file system of the asset, so you need to know the logical path on the asset running the Axeda IDM Agents. The logical path is defined by the FileRepository configuration (including RootDirectory and VirtualDirectory) for the agent.

When defining a FileRepository, you identify a RootDirectory of the asset's repository and you can identify a VirtualDirectory with an alias and an absolute path to that directory. The Alias field of the VirtualDirectory becomes the path from the root directory. The Enterprise server never knows where the files are stored on the physical storage of the asset, only the virtual path to the file, as described by the FileRepository configuration.

For example, suppose an IDM Agent has a file repository configured as follows:

         <FileRepository>
           <RootDirectory>C:\Program Files\Axeda\SomeDirectory</RootDirectory>
           <VirtualDirectory>
              <Alias>logs</Alias>
              <Directory>C:\Windows\logs</Directory>
           </VirtualDirectory>
         </FileRepository>

A user configuring a file upload request, action, or instruction would specify the files this way:

For the physical location	Specify the file to upload as follows
C:\Program Files\Axeda\SomeDirectory\mydata.txt (RootDirectory)	/mydata.txt
C:\Windows\logs\transfer.log (VirtualDirectory)	/logs/transfer.log