10.3 Installing and Connecting to the Server Management Database

You should install the Server Management database on a server where policies are enforced. This is required so that you can use the ZENworks Database policy to locate the database file, zfslog.db.

The Server Management Database object is automatically created in the tree when you run the installation program and select a server for the database.

The installation program can install only one database at a time. To install additional databases to the tree, you need to perform the steps in the following sections for each database to be installed.

Perform the steps in the following sections to install and set up the database:

10.3.1 Installing the Database

To install a Policy and Distribution Services database:

  1. On a workstation, insert the ZENworks 7 Server Management with Support Pack 1 Program CD.

    The startup screen is displayed. If the startup screen is not automatically displayed after inserting the CD, you can start it by running winsetup.exe at the root of the CD.

    IMPORTANT:Installation from a remote CD is not supported unless there is a drive mapped on the workstation to that CD. For example, if you place the CD in a Windows server CD drive, then run the installation from a workstation, you must have a drive mapped to the CD drive of that Windows server.

  2. Select the Server Management option.

  3. Click Policy-Enabled Server Management to start the installation program.

  4. If you agree with the Software License Agreement, click Accept, then click Next to display the Installation Type page; otherwise, select Decline and click Cancel to exit.

  5. On the Installation Type page, click Next to perform a new installation and display the Installation Options page.

  6. On the Installation Options page, click Next to accept the defaults and display the eDirectory Tree for Creating Objects page.

  7. Browse and select the tree to install to (you can only select one tree), then click Next.

    The tree name is not case sensitive.

  8. On the Server Selection page, click Add, then browse for the server where you want to install the database.

    You can select only one server per run of the installation program.

    You might want a database for each Distributor to write its own information to. However, Distributors can share a database. Because the Distributor writes information to the database for all Tiered Electronic Distribution objects, you should install the database on the same server as the Distributor to minimize network traffic.

    IMPORTANT:Make sure you select a server for the database where you are installing policies. The Purge Database option works only if the zfs.ncf and zfslog.db files are on the same server.

  9. Under Additional Options, select the Server Management Database check box to enable it, then click Next to display the File Installation Paths and Options page.

    The installation program checks all mounted volumes on the server to see if zfslog.db exists. If not, both the file and the database object are installed. If the file exists, the database object is still installed.

  10. Click Next to accept the defaults and display the Database Settings page.

  11. To change the default path to the database file, edit the Database Path field.

    IMPORTANT:Because the database file can become very large, we recommend that you change the default NetWare volume from sys: to another volume on that server.

  12. Accept the other defaults on the Database Settings page by clicking Next to display the Policy and Distribution Services Database Logging page.

  13. To determine logging for the Server Management database that you configured in a previous installation page, select one of the following:

    Log to an existing Server Management database: Select an existing database file for logging by browsing for and selecting the database object to associate it with.

    Log to a Server Management database that will be installed: The database object name that you configured in a previous installation page is the default. However, you can browse for and select an existing database object.

    Do not log to a Server Management database: You can elect to not log to a database at this time, even though you have configured a database in the previous installation page.

  14. On the Summary page, review your selections, then click Finish.

    The installation program now copies files and installs the database objects.

    WARNING:If you click Cancel, none of the work you did in the installation program is saved.

    After the installation has finished, you can check the installation log file (see Step 10) to see if any components failed to install.

    The ZENworks Database policy is automatically created and configured during installation of this new database.

  15. Continue with Section 10.3.2, Connecting to the Database.

10.3.2 Connecting to the Database

To make sure that the database can be written to by the Policy/Package Agent:

  1. On a server, load the agent by doing the following:

    Server Platform

    Agent Startup Method

    Windows

    1. Open the Control Panel.

    2. Click Admin Tools, then click Services.

    3. Click Novell ZENworks Service Manager, then click Start.

    NetWare

    sys:\zenworks\pds\smanager\zfs.ncf
    

    Solaris or Linux

    /etc/init.d/Novell-ZfS Start
    

    Note whether a message is displayed indicating that the agent has connected to the database.

  2. To determine whether the agent is writing to the database, do the following:

    1. At a NetWare server’s console prompt, view the monitor while the agent is loading.

      A message should display that states whether the agent connected with the database.

    2. If the message indicates that the agent did not connect to the database, you should check the following:

      • Is the database is running on the server?

      • Is there a database object that has its Policy/Distribution Management tab set up with the server where the database file is installed?

      • Is there an effective ZENworks Database policy pointing to the database object?