18.1 Starting a Driver Instance in the Remote Loader

You can configure each platform to automatically start a driver instance when the host computer starts. You can also manually start an instance.

18.1.1 Starting Driver Instances on UNIX or Linux

NetIQ provides two ways that you can start a driver instance for the Remote Loader on UNIX or Linux computers:

Starting Driver Instances Automatically on UNIX or Linux

You can configure a driver instance for the Remote Loader to start automatically when the computer starts. Place your configuration file in the /etc/opt/novell/dirxml/rdxml directory.

Using the Command Line to Start Driver Instances on UNIX or Linux

For Linux platforms, the binary component rdxml supports command line functionality for the Remote Loader. This component is located by default in the /usr/bin/ directory.

For more information about the parameters used in this section, see Understanding the Configuration Parameters for the Remote Loader.

  1. Open a command prompt.

  2. To specify the passwords for authenticating the driver instance to the Identity Manager engine, enter one of the following commands:

    • Linux: rdxml -config filename -sp password password

    • UNIX: dirxml_jremote -config config_file -sp password password

  3. To start the driver instance, enter the following command:

    • Linux: rdxml -config filename

    • UNIX: dirxml_jremote -config filename

  4. Log in to iManager, then start the driver.

  5. Confirm that the Remote Loader is working properly.

    • Linux: Use the ps command or a trace file to determine whether the command and connection ports are listening.

    • UNIX: Monitor the Java Remote Loader by using the tail command on the tracefile:

      tail -f trace filename

      If the last line of the log shows the following text, the loader is successfully running and awaiting connection from the Identity Manager remote interface shim:

      TRACE: Remote Loader: Entering listener accept()

    The Remote Loader loads the Identity Manager application shim only when the Remote Loader is in communication with the remote interface shim on the Identity Manager engine server. This means, for example, that the application shim shuts down if the Remote Loader loses communication with the server.

18.1.2 Starting Driver Instances on Windows

NetIQ provides three ways that you can start a driver instance for the Remote Loader on Windows computers:

Starting Driver Instances Automatically on Windows

You can configure a driver instance for the Remote Loader to start automatically when the Windows computer starts.

  1. Open the Remote Loader Console.

    During installation, if you created a shortcut for the Remote Loader 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.

  2. Select a driver instance, then click Edit.

  3. Select Establish a Remote Loader service for this driver instance.

  4. Save your changes, and then close the console.

Using the Console to Start Driver Instances on Windows

  1. Open the Remote Loader Console.

    During installation, if you created a shortcut for the Remote Loader 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.

  2. Select a driver instance, then click Start.

Using the Command Line to Start Driver Instances on Windows

The dirxml_remote.exe file supports command line functionality for the Remote Loader. The executable is located by default in the c:\novell\RemoteLoader directory. For more information about the parameters used in this section, see Understanding the Configuration Parameters for the Remote Loader.

  1. Open a command prompt.

  2. To specify the passwords for authenticating the driver instance for the Remote Loader to the Identity Manager engine, enter the following command:

    dirxml_remote -config filename -setpasswords password password

    For example:

    dirxml_remote -config config.txt -sp Novell4 idmpwd6
  3. To start the driver instance, enter the following command:

    dirxml_remote -config filename

    For example:

    dirxml_remote -config config.txt
  4. Log in to iManager, then start the driver.

  5. Confirm that the Remote Loader is working properly.

    The Remote Loader loads the Identity Manager application shim only when the Remote Loader is in communication with the remote interface shim on the Identity Manager engine server. This means, for example, that the application shim shuts down if the Remote Loader loses communication with the server.

  6. (Conditional) If you did not previously install the Remote Loader as a Win32 service, enter the following command:

    dirxml_remote -config filename -service install

    For example:

    dirxml_remote -config config.txt -service install