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" />

where D:\zzzzz identifies an existing directory.

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:

• 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 — Extracted image files (.jpg, .gif, .png) and JavaScript files (.js) in subdirectories corresponding to user ruleset lists
• 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 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.

• Using full-text search based in Elasticsearch
• Configuring dynamic system settings