Arun K Sriramaiah 2700076GE8 Visits (97)
The idle standby configuration enables recovery from failover to help ensure minimal impact on business operations during planned or unplanned server outages and Idle standby deployment for crash recovery.
Refer to Impl
Important: Jazz Team Server applications allow only a single server to be active at any one time to a repository; therefore the backup (or Idle) server is configured to never run asynchronous (or background) tasks. If a switch is made to the backup server, you must plan to bring the primary server back up as quickly as possible.
Index corruption can be caused by Network, database or application server issues, to name a few. Below are the steps to fix the index corruption issue on active server, using the idle standby server.
Index corrupted occurred on the Active server and you were unable to fix it by running the repotool command on it. So we can still fix the index issue by running a repotool command on the idle standby server.
Fixing the index issue on active RTC server using the Idle standby server.
Below are steps to fix the index problem, using the IDLE standby server. The standby server is on a different machine (and pointing to a different jazz_home than the active one).
Arun K Sriramaiah 2700076GE8 Visits (392)
Rational Team Concert server is expected to have a common user base management. In order to correctly perform process enforcement for Git operations by Rational Team Concert it is imperative that the identity of the Git user be known to Rational Team Concert. Therefore, the need to have a common user base across Rational Team Concert and Git server (Apache HTTP server) via a different LDAP arrangement.
We can still get the integration done using a common user name with different user base across Rational Team Concert and Git server via an different LDAP arrangement.
Example: Git is configured with Apache DS LDAP and RTC configured with different LDAP registry.
Note: Common user id used for both GIT and RTC using different registry (with different password) and provide all necessary permissions.
Below are checkpoints for verifying the integrations:
1) Verify the GIT login, just to ensure GIT login is fine
$ git remote show origin
2) Verify the GIT GIt repo configuration
Update respective "repokey" and "repourl" information
3) Verify the GIT GIt repo configuration
Update respective "pre-receive" and "post-receive" hooks information
Note: The above configuration will give a clear understanding about RTC-GIT integrations and using a common user name with different user base across Rational Team Concert and Git server via different LDAP arrangements.
Kiran Byrappa 270001YMWT Visits (362)
Post upgrade of your CLM application you may come across the below error while trying to access any Project Areas in Rational Quality Manager.
The error occurs when QM is not deployed correctly which could be the result of an incomplete / improper upgrade process and when WebSphere cache was not cleaned prior to deploying 5.0.2 war file.
Checking the logs reveals the below error:
You may follow the below steps to redeploy QM:
3. Re-deploy QM.war
4. Redo the group mapping in WebSphere by following the below steps:
Map security roles to a user or repository group:
a) Go to Applications > Application Types > WebSphere enterprise applications.
e) Enter a search string to return your group names from the LDAP server. Click Search to run the query.
Kiran Byrappa 270001YMWT Visits (476)
Post upgrade of CLM your attempt to login to Rational Quality Manager instance displays an error indicating that your server appears to be in bad state.
You may want to check the following to ensure that the required services are setup properly and are up and running.
naomimg 060001F9C7 Visits (443)
As we (Naomi Guerrero and Denise McKinnon) assume ownership responsibility for this blog from our esteemed colleague Jason (acdntlpoet: http
To the faithful followers of this blog, we promise to continue to provide you with the meaningful content and posts that help you to be successful. We want to encourage open collaboration with our followers and appreciate new ideas about topics you want to know more about. Find out a little bit more about us below!
Joined Rational support back in 2000, holds a BA in Information Systems and has over 35 years experience in IT (for those who remember programming on Punch Cards). I've held various positions as a Technical Support Engineer, Knowledge Engineer and most recently as a Social Business Analyst where I am most excited to be delivering support messages through this blog.
About Naomi :
Joined Rational Support in 2006 as a Software Engineer. I have nearly 15 years experience in IT and hold a Computer Science degree. In August, I will begin pursing an MBA advance degree. I am currently a Social Business Analyst for a subset of products within IBM.
We look forward to collaborating with you!