Pro/ENGINEER Wildfire uses an embedded browser to view the workspace in order to manage work-in-process data. Each workspace uses a local disk cache to ensure fast saves and optimize transfers to the server while safeguarding data integrity. The actual cache is transparent to the end user. It is used to store changed items prior to an upload to the server, and/or keep copies of items downloaded from the server to speed up subsequent retrieval into Pro/ENGINEER.
There are many options that can be set to improve the usability and alter behavior according to your preferences.
Controlling the storage location for the workspace/local cache. It may be beneficial to put the cache on a larger/faster disk than provided by the default location. These environment variables can be set either by you or your administrator to manage this:
|
Variable |
Default Value |
Description |
|
PTC_WF_ROOT |
%USERPROFILE%\Application
Data\PTC\ProENGINEER\
Wildfire\ |
Overrides the default location of .wf directory which contains .Settings and .Cache.
Note: Existing data will not be copied to a new location automatically. |
|
PTC_WF_CACHE |
%PTC_WF_ROOT%/.cache |
Define a folder in which all new workspace caches will be stored.
Note: Existing workspaces will continue to reside in %PTC_WF_ROOT%/.cache |
In order to optimize performance, it is important that the cache is sized properly to accommodate the largest anticipated data set (including new and modified objects). Otherwise, data will be unnecessarily streamed from the server – which will kill performance (especially in an environment with slow network connectivity or WAN).
Therefore, it is recommended that the following config.pro options also be set:
• dm_cache_mode all
• dm_cache_size size in MB (default = 400 MB)
Configuring properties in site.xconf. Edit this text file located in Pro/INTRALINK loadpoint home as indicated below.
Configuring table scrollbar display. Depending on the table view specified, the width of the table may exceed the width of the embedded browser. It is often inconvenient to scroll horizontally to reveal this control. It can also be confusing for you to have two vertical scrollbars side-by-side. A site-wide property allows you to change the location of table scrollbars to the left side:
<Property name="com.ptc.core.htmlcomp.jstable.positionScrollbarLeftside" overridable="true" targetFile="codebase/wt.properties" value="true"/>
Configuring automatic scrolling. When the workspace is displayed, the page automatically scrolls to the beginning of the item list table. To disable this behavior, set the following property:
<Property name="com.ptc.windchill.uwgm.cadx.ws.scrollToTable" overridable="true" targetFile="codebase/wt.properties" value="false"/>
Configuring the number of workspace rows displayed. By default, the number of rows displayed in the item table is based upon the height of the window. To display a fixed number of rows (for example, 10 for Windows), set the
property to false, as follows:
<Property name="com.ptc.windchill.uwgm.cadx.ws.sizeToWindow"
overridable="true" targetFile="codebase/wt.properties" value="false"/>
Propogating modifications to site.xconf. Save the site.xconf. Then from within a Windchill shell enter:
xconfmanager –p
Was this tip helpful?
Let us know.