Installing Remote Loaders and Drivers

With the Identity Manager engine installed, you are ready to start configuring your Identity Manager environment. The first step in doing this is to make sure that the Remote Loader is installed on any systems that will use it. For both Active Directory and NT domain synchronization, the Identity Manager driver and Remote Loader must be installed on an appropriate Domain Controller. The Domain Controller should have the following characteristics:

• Active Directory Domain Controller running Windows 2000 Server with Support Pack 1 and Internet Explorer 5.5 or later

• NT Domain Primary Domain Controller (PDC) running Windows NT 4 with Service Pack 6a or later

To install Remote Loader and Identity Manager driver on a Windows 2000 server running Active Directory, complete the following steps. For more information on performing the same type of installation on an NT 4 server, see the OES Linux online documentation.

1.	At the Windows 2000 server that will host the driver, insert the Identity Manager Bundle Edition CD-ROM. After a few moments, the Identity Manager Bundle Edition Installation screen will appear. Click Next.
2.	At the License Agreement screen, select the appropriate language to view the license agreement. When you have reviewed the agreement, click I Accept.
3.	If necessary, review the Identity Manager overview pages. Click Next to continue to the next overview page, and then Next again to continue the installation.
4.	At the Components screen, deselect DirXML Server, DirXML Web Components and Utilities. Then select DirXML Connected System, to install the Identity Manager Remote Loader and Drivers, and click Next.
5.	At the Location screen, specify the path to which the Remote Loader will be installed, and click Next. It is usually best to just accept the default path.
6.	At the Select Drivers for Remote Loader Install screen, select the Remote Loader Service and the DirXML Driver for Active Directory, and then click Next.
7.	Review the information on the Installation Summary screen, and click Finish. You may see a warning about LDAP conflicts. If so, click OK to close the message box.
8.	At the Create Shortcut screen, click Yes. This will create a shortcut on your Windows desktop to the DirXML Remote Loader Console.
9.	At the Installation Complete screen, click Close.
10.	Launch the Identity Manager Remote Loader Configuration Wizard using dirxml_remote.exe found in the directory specified in step 5, typically c:\Novell\RemoteLoader. At the Welcome page, click Next.
11.	At the Command Port screen, click Next. This is the port that will be used by this instance of the remote loader to listen for Identity Manager activity. Novell recommends keeping the default port.
12.	At the Configuration File screen, click Next. This is the name and location of the log file that will be used to record Remote Loader configuration options.
13.	At the DirXML Driver screen, select Native and make sure that ADDRIVER.DLL is listed in the drop-down list. Click Next.
14.	At the Connection to Identity Manager screen, provide the required information and click Next. Port Specify the port that Remote Loader will use to listen for the Identity Manager engine. Novell recommends keeping the default port. Address Specify the IP address that Remote Loader will use to communicate with the Identity Manager engine. Use SSL Check the Use SSL box if you want secure communications between the Identity Manager engine and Remote Loader. You will have to provide the self-signed certificate from the Identity Manager server in order to use SSL. For more information on using SSL, see the OES Linux online documentation.
15.	At the Tracing screen, specify the level of tracking data that you want recorded, the location of the trace file, and click Next. You will likely want to set up tracing while installing and configuring your driver. However, when the driver configuration is complete, you will probably want to set the trace level to 0 to prevent the log file from growing to fill your entire hard drive over time. Level 0 No information display or tracking Level 1 General informational messages about processing Level 2 Displays messages from level 1 plus the XML documents that are passed between the engine and driver Level 3 Displays messages from level 2 plus documents sent and received between the Remote Loader and the Identity Manager engine Level 4 Displays messages from level 3 plus information about the connection between the Remote Loader and the Identity Manager engine
16.	At the Install as a Service screen, check Install the Remote Loader Instance as a Service, and click Next. Doing this lets Remote Loader continue to run even after you have logged out of the Windows system.
17.	At the Passwords screen, specify the password you want to set for access to Remote Loader and the Driver object, and click Next.
18.	At the Summary screen, review your configuration settings, and click Finish. When prompted, click Yes to start the Remote Loader service.

With Remote Loader configured, Identity Manager will now be able to synchronize data between your central eDirectory tree and your secondary Active Directory environment. Data is mapped from one directory structure to the other as discussed previously (see Table 10.1).

To view the Remote Loader trace screen, which shows you the communication activities between the two directory environments, or to edit the configuration of your Remote Loader Driver, use the Remote Loader Console (as shown in Figure 10.2). An icon for this utility should have already been created on your desktop during the installation process.

Figure 10.2. Remote Loader Console.

The Remote Loader Console provides access to the complete Remote Loader environment. From this console, you can start and stop driver instances, access trace screens, edit the properties of Remote Loader drivers, and add or delete drivers. When using this utility, keep in mind that some actions are only available if the selected driver is in a particular state, such as running or stopped. For example, to edit a driver's configuration, stop the driver and select the Edit button. This will invoke the Remote Driver Configuration page, as shown in Figure 10.3, where all the parameters entered during the Remote Loader Configuration Wizard process can be modified.

Figure 10.3. Remote Driver Configuration page.

To create additional Remote Loader Drivers, the Add button on the Remote Loader Console can be used. Or, if you prefer, the Remote Loader Configuration Wizard can be manually started and used for the creation of additional drivers.