Important: Muted assets cannot upload files, nor can the Platform download files to those assets. If an asset is managed by a Gateway and that Gateway is muted, the asset is muted also. The exception to this is if the asset is managed by multiple redundant gateways: even if one managing Gateway is muted, the asset will not be muted until all redundant gateways defined for that asset are muted.
Depending upon the type of task you've selected from the Asset dashboard, either the upload or download file page appears. When you click Submit, the configured task is queued and will be performed on the asset when that asset next contacts the Platform. Use this task to upload a file from the asset to the Platform or download a file from the Platform to the asset.
The Axeda® Connected Product Management Applications supports large file transfers, where "large" means that the files are larger than 2GB in size. By default, the Axeda Agents and the Platform compress files before uploading or downloading them. When setting up a file upload or download, you can enable or disable compression. Due to a limitation in the tar format, the Agents and the Platform cannot compress files larger than 8GB. Therefore, you must disable compression for files larger than 8GB or results may be unpredictable. When compression is disabled, you can transfer only one file at a time. However, disabling compression also allows you to use the Pause/Resume capability of file uploads (see Uploaded Files page).
During installation, your Platform administrator may have set limits for file size. By default, if the size of a file exceeds 2GB, compression is automatically disabled.
1. Type the path (optional) and filename of the file to upload to the Platform.
Note: For Axeda Agent Embedded, do NOT use any wildcards in the file specification.
2. If
you specify a relative path on the source asset, select Path
is relative to asset's home directory. If you do not select this,
the Platform assumes this is an absolute path.
For example, "file.txt" specifies the file is to be uploaded
to the asset's home directory on the Platform; "files\file.txt"
specifies the file is to be uploaded to the "files" directory
under the asset's home directory on the Platform.
3. If you want to delete the files from the Platform after the task is performed successfully, select Delete from asset after successful upload.
1. Click Browse to locate and select the file that you want to download to the asset.
2. After selecting the file, click Upload to import the file from your computer to the Platform. The progress bar replaces the Upload button, and the message, File Uploaded Successfully, appears once the file has been imported successfully to the Platform. If an error occurs during the upload, the Platform displays one of the following error messages:
§ Network error occurred - This message appears when the network is disconnected during the file upload. If a percentage of the file is uploaded when the interruption occurs, the remaining portion of the file should be uploaded when the network is restored within a specified time period (configured by your Platform administrator). If the network is not restored with the specified time period, then this message appears. You must start the upload all over again.
§ Server is not available - This message appears if the Platform is stopped during the file upload.
§ Unknown error occurred - This message appears for all other types of errors.
3. In the Destination directory field, type the path in which to copy the downloaded file on the asset. This needs to be a valid path on the destination asset.
4. If you want to disable compression, select the Do not compress this file option. For files larger than 8GB, you must select this option (due to a limitation in tar format). If the file is already compressed, Axeda recommends that you select this option to reduce the load on the CPU of the machine transferring the file. By default, compression is disabled for files larger than 2GB.
5. If this action will download an executable (for example, .exe or.gz)) or script, you can select to unpack it and/or run it on the asset after it is downloaded.
6. If
this action will download a file that already exists on the asset in the
specified destination directory, you can select to overwrite the existing
files. If you download an archive containing multiple files that already
exist on the asset, selecting this option tells the Agent to overwrite
the existing files when it unpacks the archive.
If you do not select this check box, the original files on the asset are
not overwritten (and the downloaded duplicates of those files are not
copied to the asset).
7. If
you specified a relative path as the Destination directory on the source
asset, select the option, Path is relative
to asset's home directory. If you do not select this option, the
Platform assumes this is an absolute path.
For example, <blank>
(no directory designated) specifies the file is to be downloaded to the
asset's home directory; "files" specifies the file is to be
downloaded to the "files" directory under the asset's home directory.
8. Click Submit.
Note: If, when the action is run, it does not complete successfully, any files already downloaded are removed from the asset and the files to download remain intact in the Platform.