Installing Remote Loader 141
17
Installing Remote Loader
The Remote Loader uses the following programs to communicate with the server that hosts the Identity Manager engine:
Linux and UNIX: The rdxml executable enables the Identity Manager engine 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 Identity Manager engine server to communicate with the Identity Manager drivers running on Windows.
Section 17.1, “Using the Wizard to Install the Remote Loader,” on page 141
Section 17.2, “Performing a Silent Installation of the Remote Loader,” on page 142
Section 17.3, “Installing Java Remote Loader,” on page 143
17.1 Using the Wizard to Install the Remote Loader
The installation program guides you through the configuration settings for the Remote Loader. You can run the installation in the console or in the GUI. On UNIX and Windows computers, the installation program automatically defaults to wizard mode.
To prepare for the installation, see Section 16.1, “Checklist for Installing the Remote Loader,” on page 133. Also see the Release Notes accompanying the release. To perform an unattended installation, see Section 15.2, “Performing a Silent Installation,” on page 127.
NOTE: Your choice of performing the installation as a root or a non-root user should match the method that you used for installing the Identity Vault.
Linux: /products/IDM/install.bin
Windows: \products\IDM\windows\setup\idm_install.exe To install the Remote Loader as a root or administrative user:
1 Log in as root or administrator on the computer where you want to install the Identity Manager engine.
NOTE: You can install the Java Remote Loader as a non-root user.
2 From the directory that contains the installation files, complete one of the following actions:
Linux (console): Enter ./install.bin -i console
Linux (GUI): Enter ./install.bin
Windows: Run idm_install.exe
3 Accept the license agreement, and then click Next.
4 In the Select Components window, specify the Remote Loader components that you want to install.
For more information about the options, see Section 13.2, “Understanding the Installation Program,” on page 116.
5 (Optional) To select specific drivers for the individual components, complete the following steps:
5a Click Customize the selected components, and then click Next.
5b Expand Drivers under the component that you want to install.
5c Select the drivers that you want to install.
6 Click Next.
7 In the Activation Notice window, click OK. For more information, see Section 50.6, “Activating Identity Manager,” on page 412.
8 For Authentication, specify a user account and its password with sufficient rights in eDirectory to extend the schema. Specify the user name in the LDAP format. For example,
cn=admin,o=company.
9 For Pre-Installation Summary, verify the settings.
10 Click Install.
11 Activate Identity Manager. For more information, see Section 50.6, “Activating Identity Manager,”
on page 412.
12 Configure the Remote Loader to connect with the drivers and Identity Manager. For more information, see Chapter 18, “Configuring the Remote Loader and Drivers,” on page 145.
13 To create and configure your driver objects, consult the specific guide for that driver. For more information, see Identity Manager Drivers documentation website.
14 (Optional) For the default installation locations, see /tmp/idmInstall.log.
17.2 Performing a Silent Installation of the Remote Loader
To run a silent installation of the Remote Loader, create a properties files with the parameters required to complete the installation. The Identity Manager media includes a sample properties file:
Linux: /products/IDM/linux/setup/silent.properties
Windows: \products\IDM\windows\setup\silent.properties To perform a silent installation:
1 In the installation directory, create a properties file or edit the sample silent.properties file.
2 In a text editor, specify the following parameters in the file:
CONNECTED_SYSTEM_SELECTED
Specifies whether you want to install the 32-bit Remote Loader service and drivers. You can install both 32-bit and 64-bit versions on the same server.
X64_CONNECTED_SYSTEM_SELECTED
Specifies whether you want to install the 64-bit Remote Loader service and drivers. You can install both 32-bit and 64-bit versions on the same server.
UTLITIES_SELECTED
Specifies whether you want to install the Utilities and system components for the Remote Loader.
Installing Remote Loader 143 DOT_NET_REMOTELOADER_SELECTED
Specifies whether you want to install the .NET Remote Loader service and drivers on the Windows server.
3 To run the silent installation, issue one of the following commands from the directory for the properties file:
Linux: install.bin -i silent -f filename.properties
Windows: install.exe -i silent -f filename.properties 4 (Optional) For default installed locations, see /tmp/idmInstall.log.
17.3 Installing Java Remote Loader
In general, you install the Java Remote Loader, dirxml_jremote, on computers where the operating system is not compatible with the native Remote Loader. However, the Java Remote Loader can also run on the same servers where you might install the Remote Loader. Identity Manager uses the Java Remote Loader to exchange data between the Identity Manager engine running on one server and the Identity Manager drivers running in another location, where rdxml does not run. You can install dirxml_jremote on any supported UNIX or Linux computer that has a compatible JRE (1.5.0 minimum) and Java Sockets.
1 On the server that hosts the Identity Manager engine, copy the application shim .so or .jar files, located by default in the /opt/novell/eDirectory/lib/dirxml/classes directory.
2 Log in to the computer where you want to install the Java Remote Loader (the target computer).
3 Verify that the target computer has a supported version of JRE.
4 To access the installation program, complete one of the following steps:
4a (Conditional) If you have the .iso image file for the Identity Manager installation package, navigate to the directory containing the Java Remote Loader installation files, located by default in products/IDM/java_remoteloader.
4b (Conditional) If you downloaded the Java Remote Loader installation files from the NetIQ Downloads website, complete the following steps:
4b1 Navigate to the .tgz file for the downloaded image.
4b2 Extract the contents of the file to a folder on the local computer.
5 Copy the dirxml_jremote_dev.tar.gz file to the desired location on the target computer. For example, copy the file to /usr/idm.
6 Copy one of the following files to the desired location on the target computer:
dirxml_jremote.tar.gz
dirxml_jremote_mvs.tar
For information about mvs, untar the dirxml_jremote_mvs.tar file, then refer to the usage.html document.
7 On the target computer, unzip and extract the .tar.gz files.
For example, enter gunzip dirxml_jremote.tar.gz or tar -xvf dirxml_jremote_dev.tar.
8 Place the .so or .jar files for the application shim that you copied in Step 1 in the dirxml/
classes directory under the lib directory.
9 To customize the dirxml_jremote script so the Java executable is reachable through the RDXML_PATH environment variable, complete one of the following steps:
9a Enter one of the following commands to set the environment variable RDXML_PATH:
set RDXML_PATH=path
export RDXML_PATH
9b Edit the dirxml_jremote script and prepend the path to the Java executable on the script line that executes Java.
10 Configure the sample configuration file config8000.txt for use with your application shim.
The sample file is located by default in the /opt/novell/dirxml/doc directory. For more information, see Chapter 18, “Configuring the Remote Loader and Drivers,” on page 145.
18
Configuring the Remote Loader and Drivers 145
18