The Jazz Team Server and Rational® Engineering Lifecycle Manager applications use links to store relationships between stored artifacts that may span applications or systems, and to communicate with each other and with non-Rational Engineering Lifecycle Manager applications. Server rename remaps existing URLs to new URLs to preserve the integrity of most links. Without the remapping, those links would be broken.
Performing a server rename is not without risk, particularly if the Rational Engineering Lifecycle Manager deployment includes integrations to other non-Rational Engineering Lifecycle Manager applications. Any change to a hostname has the potential to break links in the data or to prevent Rational Engineering Lifecycle Manager products from operating correctly.
If it is necessary to make changes to your topology, the preferred approach is to always do so in a way that maintains a stable URL, such as using DNS to route the host name to a different machine, or using a reverse proxy or virtual hosts. Where this is not possible, you can use server rename.
The following precautionary steps are recommended before you perform a server rename:
Server rename is only supported for Rational Engineering Lifecycle Manager v4.0.4 or later.
Renaming a Jazz Team Server or the Rational Engineering Lifecycle Manager applications requires a remapping of the URLs that are stored in Jazz Team Server resources. You can rename the entire URL prefix, which includes all parts of the URL through the context root, but does not include the context path of a resource. Specifically, you can rename the scheme (or protocol), host, domain, port, and context root.
For example, suppose you want to rename the following old URL in a pilot deployment, which is moving to a centrally managed data center:
This URL uses an unsecure protocol (http), the default port configuration (9443), and a default context root (relm).
This URL uses a secure protocol (https), changes the host name, uses the default port (unspecified in the URL), and a custom context root (relm14).
| Part of URI | Example | Comments |
|---|---|---|
| Scheme/Protocol | http, https, ftp, Remote Connection URL | Can be changed but using http is strongly discouraged. If changing from https to http or vice versa, it will be necessary to disable or enable security settings. For the Remote Connection URLs that are used with the lab management features of Quality Management, be sure to include all schemes (Remote Desktop/VNC/FTP/HTTP/Telnet). |
| Host/Domain | myhost.mydomain.com | Use the fully-qualified hostname. |
| Port | 9443 | Can be changed but you will need to update the port information in the application server. You can also use the default port by not specifying a port in the URL. See Mapping file for server rename for details about using the default port. |
| Context root | /jts /relm, /sparql, /lqe, /admin | To change the context root, you will need to perform some extra steps before you perform the rename. See Changing the context root for details. |