I was reading the CLMHELP 4.0.4 contents wrt Changing the public URL by using server rename.

I noticed something that I think should be clarified.

In the 2 topics

– Scenario: Moving a pilot or full production deployment using server rename

– Scenario: Setting up a test staging environment with production data

If you look under Procedure

Step 5. Log into the Jazz Team Server at https:// new host : port /jts/serverRenameStatus. This starts the actual renaming process. When the rename is complete, you will be able to verify the rename and take any corrective action that is necessary. See Verifying URLs and links after a server rename for details.

My comments are as follows:

The procedure is asking to log into https:// newhost : port /jts/serverRenameStatus.

In my opnion, this URL is misleading because in the rename scenarios, you have the option to rename JTS and/or any of the CLM applications.

Now, if you only need to rename one or all of CLM applications but NOT the JTS server, then you obviously will not be logging into https:// new host : port /jts/serverRenameStatus but rather logging into the source JTS URL because this URL has not changed.

This being said, if the JTS URL does not change, the procedure should note this.

The unchanged JTS URL will be something like this

https://source JTS host:port/jts/serverRenameStatus

Thanks,

Pierre