3.12 Working Directories

Distributors and Subscribers use working directories on the servers for Distributions, patches, status files, and temporary working files. The size of a working directory is determined by the size and number of Distributions.

The working directories default to the sys: volume on NetWare servers or the C: Drive on Windows servers. Because of disk space considerations on NetWare servers, we recommend that you select a different location on the server, such as a data: volume.

The default working directory names for NetWare and Windows servers are path\zenworks\pds\ted\dist for the Distributor and path\zenworks\pds\ted\sub for the Subscriber. For Linux and Solaris servers, the paths are /var/opt/novell/zenworks/zfs/pds/ted/working/dist and /var/opt/novell/zenworks/zfs/pds/ted/working/sub. You can change working directory names in the properties of the Tiered Electronic Distribution object.

The following sections describe the Tiered Electronic Distribution directory structures:

3.12.1 NetWare Distributor Directories

The following directories are used by NetWare Distributors:

volume:\installation_path\zenworks\pds\ted

Contains the Tiered Electronic Distribution software for the Distributor.

volume:\installation_path\zenworks\pds\ted\security\private

Contains the Distributor’s private key.

volume:\working_directory

Contains one directory for each Distribution that belongs to the Distributor. The working directory name is user-defined in the Distributor object.

volume:\working_directory\distribution_directory

Each Distribution has its own directory that is created under the working directory. The Distribution directory’s name is derived from the following syntax: Tree_DN_of_Distribution. For example, TestTree_Files.Distributions.ZENworks.Novell.

volume:\working_directory\distribution_directory\time_stamp_directory

Each Distribution directory contains multiple time-stamp directories, which are named according to the date and time the Distribution was built.

Each time a Distribution is built, the Distributor checks to see if anything has changed since the last time the Distribution was built. If so, a new time-stamp directory is created.

The number of time-stamp directories kept is determined by the Maximum Number of Revisions to Keep field in the Distribution object’s properties. There are occasions when the number of time-stamp directories exceeds the maximum number specified, because the Distributor does not delete a time-stamp directory that is in use. The Distributor removes the oldest time-stamp directories first.

Sometimes a time-stamp directory name has _temp appended to it. When a Distributor builds a Distribution, it creates a \*_temp directory before it determines if anything has changed. If changes are discovered, \_temp is removed and the directory is used for the new build.

A Distributor’s time-stamp directories contain the files listed in Table 3-18:

Table 3-18 Files in the Distributor’s Time-Stamp Directories

Filename

Description

distfile.ted

The Distribution that was built. All Distributions have the same filename. They are distinguished by their time-stamp directory’s name and path.

digest_file

This file only exists if the Distributor Agent creates it (optional).

Digests are used by Distributors and Subscribers to verify that Distributions have not been tampered with while in transit. The digest provides an MD5 checksum for the Subscriber to compare.

Digests also detect corruption in a Distribution’s package. In the case of corruption, the Subscriber renames the distfile.ted Distribution file to distfile.corrupt and the Distribution is rebuilt and sent the next time the Channel’s schedule fires.

The syntax for creating the digest filename is:

    %AGENT%AgentDigest.ted

For example:

  • FTPAgentDigest.ted
  • HTTPAgentDigest.ted
  • FileAgentDigest.ted
  • CPKAgentDigest.ted

3.12.2 NetWare Subscriber Directories

The following directories are used by NetWare Subscribers:

volume:\installation_path\zenworks\pds\ted

Contains the Tiered Electronic Distribution software for the Subscriber and/or Distributor.

volume:\installation_path\zenworks\pds\ted\security

Contains certificates received from Distributors.

volume:\working_directory

Contains one directory for each Distribution that it receives from a Distributor. The working directory name is user-defined in the Subscriber object.

volume:\working_directory\distribution_directory

Each Distribution has its own directory that is created under the working directory. The Distribution directory’s name is derived from the following syntax: Tree_DN_of_Distribution. For example, TestTree_Files.Distributions.ZENworks.Novell.

volume:\working_directory\distribution_directory\time_stamp_directory

Each Distribution directory contains multiple time-stamp directories, which are named according to the date and time the Distribution was built.

The number of time-stamp directories kept is determined by the Maximum Number of Revisions to Keep field in the Distribution object’s properties.

After a threshold is met, the Subscriber receives the maximum revision information and deletes the oldest time-stamp directories first.

A Subscriber’s time-stamp directories contain the files listed in Table 3-19:

Table 3-19 Files in the Subscriber’s Time-Stamp Directories

Filename

Description

distfile.ted

The Distribution that was built. All Distributions have the same filename. They are distinguished by their time-stamp directory’s name and path.

diststatus.ted

After a Distribution has been successfully received, this file is created.

digest_file

This file only exists if the Distributor Agent has created it (optional).

Digests are used by Distributors and Subscribers to verify that Distributions have not been tampered with while in transit. The digest provides an MD5 checksum for the Subscriber to compare.

Digests also detect corruption in a Distribution’s package. In the case of corruption, the Subscriber renames the distfile.ted Distribution file to distfile.corrupt and the Distribution is rebuilt and sent the next time the Channel’s schedule fires.

3.12.3 Windows Distributor Directories

The following directories are used by Windows Distributors:

installation_path\zenworks\pds\ted

Contains the Tiered Electronic Distribution software for the Distributor.

installation_path\zenworks\pds\ted\security\private

Contains the Distributor’s private key.

3.12.4 Windows Subscriber Directories

The following directories are used by Windows Subscribers:

installation_path\zenworks\pds

Contains the Tiered Electronic Distribution software for the Subscriber.

installation_path\zenworks\pds\ted\security\private

Contains certificates received from Distributors.

local_drive:\working_directory\distribution_directory\time_stamp_directory

Each Distribution directory contains multiple time-stamp directories, which are named according to the date and time the Distribution was built.

3.12.5 Linux or Solaris Distributor Directories

The following directories are used by Linux or Solaris Distributors:

/var/opt/novell/zenworks/zfs/pds/ted/working/dist

Contains the Tiered Electronic Distribution software for the Distributor.

/var/opt/novell/zenworks/zfs/pds/ted/security/private

Contains the Distributor’s private key.

Each Distribution directory contains multiple time-stamp directories, which are named according to the date and time the Distribution was built.

3.12.6 Linux or Solaris Subscriber Directories

The following directories are used by Linux or Solaris Subscribers:

/var/opt/novell/zenworks/zfs/pds/ted/working/sub

Contains the Tiered Electronic Distribution software for the Subscriber.

/var/opt/novell/zenworks/zfs/pds/ted/security/private

Contains certificates received from Distributors.

Each Distribution directory contains multiple time-stamp directories, which are named according to the date and time the Distribution was built.