Want to connect multiple Things in ThingWorx to Windchill using different appKeys

[SP_13550302]

We currently have one Thing in ThingWorx that connects to Windchill using a single app key. Now, we want to add another Thing with a different app key. The existing integrationRuntime-settings.json file is configured with the previous app key. How can we configure an additional app key to connect the new Thing to Windchill.

[Constantine]

If by "Thing" you mean Windchill OData Connector, then you can create as many of them as you want, and all will share the same Integration Runtime, which you don't need to touch.

[SP_13550302]

Thank you for the clarification. Just to confirm—are you suggesting that one app key is sufficient for connecting to the ODataConnector, and additional app keys do not need to be defined in the integrationRuntime-settings.json file? Can other applications use their respective app keys to connect directly to the ODataConnector? If possible, could you please share any documentation link that explains this setup?

[Constantine · Accepted solution]

I'll try to clarify.

The Integration Runtime server sits between Windchill and ThingWorx:

[ ThingWorx ] <--- WebSockets ---> [ Integration Runtime ] <--- HTTPS ---> [ Windchill ]

The applications you build on ThingWorx might have as many OData Connector Things as they need, and all of them will use the same Integration Runtime server, as long as the Windchill hostname in the OData Connector Thing Configuration matches the one in the integrationRuntime-settings.json.

When the server starts, the Integration Runtime uses the app key from that JSON file to open a WebSocket tunnel to ThingWorx. The HTTP traffic for all your OData Connector things will go through that single tunnel, so there's no need to have more than one app key.

/ Constantine

[SP_13550302]

Many thanks for providing this informative content. It clarifies how communication between these systems works.