While you set up the Notes system, have your Notes Administrator work with you.
NOTE: Details about driver architecture and driver/application relationships are discussed in the driver implementation guides. You can find driver implementation guides on the Novell Documentation Web Site.
To prepare a lab workstation to provision resources to Notes users, complete the following sections in the order they are listed:
The DirXML Notes driver must always run on the same computer where the Lotus Notes server and Lotus Notes client are installed. This computer must be running the following software:
Windows NT with Service Pack 5 or Service Pack 6, or Windows 2000 Server, or Windows 2000 Professional.
Lotus Notes R5.0.4 or higher
Collecting Configuration Information
You'll need to provide a number of system-specific details when you install and configure Novell Nsure Resources for Notes. Some of these details can be collected before you complete the following procedures, and others will be defined during the process.
Print and complete the Import Driver Form for Lotus Notes, which mirrors the actual form you will fill out in iManager, or print the following table and record information there.
You will create a user ID for use exclusively by the driver. This user needs Manager access to the public address book and the CERT.LOG file.
IMPORTANT: If the CERT.LOG isn't available on the lab server, you must create it.
You will also create groups that support provisioning policies.
To create Lotus Notes accounts:
Create a Notes User ID of User Type Person with Manager access to the public address book and to the CERT.LOG file. Export the User ID information; the typical location is the c:\LotusNotes\Data directory.
Record the User ID information in the table under Collecting Configuration Information . This information will be required later during driver parameter configuration.
Insert the Novell Nsure Resources CD and copy the Notes Discovery Utility, NOTESIDTOOL.EXE, from /UTILITIES/NOTES_DISC/ to the LOTUS/DOMINO.
Double-click the utility, then enter the DN of the Loop User.
The Loop User DN will be used as the attribute value for the groups' owner and administrator attributes.
Click Generate to create the following three groups:
Employees: Contains user objects that do not have the isManager attribute indicating they are managers.
Managers: Contains user objects that do have the isManager attribute indicating they are managers. An e-mail distribution list is created based on the membership of this group.
Deny Access Group: Contains user objects representing people that have left the company or taken a temporary leave.
Figure 19
Click Paste to File to copy the Association String for each group from the fields in the Notes Discovery Utility to a text file for later use.
The strings are used by the driver to uniquely identify these objects.
You can configure database replication between Lotus Notes and eDirectory through NDSRep. NDSRep is an add-in process that sits on the Lotus Domino* server to facilitate data replication. NDSRep is responsible for sending changes from the address book on the Domino server to the output database.
Use the NDSReg executable to define the parameters used by the NDSRep process.
Copy NDSREP.EXE and NDSREG.EXE from \NT\DIRXML\DRIVERS\LOTUSNOTES\BIN to the LOTUS\DOMINO directory.
Open the \LOTUS\DOMINO directory on the Lotus Notes server and double-click NDSREG.EXE to start the NDSRep Configuration Tool.
Figure 20 NDSRep Configuration Tool
Set the NDSRep parameters as follows:
Option
Description
Automatically reload configuration
Leave it unchecked.
Replication Schedule
Set this for 1 minute.
This determines how often NDSRep checks the input database.
DN Format
The rules created by the Wizard Import file for the driver (NOTESIMPORT.XML) expect Slash.
The default rules require this field to be Slash.
Loop Detection
Make sure this is checked and enter the fully qualified DN of the Notes ID assigned to the driver.
For example, if the driver's ID is Notes Driver and it is certified by the organizational certifier (root certifier) for NotesOrg, then the DN is as follows
CN=Notes Driver/O=NotesOrg
Record this information in the table under Collecting Configuration Information . This information will be required later during driver parameter configuration.
Input Database
Enter NAMES.NSF (if you're using a different target database, enter its name).
Enter this without full path information. This filename must match the Input Database field specified in the driver parameters.
Record this information in the table under Collecting Configuration Information . This information will be required later during driver parameter configuration.
Input DB Is a Notes Directory
Check this option.
This tells the Notes driver the database type.
Output Database
Enter NDSRep.NSF (or if you're using a different database, the name of your output database).
NDSRep creates this database where filtered updates will be accessed by NOTESDRIVERSHIM.
This filename must match the Output Database field specified in the driver parameters.
Record this information in the table under Collecting Configuration Information . This information will be required later during driver parameter configuration.
Publisher Filter
This is the Publisher filter specified for the driver's Publisher channel. This file is created when NotesDriverShim starts. It can be any filename you choose. Include a full path.
Record this information in the table under Collecting Configuration Information . This information will be required later during driver parameter configuration.
Click Save Configuration.
Add NDSRep to the Server Tasks in the NOTES.INI file in the LOTUS\DOMINO directory to automatically load NDSRep on the Domino server. For example,
Installing and Configuring the Remote Loader and Driver
If you are running another DirXML Remote Loader service on this computer, such as the Remote Loader for the Exchange driver, stop that service before starting this procedure. Restart the service after completing this Remote Loader installation.
Insert the Novell Nsure Resources CD and click Next at the Welcome page.
At the License page, click I Accept.
At the Components dialog box, select DirXML Remote Loader Service, then click Next.
Accept the default installation path for the Remote Loader and click Next.
Mark the following items, then click Next.
DirXML Remote Loader Service
DirXML Driver for Notes
Review the Product Summary and click Finish to install the Remote Loader files.
When prompted, create a shortcut.
Run the DirXML Remote Loader Configuration Wizard from your desktop.
At the Welcome page, click Next.
Keep the default Command Port number, then click Next.
Keep the default Configuration File Name, then click Next.
In the DirXML Driver dialog box, mark Java, then click Next.
In the Connection to DirXML dialog box, leave the default Port settings, and ensure that Use SSL is unchecked.
Record the port number in the table under Collecting Configuration Information , then click Next. This information will be required later during driver parameter configuration.
Set Trace Level to 3, so that you'll get minimal tracking data for troubleshooting, specify a location and filename for the trace file, then click Next.
NOTE: If you are running multiple Remote Loader sessions on a single computer, you should create separate trace files.
Mark Install the Remote Loader Instance as a Service, then click Next.
Set Remote Loader and Driver Object passwords.
We recommend keeping remote passwords and driver passwords the same across systems and changing them later when you go to production. Record the passwords in the table under Collecting Configuration Information . This information will be required later during driver parameter configuration.
Review the summary and click Finish.
When prompted, start the service.
Copying the NOTES.JAR File
Copy the NOTES.JAR file from the LOTUS\NOTES directory to the NOVELL\REMOTELOADER\LIB directory.
This will ensure that NOTESDRIVERSHIM is loaded with the correct version of NOTES.JAR for your Notes installation.
The Notes system is prepared to provision resources to employees. Complete preparation of other participating systems and then proceed to Configuring DirXML Drivers .
