Environment Variables
Creo Parametric uses a user-visible workspace to manage work-in-process data. Each workspace uses a local disk cache to ensure data integrity and optimize file transfer between Creo Parametric and the server. The cache (which is managed by Creo Parametric and is not visible to the end user), is used to store changed objects prior to an upload to the server, and to keep copies of objects downloaded from the server to speed up subsequent retrieval into Creo Parametric.
As a system administrator, you may wish to put the cache on a larger disk partition than provided by the default location. The following table lists environment variables that can be set by a system administrator to manage the placement of the cache into a suitable partition:
Variable
Values
Description
PTC_WF_ROOT
/path/to/dir,
Default on Windows = [User Profile]\Application Data\PTC\ProENGINEER\ Wildfire\
Overrides the default location of .wf directory. Setting this environment variable causes Creo Parametric to use the new location as a location for the cache.
* 
Existing cache data is not copied to the new location automatically.
PTC_WF_CACHE
/path/to/dir, default=$PTC_WF_ROOT/. cache/
Allows the specification of additional cache space. If you are running out of disk space in $PTC_WF_ROOT, you can use this environment variable to define a folder in which all new workspace caches will be stored.
* 
This new folder only applies to newly created workspaces. Existing workspaces continue to reside in $PTC_WF_ROOT/.cache
PTC_WLD_ROOT
/path/to/dir,
Allows specification of the location of the .ws cache directory.
* 
By default, when you register Windchill servers and authoring applications, a .ws directory is created for cache. It is located under your user profile on your local computer. For every server location listed in the .ws directory, there are subdirectories for each workspace, and within each workspace subdirectory, there are subdirectories for each authoring application that is registered to that server.
* 
The environment variable EPM_MODE, designed for earlier versions of Creo Parametric, should not be used with Creo Parametric. Because it prevents the Conflicts ("check out on-the-fly") window from appearing when users attempt to modify a checked-in model, its use could lead to loss of data when modifications cannot subsequently be checked in.
¿Fue esto útil?