Configuring Driver Object Properties

  1. In iManager, click DirXML Management > Overview.

  2. Locate the driver set containing the eDirectory driver, then click the driver's icon.

  3. From the DirXML Driver Overview, click the eDirectory driver object, which will display the driver configurations.

  4. Locate the Driver Module option.

  5. Click Java.

  6. Enter the following eDirectoryTM Driver Java class name:

    com.novell.nds.dirxml.driver.nds.DriverShimImpl

  7. Click Authentication.

  8. Enter the following in the Authentication ID field:

  9. (Conditional) Enter a password for the remote Driver object in the Application Password field.

    This step is necessary only if you have chosen to use Driver object passwords for additional security. See Using Driver Object Passwords.

  10. In the Authentication Context field, enter the host name or IP address of the server on the remote tree, a colon, and the decimal port number to use for communicating with the remote driver (for example, 255.255.255.255:2000).

    A separate port can be specified for Subscriber and Publisher channels by specifying a second port number following a second colon. If a second port number is specified, the Publisher channel uses the second port number rather than using the same port number as the Subscriber channel (for example, 255.255.255.255:2000:2001).

    If your server has multiple IP addresses, you can specify the IP address you want the Publisher channel to use. This requires specifying the remote IP address, the Subscriber channel port, the local IP address, and the Publisher channel port. For example. 137.65.134.81:2000:137.65.134.83:2000 specifies that the Subscriber channel will communicate with the remote tree on 137.65.134.81, port 2000, and that the Publisher channel will listen on address 137:65.134.83, port 2000.

    :  If you see "java.net.ConnectException: Connection Refused," this means that there is no port connection on the remote side. This error might be caused by either 1) The driver on the remote side is not running, or 2), the driver is running but is configured to use a different port.

  11. Click Apply, then click OK.