Compression
In an Axeda environment, the default behavior of both the agent and the platform is to compress all file transfers, using a tar-gzip format. In addition, the Axeda agents support an instruction on whether to use tar-gzip or no compression when they are given an upload or a download instruction from the platform.
In a ThingWorx environment, the default behavior of the Axeda agent and the eMessage Connector is to compress all file transfers using a tar-gzip format. You can request that a file be transferred uncompressed by supplying the appropriate JSON during the invocation of the Copy service on the File Transfer Subsystem (as part of the metadata).
If a file upload is requested using a wildcard (for example, *.log) and that wildcard matches more than one file, the Axeda agent returns an error. When it receives an upload request from the ThingWorx Platform, the eMessage Connector sends upload instructions with the compression property set. The default setting for this property is tar-gzip. File uploads that are initiated by an Axeda agent may be configured with no compression. If that is the case, compression is not used when the agent initiates a file upload to the ThingWorx Platform.
Was this helpful?