The Remote Loader extends the functionality of Identity Manager by allowing the driver to access the connected system without having the Identity Vault and Metadirectory server installed on the same server as the connected system. As part of the planning process, you need to decide if you are going to use the Remote Loader or not. For more information about the planning process, see Section 3.0, Technical Guidelines.
If you want to install the Remote Loader through a non-root user, use the Java Remote Loader. The Java Remote Loader can also be used when you customize your environment and install the Java Remote Loader on a unsupported platform such as HP-UX. For more information, see Section 7.6.5, Installing the Java Remote Loader on UNIX or Linux.
The Remote Loader requires that each driver’s connected system is available and the relevant APIs are provided. Refer to the Identity Manager Driver documentation for operating system and connected system requirements that are specific to each driver.
Not all Identity Manager drivers are supported by the Remote Loader. The following is a list the drivers that have Remote Loader capability.
Active Directory
Avaya PBX
Data Collection Services
Delimited Text
GroupWise (Available only for 32-bit Remote Loader)
JDBC
JMS
LDAP
Driver for Linux and UNIX
LoopBack
Lotus Notes
Managed System Gateway
Manual Task Services
Null Services
PeopleSoft 5.2
Remedy ARS
RACF
SalesForce.com
SAP Business Logic
SAP GRC (CMP only)
SAP HR
SAP Portal
SAP User Management
Scripting
SharePoint
SOAP
WorkOrder
The drivers listed below are not capable of using the Remote Loader.
eDirectory
Entitlements Services
Role Service
User Application
The Remote Loader has different programs for the different platforms, so it can communicate with the Metadirectory server.
Linux/UNIX: rdxml is an executable that enables the Metadirectory server to communicate with the Identity Manager drivers running in Solaris or Linux environments.
Windows: The Remote Loader Console uses rlconsole.exe to interface with dirxml_remote.exe, which is an executable that enables the Metadirectory server to communicate with the Identity Manager drivers running on Windows.
To install the Remote Loader:
Verify you have met the system requirements listed in Section 6.0, System Requirements.
Ensure that you have downloaded the necessary Identity Manager files from the Novell Downloads Web site. For more information, see Section 5.0, Where to Get Identity Manager.
Start the installation, using the correct program for your platform.
Linux - GUI Install: IDM4.0_Lin/products/IDM/install.bin [-i gui]
Linux - Command Line Install: IDM4.0_Lin/products/IDM/install.bin -i console
Solaris - GUI Install: IDM4.0_Solaris/products/IDM/install.bin [-i gui]
Solaris - Command Line Install: IDM4.0_Solaris/products/IDM/install.bin -i console
Windows: IDM4.0_Win:\products\IDM\windows\setup\idm_install.exe
To execute the binary files on Linux or Solaris, enter ./install.bin [-i {gui | console}].
Use the following information provided to complete the installation:
Select Components: Select the connected system server and utilities to install the Remote Loader.
Novell Identity Manager Metadirectory Server: Select this option only if you are installing the Metadirectory server. This option requires the Identity Vault to be installed on this server. For more information, see Section 7.5, Installing the Metadirectory Server.
Novell Identity Manager Connected System Server 32-bit: This option does not require the Identity Vault to be installed on this server. It installs the 32-bit version of the Remote Loader Service on your application server.
Novell Identity Manager Connected System Server 64-bit: This option does not require the Identity Vault to be installed on this server. It installs the 64-bit version of the Remote Loader Service on your application server.
Novell Identity Manager Connected System Server (.NET): This option (Windows only) installs the .NET Remote Loader service and the SharePoint driver on this server.
Novell Identity Manager Plug-ins for Identity Manager: Select this option if you have iManager installed on this server. It installs the iManager plug-ins for Identity Manager.
Utilities: Installs utilities used to help configure the drivers for the connected systems. Not all drivers have utilities. If you are not sure if you need this, select it. It does not use much disk space.
Custom: Select this option if you want to customize the features that are installed. It allows you to select the options listed below. Before you select this option, you should select the components to install:
Remote Loader Service 32-bit: The service that communicates with the Metadirectory server.
Remote Loader Service 64-bit: The service that communicates with the Metadirectory server.
Drivers: Select which driver files to install. You should install all of the driver files. If you need to add another Remote Loader instance, you do not need to run the installation again.
Novell Identity Manager Connected System Server (.NET): (Windows Only) Installs the .NET Remote Loader service and the SharePoint driver.
Other options must be select when you select the customize for the installation to proceed.
(Windows Only) Install Location for Connected System Server: Specify the directory where the Connected System Server is installed.
(Windows Only) Install Location for .NET Remote Loader: Specify the directory where the .NET Remote Loader is installed.
(Windows Only) Install Location for Utilities: Specify the directory where the utilities are installed.
Create and configure your driver objects to use the Remote Loader. This information is contained in each driver guide. For more information, see the Identity Manager Drivers documentation.
Create a Remote Loader configuration file to work with your connected system. For more information, see Configuring the Remote Loader for Linux/UNIX by Creating a Configuration File
in the Identity Manager 4.0 Remote Loader Guide.
In order to run a silent installation of the Remote Loader you must create a properties file with the parameters required to complete the installation. There is a sample file included on the Identity Manager media:
Linux: IDM4.0_Lin/products/IDM/linux/setup/silent.properties
Solaris: IDM4.0_Solaris/products/IDM/solaris/setup/silent.properties
Windows: IDM4.0_Win:\products\IDM\windows\setup\silent.properties
Start the silent installation by using the correct program for your platform:
Linux: IDM4.0_Lin/products/IDM/install.bin -i silent -f <filename>.properties
Solaris: IDM4.0_Solaris/products/IDM/install.bin -i silent -f <filename>.properties
Windows: IDM4.0_Win:\products\IDM\windows\setup\idm_install.exe -i silent -f <filename>.properties
Create a property file <filename>.properties with the following attributes, in the location from where you run the Identity Manger installer:
For default installed locations, see /tmp/idmInstall.log.
If you have installed iManager, and you later want to install iManager plug-ins, you must set the WEB_ADMIN_SELECTED value to true.
dirxml_jremote is a pure Java Remote Loader. It is used to exchange data between the Metadirectory server running on one server and the Identity Manager drivers running in another location, where rdxml doesn’t run. It should be able to run on any system with a compatible JRE (1.5.0 minimum) and Java Sockets. It is supported on the Linux/UNIX platforms the Identity Manager supports.
Verify that the Java 1.5.x JDK/JRE is available on the host system.
Ensure that you have downloaded the necessary Identity Manager files from the Novell Downloads Web site. For more information, see Section 5.0, Where to Get Identity Manager.
Locate the Java Remote Loader installation files on the Identity Manager media:
Linux: IDM4.0_Lin/products/IDM/java_remoteloader
Solaris: IDM4.0_Solaris/products/IDM/java_remoteloader
Copy the dirxml_jremote_dev.tar.gz file to the desired location on the remote server.
Copy the dirxml_jremote.tar.gz or the dirxml_jremote_mvs.tar file to the desired location on the remote server.
For example: /usr/idm
For information on mvs, untar the dirxml_jremote_mvs.tar file, then refer to the usage.html document.
Unzip and extract the dirxml_jremote.tar.gz file and the dirxml_jremote_dev.tar.gz file.
For example: gunzip dirxml_jremote.tar.gz or tar -xvf dirxml_jremote_dev.tar
Copy the application shim .jar files to the lib subdirectory that was created when the dirxml_jremote.tar file was extracted.
Because the tar file doesn’t contain the .jar files, you must manually copy these .jar files from the Metadirectory server into the lib directory. The lib directory is under the directory where the untarring occurred.
The default installation directory for .jar files on the Metadirectory server is /opt/novell/eDirectory/lib/dirxml/classes.
Customize the dirxml_jremote script by doing either of the following:
Verify that the Java executable is reachable through the PATH environment variable by setting the environment variable RDXML_PATH. Enter the following commands to set the environment variable:
set RDXML_PATH=path
export RDXML_PATH
Edit the dirxml_jremote script and prepend the path to the Java executable on the script line that executes Java.
Configure the sample config8000.txt file for use with your application shim. For more information, see Configuring the Remote Loader for Linux/UNIX by Creating a Configuration File
in the Identity Manager 4.0 Remote Loader Guide.
Identity Manager 4.0 allows coexistence of 32-bit and 64-bit Remote Loader on a 64-bit operating system. If you are upgrading a 32-bit Remote Loader installed on a 64-bit operating system, it upgrades 32-bit Remote Loader and also installs 64-bit Remote Loader. You can have both 32-bit Remote Loader and 64-bit Remote Loader on the same machine.