Troubleshooting - ELM Server Rename 
Authors: Chao Wang, Kot Tontranakwong, Susan WuBuild basis: Build basis: ELM 6.x and 7.x and later
This page provides information on how to troubleshoot server rename issues in IBM Engineering Lifecycle Management applications (ELM).
Files to gather:
repotools-jts_importURLMappings.log:
Files to gather:
repotools-jts_importURLMappings.log
Always include the context when running server rename for the ELM applications
Duplicated source or target URL is not allowed. No multiple sources to the same target
Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Include applications that are not part of the rename, but need to be renamed.
Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Default port URL would have another pair with 443.URLs with 9443 do not.
Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Ensure target URLs are expected/valid
Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Use of IP address in the public URI?
Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text
Need query
Getting Started
Need to know:- At what stage in the rename process the failure occurs. Depending on where the failure occurs, the logs to collect and review can be different.
- What files to gather. In most cases, ISADC includes all the files that are needed for troubleshooting a rename issue.
- What to look for in those files
- How to read the logs
- Generate / Verify URL mappings
- Import URL mappings
- JTS rename status
- Link Validation
- Finalize rename
- After a successful rename
Point of Failure
1. Generate / Verify URL Mappings
Files to gather:- Repotools-jts_generateURLMappings.log
- Repotools-jts_verifyURLMappings.log
- Application logs (jts.log, ccm.log, etc.)
- In repotools-jts_generateURLMapping.log, look for the following line to see what time it starts to collect URL information and what time it fails.
2025-04-04T14:51:10,220+0000 CRJAZ2233I The server at https://<server:port>/jts/urlMappingInformation is being contacted to collect URL information. 2025-04-04T14:56:10,227+0000 CRJAZ2942E A request from this server to another server could not be completed. The other server returned a 504 HTTP error with this error text: Gateway Time-out. com.ibm.team.repository.common.transport.TeamServiceException: CRJAZ2942E A request from this server to another server could not be completed. The other server returned a 504 HTTP error with this error text: Gateway Time-out.
- If the failure occurs immediately, get the timestamp when the error occurs and search in jts.log to find out which application it was trying to get data from and fail.
- If the failure occurs at least 5+ minutes and the error indicates some time-out issue, check the following technotes for how to extend the timeout settings:
Technotes:
2. Import URL Mappings
Review the Mappings File section in this wiki page, ensure that the mapping file is good, and that the verifyURLMappings log reports no error.Files to gather:
- Repotools-jts_importURLMappings.log
- Repotools-jts_verifyURLMappings.log
repotools-jts_importURLMappings.log:
- Check for errors
- Look in the command and see which mapping file is used
- Confirm the command is run against the mapping file used in to import and that there is no error.
3. JTS Rename Status
In ELM versions (and iFix versions) prior to 7.2, 7.1 iFix004, and 7.0.3 iFix015, the progress of the rename status is not written to JTS log. As a workaround, you can manually enable the logging by adding the following log4j logger to JTS.<Logger name="com.ibm.team.repository.service.mapping.internal.ServerRenameOverallStatusRestService" level="DEBUG"/>Related Technote and Defect:
- 7058385: Jazz Team Server does not report server rename status within the jts.log
- https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/582431
Files to gather:
- Repotools-jts_importURLMappings.log
- Application logs (jts.log, ccm.log, etc.)
repotools-jts_importURLMappings.log
- Check the log to see what time the rename was run
- Check jts.log to see what time JTS polls and stops polling other applications for rename status
2025-01-31T11:59:58,781+0100 [ Thread-51] [ INFO] ping.internal.ServerRenameOverallStatusRestService - Server rename details:Application polling is complete
- Look for the error to know which applications fail and at what time.
[ INFO] ping.internal.ServerRenameOverallStatusRestService - Server rename details:Unable to contact https://<server:port>/ccm/rootservices : java.net.SocketTimeoutException: connect timed out
- Check whether the application completes the rename process or fails with an error
2025-01-31T12:30:51,717+0100 [][com.ibm.team.repository.service.mapping.internal.ServerRenameService] [ INFO] sitory.service.mapping.internal.ServerRenameHelper - CRJAZ2327I Server rename completed successfully for the application in 20213 ms.
- State of the application when JTS was polling for status
2025-01-31T12:29:25,468+0100 [com.ibm.team.repository.service.mapping.internal.ServerRenameService] [ INFO] sitory.service.mapping.internal.ServerRenameHelper - CRJAZ2366I Processing server rename mapping events...
4. Link Validation
- During the validation step, each application fetches a list of projects. If there is a problem loading the project list, look in JTS and the corresponding application logs to understand why.
- If it shows many un-renamed links, find out why. Most of the time, it’s related to the targets in the mappings file.
Technotes:
5. Finalize rename
- Most of the time, the rename process cannot be finalized because of some other issues in the rename process.
6. After a successful rename
- There are actions required as post-rename tasks. See Impact of Server Rename on ELM.
Mappings File
What to consider when you review the mapping files:- Need context root
- Duplicated source or target URL is not allowed
- Too specific URL
- No multiple sources to the same target
- Include applications that are not part of the rename, but need to be renamed. For example, LQE, LDX, DWA, etc.
- Default port URL would have another pair with 443.URLs with 9443 do not.
- Ensure target URLs are expected/valid
- Use of IP address in the public URI?
Always include the context when running server rename for the ELM applications
source=https://source.fyre.ibm.com:9443/<context> target=https://target.fyre.ibm.com:9443/<context>Too Specific URL
Duplicated source or target URL is not allowed. No multiple sources to the same target
Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Include applications that are not part of the rename, but need to be renamed.
Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Default port URL would have another pair with 443.URLs with 9443 do not.
Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Ensure target URLs are expected/valid
Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Use of IP address in the public URI?
Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text
Common Issues
URL Length Some apps fail on the rename status page(collect screenshot) All pass on the status page, but some fail on the validation (fetching PAs) Sometime the validation is very slow. Some URLs not renamed (validation steps) https://www.ibm.com/docs/en/engineering-lifecycle-management-suite/lifecycle-management/7.1.0?topic=rename-verifying-urls-links-after-server#runverificationwizard JAS - make sure the feature is there, but is disabled while rename ==> look for the technote. https://jazz.net/wiki/bin/view/Deployment/ServerRenameAddendumQ&A
Can I rename only CCM and not JTS and other apps?- Yes, although CCM is the only application being renamed, the process to copy over the .mappingEvent file to all the applications remain the same.
- https://www.ibm.com/docs/en/engineering-lifecycle-management-suite/lifecycle-management/7.1.0?topic=rename-responding-server-status-errors
- repotools-jts -exportServerRenameURLMappingHistory toFile=history.txt
| APP_RENAME_STATUS: |
|---|
| 0 - Not started |
| 1 - In progress |
| 2 - Completed |
| 3 - Error |
| 4 - Validation |
| 5 - ReadOnly |
Need query
Related topics: Deployment web home, Deployment web home
External links:
Additional contributors: TWikiUser, TWikiUser
Copyright © by IBM and non-IBM 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.
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.