6.1 Planning to Install the Remote Loader

This section provides information that helps you prepare for installing .NET Remote Loader.

6.1.1 Checklist for Installing the Remote Loader

NetIQ recommends that you complete the steps in the following checklist:

Checklist Items

  1. Review the planning information. For more information, see Section I, Planning to Install Identity Manager.

  1. Review the hardware and software requirements for the computers that will host the Remote Loader. For more information, see Meeting System Requirements and Prerequisites and Considerations for Installing the Remote Loader.

  1. Ensure that the Identity Manager engine has been installed. For more information, see Section 5.0, Installing the Engine, Drivers, and iManager Plug-ins

  1. (Conditional) To install the Remote Loader on a server that does not host the Identity Manager engine, ensure that you can establish a secure connection to the engine. For more information, see Creating a Secure Connection to the Identity Manager Engine in the NetIQ Identity Manager Driver Administration Guide.

  1. Decide whether you want to install a 32-bit or 64-bit version of the Remote Loader. For more information, see Using 32-bit and 64-bit Remote Loader on the Same Computer.

  1. Install the Remote Loader:

  1. (Conditional) To install the .NET Remote Loader, see Installing .NET Remote Loader.

  1. To configure a driver instance in the Remote Loader, see one or all of the following sections in the NetIQ Identity Manager Driver Administration Guide:

    NOTE:NetIQ Identity Manager Driver Administration Guide provides detailed instructions about configuring the Remote Loader with drivers. You must refer to this guide for such instructions.

  1. Install the rest of the Identity Manager components, including the identity applications and Identity Reporting.

6.1.2 Understanding the Installation Program

As a convenience, this installation program bundles several of the components that provide the underlying framework for your Identity Manager solution. You can choose to install all components on the same server or on individual servers. In addition to the Remote Loader, you can select the drivers that you want to install on the connected system. The installation kit provides .NET Remote Loader option for Windows operating systems.

6.1.3 Using 32-bit and 64-bit Remote Loader on the Same Computer

By default, the installation program detects the version of the operating system then installs the corresponding version of the Remote Loader. You can install both the 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, the process upgrades the 32-bit Remote Loader to the latest version and also installs the 64-bit Remote Loader.

  • If you choose to have both a 32-bit and a 64-bit Remote Loader on the same computer, the audit events are generated only with the 64-bit Remote Loader. If a 64-bit Remote Loader is installed before installing a 32-bit Remote Loader, the events are logged to the 32-bit cache.

6.1.4 Prerequisites and Considerations for Installing the Remote Loader

Before installing the Remote Loader, NetIQ recommends that you review the following considerations:

  • Install the Remote Loader on a server that can communicate with the managed systems. The driver for each managed system must be available with the relevant APIs.

  • You can install the Remote Loader on the same computer where you installed the Identity Manager engine.

  • You can install both 32-bit and 64-bit Remote Loader on the same computer.

  • You can install Java Remote Loader on platforms that do not support the native Remote Loader.

  • (Conditional) To connect Identity Manager to Active Directory, you must install Remote Loader and the driver for Active Directory on a server that is a member server or a domain controller. You do not need to install eDirectory and Identity Manager on the same server as the connected system. The Remote Loader sends all of the events from Active Directory to the Identity Manager server. The Remote Loader then receives any information from the Identity Manager server and passes that to the connected application.

For more information about the Identity Manager Remote Loader, see Deciding Whether to Use the Remote Loader in NetIQ Identity Manager Driver Administration Guide.