Configuring IIS and Windchill
Many of the instructions in this section use the Internet Information Services (IIS) Manager to configure IIS and Windchill. Consult the IIS Manager help if you need detailed information about the user interface. Microsoft Internet Information Services (IIS) does not have a direct link to standard LDAP servers. If you want to use a directory service with IIS, you should use Microsoft’s Active Directory.
|
|
When configuring IIS to work with Windchill you may have to restart IIS. Use the following steps to restart IIS:
1. Select the <ComputerName> (local computer) node in the left pane.
2. From the Actions pane, click Restart.
|
Installing PTC Embedded Servlet Engine Connector into IIS
To install the PTC Embedded Servlet Engine connector into IIS, complete the following steps:
1. Open an Administrator command prompt window and navigate to the <IISConnectorDir>/scripts directory.
2. Enter the following command (all on one line), replacing the italicized arguments as directed in the table that follows:
config_jk.bat<server><Windchill>
|
Argument
|
Description
|
|
<server>
|
Name of the IIS web site to use; the default IIS website is “Default Web Site” (including the double-quotes). You may opt to use a separate web site, that must be manually configured within the IIS Manager
If you use a value other than “Default Web Site”, be sure to use that value instead of “Default Web Site” throughout the remainder of these instructions.
|
|
<Windchill>
|
Full path to the Windchill installation directory.
|
|
<appName>
|
Optional –
The Windchill web app name. By default this is ‘Windchill’ and only needs to be specified if you are using a different web app name.
|
Examine the output of the command to ensure that there are no errors. It may be helpful to redirect the output of the command to a file by adding > outputfile to the command and loading the output file into a text editor afterwards.
Generating Authentication and Authorization Resources for Windchill Configurations
The Windchill configuration script requires two files: authenticated.txt and anonymous.txt. These files contain the authenticated and anonymous Windchillresources in a format that the configuration script can read. To generate these files complete the following steps:
1. Open a Windchill shell window and navigate to the <IISConnectorDir>/scripts directory.
2. Enter the following command:
ant -f iisPreConfig.xml
Configuring IIS for Windchill
|
|
This is the automated procedure for IIS that uses the config_windchill.bat script
The config_windchill.bat script requires two files: authenticated.txt and anonymous.txt. From the <IISConnectorDir>/scripts directory enter the following (all on one line), replacing the text as needed:
config_windchill.bat < server> < Windchill>,<appName> |
Enabling the Default Domain and Realm for IIS
Use the following procedure to enable the default domain and realm for IIS with basic authentication:
1. From the left pane of the IIS Manager, select the node <ComputerName> and in the middle pane, select Authentication.
2. Under the Authentication types listed, select Basic Authentication and in the Action pane, click Edit….
3. Enter the appropriate Default domain: andRealm: values. The default value used for Realm by Windchill with the bundled PTC HTTP Server is "Windchill".
Giving IIS Users Appropriate Permissions
The IIS user must have at least read permissions to the following files:
• <Windchill>/tomcat/connectors/conf/workers.properties
• <Windchill>/tomcat/connectors/conf/uriworkermap.properties
The IIS user must have write permissions to the following directory and its contents:
• <Windchill>/tomcat/connectors/logs
|
|
Permission may need to be re-applied after xconfmanager propagation, or after patches have been installed.
|
