You can map IDM objects to the tables in a JDBC database or to organizational units in DS using:
- Generic Mapping
Lets you store arbitrary objects without special configuration or administration.
- Explicit Mapping
Maps specific objects and properties to tables and columns in the JDBC database or to organizational units in DS.
- Hybrid Mapping
Similar to Generic Mapping, except some objects and properties are mapped explicitly.
By default, IDM uses a generic mapping for user-definable objects, for both a JDBC and a DS repository. A generic mapping speeds up initial deployment, and can make system maintenance more flexible by providing a stable database structure. In a test environment, generic tables let you modify the user and object model easily, without database access, and without the need to constantly add and drop table columns. However, generic mapping does not take full advantage of the underlying database facilities, such as validation within the database and flexible indexing. Using an explicit mapping generally results in a substantial performance improvement. It is therefore strongly advised that you change to an explicit mapping before deploying in a production environment. If you are integrating IDM with AM, and using a shared DS repository, you must use an explicit schema mapping.
Mapping strategies are discussed in the following sections, with separate topics for JDBC DS repositories.