Overview

As the following figure illustrates, the DirXML engine runs on a server as part of eDirectory. A DirXML driver shim and its configured driver communicate with an application and with the DirXML engine.

As the following figure illustrates, a connected system extends DirXML functionality across platforms:

A connected system requires a Remote Loader. This service enables the DirXML engine to exchange data with DirXML drivers running as different processes and in different locations, including the following:

• As separate processes on the server where the DirXML engine is running

  The DirXML engine runs as part of the eDirectory process. DirXML drivers can run on the server where the DirXML engine is running. In fact, they can run as part of the same process as the DirXML engine.

  However, for strategic reasons, you might want the DirXML driver to run as a separate process on the server. Typically, though, the DirXML drivers run on separate servers.

  If the driver is running as a separate process, the Remote Loader provides a communication channel between the DirXML engine and the driver.

• On servers other than the one where the DirXML engine is running

  Some DirXML drivers are unable to run where the DirXML engine is running. The Remote Loader enables you to run the DirXML engine in one environment while running a DirXML driver on a server in a different environment.

  Scenario: Separate Servers. The DirXML engine is running on a NetWare server. You need to run the DirXML Driver for Active Directory. This driver is unable to run on a NetWare server because it must run in an Active Directory environment. You install and run the Remote Loader on a Windows 2003 server. The Remote Loader provides a communication channel between the Active Directory driver and the DirXML engine.

  Scenario: Non-Host. The DirXML engine is running on Solaris. You need to communicate with a NIS system where you want to provision user accounts. That system usually doesn't host the DirXML engine. You install the Remote Loader and the DirXML Driver for NIS on the NIS system. The Remote Loader on the NIS system runs the NIS driver and enables the DirXML engine and the NIS driver to exchange data.

Identity Manager 2 provides Remote Loader functionality through dirxml_remote, rdxml, or dirxml_jremote.

Dirxml_remote

Dirxml_remote is an executable that enables the DirXML engine to communicate with DirXML drivers running on Windows.

The Remote Loader Console uses dirxml_remote. If you specify dirxml_remote from the command line, without any parameters, the Remote Loader Application Wizard is launched. If you type dirxml_remote and then pass in parameters, the Remote Loader is started.

Rdxml

Rdxml is an executable that enables the DirXML engine to communicate with DirXML drivers running in Solaris, Linux, or AIX environments.

Rdxml can support both native and Java drivers. To support Java drivers, it loads a JVM.

Dirxml_jremote

Dirxml_jremote is a pure Java Remote Loader. It is used to exchange data between the DirXML engine running on one server and DirXML drivers running in another location, where rdxml doesn't run. It should be able to run on any system with a compatible JRE (1.4.0 minimum, 1.4.2 or higher recommended) and Java Sockets, but is only officially supported on the following:

• HP-UX
• AS/400
• OS/390
• z/OS

Overview: Main Tasks

Using the Remote Loader involves the following tasks:

• If you plan to use the Secure Socket Layer (SSL), provide certificates for secure data transfers.
• Install, configure, and run the Remote Loader.
• Import, configure, and start the DirXML driver.

Some administrators prefer to import and configure the DirXML driver before setting up the Remote Loader. For example, the driver might already be running but you want to enable it to run remotely.

On the other hand, if the Remote Loader is running, you can import, configure, and start the driver, then immediately check whether proper communication is occurring among the DirXML engine, Remote Loader, and DirXML driver.