Temporary files are created in temporary files directories on the Pega Platform server to temporarily contain information that is required during installation or browsing.
On each Java virtual machine (JVM) instance, 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" />
identifies an existing directory.
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:
- LLC — Contains the lookup list cache
- PRGenBackup — Backup copies of older versions of the generated files in PRGenJava and PRGenClasses
- PRGenJava — Java source code, generated by rules assembly
- PRGenClasses — Compiled Java, from source code generated by rules assembly
- StaticContent/global/ServiceExport — Used by the archive tools for .zip files; also contains files generated from the Deployment tab of a service package data instance.
For example, if the directory is
D:/Temp, the ServiceExport directory
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
- Do not delete the temporary files directory.
- Each JVM instance must have a dedicated, distinct temporary directory.
- Microsoft Windows 2000/XP/2003 Server systems have a limit of 255 characters in the file name. Because the directory names for generated temporary files may become deep, keep the value of the explicitTempDir directory as short as possible.
- In a local area network, the temporary files directory can be on any disk, but each node in a multinode clustered system must have a distinct, dedicated temporary files directory.
- Most files in the ServiceExport directory are deleted promptly after the associated upload, download, or other processing operation on the file completes, for space and security reasons.