Configuration Guide › Relational Database Management › Important Notes When Configuring CA Identity Manager for Relational Databases

Important Notes When Configuring CA Identity Manager for Relational Databases

Before you configure CA Identity Manager to manage a relational database, ensure that the database meets the following requirements:

• The database must be accessible through a JDBC driver or an Open Database Connectivity (ODBC) driver (when Identity Manager integrates with SiteMinder). The driver should support outer joins. If more than two tables are used to represent a managed object, the driver should also support nested outer joins.

  Note: If the driver does not support outer joins, CA Identity Manager uses inner joins when querying the database. This may cause unexpected query results.

• You must be able to uniquely identify each object that CA Identity Manager manages, such as a user, group, or organization (when supported). For example, the unique identifier for users may be a login ID.

  Note: The unique identifier must be stored in a single column.

• CA Identity Manager requires some multivalued attributes, which can be stored as a delimited list in a single cell or in multiple rows in a separate table. For example, the following tblGroupMembers table stores the members of a group:

The ID column contains the unique identifier for a group and the Members column contains the unique identifier for a member of the group. For example, dmason and rsavory are members of the Research group. When a new member is added to that group, another row is added to tblGroupMembers.

• When your environment includes organizations, do the following:
  • Edit and run a SQL script, included with Identity Manager, against the database to configure organization support.
  • CA Identity Manager requires a top level organization, named the root. All other organizations relate to the root organization.

    For more information about organization requirements, see Organizations Management.