Before You Set Up the Driver

• Ensure that you have configured Novell^(R) eDirectory^TM and the DirXML Engine before configuring the DirXML Driver for NIS.
• Ensure that the iManager plug-in for DirXML is installed.
• Users and groups are placed in a specific container in eDirectory. So, ensure that you have the DN or FDN for user and group containers to be synchronized in eDirectory.
• The eDirectory schema for the DirXML Driver for NIS needs to be extended.

Setting Up the Driver

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

2. Do one of the following:

   • Select In an Existing Driver Set, then specify the path where you want the name of the object to be created or use the Object Selector icon to select it.
   • Select In a New Driver Set, then click Next.
     • Specify the name of the driver set.
     • Specify the context for the new driver set or use the Object Selector icon to select it.

3. Click Next.

4. Do one of the following:

   • Click Import a pre-configured driver from the server (.XML file), then select the appropriate .xml file from the drop-down list.
   • Click Import a pre-configured driver from the client (.XML file), then specify or browse to the appropriate .xml file.

   The preconfigured XML files NIS.xml and NIS_en.xlf are available in the /usr/lib/dirxml/rules/nds2nis directory of the machine where the driver is installed. Copy these files to the webapps/nps/DirXML.Drivers directory of the server where iManager is installed.

5. Click Next.

6. Specify the name of the driver.

   If you are updating an existing driver, select a driver from the Existing drivers drop-down list.

7. Select the database in use for your network-wide information storage.

   Select Files for local file-based storage, NIS for map-based storage, or NISPlus for hierarchical, domain-based storage.

8. If you want this driver to use entitlements granted through shared profiles, select Yes from the drop-down list.

9. Select the algorithm that is used to hash the passwords.

   This is the hashing algorithm that is used on the UNIX server for hashing passwords. The default is Crypt.

10. (Conditional) If you selected Files or NIS in Step 8, refer to Driver Settings to set the merge-password option based on your system's current settings.

    The default is No.

11. (Conditional) If you selected NIS in Step 8, specify the path of the directory where the NIS maps are to be found.

    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

12. (Conditional) If you selected NIS in Step 8, specify the path of the directory where files corresponding to the NIS maps are to be found.

    The default path is /etc/.

13. (Optional) Select Yes from the drop-down menu, if you want to create a home directory when the user is created.

    The default is No.

14. (Optional) Select Yes from the drop-down menu, if you want to remove the home directory when the user is deleted.

    The default is No.

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

15. (Optional) Select Yes from the drop-down menu, if you want to allow a duplicate uidNumber for a user or gidNumber for a group.

    The default is No.

16. (Optional) Select Yes from the drop-down menu, if you want the driver to automatically generate user IDs.

    The default is No.

17. Specify the minimum value for generating user IDs.

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

18. Specify the maximum value for generating user IDs.

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

19. Specify the default primary group ID for the user.

    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.

20. Specify the default home directory prefix for the user:

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

21. (Optional) If you want to set a default password for users, select Yes from the drop-down menu.

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

22. (Optional) If you want the driver to generate group IDs, select Yes from the drop-down menu..

    The default is No.

23. Specify the minimum value for generating group IDs.

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

24. Specify the maximum value for generating group IDs.

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

25. Select one of the following for data flow:

    • Bi-directional: Both NIS and eDirectory are authoritative sources of the data synchronized between them.

    • NIS to eDirectory: NIS is the authoritative source.

    • eDirectory to NIS: eDirectory is the authoritative source.

26. Specify the interval (in seconds) for Publisher polling.

    The polling interval is used before changes in the NIS datastores are checked for.

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

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

29. Select the option for configuring the driver:

    • Local: Driver is running locally on a DirXML server.

    • Remote: Driver is running with the Remote Loader Service on a non-DirXML server.

30. (Conditional) If you selected Remote in Step 31, do the following:

    1. Specify the hostname or IP address and the port number of the machine where the Remote Loader Service has been installed and is running for this driver.

       The default port is 8090.

    2. Specify the driver password.

       The Driver Object Password is used by the Remote Loader to authenticate itself to the DirXML server. It must be the same as specified for the Driver Object Password on the DirXML Remote Loader.

    3. Specify the password to control access to the Remote Loader instance.

       This password must be the same as specified for the Remote Loader password on the DirXML Remote Loader.

31. Click Next.

32. Click Define Security Equivalences.

33. To add the name of the object (such as Admin) whose privileges are granted to the driver, then click Add > OK.

34. (Optional) Click Exclude Administrative Roles and specify the objects to be excluded from synchronization.

35. Click Next.

36. To view the overview of the newly created driver, click Finish with Overview.

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 Administration guide.

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

• Automatic: Any time the DirXML engine is started the driver is started automatically. After you have the driver configured, you should use this option.

• Manual: The driver can be started manually. This option is often used during driver modification and testing cycles. The engine will buffer the changes to be processed when driver is started.

• Disabled: If the driver is disabled, data changes made in eDirectory during the time a driver is disabled will be automatically synchronized upon driver startup.

To configure the driver startup:

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.

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