Use the following procedure to create a Notes User ID to be used exclusively by the driver, if you are having problems getting accounts created.
Create a Notes User ID to be used exclusively by the driver and give it manager-level ACL access to the target Notes database (usually names.nsf), the output database (ndsrep.nsf) created by ndsrep, and certlog.nsf. If you are synchronizing with the names.nsf database, you should select (turn on) all ACL roles (GroupCreator, GroupModifier, NetCreator, NetModifier, PolicyCreator, PolicyModifier, PolicyReader, ServerCreator, ServerModifier, UserCreator, UserModifier).
If a Deny Access group doesn’t already exist, create this group by using the Lotus Domino Administrator tool. This group is used to hold disabled user accounts.
(Optional) Copy and save the Universal ID (UNID) for the Deny Access group you just created.
This string is used by the driver to uniquely identify this object, and you need to specify it when you are importing the driver configuration.
To get the string:
View the Document Properties of the group. (You can select the object and right-click to select Document Properties.)
Click the Meta tab (the fifth tab from the right).
Go to the end of the text in the Identifier field, and copy the character string from the last forward slash to the end. This is always 32 alphanumeric characters.
For example, if text in the Identifier field is Notes://myserver/87256E530082B5F4/85255E01001356A8852554C200753106/16A28402CCEB7A9C87256E9F007EDA9B then the UNID would be 16A28402CCEB7A9C87256E9F007EDA9B
Paste this information into a file for later use when you run the Create Driver Wizard, as noted in Creating the Driver Object in Designer.
The first time the driver runs, it searches for the Domino server (specified in the driver parameters at import time), and tries to open dsrepcfg.nsf to write the publisher parameters that ndsrep reads. If dsrepcfg.nsf does not exist, the Notes driver shim attempts to create dsrepcfg.nsf using the database template dsrepcfg.ntf that ships with the driver.
If dsrepcfg.nsf is successfully created, and contains data specifying an appropriate update database file (usually named ndsrep.nsf), then you can load ndsrep successfully at the Domino Console.
If dsrepcfg.ntf is not found, or this initial dsrepcfg.nsf creation process fails, then the Publisher channel shuts down, and you can’t load the ndsrep task at the Domino console.
You can use a Notes Client to create the dsrepcfg.nsf database by using the dsrepcfg.ntf template. After doing so, modify the ACL so that the Notes driver user has manager-level access to the database.
If you upgrade the Notes Client after installing the driver, you need to do one of the following:
Check the symbolic links, and re-create them manually if necessary. Use Table 7-1 if your Domino server is V8.x or later running eDirectory 8.8.x.
Table 7-1 Links to Check for Domino V8.x or later with eDirectory 8.8.x
|
File to Link |
Symbolic Link to Create |
|---|---|
|
Notes.jar |
/opt/novell/eDirectory/lib/dirxml/classes/Notes.jar Example: ln -s /opt/ibm/../../jvm/lib/ext/Notes.jar /opt/novell/eDirectory/lib/dirxml/classes/Notes.jar |
|
libnotesdrvjni.so |
/opt/ibm/../notes/libnotesdrvjni.so.1.0.0 Example: cp /opt/novell/eDirectory/lib/dirxml/rules/notes/libnotesdrvjni.so.1.0.0 /opt/ibm/../notes/libnotesdrvjni.so.1.0.0 ln -s /opt/ibm/../notes/libnotesdrvjni.so.1.0.0 /opt/ibm/../notes/libnotesdrvjni.so.1 ln -s /opt/ibm/../notes/libnotesdrvjni.so.1.0.0 /opt/ibm/../notes/libnotesdrvjni.so |
Back up the files listed below, then reinstall the driver. Reinstalling the driver shim re-creates the symbolic links, but it overwrites certain files. If you have made changes to them, you need to make a backup.
Back up the following files:
rdxml.startnotes
rdxml.stopnotes
findDomino
rdxml.confignotes (or wherever your configuration is stored)
After reinstalling the driver shim, copy the backups to their original location.
The sample scripts provided (rdxml.startnotes, rdxml.stopnotes, findDomino) produce a Remote Loader trace log for the driver that can be used for troubleshooting.
If you encounter this issue, follow these steps to resolve it:
Install the Domino Administrator.
Connect to the Domino server.
Start the driver.
To start the driver as a service, configure the Remote Loader with the administrative privileges before running it.
Right-click the Remote Loader shortcut icon.
In the menu that displays, select Run as administrator.
Alternatively, click Ctrl+Shift+Click keys from the keyboard.
To stop or edit the driver service, run the Remote Console utility as an administrator.