A new iManager properties page has been added on the Identity Vault. This lets you
configure the iManager URL for each individual Identity Vault. To do this, right-click an Identity
Vault and select Properties > iManager.
As a productivity convenience, the connectivity page on eDirectory and NDS applications lists the IP-Addresses/ DNS-Names
for NDS and eDirectory applications. All items in the list show in the host drop-down boxes on all of the connectivity
tabs -- LDAP, VNC, and eDirectory. If you enter an IP address or DNS name in any
host field, it is automatically added to the host list.
You can add, edit, and delete items from the host list.
The Custom Reciprocal Mapping feature allows you to create and manage backlinks between
objects. For example, the Group object includes a Members attribute that contains
pointers to all User objects that belong to that group. Similarly, each User object
includes a Members Of attribute that points to the Group objects of which that user
is a member. These two-way links between objects are known as reciprocal mappings.
Designer 3.0 allows named passwords to be managed on a driver set,
similar to how they are managed on a driver. The addition of named passwords
on a driver set in Identity Manager 3.6 allows the named passwords
to be inherited by each driver under the driver set. Allowing for inheritance,
similar to how global configuration values are inherited, allows you to
declare a single named password on the driver set instead of declaring a
duplicate named password on each driver. The inheritance is strictly a run-time
operation. When editing the named passwords of a driver, the named passwords of
the driver set are not displayed.
Designer 3.0 allows encoding for the trace file to be set
for drivers, driver sets, and jobs.
The property pages across Designer 3.0 are listed in the alphabetical order, except for the
General page, similar to that of eclipse.
The page title has been updated to be more elaborate than the label that
is displayed in the list of property pages.
The Driver Health Configuration allows you to monitor a driver's state of health (green, yellow, or red),
and to specify the actions to perform in response to each of these health states.
To do so, you define the conditions (criteria) that determine each of the health states,
along with the associated actions to perform whenever the driver's health state changes. For example,
if the driver's health changes from a green state to a yellow state (based on the conditions you've established),
you can perform such actions as restarting the driver, shutting down the driver, and sending an e-mail
to the person who is designated to resolve issues with the driver.
The Properties page lets you customize how the Identity Manager JRE can start. You can set up
additional classpath, initial heap size, and maximum heap size. The JVM options entry is a good place to
set up debugging information.
A new action has been added to Designer 3.0 to install only the English templates. To do this, right-click the
Default Notification Collection from the Outline view and select Add Default Templates. However, this action
will not install all of the localized versions of the template. In order to get the localized version of a specific
template, right-click the template and select Add Localized Templates.
The ID Provider driver is a new driver that is included with Identity Manager 3.6. It is a service driver and is
included with the core drivers. The ID Provider driver enables you to create and maintain a central source of
unique IDs that can be consumed by client applications or systems. For more information, see the
Identity Manager
3.6 ID Provider Driver Implementation Guide.
