2.5 Setting Up the Driver

If you are upgrading an existing driver, setup is not required.

If this is the first time the Delimited Text driver has been used, complete the post-installation tasks in the following sections:

2.5.1 Configuring the Driver

Importing the Sample Configuration File: iManager

  1. Create a local directory for output files.

    For example, on Windows create c:\csvsample\output.

    This directory can be any directory on your local file system. Files on this driver’s Subscriber channel are created and placed here.

  2. Create a local directory where input files can be created.

    For example, on Windows create c:\csvsample\input.

    This directory can be any directory on your local file system. Files for this driver’s Publisher channel are placed here. The driver looks in this directory for files to process.

  3. In iManager, select Identity Manager Utilities > New Driver.

  4. 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.

  5. Mark Import a preconfigured driver from the server, then select the DelimitedTextCSVSample.xml file.

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

  6. Click Next.

    You are prompted for the following information:

    Field

    Description

    Driver Name

    The eDirectory™ object name to be assigned to this driver.

    Output File Path

    Specify the platform-specific path to the local directory where output files should be created. This path is to the directory that you created in Step 1.

    Output File Extension

    Specify the extension to append to output files when the files are created.

    Input File Path

    Specify the platform-specific path to the local directory where input files exist. This path is to the directory that you created in Step 2.

    Input File Extension

    Specify the extension used to designate input files.

    Rename File Extension

    Specify the extension that an input file will be renamed with after the file has been processed. Leave this field blank if you want the file deleted.

    New User Container

    Specify the DN of the container where new users are to be placed.

    Configure Data Flow

    You can configure dataflow to one of the following options:

    • Bidirectional: Delimited Text and an Identity Vault are both authoritative sources of the data synchronized between them.
    • DT-to-eDirectory: Delimited Text is the authoritative source.
    • eDirectory-to-DT: The Identity Vault is the authoritative source.

    Password Failure Notification User

    Optionally, specify an additional user (for example, admin) to receive notification when a user’s password fails.

    Driver Is Local/Remote

    Configure the driver for use with the Remote Loader service by selecting the Remote option, or select Local to configure the driver for local use. If you select Local, you can skip the remaining parameters.

    Remote Host Name and Port

    Specify the host name or IP address and port number for where the Remote Loader service has been installed and is running for this driver. The default port is 8090.

    Driver Password

    The driver object password is used by the Remote Loader to authenticate itself to the Metadirectory server. It must be the same password that is specified as the driver object password on the Identity Manager Remote Loader.

    Remote Password

    The Remote Loader password is used to control access to the Remote Loader instance. It must be the same password that is specified as the Remote Loader password on the Identity Manager Remote Loader.

  7. Click Finish.

NOTE:You can configure and modify the driver's other parameters. For more information, refer to Configuring Driver Parameters.

Importing the Sample Configuration File: Designer

You can import the basic driver configuration file for JDBC by using Designer for Identity Manager. This basic file creates and configures the objects and policies needed to make the driver work properly.

The following procedure explains one of several ways to import the sample configuration file:

  1. Open a project in Designer.

  2. In the modeler, right-click the Driver Set object, then select Add Connected Application.

  3. From the drop-down list, select DelimitedTextCSVSample.xml, then click Run.

  4. Click Yes, in the Perform Prompt Validation window.

  5. Configure the driver by filling in the fields.

    Specify information specific to your environment. For information on the settings, see the table of information in Step 6.

  6. After specifying parameters, click OK to import the driver.

  7. Customize and test the driver.

  8. Deploy the driver into the Identity Vault.

    See Deploying a Driver to an Identity Vault in the Designer for Identity Manager 3: Administration Guide.

2.5.2 Preparing Data Locations

If you use all of the defaults provided by the sample configuration, prepare locations for Identity Manager data.

  1. Add the containers Users\Active at the root level of your Identity Vault.

  2. On Windows, point to or create an input directory and an output directory on your local file system.

    For example, point to the two directories created in Step 1 and Step 2. You can use any two directories on your local file system.

    On Solaris, Linux*, or NetWare, create input and output directories wherever you’d like. Then update the driver configuration with the correct platform-specific paths. For more information, refer to Input File Path.

2.5.3 Starting the Driver

If you changed default data locations during configuration, ensure that the new locations exist before you start the driver.

  1. In iManager, select Identity Manager > Identity Manager Overview.

  2. Locate the driver in its driver set.

  3. Click the driver status indicator in the upper right corner of the driver icon, then click Start driver.

    Synchronization takes place on an object-by-object basis as changes are made to individual objects. If you want to have an immediate synchronization, initiate that process as explained in Migrating and Resynchronizing Data.

2.5.4 Migrating and Resynchronizing Data

Identity Manager synchronizes data as the data changes. If you want to synchronize all data immediately, you can do one of the following:

  • Migrate new data into or from an Identity Vault.
  • Resynchronize existing data by using the driver set Properties page.

The Migrate from eDirectory and Synchronize options usually behave independently of any driver. However, some issues exist with these options and the Identity Manager Driver for Delimited Text.

The following figure illustrates the buttons that select the Migrate from eDirectory and Synchronize options:

The Migrate and Synchronize options

Migrating Data from eDirectory

To find eDirectory entries that do not have an Identity Manager association for the driver, click Migrate from eDirectory. Non-associated entries that are not vetoed by rules processing are written to the output file and receive an association.

NOTE:Entries that already have up-to-date associations aren't written to the output file. To output all associated entries, click Synchronize.

Migrating Data into eDirectory

With most Identity Manager drivers, migrating into eDirectory causes the Metadirectory engine to query the application through its driver. The query finds entries that can be synchronized from the application into eDirectory. These synchronized entries are created in eDirectory. The driver assigns an association value to each new entry.

The Migrate into eDirectory option has no function when used with the Identity Manager Driver for Delimited Text. This driver gets all of its input as files are placed in the input directory. Because the driver is always up-to-date concerning the files it processes, you don't need to do any additional processing or querying. If you do click Migrate into eDirectory, nothing happens because queries are disabled with this driver.

Synchronizing Data

When entries in eDirectory have an association with the selected driver, the Synchronize option causes those entries to synchronize again with the associated entries in the application. If the driver has a Subscriber channel, eDirectory is considered to be the authoritative source for the attributes in the Subscriber filter.

The Identity Manager Driver for Delimited Text can't query the application directly to determine what is out of sync. Therefore, the Metadirectory engine sends a Modify event to the driver for each associated entry. This event causes each of these entries to be written to an output file whenever you click Synchronize. If no Subscriber is configured, Synchronize has no effect with the driver.

To use Migrate from eDirectory, Migrate into eDirectory, or Synchronize:

  1. In iManager, select Identity Manager > Identity Manager Overview.

  2. Locate the driver set containing the Delimited Text driver, then double-click the driver icon.

  3. Click the appropriate migration button.

2.5.5 Activating the Driver

Activate the driver within 90 days of installation. Otherwise, the driver will stop working.

For information on activation, refer to Activating Novell Identity Manager Products in the Identity Manager 3.0.1 Installation Guide.