Skip to main content
Skip table of contents

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 write/read 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
BASH
windchill stop

2. Stop Apache

Windchill Shell
BASH
$WT_HOME/../HTTPServer/bin/apachectl stop

Windows

1. Stop all Windchill relevant services

2. Stop the Http/Apache server

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

Installation of the basic software

Linux

Navigate into the unzipped installation directory (example: innoface-wc-project-999999-R11.0-M030-1.0) and execute the following command:

Windchill Shell
CODE
ant -Dconf=<config> deploy

Windows

Navigate  into the unzipped installation directory (example: innoface-wc-project-999999-R11.0-M030-1.0) and execute the following command:

Windchill Shell
CODE
ant -Dconf=<config> deploy

Additional information can be found here

Configuration of the Apache

Linux

Windchill Shell
CODE
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!

Windchill Shell
CODE
ant setup_apache_context -Dapachedir=<Apache-home directory>

Info

After the setup, the Apache web service must be restarted.

Windows

Windchill Shell
CODE
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!

Windchill Shell
CODE
ant setup_apache_context -Dapachedir=<Apache-home directory>

Info

After the setup, the Apache web service must be restarted.

Additional information can be found here

Installation of the Data server

Linux

Carry out the installation depending on the used database (MSSQL or Oracle).

Determine the database used

Windchill Shell
XML
xconfmanager -d wt.db.dataStore

MSSQL

Info

Installation via ant command if sqlcmd client is available.

Windchill Shell

CODE
ant dataserver_install_mssql

Windows

Carry out the installation depending on the used database (MSSQL or Oracle).

Determine the database used

Windchill Shell
XML
xconfmanager -d wt.db.dataStore

MSSQL

Info

Installation via ant command if sqlcmd client is available.

Windchill Shell

CODE
ant dataserver_install_mssql

Additional information can be found here

Register JavaScript

Linux

Windchill Shell
CODE
ant std_register_scripts

Windows

Windchill Shell
CODE
ant std_register_scripts

Additional information can be found here

Start Windchill

Linux

  1. Start Apache

1.1 Without SSL

Windchill Shell
CODE
$WT_HOME/../HTTPServer/bin/apachectl start

1.2 With SSL

Windchill Shell
CODE
$WT_HOME/../HTTPServer/bin/apachectl -DSSL

  1. Start Windchill

Windchill Shell
CODE
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.

Windchill Shell
CODE
ant register_preferences

Afterward, Windchill must be restarted!

Windows

In this step, the Windchill Site Administrator credentials are required.

Windchill Shell
CODE
ant register_preferences

Afterward, Windchill must be restarted!

Additional information can be found here

Installation of the queues

Linux

  • Windchill has to run!

  • In this step, the Windchill Site Administrator credentials are required.

Windchill Shell
CODE
ant create_queues

Windows

  • Windchill has to run!

  • In this step, the Windchill Site Administrator credentials are required.

Windchill Shell
CODE
ant create_queues

Additional information can be found here

Additional steps (if a ReleaseEngine is used)

Import task delegates

Linux

Windows

  • Windchill has to run!

  • In this step, the Windchill Site Administrator credentials are required (Possibly, with Windchill 12, the Windchill installation user has to be used for the import)

  • Log in to Windchill

  • Navigate to Site → Utilities → Task Delegate Management 

  • Log in with the LDAP credentials

Import of the delegates

  • Navigate to: Import Delegates

  • The following process has to be repeated for each ie * .ldif file!

  • To have access to 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 box Overwrite leaf entries if they exist must be selected!

  • When the file is selected and the check mark is set, the file can be imported via Import.

Checking the delegates

  • Navigate to: Find Delegates

  • Select the Type Identifier "de.innoface.soap" and start the search

  • The expected delegates are, for example:

    • findObjects

    • getRepresentation

  • Windchill has to run!

  • In this step, the Windchill Site Administrator credentials are required (Possibly, with Windchill 12, the Windchill installation user has to be used for the import)

  • Log in to Windchill

  • Navigate to Site → Utilities → Task Delegate Management 

  • Log in with the LDAP credentials

Import of the delegates

  • Navigate to: Import Delegates

  • The following process has to be repeated for each ie * .ldif file!

  • To have access to 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 box Overwrite leaf entries if they exist must be selected!

  • When the file is selected and the check mark is set, the file can be imported via Import.

Checking the delegates

  • Navigate to: Find Delegates

  • Select the Type Identifier "de.innoface.soap" and start the search

  • The expected delegates are, for example:

    • findObjects

    • getRepresentation

Additional information can be found here

Import IFConneX workflows

In order to use the IFConneX workflow, it must be imported.

Siteadmin credentials are required.

  1. Stop Windchill 

  2. Run Code 

Windchill Shell
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
  1. Start Windchill 

  2. Workflow template import

Windchill Shell
CODE
windchill wt.load.LoadFromFile -d loadFiles/innoface/IFConneX_Minimal.xml
  1. Legacy Workflow Template "IFConneX" import

Windchill Shell
CODE
windchill wt.load.LoadFromFile -d loadFiles/innoface/IFConneX_Standard.xml

In order to use the IFConneX workflow, it must be imported.

Siteadmin credentials are required.

  1. Stop Windchill 

  2. Run Code 

Windchill Shell
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
  1. Start Windchill 

  2. Workflow template import

Windchill Shell
CODE
windchill wt.load.LoadFromFile -d loadFiles/innoface/IFConneX_Minimal.xml
  1. Legacy Workflow Template "IFConneX" import

Windchill Shell
CODE
windchill wt.load.LoadFromFile -d loadFiles/innoface/IFConneX_Standard.xml

Note

After the successful installation, interface-specific master attributes usually have to be added.



JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.