I have configured Thingworx opc ua client. Now I want to get that opc ua data to thingworx studio so that I can show it in Augmented Reality. As my thingworx studio composer and thingworx server is running in different port, I cannot understand how to get the Thing I created for opc ua. Please tell me the solution...
Hi Dipika Sengupta
For trial version; ThingWorx Experience Server and ThingWorx composer are hosted by PTC.
If https://xxxxxxxx.pp.vuforia.io/VuforiaExperienceService is your ThingWorx Experience Server then
https://xxxxxxxx.pp.vuforia.io:8443/Thingworx would be your ThingWorx Composer.
They are already connected and ThingWorx data can be accessed in ThingWorx Studio by using External Data option from the right pane.
Do let me know if you are hosting Experience Server on your own or if you have any further queries?
I am hosting the Experience on my own system. https://localhost:8080/Thingworx/Composer/index.html This is the link of the Experience server.
Now I want to connect it to my thingworx studio. https://ctugvfiu.pp.vuforia.io:8443/Thingworx/Composer/index.html is the link of the composer accessible by the studio.
Now my opcua data is going to the experience server in my localhost. I want it in my thingworx studio...
Hi Dipika Sengupta,
Your ThingWorx Experience Server: https://ctugvfiu.pp.vuforia.io/ExperienceService
Your ThingWorx Server associated with the ThingWorx Experience Server: https://ctugvfiu.pp.vuforia.io:8443/Thingworx
Both are hosted by PTC.
https://localhost:8080/Thingworx/Composer/index.html is your locally hosted ThingWorx instance.
Currently it is not possible to connect your local/hosted ThingWorx with the PTC hosted ThingWorx Experience Server.
This feature is avaialble for those users who host their own Experience server and the ThingWorx and connect them to each other.
Hi Dipika Sengupta,
On-premise Experience Server option is currently limited to some users.
As per my understanding you can consider connecting ThingWorx (for Experience server) with your local ThingWorx.
As suggested by Giri; Configuring the federation between your local Thingworx and (ES) ThingWorx platform should be one of the possible workaround.