Working through the 'Installing Thingworx' guide and the subsequent steps to import the Thingworx utilities, extensions, files, and the Windchill Extension patch is fairly straightforward, but would be easier if there were a wrapper script installation utility that used a staging area, like the Windchill PSI.
We managed to get the demo' setup for Trusted Host and SSO working with a separate Windchill test server (which uses SSL), and Windchill users can login and see the Navigate View Apps, but as yet none of the content in PDMLink. Our VAR had exactly the same problem using the latest available media (ie. Platform 7.2 with Utilities 7.1), but succeeded when they used v7.1 throughout. I think we have two problems to resolve...
The first problem is that the latest version of software components available under 'Smart Connected Applications' is probably not a complete and compatible set :
![Capture1.PNG]()
According to the PTC Calendar, Thingworx Platform v7.2 was released in July 2016, and Thingworx Utilities v7.2.1 was release in August 2016, but the latter is still not available for download under 'Smart Connected Applications'. However, according to the Thingworx Utilities Installation Guide v7.2.1 (Aug 2016), it is available under 'Thingworx Platform' - but the problem is that this Product Family is not accessible if you only have a license for Windchill Navigate View, not even to our VAR.
By way of confirmation, the following screen grab came from PTC Tech Support, but they seem to be unwilling or unable to make Thingworx Utilities v7.2.1 available for download under 'Smart Connected Applications', even though it is (probably...) needed to work with Thingworx Platform v7.2. Incidentally, this screen grab appears to show an expanded list of compatible database platform components at v7.2.
![Capture2.PNG]()
The second problem is that I expect we may have to use SSL encryption and trust between the Thingworx server and the Windchill server if the latter is already setup to use SSL for access to PDMLink. If this is the case, then we have to ignore the simpler Demo and Development configurations and go straight for a 'Production configuration - but is this correct ?