Manually Creating the Inventory Database Object for Sybase

To manually create the Inventory database object for Sybase:

1. In ConsoleOne, right-click in the eDirectory tree where you want to create the database object, click New, click Object, click ZENworks Database, then click OK.

2. Enter a name for the database object, then click OK.

3. Configure the Database server options of the Database object.

   1. In ConsoleOne, right-click the database object, click Properties, then click the ZENworks Database tab.

   2. Select the database server object using any of the following methods:

      • If eDirectory is installed on the database server: in the Server DN field, browse for and select the Server object for the server where the database is physically installed and running.

        The server's IP address is automatically populated to the Server IP Address or DNS Name drop-down list. If the selected server object has more than one IP address, select the appropriate IP address.

      • If eDirectory is not installed on the database server, then enter the server's IP address or the DNS name in the Server IP Address or DNS Name field.

      IMPORTANT:  If the ZENworks database is located on a NetWare 4.x server, you must enter the server's IP address in the Server IP Address or DNS Name field instead of adding the server's object to the Server DN field.

   3. Type the values for the following options:

      • Database (Read-Write) Username: MW_DBA

      • Database (Read-Write) Password: novell

      • Database (Read Only) Username: MW_READER

      • Database (Read Only) Password: novell

      • Database (Write Only) Username: MW_UPDATER

      • Database (Write Only) Password: novell

   4. Click Apply.

   5. To configure the JDBC* Driver properties, click the Jdbc Driver Information tab.

   6. Select Sybase, then click Default Settings.

      This populates the fields with default JDBC driver information.

      The database settings for Sybase are:

      • Driver: com.sybase.jdbc.SybDriver

      • Protocol: jdbc:

      • SubProtocol: sybase:

      • SubName: Tds:

      • Port: 2638

      • Flags: ?ServiceName=mgmtdb&JCONNECT_VERSION=4

      • Database Service Name: the database name specified against the -n Sybase startup parameter while invoking Sybase.

        NOTE:  By default, the value of the -n switch is the IP address of the database server. If you retain this switch value, you must enter the same IP address as the database service name.

   7. Click Apply, then click Close.

Organizing the Database Spaces for a Sybase Database on NetWare or Windows NT/2000 Servers (AlterDBSpace Tool)

If a NetWare database server has volumes other than SYS: or a Windows database server has additional hard drives, placing the Sybase database spaces files on separate volumes or drives improves performance while accessing the database.

If you install the Sybase database component of ZfS 3, the system database file and the database spaces files are installed in the location on the database server you specify. On loading the Inventory database server, the system database file (mgmtdb.db) is loaded. This mgmtdb.db file references the inventory information in the database spaces files. The database spaces files (mgmtdb1.db, mgmtdb2.db, mgmtdb3.db, mgmtdb4.db, mgmtdb5.db, mgmtdb6.db, mgmtdb7.db, mgmtdb8.db, mgmtdb9.db, mgmtdb10.db, and mgmtdb11.db) contain the inventory information.

The alterdb.props file is installed on the database server in the Inventory_server_installation_directory\wminv\properties directory. You can modify the sections in the file to specify the location of the database spaces on the volumes or drives.

The contents of the alterdb.props file are as follows:

#Database Space Properties

count=11

mgmtdb1=location_of_mgmtdb1

mgmtdb2=location_of_mgmtdb2

mgmtdb3=location_of_mgmtdb3

mgmtdb4=location_of_mgmtdb4

mgmtdb5=location_of_mgmtdb5

mgmtdb6=location_of_mgmtdb6

mgmtdb7=location_of_mgmtdb7

mgmtdb8=location_of_mgmtdb8

mgmtdb9=location_of_mgmtdb9

mgmtdb10=location_of_mgmtdb10

mgmtdb11=location_of_mgmtdb11

.....

To organize the database spaces:

1. Ensure that the database is not loaded.

2. Ensure that the Inventory Service Manager is not running on the Inventory server.

3. Manually move the database spaces files on the Inventory server.

   Arrange the database spaces files as follows for better performance:

   • MGMTDB1 and MGMTDB2 in the same location
   • MGMTDB3 and MGMTDB6 in the same location
   • MGMTDB5 and MGMTDB7 in the same location
   • MGMTDB8 and MGMTDB4 in the same location
   • MGMTDB9 and MGMTDB10 in the same location
   • MGMTDB11 in a location

   IMPORTANT:  If you move mgmtdb.db to another directory or volume on a NetWare server, update the sys:\system\mgmtdbs.ncf file with the new location of the mgmtdb.db.

   If you move mgmtdb.db to another directory or volume on a Windows NT/2000 server, run the ntdbconfig.exe located in zenworks\dbengine directory. In the NTDBCONFIG dialog box, enter the new path of the mgmtdb.db.

4. Modify the location of the eleven database spaces files in the alterdb.props file.

   For example, for NetWare, enter:

   mgmtdb3=sys:\\zenworks\\inv\\db

   or for windows nt/2000, enter:

   mgmtdb3=c:\\zenworks\\inv\\db

5. Load the database, then enter mgmtdbs on NetWare servers, or on Windows NT/2000 servers, run the database service.

   Ignore the error messages displayed on the console. These messages are displayed because the database spaces files are not loaded.

6. Ensure that the Database Location policy has been configured.

7. On the Inventory server console, run the AlterDBSpace service, then enter StartSer AlterDBSpace.

   On the Inventory server, the AlterDBSpace tool runs as a service.

   You will see a message that the database is adjusted.

8. Exit the database and then load the database.

   Ensure that there are no errors while loading the database. Errors indicate that the specified location of the database spaces files are incorrect or does not exist. Ensure that the path to the database spaces files is correct in the alterdb.props file and repeat the procedure to organize the database spaces files.

   IMPORTANT:  If you place the database spaces files in different volumes or drives, the log file should be placed in the same volume or drive as the System database file (mgmtdb.db).

Understanding the Sybase Database Startup Parameters

The startup parameters of the Sybase database are as follows:

• -c: Sets the initial memory reserves for caching database pages and other server information. For example, -c 32M reserves 32 MB cache size.

• -gc: Sets the maximum length of time in minutes that the database server runs without doing a checkpoint on each database. The default value is 60 minutes. For example, -gc sets the checkpoint time as 120 minutes.

• -m: Deletes the transaction log when a checkpoint is done, either at shutdown or as a result of a checkpoint scheduled by the server.

• -n: Specifies the host name of the database server. For example, -n IP_address.

• -ti: Disconnects the connections that have not submitted a request for a certain number of minutes. The default is 240 (4 hours). A client machine in the middle of the database transaction locks until the transaction ends or the connection terminates. The -ti option is provided to disconnect inactive connections and to free their locks. For example, specify -ti 400.

• -x: Specifies a communication link. For example, -x tcpip indicates a TCP/IP link.

• database_installation_path: Specifies the installation path of the Inventory database. For example, c:\zenworks\inv\db\mgmtdb.db.

Optimizing the Performance of the Sybase Database

Increasing the database cache size improves database performance.

You can improve the performance of the Inventory database maintained in Sybase on NetWare or Windows NT/2000 Inventory servers. The default database cache size is 32 MB; however, this database cache size may not be adequate for large databases.

You should change the database cache size to an optimum size. You must also consider server memory size while assigning a cache size. For example, if you have 128 MB RAM, then a cache size of 32 MB is recommended.

To change the database cache size on the NetWare database server:

1. Close all connections to the Inventory database.

2. Quit the Sybase server.

3. Open the mgmtdbs.ncf file in the sys:\system directory.

4. Modify the -c parameter.

   For example, -c 64M sets the cache size to 64 MB.

5. Save the file.

6. On the server console, load the Inventory database. Enter MGMTDBS.

To change the database cache size on a Windows NT/2000 database server:

1. Stop the Sybase service.

   On Windows NT, in the Control Panel, double-click Services, select Novell Database - Sybase, then click Stop.

   On Windows 2000, in the Control Panel, double-click Administrative Tools, double-click Services, select Novell Database - Sybase, then click Stop.

2. On the database server, run the ntdbconfig.exe file from the dbengine directory.

   Ntdbconfig.exe is a ZENworks database configuration utility for the ZENworks database using Sybase on Windows NT/2000 servers. This utility enables you to reconfigure the Sybase service. For the list of parameters recommended by Sybase, see Understanding the Sybase Database Startup Parameters.

3. Modify the -c parameter.

4. Click OK.

5. Restart the Sybase service.

   On Windows NT, in the Control Panel, double-click Services, select Novell Database - Sybase, then click Start.

   On Windows 2000, in the Control Panel, double-click Administrative Tools, double-click Services, select Novell Database - Sybase, then click Start.

Backing Up the Inventory Database Running Sybase

ZfS provides an option to back up the Inventory database running Sybase from the ConsoleOne and Inventory database running Oracle from the server. We recommend that you back up the database on a weekly basis. However, if you are tracking the inventory of servers frequently, increase the frequency of backup.

To back up the database on NetWare or Windows NT/2000 servers:

1. In ConsoleOne, click Tools, click ZENworks Inventory, then click Database Backup.

   If you want to back up the latest information in the Inventory database, right-click the database object, click ZENworks Inventory, then click Database Backup.

2. Enter the path to the directory where the database backup will be saved.

   If the Inventory database is running on a NetWare server, you can either enter the path or click Browse to browse for and select a directory. If you just enter the database backup directory name without specifying the complete path, the backup directory will be created in the SYS: directory.

   If the Inventory database is running on a Windows machine, you must manually enter the backup directory path. If you just enter the database backup directory name without specifying the complete path, the backup directory will be created in the \winnt\system32 directory.

   NOTE:  If you want to back up the database to a non-existent directory, only one level of the new directory will be created. To back up the database to subdirectory, ensure that the primary directory already exists. For example, if you want to back up the database to a new c:\backup directory, the backup directory will be created and the database will be backed up. But if you want to back up the database to a new database directory, located under c:\backup, the backup directory must already exist.

3. Click Start Backup.

   This backs up the database to the specified directory on the server running the database and overwrites any existing files without prompting about the overwrite.

To restore the database:

1. If the Inventory database server is up, stop the Storer service. At the database server console, enter StopSer Storer.

2. Exit the Sybase database.

   On NetWare servers: At the database server prompt, enter q to stop the Sybase database.

   On Windows NT, in the Control Panel, double-click Services, select Novell Database - Sybase, then click Stop.

   On Windows 2000, in the Control Panel, double-click Administrative Tools, double-click Services, select Novell Database - Sybase, then click Stop.

3. Copy the backup files, overwriting the working database files.

4. Restart the database server.

The backup tool creates a log file, backupst.txt, located in the consoleone\consoleone_version\bin directory on NetWare and Windows NT/2000 servers. The log records the status of the backup operation. Open this text file to view the status of the backup. This file increases in size for every backup operation. Remove the existing contents of the file if you do not require the details.

Setting Up the Inventory Database for Oracle8i

• Creating the Inventory Database for Oracle8i on a NetWare Server
• Creating the Inventory Database for Oracle8i on UNIX
• Creating the Inventory Database for Oracle8i on a Windows NT/2000 Server

Setting Up the Inventory Database for Oracle9i

• Creating the Inventory Database for Oracle9i on UNIX
• Creating the Inventory Database for Oracle9i on a Windows NT/2000/2003 Server

Manually Creating the Inventory Database Object for Oracle

To manually create the Inventory database object for Oracle:

1. In ConsoleOne, right-click a location in the eDirectory tree for the database object, click New, click Object, click ZENworks Database, then click OK.

2. Type a name for the database object, then click OK.

3. Configure the database server options of the database object.

   1. In ConsoleOne, right-click the database object, click Properties, then click the ZENworks Database tab.

   2. Select the database server object using any of the following methods:

      • If eDirectory is installed on the database server: in the Server DN field, browse for and select the Server object of the server where the database is physically installed and running.

        The server's IP address is automatically populated to the Server IP Address or DNS Name drop-down list. If the selected server object has more than one IP address, select the appropriate IP address.

      • If eDirectory is not installed on the database server, then enter the server's IP address or the DNS name in the Server IP Address or DNS Name field.

      IMPORTANT:  If the ZENworks database is located on a NetWare 4.x server, you must enter the server's IP address in the Server IP Address or DNS Name field instead of adding the server's object to the Server DN field.

   3. Type the values for the following options:

      • Database (Read-Write) Username: MW_DBA

      • Database (Read-Write) Password: novell

      • Database (Read Only) Username: MWO_READER

      • Database (Read Only) Password: novell

      • Database (Write Only) Username: MWO_UPDATER

      • Database (Write Only) Password: novell

   4. Click Apply.

   5. To configure the JDBC Driver properties, click the JDBC Driver Information tab.

   6. Select Oracle, then click Default Settings.

      This populates the fields with default JDBC driver information.

      The database settings for Oracle are:

      • Driver: oracle.jdbc.driver.OracleDriver

      • Protocol: jdbc:

      • SubProtocol: oracle:

      • SubName: thin:@

      • Port: 1521

      • Flags: Not applicable for Oracle

      • Database Service Name: orcl. (The value for the SID is the same as assigned for the database instance.)

   7. Click Apply, then click Close.

Loading the Inventory Database as a Separate Oracle Instance

The following sections explain the steps for configuring and running multiple Oracle database instances:

• Configuring and Running Multiple Oracle Database Instances on a NetWare Server
• Configuring and Running Multiple Oracle Database Instances on a Windows NT/2000 Server

Configuring and Running Multiple Oracle Database Instances on a NetWare Server

To configure and run multiple Oracle database instances:

1. Unload Oracle. At the database server prompt, enter oraunld.

2. Invoke the Net8 configuration utility. At the database server prompt, run easycfg.ncf to load the Net8 Easy configuration window.

3. Define a unique Oracle instance.

   1. Click Config > Listener > Database > Add.

   2. Assign values for Database Instance and Database Name in the Adding Instances Address window.

      For example, assign Database Instance=Indy and Database Name=mgmtdb. In this configuration, the database instance is zfs. You can specify any database instance name. The Database Domain field should be left blank.

   3. Click Accept, then click Save.

4. Configure the Listener for IPC. To run an Oracle system, the IPC and TCP addresses should be already be configured.

   1. Click Config > Listener > Address. Ensure that IPC and TCP addresses are configured for the server.

      The setting for IPC is servername_LSNR, and TCP is IPaddress or hostname. If these settings exist, click Cancel. Otherwise, assign the values for these settings > click Save.

5. Create an IPC alias.

   1. Click Config > Database Alias. The window will list the aliases for IPC, SPX, TCP, and others. Click Add to add an alias name for the new instance.

      Enter the following details:

      • Database Alias: servername-databaseinstance-IPC. For example, the database alias is austr, where austr is the server name, and indy is the database instance created earlier.

      • Protocol: IPC

      • Service/Host Name or Key Name: server_name_LSNR

      • Database Instance: Indy

   2. Click Accept, then click Save.

   3. To verify the configured alias name in the list window: Click Config > Database Alias, select the newly created alias, then click View.

      View the properties of the database alias. Ensure that the properties are correct. If the property settings are incorrect, delete the alias (click Delete) and repeat Step 5.

6. Exit the EasyCfg tool. Click Config > Exit.

7. Create a password file for logging as Internal user for this instance. Enter load orapwd81 file=oracle_volume:oracle_home\database\pwddatabase_instance.ora password=password entries=2 where oracle_volume is the NetWare volume name of your Oracle installation, PWDdatabase_instance.ORA is the password filename, and password is any password that you specify.

   For example, load orapwd81 file=oracle:\orahome1\database\pwdindy.ora password=mgmtdb entries=2. This password file will be created in the oracle_volume:\DATABASE directory. Ensure that the file exists in the directory.

8. Load the Oracle NLM^TM software. At the database server prompt, enter oraload.

9. To set the newly created ZfS instance, load the Oracle Server Manager. At the database server prompt, enter svrmgr31.

10. Enter the following commands: set instance servername-databaseinstance. For example, set instance austr-indy-ipc. This displays that the newly created instance is started.

11. Enter connect internal/password where password is the password created in Step 7.

12. Mount the Inventory database.

13. Modify the _start.sql file located in volumepath\zenworks. Enter the following lines in the file:

    set instance servername-databaseinstance-IPC

    shutdown normal

14. Create the Database object. In ConsoleOne, right-click a location in the tree for the Database object, click New, click Object, click ZENworks Database, then click OK.

15. Type a name for the Database object, then click OK

16. Configure the Database server options of the Database object. For more information, see Step 3 in Manually Creating the Inventory Database Object for Oracle

If you are loading multiple databases in separate Oracle instances, then each database reserves a separate Oracle SGA memory, where Oracle keeps all the database resources. In such environments, you should increase the amount of memory on the server. Refer to the documentation provided by Oracle.

Configuring and Running Multiple Oracle Database Instances on a Windows NT/2000 Server

To configure and run Oracle instances:

1. At the database server, run the Oracle Database Configuration Assistant. From the desktop Start menu, click Programs > Oracle > Database Administration > Oracle Database Configuration Assistant.

2. Click Create a Database > Next > Typical > Next > Copy Existing Database Files from the CD > Next.

3. Enter the following details:

   • Global Database Alias: mgmtdb.your_windows_NT/2000_name

   • SID: The value is automatically filled as mgmtdb.

4. Click Finish.

   This allows for Oracle database creation. This process takes a significant amount of time. Ensure that the OracleServiceMGMTDB service is created and started.

5. Load the Inventory database.

   Run the Oracle Server Manager. From the desktop menu, click Start > Run > SVRMGRL. Enter the following commands:

   set instance mgmtdb

   connect internal/password_for_administrator

Optimizing the Performance of the Oracle Database

If you have an Inventory database on Oracle, you can improve the performance of the database when you generate the inventory reports or query the database.

You use the database buffer cache to store the most recently used data blocks. The database cache is determined as DB_BLOCK_BUFFERS * DB_BLOCK_SIZE. These parameters are specified in the INIT.ORA file in the ZENWORKS\DATABASE directory on the database server.

DB_BLOCK_BUFFERS specifies the number of database buffers. DB_BLOCK_SIZE specifies the size of each database buffer in bytes.

The size of each buffer in the buffer cache is equal to the size of the data block.

Oracle recommends that the database buffer cache for any Online Transaction Processing Application (OLTP) should have a hit ratio of about 90%, which is optimal.

The ZfS Inventory database on Oracle has an approximate 88% hit ratio with a database cache size of 24 MB for 128 MB RAM, which is about 20% of total memory.

If there is additional memory, you configure the database cache size by increasing the DB_BLOCK_BUFFERS parameter in the init.ora file.

Backing Up the Inventory Database Running Oracle

To back up the database running Oracle:

1. If the database server is up, stop the Storer service. At the database server console, enter StopSer Storer.

2. Load the Oracle Server Manager.

   On NetWare server with Oracle, enter svrmgr31.

   On Windows NT/2000 server with Oracle Enterprise Edition, from the taskbar, click Start > Run, enter svrmgrl.

3. Enter the following commands:

   set instance databaservername-databaseinstance-IPC, where databaseinstance refers to the database instance that you have set up earlier. See Loading the Inventory Database as a Separate Oracle Instance.

   For example, set instance austr-zfs3-ipc.

4. Connect as an administrator. For example, if the administrator's internal name is internal, at the Server Manager prompt, enter connect internal/password.

   where password is the password created earlier. See Loading the Inventory Database as a Separate Oracle Instance.

   1. At the Server Manager prompt, enter select name from v$datafile;

      This displays the list of the data files that Server Inventory uses.

5. Ensure that no other databases are mounted. At the prompt, enter shutdown normal.

6. Disconnect and exit from the Server Manager. At the Server Manager prompt, enter disconnect;

   Enter exit;

7. Copy the complete schema directory to a backup volume or disk.

After the backup is done, ensure that the backup copy of the database matches the original copy. Perform database verification to verify the integrity of the backup.

To verify the database integrity on a NetWare server with Oracle, enter load DBV81.NLM FILE=path_to_the_database_file BLOCKSIZE=4096

To verify the database integrity on a Windows NT/2000 server with Oracle, enter DBV.EXE FILE=path_to_the_database_file BLOCKSIZE=4096

Example: enter DBV.EXE FILE=c:\schema\database\cim1.ora BLOCKSIZE=4096

Also, run this command for the following files: cim1.ora, cim2.ora, cim3.ora, cim4.ora, cim5.ora, cim6.ora, cim7.ora, cim8.ora, cim9.ora, cim10.ora, cim11.ora, sys1.ora, and ctl1.ora.

If the database backup is successful, ensure that there are no error messages on the verified pages. Ensure that the following displayed parameters display a zero value: TOTAL PAGES FAILING (DATA)=0, TOTAL PAGES FAILING (INDEX)=0, and TOTAL PAGES MARKED CORRUPT=0.

To restore the database:

1. If the Inventory database server is up, stop the Storer service. At the database server console, enter StopSer Storer.

2. Load the Oracle Server Manager.

   On a NetWare server with Oracle, enter svrmgr31.

   On a Windows NT/2000 server with Oracle Enterprise Edition, from the taskbar, click Start > Run, enter svrmgrl.

3. Connect as an administrator. For example, if the administrator's internal name is internal, at the Server Manager prompt, enter connect internal/password_for_administrator.

4. Ensure that no other databases are mounted. Enter shutdown normal.

5. Disconnect and exit from the Server Manager. At the Server Manager prompt, enter disconnect;

   Enter exit;

6. Copy the database from the backup location.

   If you copy the database to a different location than the earlier location, modify the location in the following files to specify the new path:

   • Edit the init.ora file located in \zfd3\oracle\database to specify the new path for the following parameters:

     control_files=location_of_ctll.ora\ctl1.ora

     background_dump_dest=location_of_trace_dir\trace

     user_dump_dest=location_of_trace_dir\trace

   • Edit the _start.sql file in the sys:\system to specify the location of init.ora file in the following parameter:

     startup pfile=location_of_the_init.ora\init.ora

   • Modify the location in the alterctrl.sql to specify new path.

     For example, modify the existing data:\zfd3\oracle\database path to oracle:\zfd3\oracle\database in alterctrl.sql.

     In this .SQL file, modify the path for the following parameters, if required.

     startup nomount pfile=database_path\INIT.ORA

     logfile group 1 'database_path\log1.ora' size 256K,

     logfile group 2 'database_path\log2.ora' size 256K

     datafile 'database_path\sys1.ora',

     'database_path\rbs1.ora',

     'database_path\cim1.ora',

     'database_path\cim2.ora',

     'database_path\cim3.ora',

     'database_path\cim4.ora',

     'database_path\cim5.ora',

     'database_path\cim6.ora',

     'database_path\cim7.ora',

     'database_path\cim8.ora',

     'database_path\cim9.ora',

     'database_path\cim10.ora',

     'database_path\cim11.ora',

     'database_path\tmp1.ora'

     Save the changes.

7. Load the restored database.

Configuring the Inventory Database for MS SQL Server 2000

Prerequisites for configuring the database include the following:

• Microsoft SQL Server 2000 version 8.00.194 must be installed on the Windows NT/2000 server.
• Minimum free disk space of 50 MB to extract the p1mssqlinvdb.zip file.
• Ensure that you have sufficient disk space to store the inventory data on the server that has the Inventory database.

To configure the Inventory database for MS SQL Server 2000:

1. Copy the p1mssqlinvdb.zip file from the zenworks_for_servers_3_product_cd\zenworks\products\rminv\database\mssql directory to path_of_inventory_database_directory_on_the_database_server.

2. Extract p1mssqlinvdb.zip.

3. From the MS SQL server desktop Start menu, click Programs > Microsoft SQL Server > Enterprise Manager.

4. In the SQL Server Enterprise Manager, browse to Console Root/Microsoft SQL Servers/SQL Server Group/machine_name_running_Inventory_database.

5. Right -click machine_name_running_Inventory_database, then click Properties.

6. In the SQL Server Properties dialog box, click the Security tab and ensure that the authentication is set to SQL Server and Windows.

   
   

7. Click OK.

8. Browse to machine_name_running_Inventory_database/Databases and right-click Databases, click All Tasks, then double-click Attach Database.

9. In the Attach Database dialog box, do the following:

   1. Click the Browse button to browse to and select mgmtdb.mdf as the .mdf database file to be attached.

   2. Ensure that the value of the Attach As field is mgmtdb.

   3. Select sa from the Specify database owner drop-down list.

   4. Click OK.

      The ZENworks Inventory database (mgmtdb) is attached to the Databases server group.

      
      

10. Select mgmtdb, then click the Tools menu, click SQL Query Analyzer.

11. In the SQL Query Analyzer, do the following:

    1. Ensure that mgmtdb is selected in the drop-down list.

    2. Click File > Open.

    3. Select the createloginnames.sql query file from zenworks_for_servers_3_product_cd\zenworks\products\rminv\database\mssql directory.

    4. Click Query > Execute.

       On successful execution, the following message is displayed in the Message pane:

       New Login Created

12. Continue with Connecting the Inventory Server and ConsoleOne to the Inventory Database Running MS SQL 2000.

Connecting the Inventory Server and ConsoleOne to the Inventory Database Running MS SQL 2000

The Inventory server components and ConsoleOne use the Microsoft JDBC driver to connect to the Inventory database on MS SQL 2000. You must install and configure the Microsoft SQL Server 2000 driver for JDBC to use the Inventory system.

To configure the Microsoft SQL Server 2000 driver for JDBC to access the Inventory database running on MS SQL 2000:

1. Download the Windows English version of Microsoft JDBC driver from the Microsoft SQL Server web site.

2. Install the driver on a Windows machine.

3. Copy the msbase.jar, msutil.jar, and mssqlserver.jar files to the inventory_server_installation_directory\inv\server\lib directory.

4. On all NetWare Inventory servers attached to the Inventory database mounted on MS SQL Server 2000, edit the sys:\system\invenv.ncf file to add the names of all the jar files of the JDBC driver in the following format:

   envset tmppath=$tmppath;$root_dir\lib\msbase.jar

   envset tmppath=$tmppath;$root_dir\lib\msutil.jar

   envset tmppath=$tmppath;$root_dir\lib\mssqlserver.jar

   ...

   ...

   envset tmppath=$tmppath;$root_dir\lib\jdbcdrv.zip

5. On all Windows NT/2000 Inventory servers attached to the Inventory database mounted on MS SQL Server 2000, do the following:

   • Edit the inventory_server_installation_directory\wminv\bin\ zensetenv.ini file to append the following entry at the end of each line containing the classpath:

     ..\..\lib\msbase.jar;..\..\lib\msutil.jar;..\..\lib\mssqlserver.jar;

   • Edit the inventory_server_installation_directory\wminv\bin\ invenv.bat file to add the following lines:

     set tmppath=%tmppath%;..\..\lib\msbase.jar

     set tmppath=%tmppath%;..\..\lib\msutil.jar

     set tmppath=%tmppath%;..\..\lib\mssqlserver.jar

6. On the machine running ZfS ConsoleOne with Inventory snap-ins, copy the msbase.jar, msutil.jar, and mssqlserver.jar files to the consoleone_installation_directory\lib\zen directory.

7. In ConsoleOne, create a database object in the same container where the Inventory server is installed.

   1. Right-click the container.

   2. Click New, click Object, select ZENworks Database from the list of objects, then click OK.

   3. Enter a name for the database object, then click OK.

8. Configure the Database server options of the Database object.

   1. In ConsoleOne, right-click the database object, click Properties, then click the ZENworks Database tab.

   2. Select the database server object using any of the following methods:

      • If eDirectory is installed on the database server, in the Server DN field, browse for and select the Server object for the server where the database is physically installed and running.

        The server's IP address is automatically populated to the Server IP Address or DNS Name drop-down list. If the selected server object has more than one IP address, select the appropriate IP address.

        IMPORTANT:  Ensure that the DNS name of the database server configured for the database object is valid. If the DNS name is invalid, you must select an appropriate database server IP address in the Database object property page.

      • If eDirectory is not installed on the database server, specify the server's IP address or the DNS name in the Server IP Address or DNS Name field.

   3. Type the values for the following options:

      • Database (Read-Write) User Name: MW_DBA

      • Database (Read-Write) Password: novell

      • Database (Read Only) User Name: MWM_READER

      • Database (Read Only) Password: novell

      • Database (Write Only) User Name: MWM_UPDATER

      • Database (Write Only) Password: novell

   4. Click Apply.

   5. To configure the JDBC Driver properties, click the JDBC Driver Information tab.

   6. Select MS SQL, then click Default Settings.

      This populates the fields with default JDBC driver information.

      Modify the database settings based on the configuration of your MS SQL Server. The database settings for MS SQL are:

      • Driver: com.microsoft.jdbc.sqlserver.SQLServerDriver

      • Protocol: jdbc:

      • SubProtocol: microsoft:

      • SubName: sqlserver://

      • Port: 1433

      • Flags: Not applicable for MS SQL

      • Database Service Name: Not applicable for MS SQL

   7. Click Apply, then click Close.