Impact of server rename on the Rational solution for Collaborative Lifecycle Management 
Authors: LisaFrankelBuild basis: CLM products, version 4.0.1 and later
Page contents
- Jazz Team Server
- Change and Configuration Management (CCM)
- Restart all clients
- Use 4.0.1 or higher clients and build engines for production scenarios
- Use staging workspace for test staging environment using production data scenario
- Check in changes into repository workspace before renaming server
- Deactivate non-Jazz Build Engine (JBE) build engines
- Update server URLs in work item templates
- Specify full URI of renamed server in full-text searches
- Query limitations
- Plan limitations
- Quality Management (QM) application
- Integrated products
Add introductory paragraph here
Jazz Team Server
Updating teamserver.properties file
Application names remain the same after a server rename operation
Change and Configuration Management (CCM)
Restart all clients
Use 4.0.1 or higher clients and build engines for production scenarios
Use staging workspace for test staging environment using production data scenario
Check in changes into repository workspace before renaming server
Deactivate non-Jazz Build Engine (JBE) build engines
Update server URLs in work item templates
Specify full URI of renamed server in full-text searches
Query limitations
Plan limitations
Quality Management (QM) application
Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section textChanges to advanced properties
Remap embedded anchored links that are non-navigable
Expand remapping beyond integration URLs
Integrated products
Rational Reporting for Development Intelligence
Rational ClearQuest
Rational ClearCase
Related topics: Deployment web home, Deployment web home
External links:
Additional contributors: TWikiUser, TWikiUser
Copyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors. Contributions are governed by our Terms of Use. Please read the following disclaimer.