1.6 Support for Standard Driver Features

The following sections provide information about how the JMS driver supports these standard driver features:

1.6.1 Local Platforms

A local installation is an installation of the driver on the same server as the Metadirectory engine, Identity Vault, and JMS vendor application. Both systems that the driver needs to communicate with (Metadirectory engine and JMS) are local to the driver.

The JMS driver can be installed on the same operating systems that are supported by the Metadirectory server. For information about the operating systems supported by the Metadirectory server, see System Requirements in the Identity Manager 4.0.1 Integrated Installation Guide.

1.6.2 Remote Platforms

The JMS driver can use the Remote Loader service. The Remote Loader service for the JMS driver can be installed on any of the Identity Manager supported platforms.

For more information about installing the Remote Loader services, see Installing Identity Manager in the Identity Manager 4.0.1 Integrated Installation Guide.

1.6.3 Entitlements

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.

1.6.4 Password Synchronization Support

The basic configuration files for the JMS driver do not include policies for synchronizing passwords.

1.6.5 Information Synchronized

The JMS driver synchronizes any messaging format you want. By default, the driver is set up with a Loopback driver configuration.