Note that the IDM Enterprise Server allows users to browse the file system of assets that are running IDM Agents. The Axeda Platform does not support this capability directly, so when requesting a file upload through the Software Management application or the Service application, you must know the location of the file you want to upload. If you want to create your own IDM extension to add this capability, refer to Using_IDM_Web_Service_Extensions.
For Axeda IDM Agents, this path 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 "/" and a filename 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 Platform adds it for you. For example,
if you want to upload the file abc.txt, you can specify either /abc.txt
or abc.txt, and the system interprets the path in the same way - the relative
path from the asset's RootDirectory in the FileRepository configuration.
If you need further assistance, refer to the user guide for the IDM Agents
and to the topic, IDM
Agent FileRepository Configuration Example.
It is important to note that Axeda IDM Agents do NOT support wildcards
in this field. For example, if you want to upload two log files, you must
specify them separately. You cannot use *.log.
For Axeda IDM Agents, this option has no effect. You must provide the logical path to the file.
Back to: Package Instructions: Upload File to Axeda® Platform or Configure upload actions or Requesting File Uploads