04.12.2012 Views

Windchill System Administrator's Guide

Windchill System Administrator's Guide

Windchill System Administrator's Guide

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Windchill</strong> Configuration Properties<br />

<strong>Windchill</strong> uses standard Java property files to dynamically configure many<br />

optional or site-dependent settings. The primary properties file, wt.properties, is<br />

located in the <strong>Windchill</strong> codebase directory, where it is available for downloading<br />

into clients. It contains properties that affect both client and server Java classes.<br />

Properties available only to server-side classes are located in separate property<br />

files. For example, properties that control access to the database, including a<br />

database password, are located outside the codebase in the <strong>Windchill</strong> db directory,<br />

in the file named db.properties.<br />

To manage site property settings, <strong>Windchill</strong> no longer recommends that you use a<br />

text editor to edit individual property files. Instead, all site changes to property<br />

files are maintained in the site.xconf file that is located in the directory where<br />

<strong>Windchill</strong> is installed. Use the following utilities to update the site.xconf file and<br />

then propagate the changes to property files:<br />

• The xconfmanager is a command line utility that you can run to add, remove,<br />

or modify properties in any <strong>Windchill</strong> property file. The utility saves your<br />

changes in the site.xconf file and provides an option to generate updated<br />

property files using the updates in the site.xconf file.<br />

• The <strong>System</strong> Configurator provides an interface for updating properties in the<br />

most common set of property files. From this application, authorized users<br />

can modify property values, save the changes to the site.xconf, and generate<br />

updated property files.<br />

The changes made through either of these utilities are saved in the site.xconf file<br />

and propagated to respective property files. When you restart your <strong>Windchill</strong><br />

system, the resulting changes are implemented.<br />

<strong>Windchill</strong> creates the site.xconf file when <strong>Windchill</strong> Info*Engine is installed and<br />

adds all properties that are set during the installation of all <strong>Windchill</strong> solutions to<br />

the file. During the installation process, <strong>Windchill</strong> also creates the<br />

declarations.xconf file that contains a list of configuration references to<br />

PTC-supplied XCONF files that are used to specify the out-of-the-box default<br />

values for properties in many of the property files. Although not all property files<br />

are initially generated from XCONF files, you should always make changes to<br />

<strong>Windchill</strong> properties through either the xconfmanager or the <strong>System</strong><br />

Configurator.<br />

Note: By using these utilities, your site.xconf file will always contain your<br />

site-specific changes. By maintaining site-specific changes to properties in the<br />

site.xconf file, you can easily identify what changes were made and these changes<br />

can be maintained when you make updates to your <strong>Windchill</strong> solution.<br />

As shown in the following diagram, making property changes through the utilities<br />

that <strong>Windchill</strong> provides always updates the site.xconf file. Then <strong>Windchill</strong><br />

propagates the changes to properties files using the site.xconf file and the XCONF<br />

files that it maintains. In this diagram, the declarations.xconf file has references to<br />

1-2 <strong>Windchill</strong> <strong>System</strong> Administrator’s <strong>Guide</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!