Unable to load Remote Loader on 64-bit Linux platform

  • 7002788
  • 20-Mar-2009
  • 10-Jun-2013


Novell Identity Manager 3.6
Novell Identity Manager Driver - Groupwise
Novell Identity Manager Driver - Linux and UNIX Settings
Novell Open Enterprise Server 2 (OES 2) SP1


After installing the Novell Identity Manager (IDM) 3.6 Remote Loader on a 64-bit Open Enterprise Server (OES) 2 SP1 server the command to set the Driver Object and Remote Loader passwords fails as follows:
rdxml -config /etc/opt/novell/dirxml/rdxml/gwconfig.conf -sp novell novell

Loading JVM
rdxml.bin: error: Unable to load JVM
As a result it is impossible to setup any Remote Loader instances on these systems, and it is impossible to run any Remote Loader using native code (non-Java).


The 64-bit Remote Loader is installed with IDM 3.6 on 64-bit platforms including OES 2 SP1 x86_64.  As a result any code that has not yet been ported to the 64-bit architecture cannot be loaded.  The workaround to this is to, once the IDM Remote Loader installation is complete, run the following commands to replace the 64-bit IDM components with the 32-bit equivalents:

These first commands may not be needed depending on your environment:
mv /opt/novell/eDirectory/lib/nds-modules/jre /opt/novell/eDirectory/lib/nds-modules/jre.bak
ln -sf /opt/novell/eDirectory/lib/nds-modules/jre1.6.0_06/ /opt/novell/eDirectory/lib/nds-modules/jre

With the directory backed up mount or extract the IDM 3.6 installation media to /mnt and proceed as follows, changing the paths for your own specific mountpoint:
cd /mnt/linux/setup/packages
ls -1 x86_64/ | sed -r 's/.x86_64.rpm//g' | xargs rpm -e
ls -1 x86_64/ | sed -r 's/.x86_64.rpm/*/g' | xargs rpm -Uvh

These commands remove the packages listed in the x86_64 directory at the path shown and install the 32-bit counterparts.

As a note this is not always required.  Upgrades form OES 2 were originally installed with the 32-bit version of eDirectory and do not have this problem.  If the password files can be created on another system and moved to the Remote Loader machine there should also not be a need to do this for any drivers using Java-only shims (eDirectory, JDBC, LDAP, etc.).

This has been resolved in IDM 3.6.2