cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Does the Agent Web Service work the same as say EDD_TEXT driver?

Highlighted
Newbie

Does the Agent Web Service work the same as say EDD_TEXT driver?

I understand that the driver, say EDD_TEXT, collects data from the source file(s) and passes that data to the Agent Data Logger. The Data Logger determines what data items get sent up to the platform.  The data get queued up and the next time the platform pings the agent for new information, that data get sent up. Do we get the same features if we use the Agent Web Services to send data to the platform? Does a Web Service call pass the data to the Data Logger, leverage the queuing mechanism, etc? Thanks.

2 REPLIES 2
Highlighted

Re: Does the Agent Web Service work the same as say EDD_TEXT driver?

Yes, when the value of a data item is set via the SetDataitem web service call, it follows the same path as data submitted by an EDD.

Couple of clarifications: (1) All communications between the Agent and the Platform are initiated by the Agent, so the Platform never polls the Agent for data. The opposite is true. (2) The Agent delivers data item updates -- and other payload information -- to the Platform as soon as possible. That is, such communications are not aligned with the ping period.

Highlighted

Re: Does the Agent Web Service work the same as say EDD_TEXT driver?

Hi Bruce,

Thanks for the great question.

For more details on agent features and data flow, please reference the Axeda Gateway Agent User's Guide.

I cut the following image from Chapter 2 of the guide.  As Dmitriy's states in his comment above, web service calls follow the same path as data submitted by EDD.

Screen Shot 2014-06-03 at 10.18.49 AM.png

Announcements

Thingworx Navigate content has a new home! Click here to access the new Thingworx Navigate forum!