Remote Templates
There are several Thing Templates that are used to communicate over web sockets to edge devices or data stores. RemoteThing is the naming convention for using web sockets to communicate to another node, or Thing, in the network. The Thing Templates for the WSEMS and the SDKs include:
• RemoteThing — a remote Thing with no file transfer or tunneling needs. Also used for OPC-DA data source things. Supports properties, services, and events.
• RemoteThingWithFileTransfer — A RemoteThing plus file transfer enablement.
• RemoteThingWithTunnels — A RemoteThing plus tunneling enablement.
• RemoteThingWithTunnelsAndFileTransfer — A RemoteThing with both file transfer and tunneling.
• RemoteDatabase — A remote OLE-DB data source.
• EMSGateway — The EMSGateway Thing Template is used to address the WSEMS as a standalone Thing. This is useful when the WSEMS is running on a gateway computer and handling communication for one or more RemoteThings, which may reside on different IP addresses within a local area network.
• SDKGateway — Similar to the EMSGateway, but to be used when you are using an SDK implementation as a gateway.
In addition to the above Thing Templates, the following remote templates can be used in a federated storage scenario, where you wish to offload the persistence objects to another server that is optimized for disk IO:
• RemoteStream — Create a local proxy object to a stream Thing that is running and persisting data on another ThingWorx server.
• RemoteValueStream — Create a local proxy object to a value stream Thing that is running and persisting data on another ThingWorx server.
• RemoteDataTable — Create a local proxy object to a Data Table Thing that is running and persisting data on another ThingWorx server.
• RemoteBlog — Create a local proxy object to a blog Thing that is running and persisting data on another ThingWorx server.
• RemoteWiki — Create a local proxy object to a wiki Thing that is running and persisting data on another ThingWorx server.