If you are running the Remote Loader, you need to upgrade the Remote Loader files.
Create a backup of the Remote Loader configuration files. The default location of the files is as follows:
Windows: C:\Novell\RemoteLoader\remoteloadername-config.txt
Linux: Create your own configuration file in the path of rdxml.
Verify that the drivers are stopped. For instructions, see Section 4.11, Stopping the Drivers.
Stop the Remote Loader service or daemon for each driver.
Windows: In the Remote Loader Console, select the Remote Loader instance, then click .
Linux: rdxml -config path_to_configfile -u
Java Remote Loader: dirxml_jremote -config path_to_configfile -u
On Linux, stop the lcache process.
If the Metadirectory server and Remote Loader are on the same server, manually stop the lcache process.
If the Metadirectory server and Remote Loader are not on the same server, the lcache process is automatically stopped by the ndsd process during upgrade.
On Windows and Solaris, kill the lcache process before starting the upgrade.
Run the installation program for the Remote Loader.
The installation process updates the files and binaries to the current version. For more information, see Installing the Remote Loader
in the Identity Manager 4.0.2 Framework Installation Guide.
After the installation finishes, verify that your configuration files contain your environment’s information.
(Conditional) If there is a problem with the configuration file, copy the backup file you created in Step 1. Otherwise, continue with Step 8.
Start the Remote Loader service or daemon for each driver.
Windows: In the Remote Loader Console, select the Remote Loader instance, then click .
Linux: rdxml -config path_to_config_file
Java Remote Loader: dirxml_jremote -config path_to_config_file
NOTE:After upgrading the Remote Loader from 32-bit to 64-bit, the GroupWise driver and the native custom drivers do not work.