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. For more information about supported platforms, see Section 15.6, System Requirements for the Remote Loader.
You can install .NET Remote Loader on any of the supported Windows operating systems running .NET Framework 3.5.1, at a minimum.
Ensure that your Linux operating system has the following kernel versions:
4.4.59-92.42.2 or later on SLES 12 SP2
3.12.74-60.64.48.1 or later on SLES 12 SP1
3.12.61-52.80.1 or later on SLES 12
3.0.101-107.1 or later on SLES 11 SP4
3.0.101-0.47.105.1 or later on SLES 11 SP3
2.6.32-696.6.3 or later on Red Hat 6.9
(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.
NetIQ recommends that you use the Remote Loader configuration with your drivers where possible. Use the Remote Loader even in cases where the connected system is on the same server as the Identity Manager server engine.
When you run the driver shim in the Remote Loader configuration, the following advantages apply:
Memory and processing isolation between driver shims allows for better performance and monitoring of the Identity Manager solution.
Patching and upgrading the driver shim does not impact eDirectory or other drivers.
Protects eDirectory from fatal issues that could occur in the driver shim.
Distributes the load from the driver shims to other servers.
The following table lists the drivers that are support the Remote Loader capability:
Active Directory
Access Review
ACF2
Banner
Blackboard
Data Collection Services
Delimited Text
GoogleApps
REST
GroupWise (for 32-bit Remote Loader)
JDBC
JMS
LDAP
Linux/UNIX Settings
Lotus Notes
Managed System Gateway
Manual Task Services
Null and Loopback
Office 365
Oracle EBS HRMS
Oracle EBS TCA
Oracle EBS User Management
PeopleSoft 5.2
Privileged User Management
Remedy
SalesForce.com
SAP Business Logic
SAP GRC (CMP only)
SAP HR
SAP Portal
SAP User Management
ServiceNow
Integration Module V2.0 for Sentinel
SharePoint
SOAP
Top Secret
WorkOrder
The following drivers do not support Remote Loader:
Bidirectional eDirectory
eDirectory
Entitlements Services
Role Service
User Application
For more information about the Identity Manager Remote Loader, see The Many Faces of Remote Loader in IDM
.