Directory structure

RICOH ProcessDirector uses specific directories and subdirectories on the system to store its files. At some point, you might need to access a directory or locate a specific file in a subdirectory.
    Note:
  • Updates might overwrite files in the /aiw/aiw1/samples directory, but they do not overwrite files in the /aiw/aiw1/control_files directory. We recommend copying sample files into the /aiw/aiw1/control_files directory and making all your changes in the copied file.

RICOH ProcessDirector directory structure

Directory name Contents
/aiw/aiw1/audit/InputDevice Completed audit files for input devices
/aiw/aiw1/audit/Instance Completed audit files for servers
/aiw/aiw1/audit/Job Completed audit files for individual jobs
/aiw/aiw1/audit/JobType Completed audit files for workflows
/aiw/aiw1/audit/Printer Completed audit files for most types of printers
/aiw/aiw1/audit/PrinterInternalAFP Completed audit files for AFP printers
/aiw/aiw1/audit/JdfOutputPrinter Completed audit files for Ricoh PDF printers
/aiw/aiw1/audit/StepTemplate Completed audit files for step templates
/aiw/aiw1/audit/User Completed audit files for users
/aiw/aiw1/config/ Miscellaneous configuration files
/aiw/aiw1/control_files/audit/ Control files for collecting audit information for jobs
Note: Some objects, such as input devices, only record messages as audit information and do not have control files to control the type of audit information that RICOH ProcessDirector retains.
/aiw/aiw1/control_files/banner_pages/ Configuration files for banner pages
/aiw/aiw1/control_files/external_programs/ Control files for use with external programs
/aiw/aiw1/control_files/passthru/ Control files for use with Passthrough printers
/aiw/aiw1/control_files/rules/ Rules files for assigning workflows and setting job properties.
/aiw/aiw1/samples/audit/ Control file templates for collecting audit information for jobs

Files in the samples directory are only used as templates for customizing control files. RICOH ProcessDirector does not use them at runtime.

Note: Some objects, such as input devices, only record messages as audit information and do not have control files to control the type of audit information that RICOH ProcessDirector retains.
/aiw/aiw1/samples/banner_pages/ Configuration templates for banner pages

Files in the samples directory are only used as templates for customizing control files. RICOH ProcessDirector does not use them at runtime.

/aiw/aiw1/samples/external_programs/ Control file templates for use with external programs

Files in the samples directory are only used as templates for customizing control files. RICOH ProcessDirector does not use them at runtime.

/aiw/aiw1/samples/passthru/ Control file templates for use with Passthrough printers

Files in the samples directory are only used as templates for customizing control files. RICOH ProcessDirector does not use them at runtime.

/aiw/aiw1/samples/rules/ Rules templates for assigning workflows and setting job properties

Files in the samples directory are only used as templates for customizing control files. RICOH ProcessDirector does not use them at runtime.

/aiw/aiw1/exits Compiled user exit programs
/aiw/aiw1/resources Job resources

               /aiw/aiw1/spool/default
               
               
            
or

               /aiw/aiw1/spool/SpoolName
               
               
               
            
Job data
/aiw/aiw1/System Input device folders
/aiw/aiw1/testfiles Sample print files
/aiw/aiw1/trace System trace files
/opt/infoprint/ippd/afpviewer/font Font configuration files for file viewer
/usr/lpp/psf/exits Sample printer-driver user exit programs

Only available when the AFP support feature is installed.

/usr/lpp/psf/reslib AFP font and form definition files

Only available when the AFP support feature is installed.