Installing or Upgrading OSLC Connect for 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.

Procedure

Prepare installation files on the Windchill server
  1. Confirm that Windchill itself is installed and is operational.
  2. Log into the Windchill server as an Administrator and as a Windchill Administrator
  3. Browse to the installation directory of PTC Windchill
  4. Run Windchill Shell with command bin/windchill shell
  5. Copy the windchill_resources zip file to a temporary staging directory, for example /tmp/sodius_install:
  6. Create a dedicated installation folder for each OSLC Connect for Windchill release and unzip the Windchill resources Zip file inside it.
  7. A default property file named extension.properties 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 extension.properties. If you a have a version of OSLC Connect for Windchill already installed, you can copy the values from the extension.properties file located inside the previous version installation folder.
  8. Stop the Windchill service
Launch the extension installation script
  1. If you are planning a fresh install : run the Ant script to install the OSLC Connect for Windchill Extension
  2. Otherwise if you are planning the update of a version already installed: run the Ant script to update the OSLC Connect for Windchill Extension
  3. The Ant script asks input arguments in addition to file extension.properties.
  4. Wait for the script to:
  5. Carefully monitor execution of the script and capture any failure messages
  6. As the extension contains custom Windchill action models, the extension script merges custom Windchill action models into Windchill custom-actionModels.xml file. If after the installation You experience issues with Windchill action models into Windchill action models, follow the procedure in Resolve OSLC Connect action model conflicts.
  7. 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.

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

Restart Windchill
  1. Start the Windchill service, and restart the Apache HTTPServer
  2. If you had a web browser open with the previous version of the extension before the installation, close all active browser sessions, or clear the browser cache.

Installation on a cluster

When using a Windchill cluster installation, the whole procedure needs to be repeated on each individual cluster node.

The only difference is that, as detailed in the steps above, the installation script must be called with the slave argument on cluster slave nodes. This will allow the installation to run faster, as some operations only need to be performed on the master node.

Troubleshooting

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.