CA Identity Manager Implementation Guide - CA Technologies

More documents

Recommendations

Info

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
Identity Manager ComponentsWhen you use the Installer, CA Identity Manager configures a connection to asingle database, called the Identity Manager Database, which contains the tablesfor each database type.Note: You can create a data store for task persistence, workflow, auditing, orreporting in a separate database and configure CA Identity Manager to connectto it. For more information, see the Installation Guide.Connector ComponentsConnector ServersA connector is the software interface to an endpoint. The Provisioning Serveruses the connector to communicate with the endpoint. It translates ProvisioningServer actions into changes on the endpoint, such as ―Create a new emailaccount on a Microsoft Exchange endpoint.‖Examples of endpoints are UNIX workstation, Windows PC, or an applicationsuch as Microsoft Exchange (for email).A connector server works with multiple endpoints. For example, if you havemany UNIX workstation endpoints, you might have one Connector Server thathandles all connectors that manage UNIX accounts. Another connector servermight handle all connectors that request Windows accounts.The distributed connector server works with multiple Connector Servers. Itprovides load balancing when one connector server is busy and high availabilitywhen a connector server is down.A connector server is a Provisioning Server component that managesconnectors. It can be installed on the Provisioning Server system or on a remotesystem.There are two types of connector servers:■■The Java Connector Server (Java CS) manages connectors written in JavaThe C++ Connector Server (CCS) manages connectors written in C++C++ Connector ServerThe C++ Connector Server is a connector server that manages C++ connectors.It can be installed on the Provisioning Server or on a remote system. The C++Connector Server provides an object-oriented application framework thatsimplifies development of connectors, which are responsible for communicationbetween the C++ Connector Server and the endpoint.Chapter 3: Identity Manager Architecture 35
Page 1 and 2: CA Identity ManagerImplementation G
Page 3: CA Product ReferencesThis document
Page 7 and 8: Task Processing and Performance ...
Page 9 and 10: Chapter 1: Managing Identities andA
Page 11 and 12: Admin Roles for User Account Manage
Page 13 and 14: Admin Roles for User Account Manage
Page 15 and 16: Password ManagementThe account temp
Page 17 and 18: CA RCM Integration■■Notificatio
Page 19: CA Enterprise Log Manager Integrati
Page 22 and 23: Complying with Business PoliciesThe
Page 24 and 25: Complying with Business PoliciesRep
Page 26 and 27: Transforming Data in the User Store
Page 28 and 29: Approving Business ChangesBusiness
Page 31 and 32: Chapter 3: Identity ManagerArchitec
Page 33: Identity Manager ComponentsFor exam
Page 37 and 38: Identity Manager ComponentsCertain
Page 39 and 40: Identity Manager ComponentsWorkPoin
Page 41: Sample CA Identity Manager Installa
Page 44 and 45: Decide What to ManageHow to Configu
Page 46 and 47: Decide What to ManageAccount Templa
Page 48 and 49: Determine Audit RequirementsYou vie
Page 50 and 51: Decide User Store RequirementsCapab
Page 52 and 53: Decide Hardware RequirementsDecide
Page 54 and 55: Choose a Method to Import UsersAddi
Page 56 and 57: Choose a Method to Import UsersExec
Page 58 and 59: Develop a Deployment PlanSynchroniz
Page 60 and 61: Develop a Deployment PlanTo deploy
Page 62 and 63: Develop a Deployment PlanEnvironmen
Page 65 and 66: Chapter 5: Integrating with SiteMin
Page 67: Password Policies with SiteMinderCA
Page 70 and 71: Role OptimizationsRole Optimization
Page 72 and 73: Role OptimizationsObjectTypeBaseObj
Page 74 and 75: Role Optimizations■■Tune the us
Page 76 and 77: Role OptimizationsTo limit the numb
Page 78 and 79: Task Optimizations■A user accesse
Page 80 and 81: Task OptimizationsRelationship Tabs
Page 82 and 83: Task OptimizationsGuidelines for Op
Page 84 and 85:
Guidelines for Group Member\Adminis
Page 86 and 87:
Identity Policy Optimizations■An
Page 88 and 89:
Identity Policy OptimizationsLimit
Page 90 and 91:
Tuning for Provisioning ComponentsC
Page 92 and 93:
Runtime Components TuningIdentity M
Page 94 and 95:
Runtime Components TuningTuning JMS
Page 97 and 98:
Chapter 7: Creating a Disaster Reco
Page 99 and 100:
Define Disaster Recovery Requiremen
Page 101 and 102:
Develop Backup PlansMulti-Site Conn
Page 103 and 104:
Develop Restore ProceduresComponent
Page 105 and 106:
Develop Restore ProceduresRestore C
Page 107 and 108:
Test the Recovery PlanTest the Fail
Page 109 and 110:
Chapter 8: Transitioning From eTrus
Page 111 and 112:
eTrust Admin Management Interfacese
Page 113 and 114:
Batch Processing in Identity Manage
Page 115:
Next Steps■etautilYou use the eta
Page 118 and 119:
How Role Evaluation Affects Perform
show all

CA Identity Manager Implementation Guide - CA Technologies

Create successful ePaper yourself

Delete template?

Save as template?