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?
Solved! Go to Solution.
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.
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 :
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?
Can we write a service on the Edge side itself in .NET and call it from the Edge as well?
Do you have a sample snippet?
Checking in to see if you have been able get the tunneling working properly. If so, please go ahead and mark the post that helped the most as the 'accepted solution' to aid others in the future when searching for this issue.
If not, let us know that and we'll keep working on it with you.
-- Craig A.