The Database File

Policy and Distribution Services uses a Sybase database file named ZFSLOG.DB. ZfS can function normally without the database, because it uses ZFSLOG.DB only to log information for Policy and Distribution Services reporting.

Database File Location

ZFSLOG.DB is normally located in the \ZENWORKS\PDS\DB directory on a server. Its location is determined when using the installation program. It can reside on both NetWare^® and Windows servers.

The Database Object

A Novell eDirectory^TM database object is created during installation. In its properties, you must list the location of the database file (ZFSLOG.DB), and you must configure the ZENworks Database policy (Service Location Package) to specify the database object. The location and policy are necessary for the database file to be found for logging information.

Running the Database

On NetWare servers, the database is run by using the MGMTDBS.NCF file (located in the SYS:\SYSTEM directory), which is executed from AUTOEXEC.NCF.

On Windows servers, the database is run by using the Novell Sybase Database service.

Database Caching

Database files can become very large, which is why a 32 MB cache is recommended on the server where you are running the database. Caching will improve server performance because of how frequently information can be logged to ZFSLOG.DB.

Database Information

ZFSLOG.DB is used by Policy and Distribution Services to log successes and failures for the Server Policies or Tiered Electronic Distribution (TED) components. Policy information can be purged automatically according to a policy setting. TED information can be purged manually from the database object. For information on purging, see Purging the Database.

ZFSLOG.DB does not contain any configuration information.

The Distributor is the only TED object that writes to the database.

The following information is written to ZFSLOG.DB by the agents:

For information on obtaining reports on the database information, see Reporting.

The following provides information on gathering data for the database:

• A Distributor keeps track of each Subscriber in its routing hierarchy, so it knows which parent Subscribers have received a Distribution.
• The Distributor knows which Subscribers are at the end of a particular route, so it can know if Subscribers have not received a Distribution because a Subscriber higher up in the hierarchy failed to receive the Distribution.
• Subscribers send messages directly to the Distributor indicating that they have received a Distribution. The Distributor does not return a confirmation that it received the Subscriber's message.
• If a Distributor is not running when a "Successfully Received" message is sent from a Subscriber, this information will not be written to the database. Because a message receipt confirmation is not received by the Subscriber, it will not re send the message.

Coexisting Databases

You can have multiple ZENworks databases in the tree. The number you have depends on whether you want consolidated reporting and can live with the additional network traffic in a WAN environment.

If you do not require consolidated reports, you can install one database object for each of your WAN segments. This will eliminate writing to the database file over a WAN link by the Distributor.

For the server selected for a database file, you should not install a ZENworks for Desktops (ZfD) database object when a ZENworks database object exists for Policy and Distribution Services. The ZfD database object will replace the ZfS database object. However, you can install a ZfS ZENworks database object where a ZfD database object exists.

Server Inventory or Management and Monitoring Services database objects can be installed where a ZENworks database object exists (or the other way around) without any database object replacement problem.