3.1 Configuring the Remote Loader on Windows

You can configure the driver on Windows through a graphical utility called the Remote Loader Console utility or from the command line.

The Remote Loader Console utility enables you to manage all Remote Loader instances for Identity Manager drivers running on the Windows server. The utility is installed during the installation of Identity Manager.

If you are upgrading, the Console detects and imports existing instances of the Remote Loader. (To be automatically imported, driver configurations must be stored in the Remote Loader directory, typically c:\novell\remoteloader.) You can then use the Console to manage the remote drivers.

  1. Double-click the Remote Loader Console icon on the desktop to launch the Remote Loader Console.

    The Remote Loader Console allows you to start, stop, add, remove, and edit each instance of a Remote Loader.

  2. Click Add to add a Remote Loader instance of your driver on this server.

  3. Use the information in the following table to configure the Remote Loader instance for your driver.

    Headings

    Description

    Description

    Specify a description to identify the Remote Loader instance in the Remote Loader Console utility.

    Driver

    Select the Java class name for the driver. If you are using the Active Directory driver, select ADDriver.dll. Table 3-3 contains a list of all of the Java class names for each driver.

    Config File

    Specify the name of the configuration file. The Remote Loader Console places configuration parameters into this text file and uses those parameters when it runs.

    Communications

    • IP Address: Specify the IP address where the Remote Loader listens for connections from the Metadirectory server.

    • Connection Port - Metadirectory Server: Specify the TCP port on which the Remote Loader listens for connections from the Metadirectory server.

      The default TCP/IP port for this connection is 8090. With each new instance you create, the default port number automatically increases by one.

    • Command Port - Local host communication only: Specify the TCP port number where a Remote Loader listens for commands such as Stop and Change Trace Level.

      Each instance of the Remote Loader that runs on a particular computer must have a different command port number. The default command port is 8000. With each new instance you create, the default port number automatically increases by one.

    NOTE:By specifying different connection ports and command ports, you can run multiple instances of the Remote Loader on the same server, hosting different driver instances.

    Remote Loader Password

    Specify the Remote Loader password. This password is used to control access to a Remote Loader instance for a driver. It must be the same case-sensitive password specified in the Enter the Remote Loader Password field on the Identity Manager driver configuration page. It is important that this password be difficult to guess and be different from the driver object password.

    Driver Object Password

    Specify the Driver Object password. The Remote Loader uses this password to authenticate to the Metadirectory server. It must be the same case-sensitive password specified in the Driver Object Password field on the Identity Manager driver configuration page. It is important that this password be difficult to guess and be different from the Remote Loader password.

    Secure Socket Layer (SSL)

    • Use an SSL Connection: You should always select this option. It is used to encrypt the transfer of data between the Remote Loader and the Metadirectory server.

    • Trusted Root File: This is the exported self-signed certificate from the eDirectory™ tree’s Organization Certificate Authority. For more information, see Section 3.5, Creating a Secure Connection.

    Trace File

    • Trace Level: Specify a trace level greater than zero to display a trace window that contains informational messages from both the Remote Loader and the driver.

      The most common setting is trace level 3. If the trace level is set to 0, the trace window is not displayed.

    • Trace File: Specify a trace filename where trace messages are written.

      Each Remote Loader instance running on a particular machine must use a different trace file. Trace messages are written to the trace file only if the trace level is greater than zero.

    • Maximum Disk Space Allowed for all Trace Logs (Mb): Specify the approximate maximum size that the trace file for this instance can occupy on disk.

    NOTE:Use the tracing options only for troubleshooting issues. Having the tracing enabled reduces the performance of the Remote Loader. Do not leave the tracing enabled in production.

    Establish a Remote Loader service for this driver instance

    Select this option if you want the Remote Loader established as a service. When this option is enabled, the operating system automatically starts the Remote Loader when the computer starts.

  4. Specify the advanced configuration parameters. To do so:

    1. Click Advanced to display the Advanced Configuration dialog box.

    2. Modify the following settings as desired.

      Parameter

      Description

      Classpath

      Additional paths for the JVM to search for package (.jar) and class (.class) files. Using this parameter is the same as using the java -classpath command. When entering multiple class paths, separate them with a semicolon (;) for a Windows JVM and a colon (:) for a UNIX/Linux JVM.

      JVM Options

      The options used when starting the JVM instance of the driver.

      Heap size

      The initial and maximum heap size for the JVM instance.

    3. Click OK, to save the advanced configuration information.

  5. Click OK to save the configuration file.

If you need to change any of the parameters:

  1. In the Remote Loader Console, select the Remote Loader instance from the Description column.

  2. Click Stop, type the Remote Loader password, then click OK.

  3. Click Edit, then modify the configuration information. See Step 3 and Step 4 for a description of each parameter.

  4. Click OK to save the changes.