The Micro Focus Identity Manager Remote Loader allows a driver shim to execute on a server separate from the main Identity Manager engine. This architecture is essential for security and connectivity. The Active Directory driver is a classic example, as it is best practice to install it via a Remote Loader on a domain controller. The JDBC and LDAP drivers are also commonly used with the Remote Loader to connect to databases and directories that reside in different network zones, such as a DMZ, without exposing the core Identity Vault server.

C. eDirectory: The eDirectory driver shim is loaded and runs directly within the eDirectory process (ndsd) on the Identity Vault server; it does not use the Remote Loader architecture.

E. Entitlement Services: Entitlement Services is a framework within Identity Manager for managing application permissions; it is not a driver and therefore cannot be hosted on a Remote Loader.

1. Micro Focus Identity Manager 4.8 Documentation - Understanding the Remote Loader: The documentation states, "The Remote Loader allows you to run the driver shim on a server other than the server where the Identity Vault and the Metadirectory engine are running." It frequently uses drivers like Active Directory, JDBC, and other application drivers as examples for this deployment model. (Reference: Identity Manager 4.8 Installation Guide, Section 7.0, "Installing the Remote Loader").

2. Micro Focus Identity Manager 4.8 Driver Documentation - Active Directory Driver Implementation Guide: This guide explicitly details the installation process using a Remote Loader. Section 3.1, "Installation Overview," states, "The driver shim is installed on a Windows server that is a member of the Active Directory domain you want to synchronize with... The driver shim runs in the Remote Loader service."

3. Micro Focus Identity Manager 4.8 Driver Documentation - JDBC Driver Implementation Guide: The guide's installation section confirms Remote Loader compatibility. Section 3.2, "Installing the Driver Files," describes placing the driver files in the Remote Loader's directory (\lib) when deploying away from the Metadirectory engine server.

4. Micro Focus Identity Manager 4.8 Driver Documentation - eDirectory Driver Implementation Guide: This document clarifies the driver's architecture. Section 1.2, "System Requirements," explains that the driver shim is a library (dxevent) loaded by the eDirectory service itself, confirming it does not use a Remote Loader.