Remote Interfaces in ThingWorx
Remote Interfaces are used to define endpoints on a device to connect to when initiating remote access sessions. In general, any TCP port can be used for remote sessions to Axeda Agents through ThingWorx. The Remote Access Server for Axeda eMessage Agents in ThingWorx is the Axeda Global Access Server (GAS).
The eMessage Connector supports the following types of remote interfaces that may be defined for your Axeda eMessage Agents:
• Remote Desktop You can continue to use Axeda Desktop Server and Axeda Desktop Viewer. Alternatively, you can use UltraVNC. The ThingWorx Platform supports UltraVNC for remote sessions, which is referred to as tunneling in ThingWorx.
• Remote Application. In Axeda Builder, you select this type of remote interface to configure SSH, RDP/Terminal Services, SQL, Telnet, and command line remote sessions. In ThingWorx Remote Access, a tunnel is created between the client's machine and the agent. Whatever server the agent supports should be supported by the ThingWorx Remote Access Client.
• Remote Browser for Web applications over HTTP.
 |
If you migrate to a ThingWorx Edge SDK, keep in mind that you will lose HTTP-based access (Web application).
|
The Axeda Remote Terminal type of session that used the jta.jar is not supported.
Remote Interfaces are stored as rows of an INFOTABLE on the Endpoints property of a Thing in ThingWorx.
In ThingWorx, the endpoints row consists of the following fields:
• name — Name of the Remote Interface
• providerConfig — JSON field that contains parsed connection string, launchOption, and description.
Example of a Remote Interface in ThingWorx endpoints Property
<Row xsi:type="endpointInfoTableRow">
<name>ssh-app</name>
<providerConfig>
<json>{"launchOption":"AUTO","connectionInformation":[{"type":"C","startPort":22}]}</json>
</providerConfig>
</Row>
<name>ssh-app</name>
<providerConfig>
<json>{"launchOption":"AUTO","connectionInformation":[{"type":"C","startPort":22}]}</json>
</providerConfig>
</Row>