The following sections provide information about how the JMS driver supports these standard driver features:
A local installation is an installation of the driver on the same server as the OpenText Identity Manager engine, OpenText Identity Vault, and JMS vendor application. Both systems that the driver needs to communicate with (OpenText Identity Manager engine and JMS) are local to the driver.
The JMS driver can be installed on the same operating systems that are supported by the OpenText Identity Manager server. For information about the operating systems supported by the OpenText Identity Manager server, see Planning Your Installation
in the OpenText™ Identity Manager Install and Upgrade Guide for Linux or Planning Your Installation
in the OpenText™ Identity Manager CE 24.4 (v4.10) Install and Upgrade Guide for Windows.
The JMS driver can use the Remote Loader service. The Remote Loader service for the JMS driver can be installed on any of the OpenText Identity Manager supported platforms.
For more information about installing the Remote Loader services, see Configuring the Remote Loader and Drivers in the OpenText™ Identity Manager Install and Upgrade Guide for Linux or Configuring the Remote Loader and Drivers in the OpenText™ Identity Manager CE 24.4 (v4.10) Install and Upgrade Guide for Windows.
The JMS driver does not have Entitlement functionality defined in its basic configuration files. The driver does support entitlements, if there are policies created for the driver to consume.
The basic configuration files for the JMS driver do not include policies for synchronizing passwords.
The JMS driver synchronizes any messaging format you want. By default, the driver is set up with a Loopback driver configuration.