This page (revision-1) was last changed on 29-Nov-2024 16:16 by UnknownAuthor

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 1 added 47 lines
!!! Overview
When using the [{$pagename}] and the [DirXML Driver] a server with the Remote Loader. The [{$pagename}] [Identity Vault|IDV] and the [Metadirectory engine|DirXML Engine] installed on the same server the [Connected Application].
When using a [{$pagename}], the [{$pagename}] [DirXML Shim] is loaded on the [DirXML Engine] which communicates to the [{$pagename}] which has the [DirXML Driver] for the [Connected Application].
[{Image src='DirXML Remote Loader/DirXML Remote Loader.png' caption='DirXML Remote Loader 3-Server' align=left width=1024 height=768 style='font-size: 120%}].
!! Some [{$pagename}] Scenarios
The [{$pagename}] enables the [DirXML Engine] to exchange data with the [Identity Vault|IDV] as different processes and in different locations, including the following scenarios.
! Non-Host [NetIQ]'s term.
The Non-Host as shown above using three different machines. This may be required as when you are running [Lotus Notes] on AIX and your [DirXML Engine] is on Linux. As the [Lotus Notes Client] requires a DLL to be used with the driver, it is possible to install a Windows Server to host the [{$pagename}] and the [Lotus Notes] client DLL.
In some clients, we often setup specific Linux servers that host [{$pagename}] with multiple [DirXML Drivers] for offloading connections from the [DirXML Engine].
As far as we know, this is a [Best Practices Remote Loader] and each [DirXML Driver] runs as a separate process implying that even if one driver would crash the others will keep working.
! Separate Process
As a separate process where the [{$pagename}] is on the same server where the [DirXML Engine] is running:
* The [DirXML Engine] runs as part of an [EDirectory] process.
* The Identity Manager drivers can run on the server where the [DirXML Engine] is running.
However, for strategic reasons and to simplifying troubleshooting, you might want the Identity Manager driver to run as a separate process on the server. This is done by installing the [{$pagename}] on the same server as the [DirXML Engine].
[{Image src='DirXML Remote Loader/DirXML Remote Loader Separate Process.png' caption='DirXML Remote Loader 1-Server' width=512 style='font-size: 120%}]
! [Connected Application] Servers
On the [Connected Application] server that is not running the [DirXML Engine].
[{Image src='DirXML Remote Loader/DirXML Remote Loader On App Server.png' caption='DirXML Remote Loader 2-Server' align=left width=1024 style='font-size: 120%}]\\
Some of the [DirXML Drivers] are unable to run where the [DirXML Engine] is running. The [{$pagename}] enables you to run the [DirXML Engine] in one environment while running an [DirXML Drivers] on a server in a different environment or on a different Operating System.
For example, you cannot run the [Microsoft Active Directory Driver] on a Linux server. The [DirXML Engine] can run on the Linux Server while the [{$pagename}] runs on an [Microsoft Active Directory] server.
!! [Best Practice|Best Practices Remote Loader]
[Best Practices Remote Loader] describes why you should always us [{$pagename}]
!! [DirXML Drivers That Support Using DirXML Remote Loader|[DirXML Drivers#ThatSupportUsingDirXMLRemoteLoader]
A list of [DirXML Drivers That Support Using DirXML Remote Loader|[DirXML Drivers#ThatSupportUsingDirXMLRemoteLoader]]
!! More Information
There might be more information for this subject on one of the following:
[{ReferringPagesPlugin before='*' after='\n' }]
----
* [#1] - [Remote Loader Overview|https://www.netiq.com/documentation/idm402/idm_remoteloader/data/be4sfxm.html|target='_blank'] - based on 2015-03-31