Workday Driver 1.3.1.0000 Readme

Overview

The Workday driver for Identity Manager can seamlessly provision users and their attributes from the Workday cloud application. The provisioning is done keeping the user identity information consistent across the Identity Vault and the Workday cloud application.

The driver version will be changed to 1.3.1.0000 after applying this patch.

This readme document consists of the following sections:

System Requirements

  • Identity Manager 4.8.x
  • Installing the Workday Driver

    Installing the Workday Driver Files

    1. Download and unzip the contents of the IDM_WorkDayDriver_1.3.1.zip file to a temporary location on your computer.

    2. To install the driver files as a root user:

      1. Login as root on the server where you want to apply the driver jar file.

      2. Navigate to the extracted IDM_WorkDayDriver_1.3.1.zip directory and perform one of the following actions for your platform:

        • For Linux: Install the new novell-DXMLWday.rpm in your driver installation directory by running the following command in a terminal window:

          • If you are installing the binary, run the command: rpm -Ivh (binaries-path)/novell-DXMLWday.rpm

        • For Windows: Copy the WorkdayShim.jar and WorkdayUtil.jar file to your driver installation folder. For example, \NetIQ\IdentityManager\NDS (local installation) or \Novell\RemoteLoader\64bit (remote installation).

      3. Find the dependent jar files and perform the following actions as required:

        • Linux:
          • Copy the imgscalr-lib-4.2.jar, jcce-1.3.0.jar, and jcce-oauth-1.3.0.jar from IDM_WorkDayDriver_1.3.1/common folder and place it in the driver installation folder. For example, /opt/novell/eDirectory/lib/dirxml/classes/ (for local or remote installation).

        • Windows:
          • Copy the imgscalr-lib-4.2.jar, jcce-1.3.0.jar and jcce-oauth-1.3.0.jar from IDM_WorkDayDriver_1.3.1/common folder and place it in the driver installation folder. For example, \NetIQ\IdentityManager\NDS (local installation) or \Novell\RemoteLoader\64bit (remote installation).


    3. (Conditional) To install the driver files as a non-root user:

      1. Verify that /rpm directory exists and contains _db.* file.

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

      3. To set the root directory to the location of non-root Identity Vault, enter the command ROOTDIR=non-root eDirectory location in the command prompt.

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

      4. To install the Workday driver files, enter the following command:

        For example, to install the Workday driver RPM, use this command:

        rpm --dbpath $ROOTDIR/rpm -Ivh --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-DXMLWday.rpm

        Note: In the above command /opt/novell/eDirectory is the location where non-root Identity Vault is installed, and /home/user/ is the home directory of the non-root user.

      5. Find the dependent jar files and perform the following actions as required:

        • Linux:
          • Copy the jar files imgscalr-lib-4.2.jar, jcce-1.3.0.jar and jcce-oauth-1.3.0.jar and place it in the driver installation folder.

        • Windows:
          • Copy the jar files imgscalr-lib-4.2.jar, jcce-1.3.0.jar and jcce-oauth-1.3.0.jar and place it in the driver installation folder.

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

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

    Upgrading the Workday Driver

    The driver upgrade process involves the following tasks:

    Upgrading the Driver Packages

    1. Download the required Workday Driver Packages from Workday Driver plugins to a temporary location on your computer.
    2. Name Package Name Version Build Date Build Number
      Workday Base NETQWDBASE 1.1.2 20240830 094740
      Workday Default Configuration NETQWDDCFG 1.1.1 20241024 162900

    3. Open Designer.

    4. In the Outline view, right-click Package Catalog.

    5. Click Import Package.

    6. Navigate to the location where you downloaded the Workday packages.

    7. Click Select All to import all of the packages displayed.

    8. Click OK.

    9. (Conditional)To update packages in designer with internet connectivity:-On the menu bar, navigate to Help and select Check for Package Updates. Install the required Workday packages

    10. Open the project contains the driver.

    11. Right-click the driver for which you want to upgrade an installed package, then click Driver > Properties.

    12. Click Packages.
    13. A check mark indicates a newer version of a package in the Upgrades column.

    14. Click Select Operation for the package that indicates there is an upgrade available.

    15. From the drop-down list, click Upgrade.

    16. Select the version that you want to upgrade to, then click OK.
    17. NOTE: Designer lists all versions available for upgrade.

    18. Click Apply.

    19. (Conditional) Enter required details to upgrade the package, then click Next.
    20. Read the summary of the packages that will be installed, then click Finish.

    21. Review the upgraded package, then click OK to close the Package Management page.

    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_WorkDayDriver_1.3.1.zip file to a temporary location on your computer.

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

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

      2. Navigate to the extracted IDM_WorkDayDriver_1.3.1.zip directory and perform one of the following actions for your platform:


      3. Find the dependent jar files and perform the actions as shown in Step 3.

    6. (Conditional) To upgrade 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. The absence of this file might indicate that Identity Manager is not installed properly. You must reinstall the Identity Manager to correctly place the file in the directory.

      3. To set the root directory to the location of non-root Identity Vault, enter the following command in the command prompt:
      4. ROOTDIR=<non-root eDirectory location>

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

      5. To upgrade the driver files, enter the following command.
      6. For example, to upgrade the Workday 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-DXMLWday.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. Find the dependent jar files and perform the following actions as shown in Step 4.

    Technical Support Information

    Issues Fixed in Current Release

    Issues Fixed in Previous (1.3.0.0300) Release