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.
http://windchill.acme.com/Windchill/appin a web browser.
extension.propertiesis 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
wt.db.typeis the type of the database:
oraclefor Oracle, or
sqlserverfor SQL Server
wt.install.diris the path to the root directory of Windchill install (example :
windchill.contextPathis the context path inside the Windchill URL. (example : value
wt.apache.httpServeris the apache configuration directory path (example:
C:\\ptc\\Windchill_11.0\\HTTPServer\\conf\\conf.d). If this property is not set, the install script will use the default directory
extension.propertiesfile located inside the previous version installation folder.
ant -f extensionInstall.xml, if installing the extension on a monolithic Windchill or a Windchill cluster master node
ant -f extensionInstall.xml slave, if installing the extension on a Windchill cluster slave node
ant -f extensionUpdate.xml, if installing the extension on a monolithic Windchill or a Windchill cluster master node
ant -f extensionUpdate.xml slave, if installing the extension on a Windchill cluster slave node
db-passwordis the password matching the Windchill user, property [wt.pom.dbUser] configured in wt.home/Windchill/db/db.properties
/oslc-connecturl to Windchill Apache HTTPServer
xconfmanagerproperties propagation task
custom-actionModels.xmlfile. 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.
When the script runs successfully, this completes deployment of the extension.
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.