Changing the public URL by using server rename

This section discusses strategies and instructions for changing the public URL for IBM Engineering Lifecycle Management (ELM) version 4.0.1 and later applications by using server rename.

Important: Server rename operations change the public URLs of referenced artifacts in an IBM Engineering Lifecycle Management (ELM) deployment and might affect external links. For example, URL changes can invalidate external references such as those in email notifications, or external Open Services for Lifecycle Collaboration (OSLC) references from tools that do not support server rename. If you perform a server rename in a production environment, these changes might disrupt users. However, the server rename operation is useful for routine administrative tasks, such as refreshing data in a staging environment by using a snapshot of the production environment.

To perform a server rename, you must obtain a feature key file from IBM Software Support. When you contact IBM Support, mention that you are requesting a server rename feature key file. The key file is named ImportURLMappings.activate. Copy the file to the JazzInstallDir/server/conf directory for the applications that you will rename. The key is only needed to execute the repotools importURLMappings command.

For advanced or deployment-specific information about server rename including best practices and limitations and workarounds, see the Server rename section of the Deployment wiki.

  1. Planning for server rename
  2. Impact of server rename on the IBM Engineering Lifecycle Management
  3. Preparing Jazz Authorization Server for server rename
  4. Performing a server rename
  5. Verifying and troubleshooting server rename
  6. Move the CCM or RMM application to a new location