Installing the Adapter 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.

Procedure

  1. Deploy the RLIA Servlet 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 bin/windchill shell
  6. Web browse to download the extensions for Windchill from the RLIA servlet
  7. Copy the zipfile windchill_resources.zip to a temporary staging directory, for example /tmp/sodius_install
  8. Change to the Sodius Installation directory
  9. Unzip the Windchill Resources Zip file
  10. Run the Ant script to install the Sodius Windchill Extensions
  11. Wait for the script to:
  12. Carefully monitor execution of the script and capture any failure messages

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

Installation Verification Steps

Read this section to understand and perhaps manually retry one or more of the steps of the automated installation process.

File Existence Check
  1. Visually confirm that the following folders and files are present in the Windchill application directory:
Sodius config.xml to Locate the Adapter

The Sodius config.xml file (Windchill installation path/Windchill/sodius/config/config.xml) has XML that informs Windchill where to find the RLIA Adapter server and service. The server.url parameter in the execution of the extensionBuild.xml ant script should have altered this config.xml file to point to the proper services. Assure that the complete URL is correct and modify it by hand if it needs to be corrected.

For further information, see Referencing the Windchill adapter

Modification of the Windchill SQL Database Tables

When the SQL Database used by Windchill is not co-located with the Windchill application on the same server, the extensionBuild.xml ant script cannot (easily) update that SQL server. Typically, this is because a database administration shell like Oracle’s sqlplus utility is not installed on the Windchill server.

If this applies to your deployment of Windchill, you must manually copy the SQL schema scripts from the wtSafeArea, copy these to the remote database server, and run the SQL administration utility on that server to read the SQL data modification language scripts. Please have your designated database administrator and your Windchill administrator perform this critical task for you.

The SQL scripts are located in the wtSafeArea/siteMod/db/sql/com/sodius directory.

These scripts create the table and its index for the storage of the links to OSLC resources from Windchill Baselinable resources.

Registration of the Adapter site.xconf Properties

This step is automatically performed by the extensionBuild.xml ant script.

If you modify the properties in the Sodius site.xconf file manually, you will need to re-propagate those changes.

  1. Run the Windchill Shell
  2. Within the Windchill directory, import the Sodius configuration properties:
Recombination of the Windchill_all.js Source

This step is automatically performed by the extensionBuild.xml ant script.

  1. Have Windchill recombine all its Javascript sources along with the Sodius extension Javascript:
Registration of Spring Bean Model-View-Controller Builders

Some components of the Sodius Windchill extension rely on Spring MVC beans. This configuration should be automatically performed by the extensionBuild.xml ant script.

To confirm proper execution of the script, examine the beans files for ChangeRequests and for Parts.

For ChangeRequests
  1. View the following file: <Windchill>\codebase\config\mvc\ChangeRequest-configs.xml
  2. Confirm that the following lines appear within the Spring MVC <beans></beans> XML element:
    <bean class="com.sodius.oslc.builders.ServiceProviderAssociationTableBuilder"/>
    <bean class="com.sodius.oslc.builders.WorkItemTreeBuilder"/>
    <bean class="com.sodius.oslc.controller.PreviewController"/>
    <bean class="com.sodius.oslc.controller.RelatedChangeRequestEditController"/>
    <bean class="com.sodius.oslc.controller.ServiceProviderEditController"/>
For Parts
  1. View the following file: <Windchill>\codebase\config\mvc\Oslcdelegate-configs.xml
  2. Confirm that the following lines appear within the Spring MVC <beans></beans> XML element:
    <bean class="com.sodius.mvc.builders.OslcdelegateTable" />
    <bean class="com.sodius.mvc.builders.OslcdelegateInfoBuilder" />
    <bean class="com.sodius.mvc.builders.OslcdelegateInfoAttributesBuilder" />
    <bean id="sodius.oslcdelegate.SetAttributesPanel" class="com.sodius.mvc.builders.OslcdelegateSetAttributesPanelBuilder" />
Starting Windchill Server (If Necessary)

Now that all extensions have been properly registered, you can restart the Windchill server:

  1. Run the Windchill Shell
  2. Start Windchill, type: windchill start
C:\ptc\Windchill_10.2\Windchill>windchill start
2019-05-01 17:32:50,560 INFO  [main] wt.manager.ServerLauncher