The Remote Loader can host the Identity Manager application shims contained in .dll, .so, or .jar files. For the Remote Loader to run, the application needs a configuration file, such as LDAPShim.txt. The Remote Loader Console utility (the Console) helps you manage all instances of Identity Manager drivers running on the Windows server. You can start, stop, add, remove, and edit each instance of a Remote Loader. The installation program for the Remote Loader also installs the Console.
If you are upgrading, the Console detects and imports existing driver instances. For a driver to be automatically imported, its configuration file must be stored in the Remote Loader directory, located by default at c:\novell\remoteloader. You can then use the Console to manage the remote drivers.
You can use the command line or the Remote Loader Console to configure the Remote Loader to recognize a driver on Windows. For more information about using the command line, see Section 17.2, Understanding the Configuration Parameters for the Remote Loader.
This section provides instructions for the following activities:
Open the Remote Loader Console.
NOTE:During installation, if you selected to create a shortcut for the Console, use the Identity Manager Remote Loader Console icon on the desktop. Otherwise, run the rlconsole.exe located by default in C:\novell\remoteloader\nnbit.
To add an instance of your driver on this server, click Add.
For Description, provide a short name to represent the instance.
The Console uses this information in the default value for Config File.
For Driver, select the Java class name.
NOTE:To use the Active Directory driver, select ADDriver.dll. For more information about the class names for each driver, see Understanding the Names for the Java -class Parameter.
For Config File, specify the path to the file where Remote Loader stores its configuration parameters. The default value is C:\novell\remoteloader\nnbit\Description-config.txt.
Specify passwords for the Remote Loader and driver object.
(Optional) To use a TLS/SSL connection between the Remote Loader and the Identity Manager engine server, complete the following steps:
Select Use an SSL Connection.
NOTE:NetIQ recommends using the same version of SSL on both the Identity Manager engine server and the Remote Loader. If the versions of SSL on the server and the Remote Loader do not match, the server returns a “SSL3_GET_RECORD:wrong version number” error message. This message is only a warning, and communication between the server and Remote Loader is not interrupted. However, the error might cause confusion.
For Trusted Root File (base64 format file), specify the exported self-signed certificate from the eDirectory tree’s Organization Certificate Authority. For more information, see Section 17.1, Creating a Secure Connection to the Identity Manager Engine and Section 17.2, Understanding the Configuration Parameters for the Remote Loader.
(Optional) To configure the trace file for the Remote Loader, complete the following steps:
NOTE:NetIQ recommends using the trace functionality only for troubleshooting issues. Having the trace enabled reduces the performance of the Remote Loader. Do not leave the trace enabled in production.
For Trace Level, specify a value greater than zero that defines the level of informational messages from both the Remote Loader and the driver that you want display in a trace window. Values 1 to 4 are pre-defined by the Console. To create your own message types, specify a value of 5 or higher.
The most common setting is trace level 3, which provides general processing, XML documents, and Remote Loader messages.
For Trace File, specify the path to a file where trace messages are logged. For example, C:\novell\remoteloader\64bit\Test-Delimited-Trace.log.
You must specify a unique trace file for each driver instance running on a particular computer. Trace messages are written to the trace file only if the trace level is greater than zero.
For Maximum Disk Space Allowed for all Trace Logs (Mb), specify an approximate value for the most disk space that the trace file for this instance can occupy.
(Optional) To allow the Remote Loader to start automatically when the computer starts, select Establish Remote Loader Service for this driver instance.
NOTE:If the SSL connection fails due to handshaketimeout when Remote Loader establishes connection with Identity Manager engine then, update the default handshaketimeout variable to 10000 and restart both driver and remote loader.
(Conditional) To modify the parameters for Java configuration, complete the following steps:
Select Advanced.
For Classpath, specify the paths for the JVM to search for package (.jar) and class (.class) files. To specify multiple paths, separate the paths with a colon for UNIX or Linux JVM and a semicolon for Windows JVM.
This parameter functions the same as the java -classpath command.
For JVM Options, specify the options that you want to use when starting the JVM instance of the driver.
Specify the initial and maximum heap size for the JVM instance in MB.
Click OK.
Click OK.
In the Remote Loader Console, select the driver instance from the Description column.
Click Stop.
Enter the password for the Remote Loader, then click OK.
Click Edit.
Modify the configuration information. For more information about each parameter, see Creating a New Driver Instance in the Remote Loader on Windows.
To save the changes, click OK.