Skip to main content
1-Visitor
September 7, 2018
Solved

Tunnelling and Remote Access

  • September 7, 2018
  • 1 reply
  • 3041 views

Hi,

 

Is there a way to bypass the need to set up configuration for tunnelling on the platform but instead configure it only from the .NET Edge SDK side programmatically?

Best answer by CarlesColl

You can create a custom service on the platform (at ThingShape or ThingTemplate level) and do the job there in server sida javascript, then just call this custom service from the Edge.

1 reply

5-Regular Member
September 14, 2018

Hi @pujasaha could you share some more information on what the actual use case is requiring you to not configure the tunnelling subsystem?

 

Currently documented steps (officially supported) of setting up requires configuration to be done for the Tunnel subsystem on the platform. If you are looking to avoid manually changing it you could look into the services that are available for Tunneling subsystem to may be set them via REST calls or ThingWorx Services.

pujasaha1-VisitorAuthor
1-Visitor
September 14, 2018

Hi @supandey,

 We have a lot of assets in the field and are trying to reduce the number of manual steps required to do any kind of configurations on the platform. If there is a way to achieve something purely programmtically using .NET Edge SDK then that's the way we prefer to do it. Thereby, reducing the number of manual configurations on the Platform. 

At the moment the only tunneling related line of code we have is :

            client.getTunnelManager().Initialize(config);

Then  on the platform we edit the Thing to and under "Configuration" --> "My Tunnels" we "Add My Tunnel" info.

 It is this manual configuration step that we want to perform programmatically from the Edge.

Is there a way to do so?

1-Visitor
September 14, 2018

You can create a custom service on the platform (at ThingShape or ThingTemplate level) and do the job there in server sida javascript, then just call this custom service from the Edge.