File Structure

When Process Manager is installed, it creates several directories under its top directory. Some of these directories contain scheduling data, others contain working files, or historical data. Some directories are created when the Process Manager server is started, rather than immediately after installation.

Files created on the server host

The following describes what each directory contains:

Directory

Contents

<version>/app

Contains the files required to run Process Manager Client.

<version>/bin

Contains the executables for all of the Process Manager commands and the Process Manager Client applications.

<version>/etc

Contains the Process Manager messages and the data specification used by the Process Manager software when creating flows.

<version>/examples

Contains example flows you can use and customize.

<version>/jre

On Windows only, contains the Java™ runtime environment files for the client applications.

<version>/install

On UNIX only, contains the Process Manager README file and install.config and other installation-specific information.

<version>/lib

Contains the Process Manager Java™ files.

<version>/resources

Contains the properties files used by Process Manager.

<version>/man

On UNIX only, contains the man pages for each of the Process Manager commands.

<version>/platform

Contains files specifically for running the Process Manager software on each platform.

conf

Contains the configuration files used by the install script to define the Process Manager environment, including js.conf and fod.conf, (if failover is installed) cshrc.js and profile.js.

log

Contains the log files created by Process Manager to store Process Manager Server and failover error logs. Process Manager creates a log file called jfd.log.hostname, which contains the error logs.

work

Contains working information and recovery data required by Process Manager to complete its processing, including the following directories:

  • alarms—contains all alarm definitions
  • calendar—contains all system calendar definitions
  • events—contains persisted events
  • history—contains all historical data
  • lock—contains lock files to prevent multiple Process Manager Servers from accessing the same working files
  • storage—contains copies of active and completed flows
  • system—contains system status data used byProcess Manager Server during recovery
  • templates—contains templates for inserting custom applications in a flow
  • var_comm—contains temporary values for user variables
  • variable—contains the current values of any global or local user variables
  • proxy_storage—contains persisted proxy event definitions

Process Manager history files

The log files containing Process Manager audit data are located in JS_TOP/work/history. Process Manager writes audit data to history files called history.log.<index>.

Process Manager creates a new history.log.<index> file when the log age has reached the number of hours specified with the parameter JS_HISTORY_LIFETIME in js.conf, or the log size has reached the maximum number of bytes indicated with the parameter JS_HISTORY_SIZE in js.conf. The <index> is incremented by 1 every time a new log is created. When JFD is restarted, JFD scans the JS_HOME/work/history directory to determine the last index, and uses that for calculating the index of the next history log file.

History log files are periodically cleaned up according to the time period specified by the parameter JS_HISTORY_CLEAN_PERIOD in js.conf. History log files older than the specified time period are cleaned up by the Process Manager server (JFD). The default is 15 days.

If you do not want history log files to be deleted, you can set the parameter JS_HISTORY_ARCHIVE_DIR in js.conf and specify a directory in which to store archived history logs. When this parameter is set, instead of deleting the old history logs, the Process Manager Server(JFD) moves them into the directory specified by JS_HISTORY_ARCHIVE_DIR according to the time period specified by JS_HISTORY_CLEAN_PERIOD in js.conf.

The parameter JS_HISTORY_LIMIT in js.conf specifies the maximum number of history records retrieved when the jhist command is used and the Process Manager Client and Process Manager Server are on different hosts. If more than the maximum number of records are available, only the oldest number of records specified in this parameter are retrieved.

Process Manager log files

Process Manager creates a log file called jfd.log.hostname, which contains the error logs. The file is located within the directory defined by the JS_LOGDIR configuration setting in js.conf. By default, this directory is JS_TOP/log. However, after installation, you can change the value in js.conf to use a different directory.
Tip: The Process Manager log and event files can contain personal information (for example, UNIX usernames and email addresses). OS-level access control is one level of protecting this persona data; for further protection, you can use encryption software tools to encrypt the disk partition or volume used to store the log and events files. Process Manager log and event files are located at JS_TOP/log and JS_TOP/work.