For those supported systems drivers and configuration files have been pre-built and made ready for user customization. While a large number of systems are supported out of the box the possibility of integrating with other systems is there through customized drivers and configurations.
The current release of Identity Manager also provides integration with Novell's Security Information and Event Management (SIEM) product called Novell Sentinel. Among other things the integration lets Sentinel understand which of various users and roles are tied to a single person. This means that while a single person may have multiple usernames across various systems they can all be tied back to one individual because IDM sends the relevant relationships to Sentinel.
Novell also offers traditional pay-per-issue support options for its customers along with a consulting option to completely implement a new system.
Novell's partners are a viable alternative to using Novell support directly and may be a more cost-effective method of receiving answers that were not found via the free channels.
A newer method of administration, and especially, deployment, is now available through a product known as Designer A free companion to IDM, Designer is written in Eclipse and runs on either a Linux or Windows workstation. Because it is a fat client it does not need to be connected to any networks to make changes to drivers though it does need to deploy changes for them to take effect. Designer is made to speed up the process of deploying new drivers and modifying and testing existing drivers by removing the multiple-click requirement that comes with any web interface, and offering quicker access to driver configuration settings. As of Designer 3.0, Designer also provides Subversion based version control. This simplifies development of an IDM implementation in a team environment, and also provides access to a history of changes made to IDM objects.
Along with changing and deploying entire environments Designer offers the added benefit of real-time testing of drivers before they are placed in production. An operation document can be fed into Designer and run through the driver's configuration and policies to see what will come out after the processing takes place. It is this output that would be used to make changes on either the eDirectory or application system. Because the test operation document is XML, just like the IDM configurations, the document can be easily viewed in a text editor or web browser before and after the simulation operation.