Setting Up the Driver

This section explains:


Before You Set Up the Driver


Setting Up the Driver Using ConsoleOne

  1. In ConsoleOne®, log in to the desired tree.

  2. Click Wizards > Create a New Application Driver.

  3. Select In an Existing Driver Set, then continue with Step 4.

    or

    Select In a New Driver Set, then skip to Step 5.

  4. If you selected In an Existing Driver Set in Step 3:

    1. Browse the tree to select the path where you want the name of the object to be created.

    2. Click Next, then skip to Step 6.

  5. If you selected In a New Driver Set in Step 3:

    1. Click Next.

    2. Enter the name of the driver set.

    3. Browse to select the context for the new driver set.

    4. Browse to select the Server object to be used for the new driver set.

    5. Ensure that Create a New Partition on This Driver Set is enabled.

    6. Click Next.

  6. If you want to use a preconfigured driver, select the Import a Preconfigured Driver (.XML file) for setting up the driver.

    The preconfigured xml files are: NISFiles.xml for Files, NISYP.xml for NIS, and NISPlus.xml for NIS+ that can be found in /usr/lib/dirxml/rules/nds2nis directory. Copy the appropriate preconfigured XML files to the system where ConsoleOne is running.

  7. Click Next.

    Follow the prompts to configure the driver parameters.

  8. Enter the name of the driver.

  9. Select Yes from the drop-down menu if you want to merge the Password and Shadow information.

    The default is No.

    Ensure that you set the merge-password option based on your system's current settings. For information on recommended values, refer to Driver Settings.

  10. Enter the path of the directory where the NIS map files are to be stored.

    Typically, this is /var/yp/domain name. Run the domainname command to get the domain name.

    The default path is /var/yp/org.domain.com

    NOTE:   This option is for NIS(YP) only.

  11. Select Yes from the drop-down menu if you want to create a home directory when user is created.

    The default is No.

  12. Select Yes from the drop-down menu if you want to remove the home directory when user is deleted.

    The default is No.

    NOTE:  If this option is set to Yes, the user's home directory and its contents will be completely deleted and cannot be recovered.

  13. Select Yes from the drop-down menu if you want to allow duplicate uidNumbers for user or gidNumber for group.

    The default is No.

  14. Select Yes from the drop-down menu if you want the driver to generate User IDs.

    The default is No.

  15. Enter the minimum value for generating user IDs.

    ID generation will use this value as the first user ID. The default is 500.

  16. Enter the maximum value for generating user IDs.

    ID generation will use this value as the last user ID. The default is 60000.

  17. Enter the default primary group ID for user.

    The default is 500.

    Ensure that the corresponding group exists and is synchronized through this driver. You can create this group after the driver is configured and the group is synchronized.

  18. Enter the default home directory prefix for the user:

    The default is /home.

    The home directory is set as the user's common name prefixed with the string that is provided.

  19. Select Yes from the drop-down menu if you want to set default password for users.

    The default is No.

    The password is set to the users' common name.

  20. Select Yes from the drop-down menu if you want the driver to generate Group IDs.

    The default is No.

  21. Enter the minimum value for generating group IDs.

    ID generation will use this value as the first group ID. The default is 500.

  22. Enter the maximum value for generating group IDs.

    ID generation will use this value as the last group ID.The default is 60000.

  23. Select Yes from the drop-down menu if you want to disable the Publisher channel.

    Specifying Yes disables the Publisher channel and No enables the Publisher channel.

    The default is No.

  24. Enter the interval in seconds for Publisher polling.

    The polling interval is used before checking new source files to process.

    The default is 60 seconds.

  25. Enter in dot format or browse to select the DN of the container from or to where users should be synchronized to the application.

  26. Enter in dot format or browse to select the DN of the container from or to where groups should be synchronized to the application.

  27. Click OK.

  28. Click Yes to define security equivalences.

  29. Click Add to add the name of the object whose privileges are granted to the driver, then click OK. (e.g. admin)

  30. Specify the objects to be excluded from synchronization.

  31. Click Finish.


Setting Up the Driver Using iManager

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

  2. Select In an Existing Driver Set, then continue with Step 3.

    or

    Select In a New Driver Set, then skip to Step 4.

  3. If you selected In an Existing Driver Set in Step 3:

    1. Enter or browse the Object Selector icon to select the path where you want the name of the object to be created.

    2. Click Next, then skip to Step 6.

  4. If you selected In a New Driver Set in Step 3:

    1. Click Next.

    2. Enter the name of the driver set.

    3. Enter or browse the Object Selector icon to select the context for the new driver set.

    4. Enter or browse to select the Server object to be used for the new driver set.

    5. Ensure that Create a New Partition on This Driver Set is checked.

    6. Click Next.

  5. If you selected In a New Driver Set in Step 3:

    1. Click Next.

    2. Enter the name of the driver set.

    3. Browse to select the context for the new driver set.

    4. Browse to select the Server object to be used for the new driver set.

    5. Ensure that Create a New Partition on This Driver Set is enabled.

    6. Click Next.

  6. Do one of the following:

    • Click Import a pre-configured driver from the server (.XML file), then choose the appropriate .xml file from the dropdown list.
    • Click Import a Preconfigured Driver from the Client (.XML file), then enter or browse for the appropriate .xml file.

    The preconfigured xml files are: NISFiles.xml for Files, NISYP.xml for NIS, and NISPlus.xml for NIS+ that can be found in /usr/lib/dirxml/rules/nds2nis directory. Copy the appropriate pre-configured XML files to webapps/WEB-INF/classes/templates/browser/DirXML.Drivers directory of the Tomcat server where iManager is installed.

  7. Click Next.

    Follow the prompts to configure the driver parameters.

  8. Enter the name of the driver.

  9. Select Yes from the drop-down menu if you want to merge the Password and Shadow information.

    The default is No.

    Ensure that you set the merge-password option based on your system's current settings. For information on recommended values, refer Driver Settings.

  10. Enter the path of the directory where the NIS map files are to be stored.

    Typically, this is /var/yp/domain name. Run the domainname command to get the domain name.

    The default path is /var/yp/org.domain.com

    NOTE:   This option is for NIS(YP) only.

  11. Select Yes from the drop-down menu if you want to create a home directory when user is created.

    The default is No.

  12. Select Yes from the drop-down menu if you want to remove the home directory when user is deleted.

    The default is No.

    NOTE:  If this option is set to Yes, the user's home directory and its contents will be completely deleted and cannot be recovered.

  13. Select Yes from the drop-down menu if you want to allow duplicate uidNumber for user or gidNumber for group.

    The default is No.

  14. Select Yes from the drop-down menu if you want the driver to generate user IDs.

    The default is No.

  15. Enter the minimum value for generating user IDs.

    ID generation will use this value as the first user ID. The default is 500.

  16. Enter the maximum value for generating user IDs.

    ID generation will use this value as the last user ID. The default is 60000.

  17. Enter the default primary group ID for the user.

    The default is 500.

    Ensure that the corresponding group exists and is synchronized through this driver. You can create this group after the driver is configured and the group is synchronized.

  18. Enter the default home directory prefix for the user:

    The default is /home.

    The home directory is set as the user's common name prefixed with the string that is provided.

  19. Select Yes from the drop-down menu if you want to set a default password for users.

    The default is No.

    The password is set to the user's common name.

  20. Select Yes from the drop-down menu if you want the driver to generate group IDs.

    The default is No.

  21. Enter the minimum value for generating group IDs. ID generation will use this value as the first group id.

    The default is 500.

  22. Enter the maximum value for generating group IDs.

    ID generation will use this value as the last group ID. The default is 60000.

  23. Select Yes from the drop-down menu if you want to disable the Publisher channel.

    Specifying Yes disables the Publisher channel and No enables the Publisher channel.

    The default is No.

  24. Enter the interval in seconds for Publisher polling.

    The polling interval is used before checking new source files to process.

    The default is 60 seconds.

  25. Enter in dot format or browse to select the DN of the container from or to where users should be synchronized to the application.

  26. Enter in dot format or browse to select the DN of the container from or to where groups should be synchronized to the application.

  27. Click Next.

  28. Click Define Security Equivalences.

  29. Click Add to add the name of the object whose privileges are granted to the driver, then click OK. (e.g. admin)

  30. Specify the objects to be excluded from synchronization.

  31. Click Finish.


Configuring Driver Startup

The driver can be started using any of the startup options provided. However, if eDirectory is not installed on the application platform, you must use the Remote Loader to start it. For more information, refer to the DirXML 1.1a Administration Guide.

You can set driver startup to any of the following three options:

To configure the driver startup using ConsoleOne:

  1. Right-click the Driver object > select Properties.

  2. Click Startup Option > select either Manual, Automatic, or Disabled, then click OK.

    If the driver must be run through a Remote Loader setup, continue with Step 2a. Otherwise, skip to Step 3.

    1. Click Driver Module, then select Connect to Remote Loader.

    2. Click Driver Object Password, enter the driver password, then re-enter the driver password.

    3. Click Authentication, enter the Remote Loader password in the Application Password Section, then re-enter the Remote Loader password.

    4. In the Remote Loader connection parameters, enter the IP address or resolvable host name and the connection port of the machine running the Remote Loader in the following format:

      hostname=<IP address> port=<port number>

      Click OK.

  3. Right-click the Driver-Set object > select Properties.

  4. Click DirXML-Drivers.

  5. Select the Driver, then click Start.

To configure the driver startup using iManager:

  1. In iManager, select DirXML Management > Overview.

  2. Select the driver set containing the driver, click the driver icon to see the driver overview, then click the driver icon again to get the Modify Object page.

  3. Click Driver Configuration at the top of the page, then select one of the three options listed under Startup Option.

  4. Click OK.

NOTE:  The DirXML Driver for NIS can be run only on the application platform, which is the machine with the Files, NIS, or NIS+ databases.



  Previous Page: Configuring the DirXML Driver for NIS  Next Page: Configuring the Remote Loader