CA Identity Manager Implementation Guide - CA Technologies

More documents

Recommendations

Info

Runtime Components TuningTuning JMS SettingsThe following application server JMS tuning parameters define Queueconnections and Message Driven Bean instance pools.■WebSphere JMS TuningWebSphere provides two parameters that you can configure to improveperformance of event state transactions:– The number of connections in the Queue Connection Factory that areavailable for posting JMS messages– The number of instances of Message Driven Bean objects for processingthe posted messagesUse the WebSphere Administration Console to set the following properties:– Set the maximum session pool connections for the EventMsgQueueQueue Connection Factory to 128– Set the maximum sessions for the SubscriberMessageEJBPort ListenerPort in the Message Listener Service to 128■WebLogic TuningIn WebLogic application servers, Queue Connection Factories obtainconnection-handling threads from the server's JMS Thread Pool or thedefault execute pool, depending on the JMS Thread Pool size. If the JMSThread Pool size is 0, then WebLogic uses the threads in the execute pool.CA recommends setting the number of JMS Thread Pool threads equal to themaximum Bean Pool size for the Identity Manager Event Message DrivenBean, which is set to 128 by default.You use the WebLogic Server Console to set the JMS Thread Pool size in theJMS Services properties for the domain and server where CA IdentityManager is installed.The Identity Manager Event Message Driven Bean pool size is set bymodifying the max-beans-in-free-pool setting in the descriptor file in thefollowing location:WebLogic_home\domain\applications\IdentityMinder.ear\identityminder_ejb_jar\META-INF\weblogic-ejb-jar.xmlSubscriberMessageEJB12816com.netegrity.ims.msg.queue94 Implementation Guide
Runtime Components Tuning■JBoss TuningIn JBoss application servers, Queue Connection Factories obtainconnection-handling threads from the server’s Standard JMS Pool sessionfactory. By default, the number of maximum threads is set to 15.CA recommends setting this value to match the maximum size value of theStandard Message Bean Container.The JMS Session Pool section factory is set in the MaximumSize element ofthe JMSContainerInvoker in the following file:jboss_home\server\default\conf\standardjboss.xmlmessage-driven-bean….DefaultJMSProviderStdJMSPool1281….The Identity Manager Event Message Driven Bean pool size is set bymodifying the maximum size value in the following descriptor file:jboss_home\server\default\conf\standardjboss.xmlStandard Message Driven Beanfalsemessage-driven-bean……128Chapter 6: Optimizing Identity Manager 95
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 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 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?