It's all about the answers!

Ask a question

Server Rename Status fails with CRJAZ2373E. How do I make it look at application /ccm instead of /jazz?


Kishore Nagareddy (3026) | asked Dec 15 '14, 2:36 p.m.
retagged Dec 15 '14, 2:51 p.m. by Laura W. Hinson (16126)
 I'm trying to perform a server rename (Production to Staging) to create a test sandbox of the production server. The importing of the database and the URL mappings were successful. When I start the server and checked the status of the rename using the url https://myhost.mycompany.com:9443/jts/serverRenameStatus, I see the error following error:

############################
/jazz
The server could not retrieve the server rename status for application "/jazz". Please consult the log files for more detailsID CRJAZ2373E
############################

I cannot finalize the server rename due to this error. I'm guessing that the reason for this error is that the application name for the source host had /jazz and the target host has /ccm. I was under the impression that the importURLMappings step will take take care of this change. 
Why is the server still looking at /jazz instead of /ccm? How do I change this to look at /ccm instead of /jazz to retrieve the server rename status of the /ccm application and then be able to complete the finalize step?

Accepted answer


permanent link
Lily Wang (4.9k714) | answered Dec 16 '14, 1:48 a.m.
Per my understanding, the server rename would change the server URL from something like "https://myhost.mycompany.com:9443/jazz" to "https://myhost.mycompany.com:9443/ccm".
It will not change the entry's name (/jazz) in registered applications. You need to change it manually after complete the server rename.

It seemed the server rename you performed includes production to staging and changing the context root. I suggest you restore the database from backup and do it again.
Please make sure you also follow the steps in Changing the Context Root (https://jazz.net/help-dev/clm/index.jsp?re=1&topic=/com.ibm.jazz.install.doc/topics/t_change_context_root.html) scenario.
Before the server rename, you may need to check the "Registered Applications" from /jts/admin to ensure all the information is correct.
Kishore Nagareddy selected this answer as the correct answer

Comments
Kishore Nagareddy commented Dec 16 '14, 2:20 p.m.

Thanks Lily. 

Here is what I had to do to make this work. 
1. Re-installed the server (4.0.7) with the context root changed to /jazz instead of the default /ccm. 

2. Imported the data (jts and ccm)

3. Imported the URL mappings. The url mapping for the /jazz application in the mappings file was set to the following:
source=https://sourcehost.mycompany.com:30001/jazz
target=https://targethost.mycompany.com:9443/jazz

4. Started the server and went to https://targethost.mycompany.com:9443/jts/serverRenameStatus
Online server rename was initiated and completed successfully. 

My source server was on 4.0.7 with WAS and DB2 and the target server is version 4.0.7 with the default Tomcat and Derby.

Your answer


Register or to post your answer.