In iManager:
In iManager, click to display the Identity Manager Administration page.
Open the driver set that contains the driver whose properties you want to edit. To do so:
In the
list, click .If the driver set is not listed on the
tab, use the field to search for and display the driver set.Click the driver set to open the Driver Set Overview page.
Locate the Delimited Text driver icon, then click the upper right corner of the driver icon to display the
menu.Click
to display the driver’s properties page.In Designer:
Open a project in the Modeler.
Right-click the driver icon or line, then select click
The Driver Configuration options are divided into the following sections:
The Driver Module section lets you change the driver from running locally to running remotely or the reverse.
The Authentication section stores the information required to authenticate to the connected system.
The Startup Option section enables you to set the driver state when the Identity Manager server is started.
The Driver Parameters section lets you configure the driver-specific parameters. When you change driver parameters, you tune driver behavior to align with your network environment. For example, you might find the default Publisher polling interval to be shorter than your synchronization requires. Making the interval longer could improve network performance while still maintaining appropriate synchronization.
Parameter |
Description |
---|---|
|
Displays or specifies the server name or IP address of the server whose driver parameters you want to modify. |
|
Opens an editor so that you can edit the driver’s configuration file. |
Driver Options |
|
|
Specifies the character that is used to delimit field values in the input files. It must be one character. The default is a comma. If the values of any of the input fields contain this character, enclose the entire value in quotes to prevent it from being seen as a delimiter. Changing this delimiter parameter to something other than a comma does not automatically change the delimiter character used in the output files when a Subscriber is used. To change the delimiter character in the output files, edit the Output Transform style sheet. The delimiter character is assigned to a variable near the top of that style sheet. |
|
Specifies a comma-separated list of attribute names that can be referred to in the Schema Mapping rule. In the input files, the fields of the records must correspond to the order and positioning of the names in this list. For example, if you list eight field names in this parameter, each record of the input files should have eight fields separated by the field delimiter character. On Windows*, see sample.csv in the delimitedtext/samples directory for an example. On Solaris* and Linux*, sample.csv is located in the /usr/lib/dirxml/rules/delim directory. The default values are LastName, FirstName, Title, Email, WorkPhone, Fax, WirelessPhone, and Description. |
|
Specifies the Novell® eDirectory™ class name that should be used when creating new objects to correspond to input files. |
|
Prevents you from inadvertently creating a situation in which the driver writes output files that are immediately read in again as input of the same driver. The default is . By default, the driver won't load if all the following conditions occur:
If you want to feed the output of the Subscriber channel into the input of the Subscriber channel as a way to detect Identity Vault events to trigger other changes in the Identity Vault, set this parameter to . For example, to update the Full Name attribute when the Given Name, Surname, or Initials attributes are updated, set this parameter to . |
Subscriber Options |
|
|
Specifies the directory on the local file system where output files will be created. An error occurs if this directory doesn’t exist. The default values are: Windows: c:\csvsample\output Solaris or Linux: /csvsample/output |
|
Output files have a unique name that ends with the characters in the parameter. If the output files from a Subscriber channel are used as input files for the Publisher channel of another Delimited Text driver, the destination file extension must match the source file extension parameter of the second driver. |
|
When this parameter contains no value, the default Java character encoding for your locale is used. To use an encoding other than the default for your locale, enter one of the canonical names from the Supported Encodings table. The Publisher and Subscriber channels can use different character encodings. |
|
Specifies the maximum number of transactions that are written to a single output file. When the file transaction limit is reached, the file closes, and a new file is created for subsequent transactions. To limit the number of transactions that can be written to a single file, leave this parameter blank or set it to zero. For more information, see the next item, . |
|
If no new transactions have been written to the output file in the amount of time specified in this parameter, the file is closed. When new transactions need to be written, a new output file is created. If you don’t want to limit the time that can pass before the output file is closed, leave this parameter blank or set it to zero. |
|
If a value is supplied for this parameter, the current output file is closed at the specified time each day. Subsequent transactions are written to a new file. This parameter does not prevent the or the parameters from also acting as output file thresholds. If you use this parameter and only want one file per day, set the other two parameters to zero.The format of this parameter can be HH:MM:SS (using the 24-hour clock) or H:MM:SS AM/PM. An hour is required, but the minutes and seconds are optional. Because the parameter assumes local time, any time zone information included in the value is ignored. The previous three parameters ( , , and ) are all capable of acting as a threshold for the transaction size a file is able to grow to, or for the time that it remains open to accept new transactions.As long as an output file is still open for writing by the Delimited Text driver, it shouldn’t be considered as finalized. Avoid opening the file in any other process until the driver closes the file. For this reason, one of the three previous parameters must be set to assure that output files don’t remain open indefinitely. To avoid this condition, if the driver detects that all three parameters are blank (or zero), it automatically sets the Maximum Number of Transactions per Output File to the value of 1. |
Publisher Options |
|
|
The Publisher channel looks for new input files in the Input File Path, which is a directory on the local file system. Example paths:
|
|
The extension used to designate input files (for example, csv). |
|
When this parameter contains no value, the default Java character encoding for your locale is used. To use an encoding other than the default for your locale, enter one of the canonical names from the Supported Encodings table. If the Input File Extension parameter is .xml, the Source File Character Encoding can be indicated in one of two ways.
|
|
The Publisher channel uses only files that have the extension specified in the parameter. After the files have been processed, the value of the parameter is appended to the filename, so the Publisher channel won’t try to process the same file again. If the value of the Rename File Extension parameter is left blank, the source file is deleted after it is processed.IMPORTANT: If you change the default, use only characters that are valid in filenames on your platform. Invalid characters cause the rename to fail and the driver to reprocess the same file repeatedly. |
|
When the Publisher channel has finished processing all source files, it waits the number of seconds specified in this parameter before checking for new source files to process. |
Enables you to add ECMAScript resource files. The resources extend the driver’s functionality when Identity Manager starts the driver.