CA Identity Manager 12.x uses caching for transactions. The utilization of this feature can cause synchronization issues if the application is setup in a high availability mode without application server clustering.
An example I can give is a project I was involved with using JBoss as the CA IdM application server. As such I will be addressing JBoss clustering in this entry.
JBoss uses a Hypersonic database to manage internal JMS data (JMS Queues). JBoss uses the JMS queues for tracking tasks and processes within the application. It is recommended to use a shared MS SQL database for the JMS database. There are documents available online which explain how to migrate from Hypersonic to MS SQL. In my example we opted to use the same MS SQL infrastructure used by Identity Manager to house the JMS database. In simplified terms, the steps to accomplish to clustering of IdM on JBoss is as follows:
1. Create a new SQL database (JBOSS_JMS)
2. Create a user/owner for this DB (jbossjms)
3. Migrate JBoss to SQL from the Hypersonic DB
4. Bring all services back up and test to ensure the migration was successful
5. Follow the procedures in the IdM documentation to configure JBoss clustering
More Here
Courtesy:http://www.idmworks.com/blog/ca-identity-manager-high-availability-jboss-clustering
An example I can give is a project I was involved with using JBoss as the CA IdM application server. As such I will be addressing JBoss clustering in this entry.
JBoss uses a Hypersonic database to manage internal JMS data (JMS Queues). JBoss uses the JMS queues for tracking tasks and processes within the application. It is recommended to use a shared MS SQL database for the JMS database. There are documents available online which explain how to migrate from Hypersonic to MS SQL. In my example we opted to use the same MS SQL infrastructure used by Identity Manager to house the JMS database. In simplified terms, the steps to accomplish to clustering of IdM on JBoss is as follows:
1. Create a new SQL database (JBOSS_JMS)
2. Create a user/owner for this DB (jbossjms)
3. Migrate JBoss to SQL from the Hypersonic DB
4. Bring all services back up and test to ensure the migration was successful
5. Follow the procedures in the IdM documentation to configure JBoss clustering
More Here
Courtesy:http://www.idmworks.com/blog/ca-identity-manager-high-availability-jboss-clustering
CA Identity Manager Online Training
ReplyDeletehttp://www.21cssindia.com/courses/ca-identity-manager-online-training-70.html
Describe CA Identity Manager - Identify the Features and Functions of CA Identity Manager - Describe the CA Identity Manager Architecture - Install CA Identity Manager - Identify System Requirements - Install CA Identity Manager - Validate and Troubleshoot the Installation - Install the Report Server - Install the Report Server - Install Connector Xpress - Describe Connector Xpress - Install Connector Xpress - Install and Configure Endpoint Agents - Configure SSL for Active Directory - Install and Configure the Exchange Agent - Install and Configure the UNIX Agent - Install and Configure Password Synchronization - Install and Configure the Active Directory Password Synchronization Agent - Install and Configure UNIX Password Synchronization - Configure Siteminder Integration - Configure CA Siteminder Integration - Set Up the CA Identity Manager Environment - Build the CA Identity Manager Environment - Configure the Identity Manager Environment - Import Users - Import Users into the CA Identity Manager System - Configure the Report Server, GINA, and the Database - Configure the Report Server - Configure the GINA and the Credential Provider - Configure the Database to Split Out Database Configuration - Troubleshoot CA Identity Manager - Troubleshoot CA Identity ManagerEmployees to learn at their own pace and maintain control of learning “where, when and how” with boundless access 24/7by 21st Century Software Solutions. contact@21cssindia.com