This note explains how to clean the following Platform Process Manager's work directories and how to set up automatic directory cleaning for some of the directories:

• %JS_TOP%\work\history: This directory contains all of the flow-instance history information. When you want to check the history of a finished flow instance, FlowManager looks up that history in this directory. To set up automatic cleaning for this directory, add the following parameter to the js.conf file:
  js_history_clean_period=days
  In this parameter, days specifies how often (in number of days) you want the file cleaned.
• %JS_TOP%\work\events: This directory contains flow-instance status information, which is critical for JFD recovery purposes. To clean this directory, delete the js.events.n files. You can safely delete these files, but be sure that you DO NOT delete the file named js.events because it contains critical information.
• %JS_TOP%\work\storage\flow_instance\finished: This directory contains information about the finished flow instances. When you want to view the finished flow instances, FlowManager looks for those instances in this directory. Note: When this directory is being cleaned, you cannot see the finished flow instances.

  To automatically clean this directory, you need to remove the comment delimiters from the following lines:

  • js_im_policy_lifetime=days (where days specifies the lifetime of the policy)
  • js_im_activepolicy=jf_im_tpolicy

  For more details on these parameters, see Administering Platform Process Manager, Version 3.0

Operating System and Release Information