Sent by Art Bergquist on 05/16/2015 11:21:19 AM:
I'm in the process of migrating a FoxWeb web site from Windows Server 2003 (which, of course, is about to be no longer supported by Microsoft) to Windows Server 2008. The Windows Server 2008 has already been set up and I can access it via RDC.
The (current) web site is 24-7 so the client wants the ability to first test the new web site on Windows Server 2008 while still running it (i.e., maintain uptime) on Windows Server 2003. The new web server (Windows Server 2008) already has access to a copy of the database on it (via mapped drives to a new database server) so that it would interact with the new database; as a result, it's a totally separate (encapsulated/isolated) environment.
It's my understanding that we could (temporarily) refer to the new website with its IP address; for example, if the new server's IP address is 18.104.22.168, then we could test the new web site by going to the following URL:
Once we're satisfied that the new web site (on Windows Server 2008) works as well (or better) than the current web site (on Windows Server 2003), then we would have to transfer the domain (i.e., the user-friendly name of the web site) from the current (Windows Server 2003) to the new (Windows Server 2008).
1. Is the above correct? (If not, feel free to correct how I'm wording the scenario as well; I want to not only solve this issue but also to state it correctly as well.)
2. Also, per the "Locating and Addressing Scripts" FoxWeb help topic, I'm thinking that it would be a good idea to first switch all the URLs within the FoxWeb web site (except for the main web page) from Fully Qualified URLs to Relative URLs. Would you also recommend that?