The ZENworks database should be installed on a server where policies are enforced. This is required so that you can use the ZENworks Database policy to locate ZFSLOG.DB.
The database object is automatically created in the tree when you run the Installation Wizard 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 will 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:
To install the ZENworks database:
On the workstation, insert the ZENworks for Servers product 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 NT* server CD drive, then run the installation from a workstation, you must have a drive mapped to the CD drive of that NT server.
Click the ZENworks for Servers option > click the Install Policy and Distributions Services option.
Review the License Agreement > click Accept if you agree > click Next.
or
Click Decline > click Next to exit the Installation Wizard.
Browse and select the tree to install to (only one tree can be selected) > click Next.
The tree name is not case-sensitive.
Click Next on the License page.
Click Add > browse for the server or multiple servers (use Shift or Ctrl) where you want to install the database.
Check the radio button under the Database column for each server where you want a database to be running.
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 TED objects, the database should be installed on the same server as the Distributor to minimize network traffic.
If you have not previously installed the ZfS 2 database, enable this option for at least one Distributor. If you enable this option, 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 will be installed. If the file exists, the database object will still be installed.
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.
To install the necessary software for the database objects, click the Copy Files and Create Objects for the Selected Components radio button.
If this option is not selected, software will not be installed and the database objects will not be created in the tree.
To have the installation program modify AUTOEXEC.NCF, check this box.
The Modify AUTOEXEC.NCF option will ensure that the database will be started.
To pause the installation and give you the opportunity to unload Java* before continuing the installation, check the Pause Installation If JAVA.NLM Is Loaded On Target Server box.
If this box is not checked, the installation program skips any servers where Java is loaded and does not install the database. An error for each such server will be logged to:
C:\TEMP\_RESNumber.TXT
where Number is increased incrementally each time a new installation log is created.
When you have finished configuring the component options, click Next.
The Database page is displayed.
Select a volume for the database > click Next.
SYS: is not recommended because ZFSLOG.DB can become large. It is used for logging report information on server policies and TED usage.
The Summary page is displayed.
Review your selections > click Finish.
The Installation Wizard now copies files and installs the database objects.
WARNING: If you click Cancel, none of the work you did in the Installation Wizard 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.
Continue with setting up the database (see Configuring the ZENworks Database Policy ).
You must set up a database locator policy so that information can be logged to the database.
The Distributor Agent requires a database policy that is associated. The Policy/Package Agent requires a database policy that is distributed to each Subscriber server where the agent is installed.
The Distributor Agent writes distribution information, and the Policy/Package Agent writes policy information.
Perform the following applicable tasks:
To configure the required attributes for the ZENworks Database policy:
In ConsoleOne®, browse eDirectory for the container you created specifically for Policy Package objects.
If necessary, create the container object.
Right-click the policies container > click New > click Policy Package to open the Policy Package Wizard.
Under Policy Packages, select Service Location Package > click Next.
Name the package > click Next > click Finish to create the package.
Name the package so that it is identified with its ZENworks Database object.
Right-click the Service Location Package > click Properties > click the Policies tab.
If the box under the Enabled column is not checked for the ZENworks Database policy, click it before clicking Properties. A policy must be enabled to activate the Properties button.
Click the check box under the Enabled column for the ZENworks Database policy to enable it > click Properties.
Click to make sure you are viewing the Policy/Distribution Management tab.
Browse for a Database object (or enter its DN) > click Apply > click Close > click OK.
For example, the Database object might read:
ZfS Database.Development.Novell
The Database object was automatically created when you installed the Database. It is located in the same container as the Server object where the database was installed.
Click the Associations tab > click Add.
Browse to the container containing the Distributor objects > click Apply > click Close > click OK.
If you have your Distributor objects in different containers, add the other containers to the list.
The Service Location Package object must be associated so that ZFSLOG.DB can be found by the Distributor Agent for logging information.
Click OK when finished associating the Service Location Package.
To configure the required attributes for the ZENworks Database policy:
In ConsoleOne, browse eDirectory for the container you created specifically for Policy Package objects.
If necessary, create the container object.
Right-click the policies container > click New > click Policy Package to open the Policy Package Wizard.
Under Policy Packages, select Distributed Server Package > click Next.
Name the package > click Next > click Finish to create the package.
Name the package so that it is identified with its ZENworks Database object.
Right-click the Distributed Server Package > click Properties > click the Policies tab.
Click the check box under the Enabled column for the ZENworks Database policy to enable it > click Properties.
Click to make sure you are viewing the Policy/Distribution Management tab.
Browse for a Database object (or enter its DN) > click Apply > click Close > click OK.
For example, the Database object might read:
ZfS Database.Development.Novell
The Database object was automatically created when you installed the Database. It is located in the same container as the Server object where the database was installed.
Click OK when finished.
Distribute the Distributed Server Package object.
For information on distributing policy packages, see Distributing Policies .
The Distributed Server Package object must be distributed so that ZFSLOG.DB can be found by the Policy/Package Agent for logging information.
To make sure that the database will be written to by the Policy/Package Agent and the Distributor Agent:
On a server, load the Policy/Package Agent by doing the following:
Note whether a message is displayed indicating that the Policy/Package Agent has connected to the database.
On a server, load the Distributor Agent by doing the following:
Note whether a message is displayed indicating that the Distributor Agent has connected to the database.
Repeat Step 1 and Step 2 for each server where a Policy/Package Agent or Distributor Agent has been installed.
IMPORTANT: You must repeat Step 2 for each Distributor server because the Distributor Agent must be started or restarted to connect with the database.
To determine whether the Policy/Package Agent or the Distributor Agent is writing to the database, do the following for each agent:
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.
If the message indicates that the agent did not connect to the database, you should check the following: