The observation here is correct.  The rename of the Setup server (based on the Jazz Team Server) itself is going through a "reset" process.  It would essentially just require the user to re-register the user credential on the Setup server, while the configuration data input by the user previously would stay intact for access (i.e. the user input fields on the setup wizard pages would still be populated with those entered before).

Hope this helps.

So really I can just restore the empty derby database and change the its properties so it thinks it is a new setup and run through the setup dialog and that will essentially do the server rename.  The documentation talks about doing a clm like server rename - do the generate URLMappings but it never says anything about importing them back in.  I believe that is very confusing.  If what I say at the beginning can be done I think that is much clearer 

Actually, the "serverrename" operation is still required (notice that it is specific to RRDI/Insight, bot the Jazz Team Server).  The operation will go through the "user input" data (NOT in the derby-based repository Jazz Team Server uses) which may contain server name references, and make necessary changes due to the server rename.

So my first note is the correct way.  Export the URLMappings, reset the derby database and its properties and then import the mappings file?  If so the documentation never says anything about doing the last step (it refers to the clm documentation but says nothing about the serverrename.bat file that was mentioned for the export).  I think the documentation needs to be updated if the first sentence in the comment is correct. 

The "importing" part of the URLMappings is described in a separate topic (the next topic in the same folder in the Info Center) -- Post-rename tasks