Temporary files are created in temporary files directories on the Pega 7 Platform server or your workstation to temporarily contain information that is required during installation or browsing.
On each server node of a system, temporary files that include Java code and compiled Java classes, are created in a directory that you identify during installation.
This directory is defined by the
explicitTempDir entry in the prconfig.xml file or Dynamic System Settings:
<env name="Initialization/explicitTempDir" value="D:\zzzzz" />
D:\zzzzz identifies an existing directory.
Note: In some cases, the directory can be specified through JNDI rather than explicitly. The system does not create the directory if it is not found.
If this prconfig.xml entry is not present, temporary files are placed in the working directory of the application server, for example, /work/Catalina/localhost/prweb for Tomcat.
This directory is parent to other directories:
For example, if the directory is D:/Temp, the ServiceExport directory is D:/Temp/StaticContent/global/ServiceExport.
In addition to the above content, the temporary files directory on many systems also contains index files that support the full-text search facility, within three subdirectories (WorkIndex, RuleIndex, and
DataIndex) of a directory named Index. The directory used for full-text indexes is determined by a Dynamic System Setting named indexing/explicitindexdir.
Correspondence processing by using Microsoft Word requires disk space for temporary files on the user's workstation. These temporary files are created in the directory identified by the Windows TEMP environment variable, or in C:/PegaTemp if the TEMP variable is not found or identifies a device other than C:.
Open topic with navigation