What is use of Tunnel session created by EMS for Remote Desktop control session, where as we can connect to VNC server via any VNC client without tunnel session.
Jitender, the EMS essentially creates a websocket through which the connection/ communication/ data flows through. Are you talking about a specific session that gets created and remains open until the tunnel duration?
Question is what is the need of that session, because any vnc client like vnc viewer/tight VNC can connect without any kind of tunnel session then why Thingworx need this tunnel session for RDP connection.
Jitender, I believe its because of the proprietary protocol in action as you know WS EMS works with AlwaysOn, whereas a VNC client employs Remote Frame Buffer protocol (RFB).
AlwaysOn is designed for securing the communication while still keeping the low latency bi-directional communication yet reducing power consumption and bandwidth. Yet you have the RESTful HTTP interface, allowing other applications to communicate to it. Thus extending the reach to the edge devices which provide minimalistic platform for a software to execute
RFB is a simple protocol mainly designed for GUI later evolved to include features like file transfer and compression. That's why you need VNCServer or SSH or MicrosoftRDP for doing remote desktop to the Edge device running WS EMS.
Hope this helps.
the short answer is:
You are right, you may use a VNC client, but you don't have to.
And if you wanna do some automated stuff for a bigger set of devices it is very convenient to have this tunnel.
Happy thinging... ;o)
Hi jitender hooda ,
I am trying to give in brief uses/advantages of Tunneling. Considering Thingworx as an IOT application providing connectivity to huge number of devices and sensors.
Few important advantages are :
So for your question above , if we consider 3rd point , we are somewhat able to correlate why tunnel session is created for EMS server.
Let me know if you find this helpful.