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 13.2.1, 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 Stop.
Linux: rdxml -config path_to_configfile -u
Java Remote Loader: dirxml_jremote -config path_to_configfile -u
(Conditional) To install .NET Remote Loader, kill the lcache process on the Windows server.
(Conditional) To run a silent installation on a Windows server, ensure that the silent.properties file includes the path to the directory that contains the installed Remote Loader files. For example:
X64_CONNECTED_SYSTEM_LOCATION=c:\novell\remoteloader\64bit
The installation program does not detect the default path for the previous installation.
Run the installation program for the Remote Loader.
The installation process updates the files and binaries to the current version. For more information, see Section IV, Installing the Identity Manager Engine, Drivers, and Plug-ins.
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 that you created in Step 1. Otherwise, continue with Step 9.
Start the Remote Loader service or daemon for each driver.
Java Remote Loader: dirxml_jremote -config path_to_config_file
Linux: rdxml -config path_to_config_file
Windows: In the Remote Loader Console, select the Remote Loader instance, then click Start.
NOTE:After upgrading the Remote Loader from 32-bit to 64-bit, the GroupWise driver and the native custom drivers do not work.