Installation process first-time installation
In the following process
$WT_HOME/../deploy/innoface-wc-project-999999-R11.0-M030-1.0
is referred to as the installation directory.The basic software has to be installed by a system user with administrative and unrestricted read/write rights to all subfolders in the Windchill directory.
All commands have to be executed in a Windchill shell!
All commands / actions have to be executed in the installation directory.
If the commands / actions have been executed successfully, a "BUILD SUCCESSFUL" usually appears at the end.
If the parameter "Java Args" is requested, please specify the value -Xms256
Stop Windchill
Linux
1. Stop Windchill
Windchill Shell
windchill stop
2. Stop Apache
Windchill Shell
$WT_HOME/../HTTPServer/bin/apachectl stop
Windows
1. Stop all Windchill services
2. Stop the Http/Apache servers
Additional information can be found here
Clear Tomcat cache
Linux
To clear the cache, the directory $WT_HOME/tomcat/instances
has to be emptied (not deleted).
Windows
To clear the cache, the directory WT_HOME%\tomcat\instances
has to be emptied (not deleted).
Additional information can be found here
Basic software installation
Linux
Navigate to the unzipped installation directory (example: innoface-wc-project-999999-R11.0-M030-1.0
) and execute the following command:
Windchill Shell
ant -Dconf=<config> deploy
Windows
Navigate to the unzipped installation directory (example: innoface-wc-project-999999-R11.0-M030-1.0
) and execute the following command:
Windchill Shell
ant -Dconf=<config> deploy
Additional information can be found here
Configuration of the Apache
Linux
Windchill Shell
ant setup_apache_context
The Apache home directory is by default $WT_HOME/../HTTPServer/
If the Apache directory differs from the Windchill default, it has to be specified as well!
ant setup_apache_context -Dapachedir=<Apache-Homeverzeichnis>
After the setup, the Apache web service must be restarted.
Windows
Windchill Shell
ant setup_apache_context
The Apache home directory is by default %WT_HOME%\..\HTTPServer\
If the Apache directory differs from the Windchill default, it has to be specified as well!
ant setup_apache_context -Dapachedir=<Apache-Homeverzeichnis>
After the setup, the Apache web service must be restarted.
Additional information can be found here
Data server installation
Linux
Windows
Carry out the installation depending on the database used (MSSQL or Oracle).
Carry out the installation depending on the database used (MSSQL or Oracle).
Determine the database used
xconfmanager -d wt.db.dataStore
MSSQL
Installation via ant command if an sqlcmd client is available.
ant dataserver_install_mssql
Determine the database used
xconfmanager -d wt.db.dataStore
MSSQL
Installation via ant command if an sqlcmd client is available.
ant dataserver_install_mssql
If an sqlcmd client is not available in the Windchill system, the following SQL script:
>innoface-wc-project-999999-R11.0-M030-1.0/dataserver/dataserver_sqlserver.sql
can be executed with any client directly on the Windchill database instance in order to create data server tables.
Oracle
Installation via ant command if an sqlplus client is available.
If the ORACLE_HOME environment variable has not been set, it must be set, e.g.
export ORACLE_HOME=/opt/oracle/product/18C/dbhome_1/
ant dataserver_install_oracle
Oracle
Installation via ant command if an sqlplus client is available.
If the ORACLE_HOME environment variable has not been set, it must be set, e.g.
set ORACLE_HOME=/opt/oracle/product/18C/dbhome_1/
ant dataserver_install_oracle
If an sqlplus client is not available in the Windchill system, the following SQL script:
innoface-wc-project-999999-R11.0-M030-1.0/dataserver/dataserver_oracle.sql
can be executed with any client directly on the Windchill database instance in order to create data server tables.
Additional information can be found here
Register JavaScript
Linux
ant std_register_scripts
Windows
ant std_register_scripts
Additional information can be found here
Start Windchill
Linux
1. Start Apache
1.1 Without SSL
$WT_HOME/../HTTPServer/bin/apachectl start
1.2 With SSL
$WT_HOME/../HTTPServer/bin/apachectl -DSSL
2. Start Windchill
windchill start
Windows
1. Start the Http/Apache server
2. Start all Windchill-relevant services
Register preferences
Linux
In this step, the Windchill site administrator credentials are required.
ant register_preferences
Afterward, you must restart Windchill!
Windows
In this step, the Windchill site administrator credentials are required.
ant register_preferences
Afterward, you must restart Windchill!
Additional information can be found here
Queue installation
Linux
Windchill has to run!
In this step, the Windchill site administrator credentials are required.
ant create_queues
Windows
Windchill has to run!
In this step, the Windchill site administrator credentials are required.
ant create_queues
Additional information can be found here
Additional steps (when a ReleaseEngine is in use)
Import task delegates
Linux
You must have site administrator rights
You must have the LDAP administrator credentials (Possibly, starting Windchill 12, the Windchill installation user must be used for importing.
Log in to Windchill
Navigate to Site → Utilities → Task Delegate Management
If required, log in with the LDAP credentials
Importing the delegates
Navigate to: Import Delegates
The following process has to be repeated for each ie * .ldif file!
To be able to access the files, this step should be performed on the Windchill installation server.
Click Choose File and select the ie*.ldif file in
$WT_HOME/tasks/de/innoface/soap
The Overwrite leaf entries box must be checked!
When the file is selected and the box is checked, the file can be imported by clicking Import.
Checking the delegates
Navigate to: Find delegates
Select the "de.innoface.soap" type identifier and start the search
The expected delegates are, for example:
findObjekts
getRepresentation
Windows
You must have site administrator rights
You must have the LDAP administrator credentials (Possibly, starting Windchill 12, the Windchill installation user must be used for importing.
Log in to Windchill
Navigate to Site → Utilities → Task Delegate Management
If required, log in with the LDAP credentials
Importing the delegates
Navigate to: Import Delegates
The following process has to be repeated for each ie * .ldif file!
To be able to access the files, this step should be performed on the Windchill installation server.
Click Choose File and select the ie*.ldif file in
%WT_HOME%\to_windchill\copy\tasks\de\innoface\soap
The Overwrite leaf entries box must be checked!
When the file is selected and the box is checked, the file can be imported by clicking Import.
Checking the delegates
Navigate to: Find delegates
Select the "de.innoface.soap" type identifier and start the search
The expected delegates are, for example:
findObjekts
getRepresentation
Additional information can be found here
Import IFConneX workflows
Linux
To use the IFConneX workflow, it must be imported.
The credentials of the site administrator must are required.
1. Stop Windchill
2. Run code
cd $WT_HOME
ant -f bin/tools.xml bundle_custom -Dbundle.forceCompile=true -Dbundle.input=wt.util.resource.resourceCustomize
ant -f codebase/MakeJar.xml
ant -f codebase/MakeJar.xml custUpdate
3. Start Windchill
4. Import the "IF5" workflow template
windchill wt.load.LoadFromFile -d loadFiles/innoface/IFConneX_Minimal.xml
5. Import the "IFConneX" legacy workflow template
windchill wt.load.LoadFromFile -d loadFiles/innoface/IFConneX_Standard.xml
Windows
To use the IFConneX workflow, it must be imported.
The credentials of the site administrator must are required.
1. Stop Windchill
2. Run code
cd %WT_HOME%
ant -f bin\tools.xml bundle_custom -Dbundle.forceCompile=true -Dbundle.input=wt.util.resource.resourceCustomize
ant -f codebase\MakeJar.xml
ant -f codebase\MakeJar.xml custUpdate
3. Start Windchill
4. Import the "IF5" workflow template
windchill wt.load.LoadFromFile -d loadFiles/innoface/IFConneX_Minimal.xml
5. Import the "IFConneX" legacy workflow template
windchill wt.load.LoadFromFile -d loadFiles/innoface/IFConneX_Standard.xml
Note
After successful installation, usually, interface-specific master attributes have to be added.