Axeda Transport enables communication between your Axeda® Platform and assets in the field that are not online during normal operation but do have an Axeda® Agent installed. The basis of this "mobile" communication between the Platform and a disconnected Axeda Agent is a data file. The primary means for this communication is a laptop computer that is also running an Axeda Agent.
The standard HTTP communication between the Platform and Axeda Agents follows the Request/Response protocol. Typically, the Axeda Agent always initiates the Request. Using a file to communicate information, either the Platform or the Axeda Agent can initiate the workflow. When the Platform initiates the workflow, the destination assets must either have had a direct connection to the server at one time or have already been defined directly by a user of the Axeda® Configuration application. When the Axeda Agent initiates the workflow, the asset may be registering with the Platform for the first time.
From the Axeda® Service application you can select the destination assets and request the Platform to assemble all queued commands in an archive (tar.gz). The archive can include files containing SOAP commands for the Axeda Agent as well as files associated with a package created using the Axeda® Software Management application.
The next step in the workflow is to export the archive file to the Axeda Agent and travel to the location of the destination asset(s). When started at the site, the Axeda Agent extracts the files from the archive and processes the commands in the same way as if it were directly connected to the Platform. When triggered to do so, the Axeda Agent exports to a file the queue of messages that it has collected for the Platform. These files are compressed into a single archive for importing to the Platform. A user of the Service application initiates the import to the Platform through the Transport - Browse for Assets page.
Notes
Axeda Transport requires that the source and destination assets be running
an Axeda® Agent. It does not work with tracking assets that monitor mobile
assets (for example, an Edge device).
Axeda Transport does NOT support large file uploads. You can transfer files
up to 2 GB in size using Axeda Transport. For larger files, use Axeda
Software Management packages or the Download File from Enterprise action.
This release of Axeda Transport does not support the Axeda® IDM Agents.
For a description of the supported features of these agents, refer to
Axeda® IDM Agents.