Note that the IDM Axeda® Enterprise Server allows users to browse the file system of assets that are running IDM Agents. The Axeda Platform does not support this capability, so when requesting a file download through the Software Management application or the Axeda® Service application, you must know the destination directory for downloading a file to an asset running an IDM Agent.
The path you specify as the Destination for a download must always include
the logical path, even if it
is just the forward slash ("/"). The logical path is defined
by the FileRepository (including VirtualDirectory) configuration for the
Agent. A path that is just "/" indicates the relative path from
the asset's RootDirectory in the FileRepository configuration.
For the IDM Agents, this field must always start with a forward slash,
so if you omit the forward slash, the system adds it for you. If you need
further assistance, refer to the user guide for the IDM Agents and to
the topic, IDM
Agent FileRepository Configuration Example.
If you specify a path that does not exist on the agent machine, then the IDM Agent automatically creates the directory for you. Note that you must surround the new directory name with forward slashes; for example: /new_log_files/.
Selecting this option for an Axeda IDM Agent or AWP Agent has no effect on the download.
Back to: Package Instructions: Download File from Enterprise Server or Configure download actions