2.0 Installing the Driver Files

By default, the JMS driver files are installed on the OpenText Identity Manager server at the same time as the OpenText Identity Manager engine. The installation program extends the OpenText Identity Vault’s schema and installs both the driver shim and the driver configuration files. It does not create the driver in the OpenText Identity Vault (see Section 3.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 OpenText Identity Manager 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 OpenText Identity Manager (where OpenText Identity Manager engine and OpenText Identity Vault are located), OpenText 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: