wt.properties file

To use Windchill, the following properties must be set in the wt.properties file (this is usually done at installation). Note that you must use double back slashes to specify path names in the wt.properties file. This is necessary because the string is read by a Java program.

• wt.home, which specifies the top level of the class directory structure where Windchill is installed. The default value is c:\\windchill.

• wt.server.codebase, which is used by client applications. It specifies a URL from which client applications can download server resources such as property files. Server applications may use this property when writing dynamically generated HTML to be returned to a client browser. It is used to build URLs for static resources such as images or HTML files that reside under the server’s codebase directory.

• java.rmi.server.hostname, which specifies a host name used to identify the server host. It is used by the Java RMI runtime for clients to look up the IP address of the server. It can be specified as a symbolic name, such as a fully-qualified Internet domain name, or numerically in dot notation (for example, 127.0.0.1). If not specified, the RMI runtime will use the name returned by InetAddress.getLocalHost() method, which may return a name that is not known to remote clients. We recommend that this property be set to the fully-qualified Internet domain name of the server host.

• wt.access.enforce

This property enforces access control. By default. it is true. However, if you are debugging and want to bypass access control temporarily, you can set it to false.

This property enables and disables logging in applications that support it, such as the Windchill Server Manager and Method Server applications. By default, it is false. To write debugging messages to a log file, you must set it to true.

• wt.method.verboseClient and wt.method.verboseServer

These properties cause trace messages to be printed from the client-side and server-side, respectively, of the method server remote interfaces. By default, it is false. Turning on these properties causes trace information to be written to logs for debugging purposes.

In looking through the properties, you will see many service names followed by the word “verbose” (for example, wt.access.verboseExecution and wt.access.verbosePolicy). In general, these properties allow you to turn on debug tracing.