Community Tip - Need to share some code when posting a question or reply? Make sure to use the "Insert code sample" menu option. Learn more! X
When using the Auto-bind section of an EMS configuration it is very important to note the difference between "gateway":true and "gateway":false. Using either gateway value, when used with a valid "name" field, will result in the EMS attempting to bind the Thing with the ThingWorx platform, and will allow the EMS to respond to file transfer and tunnel services related to the auto-bound things, but this is around where the similarities end.
Non-Gateway:
Gateway:
Clarification on the non-gateway type. If you have a non-gateway auto_bind entry in the EMS config, a script resource (or other application) isn't required. Your config could look like this:
"auto_bind" : [
{ "name": "MyThing" }
]
This would allow the EMS to facilitate tunnels and file transfers to MyThing, without a script resource running.
However, if you had your own application with a HTTP interface, and you'd like the platform to be able to send it property/service requests, then you could expand on your config:
"auto_bind" : [
{ "name": "MyThing",
"host": "10.128.0.2",
"port": 80,
"path" : "/MyApp" }
]
If your application was running at http://10.128.0.2:80/MyApp then the EMS would direct any non-tunnel and non-file transfer messages to your application. Note that your application would have to be able to consume ThingWorx formatted messages, and that they would be delivered to a ThingWorx path (e.g., /MyApp/Thingworx/Things/MyThing/Properties/temperature).