Mapping a file for server rename

The structure of the mapping file is generated by using the generateURLMappings command and provides instructions on how to edit the mapping file for your deployment.

Important: The default port used for deployments on containers is 443, but for on-premises installation it is 9443.

When you are ready to generate a mapping file, follow the instructions in Preparing the mapping file for Engineering Lifecycle Management on Hybrid Cloud. The mapping file contains source-target URL pairs for the Jazz® Team Server, its registered IBM Engineering Lifecycle Management applications, and other URLs contributed by the applications. The URLs are divided into two types:

URL pairs that indicate URLs that change during the rename: The URL pairs that are part of the rename include anything under the domain of the Jazz Team Server. It includes the Jazz Team Server public URL, application public URLs, and other URLs contributed by applications.

Affected URLs that indicate external systems by a rename: Affected URLs include any other systems that interact with this topology but are not under the domain of this Jazz Team Server. An Engineering Lifecycle Management application that is registered to a different Jazz Team Server but is friends with this Jazz Team Server represents an affected URL. An external integration such as ClearQuest® also represents an affected URL.

Description of mapping file

#/qm 
source=https://source.example.org:443/qm 
target=https://target.example.org:443/qm
 
#/qm 
source=https://source.example.org/qm 
target=https://target.example.org/qm 

#/ccm 
source=https://source.example.org:443/ccm
target=https://target.example.org:443/ccm 

#/ccm 
source=https://source.example.org/ccm 
target=https://target.example.org/ccm 

#/ENI 
source=https://source.example.org:443/ENI 
target=https://target.example.org:443/ENI

#/ENI 
source=https://source.example.org/ENI 
target=https://target.example.org/ENI 

#/dcc 
source=https://source.example.org:443/dcc 
target=https://target.example.org:443/dcc 

#/dcc 
source=https://source.example.org/dcc 
target=https://target.example.org/dcc 

#/gc 
source=https://source.example.org:443/gc 
target=https://target.example.org:443/gc 

#/gc 
source=https://source.example.org/gc 
target=https://target.example.org/gc 

#/rm 
source=https://source.example.org:443/rm 
target=https://target.example.org:443/rm 

#/rm 
source=https://source.example.org/rm 
target=https://target.example.org/rm 

#/rs 
source=https://source.example.org:443/rs 
target=https://target.example.org:443/rs 

#/rs 
source=https://source.example.org/rs 
target=https://target.example.org/rs 

#/lqe 
source=https://source.example.org:443/lqe 
target=https://target.example.org:443/lqe 

#/lqe 
source=https://source.example.org/lqe 
target=https://target.example.org/lqe 

#source.example.org/jts 
source=https://source.example.org:443/jts 
target=https://target.example.org:443/jts 

#source.example.org/jts 
source=https://source.example.org/jts 
target=https://target.example.org/jts 

#Additional URLs included in rename by source.example.org/jts 
#(URL Alias Property - Alias of https://source.example.org/ccm/ 
#This URL was also contributed by "/qm" 
#This URL was also contributed by "/ccm" 
#This URL was also contributed by "/gc" 
#This URL was also contributed by "/rm") 
source=https://ibm-elm-ccm:20006/ccm/;https://source.example.org:443/ccm/ 
target=https://ibm-elm-ccm:20006/ccm/;https://target.example.org:443/ccm/ 
#(ELM Help URL) 
source=http://www.ibm.com/docs/SSF34G 
target=http://www.ibm.com/docs/SSF34G 
#(This URL was generated as an alternate URL to http://www.ibm.com/docs/SSF34G, which contains the default port or has no port specified.) 
source=http://www.ibm.com:80/docs/SSF34G 
target=http://www.ibm.com:80/docs/SSF34G

The generated mapping file is a template that must be edited before running importURLMappings. It is important to understand that the systems in topology are renamed correctly. The file includes the URL pairs that are part of the rename. In this example, you can see URL pairs for the public URL of the Jazz Team Server and all its registered applications, you can also see URL pairs that are contributed by applications, such as the Engineering Lifecycle Management helps URL pair that contributes the Jazz Team Server and the converter URL pair contributed by the DOORS® application.

Check each URL and determine the dynamic. Update the targets for any source URL that is renamed with new values. If a source URL is not renamed, comment out the pair by using #.

# JTS 
#source=https://clmhost.example.org:443/jts 
#target=https://clmhost2.example.org:443/jts

Note: The mapping file also contains a list of affected URLs that are commented out. These URLs are not part of the rename, but get impacted by the changing URLs. Unless you need to mask out production URLs, you should leave these URLs commented out as they are only for reference purpose. If you are in a staging environment, you should always mask out affected URLs to ensure that there is no cross-linking between the staging and production servers.