Implement data transformation on Edge side for thingworx industrial connectivity Kepware
I can implement customized device data transformation using Java SDK/Protocal Adapter Toolkits/EMS on the Edge side before sending data to Thingworx Server.
However, Kepware connects to Thingworx directly and it seems I can only implement the data transformation in Thingworx server (except using the advanced tag of Kepware) . Is it possbile to implementation the transformation of Kepware data tag in Edge as well ? (It is best to use JAVA) .
I don't see why creating a proxy like that will be impossible, however it must be pretty hard in practice, because you need to understand / reverse-engineer the protocol of the industrial gateway (which properties it reads / writes, which services are executed remotely, etc.) Plus it adds another component to your system architecture, which you need to host, monitor, maintain, etc.
Why don't you want to transform data on ThingWorx side? If it's a question of performance, then my gut feeling tells me that optimizing it via a Java extension will be much easier than creating a proxy between your Kepware and ThingWorx.
I want to keep the handling for the device data unified . We're using the virtual thing of Java SDK and Protocal adapter toolkits to handle device data, including filter and transformation (standardize the data format ). Mitigating the load of the thingworx server is one of the reason, and I also hope all of these can be done on the Edge side , otherwise I have to duplicate the same logic in Thingworx service.