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 engine 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 using a nonroot user, use the Java Remote Loader. It can also be used when customizing your environment and installing it on a unsupported platform such as HP-UX*. For more information, see Section 7.3.5, Installing the Java Remote Loader on UNIX, Linux, or AIX.
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. Table 7-1 lists the drivers that are Remote Loader capable.
Table 7-1 Remote Loader Capable Drivers
|
Active Directory |
Avaya PBX |
|
Delimited Text |
GroupWise |
|
JDBC |
JMS |
|
LDAP |
Driver for Linux and UNIX |
|
Lotus Notes |
PeopleSoft 5.2 |
|
Remedy ARS |
SAP HR |
|
SAP User Management |
Scripting |
|
SOAP |
WorkOrder |
|
Manual Task Services |
Null Services |
|
LoopBack |
|
The drivers listed in Table 7-2 are not capable of using the Remote Loader.
Table 7-2 No Remote Loader Capabilities
|
eDirectory |
Entitlements Service |
|
Role Service |
User Application |
The Remote Loader has different programs for the different platforms that allow it to communicate with the Metadirectory engine.
Windows: The Remote Loader Console uses rlconsole.exe to interface with dirxml_remote.exe, which is an executable that enables the Metadirectory engine to communicate with the Identity Manager drivers running on Windows.
Linux/UNIX: rdxml is an executable that enables the Metadirectory engine to communicate with the Identity Manager drivers running in Solaris, Linux, or AIX environments.
To install the Remote Loader:
Verify you have met the system requirements listed in Section 6.0, System Requirements.
Start the installation, using the correct program for your platform.
Windows: IDM3.6.1_Win:windows\setup\idm_install.exe
Linux - GUI Install: IDM3_6_1_Lin/linux/setup/idm_linux.bin [-i gui]
Linux - Command Line Install: IDM3_6_1_Lin/linux/setup/idm_linux.bin -i console
Solaris - GUI Install: IDM3_6_1_Solaris/solaris/setup/idm_solaris.bin [-i gui]
Solaris - Command Line Install: IDM3_6_1_Solaris/solaris/setup/idm_solaris.bin -i console
AIX - GUI Install: IDM3_6_1_AIX/aix/setup/idm_aix.bin [-i gui]
AIX - Command Line Install: IDM3_6_1_AIX/aix/setup/idm_aix.bin -i console
To execute the binary files on Linux\Solaris\AIX, enter ./install.bin [-i {gui | console}].
IMPORTANT:The only supported AIX maintenance level is 5300-09. Newer or older maintenance levels are not supported.
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.2, Installing the Metadirectory Server.
Novell Identity Manager Connected System Server: This option does not require the Identity Vault to be installed on this server. It installs the Remote Loader Service on your application server.
None: Select this option if you want to install the iManager plug-ins or the utilities without installing the Metadirectory server or the connected system server on this server.
Novell Identity Manager Web-based Administration Server: 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.
WARNING:For installing Identity Manager 3.6.1, do not select the Utilities component. The installation does not proceed if you select the Utilities component.
Custom: Select this option if you want to customize the features that are installed. It allows you to select the following options:
Remote Loader Service: The service that communicates with the Metadirectory engine.
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.
Register the Identity Audit System Components for Identity Manager: Select this option if you have Identity Audit or Novell Sentinel installed.
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 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 3.6.1 Remote Loader Guide.
By default 64-bit Remote Loader is installed. To install a 32-bit Remote Loader, do the following:
On Windows:
Browse the 32bit_RL_Install.properties file in the IDM3.6.1_Win:Windows\setup\ folder and set the property values to as follows:
RL_32BIT_INSTALL_ON_64BIT=true
In the command prompt, change the directory path to IDM 3.6.1 installation folder (say, C:\IDM3.6.1\windows\setup) and enter one of the following commands:
idm_install.exe -i gui -f 32bit_RL_Install.properties
idm_install.exe -i console -f 32bit_RL_Install.properties
Follow from Step 3 of Section 7.3.3, Installation Procedure to complete the installation.
On Linux:
Browse the 32bit_RL_Install.properties file in the IDM3_6_1_Lin/linux/setup folder and set the property values to as follows:
RL_32BIT_INSTALL_ON_64BIT=true
In the terminal, change the directory path to IDM 3.6.1 installation folder (say,../linux/setup) and enter one of the following commands:
idm_linux.bin -i gui -f 32bit_RL_Install.properties
idm_linux.bin -i console -f 32bit_RL_Install.properties
Follow from Step 3 of Section 7.3.3, Installation Procedure to complete the installation.
Start the silent installation by using the correct program for your platform:
Linux: IDM3_6_1_Lin/linux/setup/idm_linux.bin -i silent -f <filename>.properties
Solaris: IDM3_6_1_Solaris/solaris/setup/idm_solaris.bin -i silent -f <filename>.properties
AIX: IDM3_6_1_AIX/aix/setup/idm_aix.bin -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.
NOTE:If you have installed iManager, and later you want to install iManager plug-ins, then 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 engine 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 (JRE 1.5.0) and Java Sockets. It is supported on the Linux/UNIX platforms the Identity Manager supports. JRE 1.6.0 update 06 was shipped with Identity Manager 3.6.1.
Verify that the Java 1.5.x JDK*/JRE is available on the host system.
IMPORTANT:For updating your JRE, you must note that JRE 1.6 versions upto update 23 ship with CVE-2010-4476 security vulnerability. This security vulnerability has been addressed in JRE 1.6.0-24 version. You must use the FPUpdater tool that Sun has recently released to update your JRE version to JRE 1.6.0-24 version. The instructions for installing the latest JRE versions are available at the JRE Patch Download Site.
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
The file is located in the same location on the Linux or UNIX ISO images. The files are located in the java_remoteloader folder off the root of the ISO image. 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 drivers, you must manually copy the drivers into the lib directory. The lib directory is under the directory where the untarring occurred.
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 3.6.1 Remote Loader Guide.