CA Identity Manager Implementation Guide - CA Technologies

More documents

Recommendations

Info

Decide Hardware RequirementsDecide Hardware RequirementsThe hardware that you need for an Identity Manager installation depends on thefunctionality that you want to implement and the size of your deployment.The following sections describe typical Identity Manager implementations andtheir required hardware.Deployment TypesWhen planning the hardware needed for a CA Identity Manager deployment,consider the features that you want to implement and the initial size of thedeployment. Use one of the following categories to estimate the size of thedeployment.Note: The deployment type you select determines the size of the DxGrid file thatis used by the Provisioning Directory. You specify the deployment type when youinstall the Identity Manager Server.DemonstrationBasicA single server deployment for use in demonstrations or basic testing in aDevelopment environment. A demonstration deployment supports up to10,000 provisioned accounts.Note: This implementation type does not support productionimplementations.A high availability implementation that is suitable for most small to mediumsize implementations. A basic implementation supports up to 400,000provisioned accounts.This type of implementation requires two servers for running the IdentityManager application and its components and two servers for running theIdentity Manager database and the user store.52 Implementation Guide
Decide Hardware RequirementsIntermediateA high availability implementation that is suitable for medium sizeimplementations. An intermediate deployment supports up to 600,000provisioned accounts.Large EnterpriseA high availability implementation that includes additional server clusters toaddress additional users and an increased number of transactions. A largedeployment supports more than 600,000 provisioned accounts.Note: For more information about high availability implementations, see theInstallation Guide.Additional Requirements for ProvisioningIn addition to the components required for a basic CA Identity Managerimplementation, the following additional components are required when CAIdentity Manager includes provisioning:■Provisioning ServerCan be installed on the same machine as the Identity Manager server.■Provisioning Directory InitializationImportant! The Provisioning Directory Initialization must be installed on CADirectory.■Provisioning ManagerCan be installed on any Windows machine that can access the ProvisioningServer.Note: In a development environment, these components can be installed on onemachine that also includes the basic installation components.Chapter 4: Planning Your Implementation 53
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 and 34: Identity Manager ComponentsFor exam
Page 35 and 36: Identity Manager ComponentsWhen you
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 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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?