Installing the Driver

The DirXML® Driver for JDBC requires Novell® eDirectoryTM and database-side configuration. We recommend that you configure your database and test it independently of the driver.

You should use these instructions if no previous installation exists for the driver. After you have downloaded the CD image, complete the following instructions to install the driver:


Installing the Driver

  1. Shut down eDirectory.

  2. Copy JDBCShim.jar, JDBCUtil.jar, and CommonDriverShim.jar into the appropriate directory for your platform. Use the following table to determine the appropriate directory:

    Platform Directory Path

    NetWare®

    SYS:\SYSTEM\LIB

    Solaris or Linux

    /usr/lib/dirxml/classes

    Windows NT/2000

    NOVELL\NDS\LIB

  3. Copy the appropriate third-party driver files into the same directory you specified in the previous step.

    NOTE:  These third-party files are not bundled with the driver. These files should be properly licensed, if necessary, when used in a production environment.

    The following table includes third-party driver download information, by vendor.

    Vendor Database Filename(s) Download Instructions

    Oracle

    Oracle 8i

    classes12.zip, nls_charset12.zip

    Oracle Technology Network

    You must first register for free with Oracle's Technology Network. You should download version 8.1.7.1 or later.

    Oracle

    Oracle 9i

    classes12.zip, nls_charset12.zip

    Oracle Technology Network

    You must first register for free with Oracle's Technology Network. You should download version 9.2.0.1 or later.

    BEA Systems

    Microsoft SQL Server 7/2000

    unspecified

    BEA Download Center

    This driver requires free registration and expires on a monthly basis. You should select the JDBC Drivers product and download MSSQLServer4 Kit, Version 7 and 2000.

    You will need to zip/jar the file yourself. To do this:

    1. Place the weblogic\mssqlserver4v70\license\WeblogicLicense.xml file into the \weblogic\smsqlserver4v70\classes directory.

    2. Zip/jar the ...\classes\weblogic directory, including its contents, and the ...\classes\WeblogicLicense.xml file. This directory and XML file must be at the root of the zipped/jarred file.

    Microsoft

    SQL Server 2000

    msbase.jar

    mssqlserver.jar

    msutil.jar

    Microsoft Downloads

    Click the appropriate download option for your platform.

    IBM

    DB2 Universal Database (UDB) 7.2

    db2java.zip

    IBM Downloads

    This driver is part of the free DB2 UDB Personal Developer's Edition download.

    If you apply Fixpacks, ensure that you use the db2java.zip file on the patched server and not the file supplied with the original download.

    Sybase

    Adaptive Server Enterprise (ASE) 12.5

    jconn2.jar

    Sybase Downloads

    To download this driver, select jConnect for JDBC.

    MySQL

    MySQL 3.23

    mysql-connector-java-2.0.14-bin.jar

    MySQL Downloads

    Select MySQL Connector/J2 or later.

    Informix

    Informix Dynamic Server (IDS) 9.3

    ifxjdbc.jar

    not available for download

    Sun

    N\A

    N\A

    Sun Downloads

    Sun's JDBC-ODBC Bridge driver is freely available as part of the Java Runtime Environment (JRE).

  4. Restart eDirectory.

  5. Start ConsoleOne or iManager.


Importing a Driver Configuration

The driver configurations are the sample configurations only. We recommend that you install a driver configuration and run it before customizing the driver. Driver configurations are provided for the following databases:

Database 1.6.1 or Earlier Filename 1.6.2 Filename

Oracle 8i, 9i

JDBCOracleDirect.xml

JDBCOracleIndirect.xml

JDBCOracle.xml

Microsoft SQL Server 7/2000

JDBCMSSQLDirect.xml

JDBCMSSQLIndirect.xml

JDBCMSSQL.xml

IBM Universal Database (UDB) 7.2

JDBCDB2Direct.xml

JDBCDB2Indirect.xml

JDBCDB2.xml

Sybase Adaptive Server Enterprise (ASE) 12.5

JDBCSybaseDirect.xml

JDBCSybaseIndirect.xml

JDBCSybase.xml

MySQL 3.23

JDBCMySQLIndirect.xml

JDBCMySQL.xml

Informix Dynamic Server (IDS) 9.3

JDBCInformixDirect.xml

JDBCInformixIndirect.xml

JDBCInformix.xml

All configurations use the same conventions, regardless of database:

  • String field lengths are 64 characters. Fields of this length can hold most eDirectory attributes. You may want to refine field lengths to enhance storage efficiency.
  • Primary key field lengths are 8 digits.
  • The record_id column in the eventlog table has the maximum numeric precision permitted by each database.
  • All table, trigger, stored procedure, index, and constraint names are lowercase. This is the most commonly used case convention.
  • Triggers names are prefaced with t_, stored procedure names are prefaced with sp_, index names are prefaced with i_, check constraints are prefaced with chk_, primary key constraints are prefaced with pk_ and foreign key constraints are prefaced with fk_.
  • Check, primary, and foreign key constraints follow this naming convention: prefix_table-name_column-name (for example, pk_emp_empno, fk_phone_empno, chk_eventlog_event_type)
  • Triggers follow this naming convention: t_table-name_operation (for example, t_emp_insert)
  • Indexes follow this naming convention: i_table_name_number (for example, i_eventlog_1)
  • Identity columns and sequence objects cache 100 values.
  • Usernames are the last name of a User concatenated with a primary key value (for example, John Doe's username could be Doe1).
  • Initial passwords are the last name of a User (for example, John Doe's password would be Doe). Sybase passwords must be at least 6 characters long. When shorter than 6 characters, last names are padded with the character 'p' (for example, John Doe's password would be Doeppp). The padding character can be adjusted in the Subscriber Command Transformation style sheet.

Importing the Driver Configuration

The driver configuration (XML) file creates and configures the objects needed in order for driver work properly. It also includes sample rules and style sheets you can modify for your implementation.

  1. In iManager, select DirXML Management > Create Driver.

  2. Select a driver set.

    If you place this driver in a new driver set, you must specify a driver set name, context, and associated server.

  3. Mark Import a Driver Configuration from the Server and select the .xml file.

    The driver configuration file is installed on the Web server when you set up iManager.

  4. You will be prompted to enter a name for the driver. Enter the driver's name and click Next to continue.

  5. (Optional) Click Define Security Equivalences.

    1. Click Add, then select an object with Admin rights (or any other rights that you want the driver to have).

    2. Click Apply, then click OK.

  6. (Optional) Click Exclude Administrative Roles to exclude objects from replication.

    1. Click Add, then select any users you want to exclude (such as the admin user).

    2. Click Apply, then click OK.

  7. Click Next to view the import summary. Verify that the configuration is correct, then click Finish with Overview.

The necessary Identity Manager objects have now been created. If you didn't define security equivalences or exclude administrative users during the import, you can complete these tasks by modifying the driver object's properties.