CA Identity Manager Implementation Guide - CA Technologies

Identity Manager ComponentsIn this situation, changes to the user store/Provisioning Directory can beinitiated by CA Identity Manager, the Provisioning Server, or an endpoint.Note: When CA Identity Manager uses a combined user store and ProvisioningDirectory, organizations are not supported. If you need to manageorganizations, use a separate user store and Provisioning Directory. How toChoose a User Store Solution (see page 49) lists additional differences betweencombined and separate user store/Provisioning Directory implementations.DatabasesCA Identity Manager uses data sources to connect to databases that storeinformation required to support CA Identity Manager functionality. Thesedatabases can reside in a single physical instance of a database, or in separateinstances.Object Database (required)Contains CA Identity Manager configuration information.Task Persistence Database (required)Maintains information about CA Identity Manager activities and theirassociated events over time. This allows the system to accurately track CAIdentity Manager activities, even if you restart the Identity Manager Server.Workflow DatabaseStores workflow process definitions, jobs, scripts, and other data required bythe Workflow Engine.Audit DatabaseProvides a historical record of operations that occur in an Identity Managerenvironment.Note: You can configure the amount and type of information that CA IdentityManager stores in the audit database. See the Configuration Guide for moreinformation.Reporting DatabaseStores snapshot data, which reflects the current state of objects in CAIdentity Manager at the time the snapshot is taken. You can generate reportsfrom this information to view the relationship between objects, such as usersand roles.34 Implementation Guide