JDBC Driver 4.2.2.0200 Readme

Overview

This patch is applicable for JDBC drivers running Identity Manager 4.7.2 or later. The driver version will be changed to 4.2.2.0200 after the patch is applied.

What's New

  • Supports Azure Database for PostgreSQL flexible servers. For more information refer to:Azure Database for PostgreSQL flexible servers

    • This Readme comprises the following sections:

    System Requirements

    Identity Manager 4.8 or later

    Upgrading the Driver

    The driver upgrade process involves the following tasks:

    Upgrading the Driver Packages

    1. Download the following packages:

      Name Package Name Version Build Date Build Number
      MySQL Base NOVLJDBCMYBS 2.4.2 20220823 165540


    2. Open the project in Designer to deploy the driver.

    3. Navigate to Help menu and select Check for Package Updates. Install the above JDBC packages.

    4. Drag the driver from Designer Palette > Tools.

    5. Configure the driver as mention in JDBC Implementation Guide.

    6. To verify driver configuration and packages, right click the connector line and navigate to Properties > Packages.

    Upgrading the Driver Files

    1. Take a back-up of the current driver configuration.

    2. (Conditional) If the driver is running locally, stop the driver instance and the Identity Vault.

    3. (Conditional) If the driver is running with a Remote Loader instance, stop the driver and the Remote Loader instance.

    4. Download and unzip the contents of the IDM_JDBC_4.2.2_P2.zip file to a temporary location on your computer.

    5. (Conditional) To update the driver files as a root user:

      1. On the server where you want to apply the driver patch, log in as root.

      2. Perform the following steps based on your platform:


    6. (Conditional) To update the driver files as a non-root user:

      1. Verify that <non-root edirectory="" location="">/rpm directory exists and contains _db.* file.

        2. The _db.* file is created during a non-root installation of the Identity Manager engine. Absence of this file might indicate that Identity Manager is not properly installed. Reinstall Identity Manager to correctly place the file in the directory.

      2. To set the root directory to the location of non-root Identity Vault, enter the following command in the command prompt:

        3. ROOTDIR=<non-root eDirectory location>

        This will set the environmental variables to the directory where Identity Vault is installed as a non-root user.

      3. To install the driver files, enter the following command:

        4. For example, to install the JDBC driver RPM, use this command:

        rpm --dbpath $ROOTDIR/rpm -Uvh --relocate=/usr=$ROOTDIR/opt/novell/eDirectory --relocate=/etc=$ROOTDIR/etc --relocate=/opt/novell/eDirectory=$ROOTDIR/opt/novell/eDirectory --relocate=/opt/novell/dirxml=$ROOTDIR/opt/novell/dirxml --relocate=/var=$ROOTDIR/var --badreloc --nodeps --replacefiles /home/user/novell-DXMLjdbc.rpm

        where /opt/novell/eDirectory is the location where non-root eDirectory is installed and /home/user/ is the home directory of the non-root user.

    7. (Conditional) If the driver is running locally, start the Identity Vault and the driver instance.

    8. (Conditional) If the driver is running with a Remote Loader instance, start the Remote Loader instance and the driver instance.

    Technical Support Information

    Issues Fixed in Current Release

    Issues Fixed in Previous Release (4.2.2.0100)