When using a DirXML Remote Loader, the DirXML Remote Loader DirXML Shim is loaded on the DirXML Engine which communicates to the DirXML Remote Loader which has the DirXML Driver for the Connected Application.
![]() |
In some clients, we often setup specific Linux servers that host DirXML Remote Loader 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.
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 DirXML Remote Loader on the same server as the DirXML Engine.
![]() |
![]() |
Some of the DirXML Drivers are unable to run where the DirXML Engine is running. The DirXML Remote Loader 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 DirXML Remote Loader runs on an Microsoft Active Directory server.
- based on 2015-03-31