4.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. For more information about server requirements, see the Planning to Install the Engine, Drivers, and Plug-ins for each component, the guide for the individual driver, and the latest Release Notes.

The installation program provides the following options for component installation:

Identity Manager Server

Installs the Identity Manager engine, schema, drivers, and audit components.

Connected System Server (32-bit, 64-bit, .NET)

Installs the Remote Loader service and the driver instances in the loader. The Remote Loader allows you to run Identity Manager drivers on connected systems that do not host the Identity Vault and Identity Manager engine. In the installation program, you can select the drivers that you want to install with the Remote Loader on the connected system

Fanout Agent

Installs the Fan-Out agent for the JDBC Fan-Out driver. The JDBC Fan-Out driver uses the Fan-Out agent to create multiple JDBC Fan-Out driver instances. The Fan-Out agent loads the JDBC driver instances based on the configuration of the connection objects in the Fan-Out driver. For more information, see NetIQ Identity Manager Driver for JDBC Fanout Implementation Guide.

iManager Plug-ins for Identity Manager

Installs the iManager plug-ins that allow you to use iManager to manage Identity Manager drivers that have structured Global Configuration Values (GCVs).


Identity Manager drivers synchronize identity information among several types of directories, databases, and business applications and the Identity Vault. You can configure the driver to synchronize the data in a single direction or in both directions.

In the installation program, you can select the drivers that you want to install with the other components. You might want to install some of the drivers on a server that does not host the Identity Manager engine. In this case, you would also need to install the Remote Loader service on that server.