HPOS 3.5 Job Monitoring in Interdomain Delivery

ManualsBrandsHP ManualsSoftwareHP Output Management Services Software

HP Output Server 3.5 1

Technical Note

List of Directories that can be Deleted

After Performing an HP Output Server

Upgrade

This technical note identifies which files and directories can be safely deleted and which are required to be present

after upgrading to a latest version of HP Output Server. Additionally, it will assist the administrator in determining

which related files and directories can be safely deleted from an upgraded installation, and it will identify the purpose

of specific directories.

NOTE: This document covers standard HP Output Server installations only. It does not cover any

customized installations made by administrators and/or HP Professional Services. If the

HP Output Server installation has been customized, avoid deleting files or directories

created as a part of those customizations. In addition, not all files and directories that are

created by the normal use of the product (such as log files) are listed in this document.

List and use of HP Output Server 3.5 directories

A standard HP Output Server 3.5 server installation uses a specific directory structure. Following is the list of the

important files and directories and their relevant use in the HP Output Server 3.5 installation:

Directory Use

DAZEL_HOME Output server installed directory

DAZEL_HOME/bin Executable and other binary files

DAZEL_HOME/custom User and PS-custom files, scripts and executable

(protected during upgrades and patch operations)

DAZEL_HOME/customDPAOIDs.custom File containing all customized DPAOIDs

DAZEL_HOME/custom/templates Custom delivery object templates

DAZEL_HOME/etc Miscellaneous files, including installation and

configuration files

DAZEL_HOME/etc/versions Currently installed version information

DAZEL_HOME/examples Example files

Summary of content (6 pages)

PAGE 1
Technical Note List of Directories that can be Deleted After Performing an HP Output Server Upgrade This technical note identifies which files and directories can be safely deleted and which are required to be present after upgrading to a latest version of HP Output Server. Additionally, it will assist the administrator in determining which related files and directories can be safely deleted from an upgraded installation, and it will identify the purpose of specific directories.
PAGE 2
List of Directories that can be Deleted After Performing an HP Output Server Upgrade List and use of HP Output Server 3.
PAGE 3
List of Directories that can be Deleted After Performing an HP Output Server Upgrade Upgrading from HP Output Server 3.3 and 3.4.1 Directory Use DAZEL_HOME/var/jobdb/dsup DSM files DAZEL_HOME/var/lock Lock files DAZEL_HOME/var/log Log files DAZEL_HOME/var/mysql Installation and data for MySQL (if installed using defaults) DAZEL_HOME/var/nm NM files DAZEL_HOME/var/nm/dazel.
PAGE 4
List of Directories that can be Deleted After Performing an HP Output Server Upgrade Upgrading from HP Output Server 3.3 and 3.4.1 /lib/dzl_dquery.pl /lib/dzl_jquery.pl /lib/dzl_r3_common.pl /lib/dzl_submit.pl /lib/r3emon.pl /lib/r3emonmgr.pl /lib/r3print.pl /lib/r3stat.pl /var/log/dazel_setup.log /var/log/dazel_upgrade.log /var/log/patch.log /var/log/patchos.
PAGE 5
List of Directories that can be Deleted After Performing an HP Output Server Upgrade Mandatory files and directories in HP Output Server 3.5 Windows platform only The following file is backed-up on Windows platforms during patches and upgrades: /bin/DPAOIDs Mandatory files and directories in HP Output Server 3.5 Following files and directories are required in HP Output Server 3.
PAGE 6
List of Directories that can be Deleted After Performing an HP Output Server Upgrade Conclusion The following files, if they exist, must be removed from DAZEL_HOME/unsupported/tools: aim_dump(.exe) attribute.pl dbindex.exe dbreorg.pl dbreorg.txt prune.pl snapshot2.pl snapship2.txt pddump(.exe) The examples/and tools/ subdirectories (and their contents) must be moved to DAZEL_HOME(so the user will have DAZEL_HOME/examples, instead of DAZEL_HOME/unsupported/examples.