23.1 About the User Application Driver

The User Application driver is responsible for starting provisioning workflows and for notifying the identity applications of changes in the Identity Vault. For example, when you make changes to the directory abstraction layer using the Designer for Identity Manager. Only the Subscriber channel is used in this driver. The driver processes messages from the Identity Vault to the identity applications running on an application server. Although there are events that occur in the identity applications that are reported back to the Identity Vault, these events do not flow through the Publisher channel of the User Application driver.

When the application server is started, the driver establishes a session with the application server. The driver sends messages to the identity applications running on the application server (for example, “retrieve a new set of virtual directory definitions”).

The source components of the driver include:

  • ComposerDriverShim.jar – The Composer Driver Shim. It is installed in the lib directory \Netiq\NDS\lib in Windows or the classes directory /usr/lib/dirxml/classes in Linux.

  • srvprvUAD.jar – The Application Driver Shim. It is installed in the lib directory \Netiq\NDS\lib in Windows or the classes directory /usr/lib/dirxml/classes in Linux.

  • UserApplicationDriver.xml – A file that contains configuration data for setting up the new driver. It is installed in the DirXML.Drivers directory, which is \Tomcat\webapps\nps\DirXML.Drivers in Windows and either /opt/netiq/eDirectory/lib/dirxml/rules/ or /var/opt/netiq/iManager/nps/DirXML.Drivers in Linux.

The User Application driver components are installed when you install Identity Manager. Before you can run the identity applications, you must add the User Application driver to a new or existing driver set, and activate the driver.

Depending on your work environment, very little configuration of the User Application driver might be required, or you might want to implement a complex set of business rules in the driver policies. The User Application driver provides the same flexible mechanisms for data synchronization as other Identity Manager drivers.