You can configure each platform to automatically start a driver instance when the host computer starts. You can also manually start an instance.
NetIQ provides two ways that you can start a driver instance for the Remote Loader on UNIX or Linux computers:
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.
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.
Open a command prompt.
To specify the passwords for authenticating the driver instance to the Identity Manager engine, enter one of the following commands:
Linux/UNIX: rdxml -config filename -sp Remote Loader password Driver Object password
Java Remote Loader: dirxml_jremote -config filename -sp Remote Loader password Driver Object password
To start the driver instance, enter the following command:
rdxml -config filename
Log in to iManager, then start the driver.
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 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.
NetIQ provides three ways that you can start a driver instance for the Remote Loader on Windows computers:
You can configure a driver instance for the Remote Loader to start automatically when the Windows computer starts.
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.
Select a driver instance, then click Edit.
Select Establish a Remote Loader service for this driver instance.
Save your changes, and then close the console.
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.
Select a driver instance, then click Start.
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.
Open a command prompt.
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
To start the driver instance, enter the following command:
dirxml_remote -config filename
For example:
dirxml_remote -config config.txt
Log in to iManager, then start the driver.
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.
(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