By default, the JMS driver files are installed on the Metadirectory server at the same time as the Metadirectory engine. The installation program extends the Identity Vault’s schema and installs both the driver shim and the driver configuration files. It does not create the driver in the Identity Vault (see Section 4.0, Creating a New Driver Object) or upgrade an existing driver’s configuration (see Section 5.0, Upgrading an Existing Driver).
You don’t need to install the Metadirectory engine on this same machine. Using a Remote Loader, you can separate the engine and the driver shim, allowing you to balance the load on different machines or accommodate corporate directives.
The installation scenario you select determines how the driver shim is installed. If you choose to install the driver shim on the same machine as Identity Manager (where the Metadirectory engine and the Identity Vault are located), Identity Manager calls the driver shim directly. If you choose to install the driver shim on another machine, you must use the Remote Loader.
You can install the driver in one of the following ways:
On a local machine: Install the JMS driver files on the Metadirectory server and connect to the JMS server by using the JMS PROVIDER URL (Connection Properties). See the instructions in Installing Identity Manager
in the Identity Manager 4.0.2 Integrated Installation Guide.
On a remote machine, you can install in one of the following ways:
You can install the Identity Vault, the Metadirectory engine, and the driver on a separate computer from the JMS domain controller. This configuration leaves the domain controller free of any Identity Manager software.
Alternatively, you can install the Remote Loader and driver shim on the JMS domain controller, but install the Identity Vault and the Metadirectory engine on a separate server.
See the instructions in Installing Identity Manager
in the Identity Manager 4.0.2 Integrated Installation Guide.