Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Clearing the WebSphere tempWork directory

Updated on May 8, 2019

To clear the WebSphere tempWork directory, you must redeploy the .WAR file completely or delete the marker file. The WebSphere System Console offers three choices in related to clearing cache:

  • ClearCache and DeleteStaticContentCache buttons from the Rule Cache Summary option,

  • DeleteLookupListCache from the LookupList Cache Detail. 

Despite choosing all three of these options, we observe that not all of the files in the WebSphere tempWork directory have been deleted or had their dates updated.  Does this indicate an error, or normal behavior?


 

 

Suggested Approach

These three buttons work as follows:

  • ClearCache is used to clear a memory cache. 
  • DeleteStaticContentCache is used to remove files that have been pulled out of the Rule-File-* instances in the PegaRULES database  
  • LookupListCache has its own directory of XML files that support the Class Explorer and other lists.

None of these affect the temp directory.  The temp directory is changed if you redeploy your .WAR file completely, or if you delete the marker file.  Otherwise, the temp directory should not change, so the behavior you are seeing is accurate. 

You may see files with older dates in the temp directory, but that reflects the dates of the generated Java.  But the rules and data with which you'll be working, and on which you'll be operating, will be current.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us