Server

On each server node of a Process Commander system, temporary files including Java code and compiled Java classes are created in a directory identified during installation.

This directory is defined by the explicitTempDir setting in the prconfig.xml file:

<env name="Initialization/explicitTempDir" value="D:/zzzzz" />

where D:/zzzzz identifies an existing directory. (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 5.5.

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 images (JPG, GIF, PNG), 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

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 practical.

Although not needed in ordinary system operation, you can delete (re-initialize to empty) the static content directories 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 Process Commander system must have a distinct, dedicated temporary files directory.

Beginning with V5.5, 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. Select Tools > Internet Options > General > Temporary Internet Files from the Internet Explorer to set the directory that contains this cache.

Correspondence temporary files

Correspondence processing using Microsoft Word requires disk space for temporary files on the use workstation. Process Commander creates these temporary files 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:

Visio and open authoring temporary files

Process Commander saves temporary workstation files created by Microsoft Visio and by open authoring of HTML, XML or Java code in the Local Settings/Temp directory.

	extract marker file, lookup list cache, open authoring, rules assembly, static content
	Caching in Process Commander How to set up Internet Explorer 6 How to set up Internet Explorer 7 About the System Management application

Definitions — T