Installing the Sybase Database

If you have not installed an ODBC-compatible database to use, you can install the Sybase database included on the ZENworks for Desktops Program CD or the ZENworks 6 Desktop Management Program CD. For information about installing the Sybase database, see "Installing the ZfD Server Software "in "Installing" in ZENworks for Desktops 4.0.1 Installation Guide.

Sybase is also used for the Workstation Inventory database. If you plan to use a database for Application Management reports and you also plan to use Workstation Inventory, you can use the same database installation for both purposes. Each component will create its own database file. Application Management creates a nal.db database file and Workstation Inventory creates a mgmtdb.db database file.

Because the main requirement for Application Management reporting is that the database be at the same site as the users, you should follow the instructions provided for Workstation Inventory to deploy your databases, and then choose one or more databases to use for Application Management reporting. For information about database deployment for Workstation Inventory, see Setting Up Workstation Inventory .

Using an ODBC-Compatible Database

If you will use an ODBC-compatible database other than Sybase, you need to make sure the database is installed. You do not need to create any tables in the database. The first time Application Management sends an event to the database, the appropriate tables will be created.

Installing ODBC Drivers to Workstations

Application Launcher uses an ODBC driver to write application event information to the database.You need to ensure that the correct ODBC driver for your database is installed on each workstation for which you want to record event information.

The correct ODBC driver for the Sybase database is installed by default. However, on Windows 98, you might need to install two additional DLLs (odbccp32.dll and odbcint.dll) that are not installed during a Windows minimal installation. To install these files, copy them from the nal reporting directory on the ZENworks for Desktops Companion CD (or the zenworksfordesktops\nal reporting directory on the ZENworks 6 Companion 1 CD) to the Windows System directory (for example, c:\windows\system). You can also use an Application object to distribute them to the appropriate workstation. You do not need to do this on Windows NT/2000/XP. The files are already present.

Creating a ZENworks Database Object

If you are using the Sybase database that comes with ZfD and have already installed it, the installation program creates a Database object (servername_nalDatabase) in eDirectory. You can skip to the next section, Configuring the Database's ODBC Information.

If you are using another database, you will need to create a ZENworks Database object in eDirectory to represent the database.

To create a ZENworks Database object:

1. Right-click the container where you want to create the object > click New > click Object to display the New Object dialog box.

2. Select ZENworks Database > click OK to display the New ZENworks Database dialog box.

   
   

3. In the Name box, type a name for the database, such as ZfDAppManReports.

4. Select the Define Additional Properties box > click OK to display the ZENworks Database property page.

   
   

5. In the Server DN field, browse for and select the Server object for the server where the database is physically installed and running.

6. If the ZENworks database is located on a NetWare^® 4.x server, replace the DNS name in the Server IP Address or DNS Name field with the server's IP address by selecting the IP address from the field's drop-down list.

7. Fill in the name and password fields for the Read-Write, Read Only, and Write Only users:

   Database (Read-Write) User Name: Enter a user name that will provide both read and write access to the database. If you are using a Sybase database created by the ZfD installation program, the user name is MW_DBA.

   Database (Read-Write) Password: Enter the password for the Read-Write user. If you are using a Sybase database created by the ZfD installation program, the user name is novell.

   Database (Read Only) User Name: Enter a user name that will provide only read access to the database. If you are using a Sybase database created by the ZfD installation program, the user name is MW_READER.

   Database (Read Only) Password: Enter the password for the Read-Write user. If you are using a Sybase database created by the ZfD installation program, the user name is novell.

   Database (Write Only) User Name: Enter a user name that will provide only write access to the database. If you are using a Sybase database created by the ZfD installation program, the user name is MW_UPDATER.

   Database (Read-Write) Password: Enter the password for the Read-Write user. If you are using a Sybase database created by the ZfD installation program, the user name is novell.

8. Click OK to save the information.

Configuring the Database's ODBC Information

Application Launcher uses an ODBC driver to write event information to the database. You need to configure the database object with the ODBC driver information that Application Launcher will need.

To provide the ODBC information:

1. Right-click the database object > click Properties.

2. Click the ODBC Driver Information tab.

   
   

3. Fill in the following fields:

   Driver File Name: Enter the name of the workstation ODBC driver file that Application Launcher will use to access the database. For Sybase, you can enter dbodbc6.dll (for ZfD 4) or dbodbc7.dll (for ZfD 4 SP1 or ZfD 4.0.1), or you can leave the field empty, in which case Application Launcher automatically detects the installed driver.

   Data Source Name: Enter NAL Reporting.

   Connection Parameters: Enter the appropriate commands to connect to the database. For Sybase, these commands are:

   CommLinks=TCPIP{Host=IPAddress:2638};AutoStop=Yes;Integrated=No;DBN=NAL;ENG=IPAddress

   where IPAddress is the actual IP address of the server where the database resides.

4. Click OK to save the ODBC driver information.

Granting ODBC Property Rights to Users

You need to grant users Read and Compare rights to the ODBC properties you defined for the database object in the previous section. This allows Application Launcher to retrieve the ODBC information it needs to access the database.

To grant rights:

1. Right-click the ZENworks Database object > click Trustees of This Object.

2. Click Add Trustee.

3. Select [PUBLIC] > click OK to add [PUBLIC] to the list of trustees.

   Adding [PUBLIC] as a trustee gives every user Read and Compare rights to all of the database object's properties, including the various user names and passwords that can be used to access the database. To avoid this, you need to limit the [PUBLIC] access to the three ODBC properties.

4. In the Property list, select [All Attribute Rights] > click Delete Property to remove it from the list.

5. Click Add Property to display the Add Property dialog box > select zendbODBCConnectionParameters > click OK to add it to the Property list.

   The default rights, Read and Compare, are sufficient. You do not need to change these rights.

6. Repeat Step 5 to add the following properties (keep the default rights: Read and Compare):

   zendbODBCDataSouceName

   zendbODBCDriverFileName

   Host Server

   Network Address

   zendbUser

   zendbPassword

7. Click OK > OK to save the changes.

Enabling the ZENworks Database Policy

Before Application Management can use the database, you need to:

• Activate a Database policy in an eDirectory Service Location Package. The Database policy simply points to the location of the ZENworks database you are using. A Service Location Package can have only one Database policy, and each Database policy can point to only one database. If you haven't created a Service Location Package, or if your current packages' Database policies are being used for other databases, you will need to create a new Service Location Package. Instructions are provided in the steps below.
• Associate the Service Location Package with the containers where the users or workstations reside whose reports you want sent to the database. This association is how Application Launcher knows which database to use when reporting events for a user or workstation.

To activate a ZENworks Database policy and associate containers with it:

1. In ConsoleOne^®, right-click the Service Location Package you want to use > click Properties.

   or

   If you do not have a Service Location Package, right-click the container where you want to create one > click New > click Policy Package. Follow the instructions provided in the Policy Package Wizard to create a Service Location Package.

   
   

2. On the General page, check the box in the Enabled column to enable the ZENworks Database Policy.

3. Select the ZENworks Database Policy in the list > click Properties to display the ZENworks Database properties page > click the Application Management tab to display the Application Management page.

   
   

4. In the ZENworks Database DN field, browse for and select the database object you want to use for Application Management reporting. This should be the same object you configured in Configuring the Database's ODBC Information.

5. Click OK to return to the General page.

6. Click Associations to display the Associations page.

   
   

   You use this page to associate the Service Location Package with the containers where the users or workstations reside whose reports you want sent to the database. If a parent container includes several containers where User and Workstation objects reside, you can select the parent container rather than each individual container.

7. Click Add > browse for and select the container you want to add > click OK to add it to the list.

8. Repeat Step 7 to add additional containers.

9. When you've finished adding containers, click OK to save the information.

Configuring Application Objects to Use Database Reporting

After you've set up the database you will use for reporting, you can start configuring Application objects to use database reporting. Because event reporting is configured on a per-application basis, you can choose which applications you want to collect event reports for and which ones you don't.

For detailed instructions about configuring an application to use database reporting, SNMP trap reporting, or log file reporting, see Configuring Applications to Use Reporting.