Installing the OSLC Connect for Windchill Extensions to Windchill

These procedures extend Windchill so that the Windchill user is presented with additional Windchill User Interface elements that expose controls and forms for the consumption of OSLC information from configured OSLC Providers. The procedures also manually configure Windchill with new properties to store relationships with chosen OSLC Providers.


  1. Deploy OSLC Connect for Windchill WAR to its server and servlet web application server
  2. Confirm that Windchill itself is installed and is operational.
  3. Log into the Windchill server as an Administrator and as a Windchill Administrator
  4. Browse to the installation directory of PTC Windchill
  5. run Windchill Shell with command bin/windchill shell
  6. Web browse to download the extensions for Windchill from the OSLC Connect for Windchill web application
  7. Copy the zipfile to a temporary staging directory, for example /tmp/sodius_install
  8. Unzip the Windchill Resources Zip file
  9. A default property file named is at the same level as the unzipped files.
    This property file contains default value of needed properties for extension to install.
    The needed properties are the identifier of database, the path to the Windchill install and the url of OSLC Connect for Windchill.
    You must change the values by editing the file
  10. Stop the Windchill service
  11. Run the Ant script to install the OSLC Connect for Windchill Extension
  12. The Ant script asks input arguments in addition to file
  13. Wait for the script to:
  14. Carefully monitor execution of the script and capture any failure messages
  15. As the extension contains custom Windchill action files, be aware that other preceding custom Windchill action files could conflict with the ones from the extension. In that case follow the procedure in Resolve OSLC Connect action model conflicts.
  16. As the extension contains a configuration file for the Apache HTTPServer, be aware that the Ant script won't install the file if the Apache HTTPServer is not on the same machine as Windchill. In that case this file must be deployed manually. See the Check the deployment of the OSLC Connect for Windchill Extension page to locate the destination folder.
  17. Start the Windchill service, and restart the Apache HTTPServer

When the script runs successfully, this completes deployment of the extension.


Any trouble?
Follow our guides to Check the deployment of the OSLC Connect for Windchill Extension,
and to fix SodiusWillert extensions deployment with database errors.