Temporary files and temporary files directories

Temporary files are created in temporary files directories on the Pega Platform server or your workstation to temporarily contain information that is required during installation or browsing.

Server temporary files

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.

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:

• 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.
• SystemManagement/SystemManagementInformation — Contains .zip files named SMA_INFO_date.zip created on request by the System Management application.

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.

Notes:

• 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.
• Although not needed in ordinary system operations, you can delete (reinitialize to empty) the static content directories by using the System Management application. Alternatively, deleting the extract marker file on a node causes the system to clear this directory (and others) during the next system startup.
• 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.

Internet Explorer temporary files

The workstation cache for the Internet Explorer holds web pages, images, CSS files, and JavaScript files. In Internet Explorer, click Tools > Internet Options > General > Temporary Internet Files to set the directory that contains this cache.

Correspondence temporary files

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