Answers to: Any harm keeping 2 distinct URLs for JTS and RTC respectively on a single server?https://jazz.net/forum/questions/256465/any-harm-keeping-2-distinct-urls-for-jts-and-rtc-respectively-on-a-single-server<p> We are tasked with upgrading RTC 4.0.7 to 6.0.6 via 5.0.2, as this is a 2-step upgrade.
</p><div>
<br>
<div>
Below are what have been either in place, or planned and procured, i.e. we are not allowed to change:
</div>
</div>
<div>
<ul>
<li>
4.0.7 JTS and RTC are on 2 separate Linux hosts
</li>
<ul>
<li>
on PRD: jtsPfqn and rtcPfqn with public URI/contextRoot <a href="https://jts.Ddom.com/jts">https://jts.Ddom.com/jts</a> and <a href="https://jazz.Ddom.com/jazz">https://jazz.Ddom.com/jazz</a> respectively
</li>
<li>
on TST: jtsTfqn and rtcTfqn with public URI/contextRoot <a href="https://jtsTfqn/jts">https://jtsTfqn/jts</a> <a href="https://jazzTfqn/jazz">https://jazzTfqn/jazz</a> respectively on domain Tdom.com.
</li>
</ul>
</ul>
<ul>
<li>
6.0.6 will be on a new server, with topology changed to single host
</li>
<ul>
<li>
on PRD: nCLMpFQN
</li>
<li>
on TST: nCLMtFQN
</li>
</ul>
</ul>
<ul>
<li>
MS SQLserver DBs are on Windows servers, and 6.0.6 DBs would also be on new servers.
</li>
</ul>
<div>
We are to plan the upgrade through the shortest route possible, while keeping it transparent to users.
</div>
</div>
<div>
<br>
</div>
<div>
We are planning to use TST env as POC for PRD, and have cloned the PRD DBs over to TST, with DB backup synced to AppSide index backup.
</div>
<div>
<br>
</div>
<div>
Our proposed use of hosts file spoofing on TST was shot down by management for the risk of contamination of PRD, as PRD and TST are not on isolated networks. So we will have to recourse to "server rename" on TST to be able to start the upgrade with PRD-cloned DBs.
</div>
<div>
<br>
</div>
<div>
Here is our current plan:
</div>
<div>
<ul>
<li>
Create 2 DNS aliases for the new TST server nCLMtFQN:
</li>
<ul>
<li>
JTStst.Ddom.com
</li>
<li>
JAZZtst.Ddom.com
</li>
</ul>
<li>
"Server Rename" the 2 PRD public URIs to the 2 TST public URIs, constructed with the 2 new DNS aliases on TST
</li>
<ul>
<li>
<a href="https://jts.Ddom.com/jts">https://jts.Ddom.com/jts</a> to <a href="https://JTStst.Ddom.com/jts">https://JTStst.Ddom.com/jts</a>
</li>
<li>
and <a href="https://jazz.Ddom.com/jazz">https://jazz.Ddom.com/jazz</a> to <a href="https://JAZZtst.Ddom.com/jazz">https://JAZZtst.Ddom.com/jazz</a>
</li>
</ul>
<li>
Flip the 2 DNS aliases JTStst and JAZZtst over to the old JTS server jtsTfqn and the old RTC server rtcTfqn respectively.
</li>
<li>
Validate the cloned DBs with 4.0.7
</li>
<li>
Install 5.0.2 JTS and RTC on the old JTS server jtsTfqn
</li>
<li>
Flip the DNS JAZZtst over to the old JTS server jtsTfqn (from the old RTC server rtcTfqn) to accommodate the change of topology to single host for 5.0.2
</li>
<li>
Upgrade to 5.0.2
</li>
<li>
Light on test of 5.0.2 with existing TST DBserver (SQLserver 2008)
</li>
<li>
Copy the DBs to the new TST DBserver (SQLserver 2012)
</li>
<li>
Validate 5.0.2
</li>
<li>
Flip back the 2 DNS aliases to the new TST appServer nCLMtFQN
</li>
<li>
Install and upgrade to 6.0.6
</li>
<li>
Validate 6.0.6
</li>
</ul>
<div>
We will proceed same on PRD without any "server rename" as the start-from DBs are the same existing ones on PRD.
</div>
<div>
<br>
</div>
<div>
There are worries about the unusual use of 2 distinct public URIs for single host topology for JTS and RTC respectively.
</div>
<div>
We couldn't think of or google for any harm using the same 2 public URIs on a single host topology. We have also validated the use of 2 distinct public URIs on POC with a fresh install of 6.0.6. Pls let us know if we miss any consequences serious enough having to:
</div>
<div>
<ul>
<li>
Add a topology conversion step on 4.0.7 to consolidate to 1 public URI, requiring
</li>
<ul>
<li>
The addition of a "server rename" on PRD, which is in Production, and clearly outside of the supported cases, against the severe warnings from IBM on the use of "server rename" below.
</li>
<li>
An install of 4.0.7 to bring RTC to the JTS server on both TST and PRD
</li>
</ul>
<li>
Be considered unworkable that "server rename" on PRD has to be used as last resort.
</li>
<li>
IBM warnings on using "server rename"<b> *** Important:<span> Server rename is a complex and potentially disruptive operation because correcting the stored links to the server from other applications and systems may be difficult or impossible. Server rename is only supported for a specific set of scenarios and requires careful planning. Use server rename only as a last resort when other approaches are unworkable.</span><span>"</span></b><span><b>.</b> </span>
</li>
</ul>
</div>
<div>
<br>
</div>
<div>
<br>
</div>
</div><p></p>enMon, 10 Sep 2018 09:05:41 -0400Comment by l4short on l4short's questionhttps://jazz.net/forum/questions/256465/any-harm-keeping-2-distinct-urls-for-jts-and-rtc-respectively-on-a-single-server#256484<p>
</p><ul>
<li>
cont'd ...
</li>
<li>
Copy the DBs to the new PRD DBserver (SQLserver 2012)
</li>
<li>
Validate 5.0.2
</li>
<li>
Flip the 2 DNS aliases jts and rtc to the new PRD appServer nCLMpFQN
</li>
<li>
Install and upgrade to 6.0.6
</li>
<li>
Validate 6.0.6
</li>
</ul><p></p>l4shortMon, 10 Sep 2018 09:04:52 -0400https://jazz.net/forum/questions/256465/any-harm-keeping-2-distinct-urls-for-jts-and-rtc-respectively-on-a-single-server#256484Comment by l4short on l4short's questionhttps://jazz.net/forum/questions/256465/any-harm-keeping-2-distinct-urls-for-jts-and-rtc-respectively-on-a-single-server#256483<p> PRD upgrade
</p><ul>
<li>
Shut down RTC and JTS.
</li>
<li>
Install 5.0.2 JTS and RTC on the old JTS server jtsPfqn
</li>
<li>
Flip the DNS rtc over to the old JTS server jtsPfqn (from the old RTC server rtcPfqn) to accommodate the change of topology to single host for 5.0.2
</li>
<li>
Upgrade to 5.0.2
</li>
<li>
Light on test of 5.0.2 with existing PRD DBserver (SQLserver 2008)
</li>
<li>
... continued
</li>
</ul><p></p>l4shortMon, 10 Sep 2018 09:05:41 -0400https://jazz.net/forum/questions/256465/any-harm-keeping-2-distinct-urls-for-jts-and-rtc-respectively-on-a-single-server#256483