Server rename process

Use this checklist to do a server rename.

If you are moving to new hardware, the source and target represent two distinct installations on two distinct physical systems. If you are using the same hardware (doing a rename in place), the source and target represent two distinct installations on the same physical system.

Checklist

If you want, print this topic, and check off the steps as you complete them. Where available, click the link in a step for more information.
Tip: To keep this topic open while you check details of a step, right-click the link and select Open Link in New Tab or Open Link in New Window, depending on your browser.
Note: This checklist is a guide to give you a view of the server rename process. For detailed instructions on how to do server rename, see Setting up a test staging environment with production data and Moving a pilot or full production deployment by using server rename.
  1. Review Server rename to understand the risks, precautions, restrictions, software requirements, and other things to know about server rename.
  2. Review Supported scenarios for using server rename to learn what scenarios are supported and not supported for server rename.
  3. Review Server rename topology diagrams and mapping file examples to help you do a server rename.
  4. Review Impact of server rename on the IBM Engineering Lifecycle Management to help you evaluate what impact there might be for your integration or integrations before you proceed with the actual steps of renaming a server.
  5. Review Planning your URIs to help you decide what URI to use for the server.
  6. In the target environment, install and configure IBM Engineering Lifecycle Management.
    Important: Do not run the setup tasks on the target server.
  7. In the source environment stop Jazz® Team Server, Engineering Lifecycle Management servers, and other affected servers.
  8. Back up the current source environment and restore it in the new target environment. For information about copying text indexes, configuration files, taking back up of the application database. And restoring them in the target environment. See step 3 of Moving a pilot or full production deployment by using server rename.
  9. In the target environment, verify that the source public URI is supported by updating the system hosts file.
    The following is a pseudo example of the entries in the hosts file:
    # ASSUMIN SOURCE DNS = mysource.ibm.com and my source IP ###.###.0.2
# ASSUMIN TARGET DNS = mytarget.ibm.com and my source IP ###.###.0.3
# RESOLVES_TO | DNS TO RESOLVE
###.###.0.3 mysource.ibm.com

    Similarly, you must also update the hostname of the database servers so that requests from the target server does not go to the source database.

  10. Review the URI aliases configured in all applications to prevent request from the target environment to the source environment.

    The URI aliases settings are available in the com.ibm.team.repository.url.aliases property in the teamserver.properties file of each application.

  11. In the target environment, start the Engineering Lifecycle Management applications to ensure artifacts that are copied from the source server are accessible.
  12. Make sure each Engineering Lifecycle Management application runs without any errors.
  13. If Data Collection Component is installed, complete the pre-rename steps for Data Collection Component
  14. If Lifecycle Query Engine and Link Index Provider (LDX) applications are installed, complete the pre-rename steps for Lifecycle Query Engine and LDX.
  15. In the target environment, generate or edit and verify your mappings file that you will use to rename your Engineering Lifecycle Management servers; see Preparing the mapping file.
  16. In the target environment, fix any mappings file errors; see Fixing generateURLMappings errors.
  17. Obtain a feature key file from IBM Support. Mention that you are requesting a server rename feature key file. The key file is named ImportURLMappings.activate. Submit the mapping file generated in step 14 - 16 along with the request.
  18. In the target environment, copy the ImportURLMappings.activate file to the JazzInstallDir/server/conf directory for the applications that you rename. The key is only needed to run the repotools importURLMappings command.
  19. In the target environment, shut down the Engineering Lifecycle Management applications that are started in step 10.
  20. In the target environment import the mappings file to the target JTS.
  21. If Lifecycle Query Engine and Link Index Provider applications are installed, complete the During server rename.
  22. In the target environment, start JTS and the distributed Engineering Lifecycle Management applications on the target servers.
  23. In the target environment:
    1. Go to the rename status page and wait for application renaming to complete.
    2. Verify the renamed application data in read-only mode.

    See Verifying URLs and links after a server rename.

  24. In the target environment, do the post-rename steps, see Completing the server rename verification process.
  25. Register the applications in the JTS application, see Registering applications with Jazz Team Server.
  26. For Lifecycle Query Engine and Link Index Provider, complete the post-rename steps for Lifecycle Query Engine and Link Index Provider
  27. For Data Collection Component, complete the post-rename steps for Data Collection Component.
  28. The servers are fully operational now.
  29. For Report Builder, complete the post-rename steps for Report Builder.