Intranet won't link to 2nd server without hard coded URL?

I have 2 servers, both running http, our Intranet is on one of them, but we are moving over to the other server slowly…

With this goal in mind, I created 2 databses on the new server that we wanted to link to from the intranet. I created a text link, set it up in the outline as a Named Element, used the Properties box to pick the database from the list, and the frameset from the list. All seemed ok, no errors.

When I refreshed the Intranet, the text for the link was there… but it wasn’t “hot”. [no link] The only way I could get it to link, was to enter it as a URL and paste in the url as:

http://DomSvrName/FolderName/DBname.nsf

any clues on this? we have a LOT of databases to move to the new server and I don’t want to hard code thi s for every one of them.

Ruth

Subject: Intranet won’t link to 2nd server without hard coded URL ?

This is normal behavior - the http stack on server1 won’t get data from a database on server2. The user session has to be on server 2 to connect to that data.

Subject: plan…

so basically i can’t move this intranet a little at a time… i have to move it all at once?

Subject: RE: plan…

That’s one way to do it, yes. If I were in this situation, I would create replicas of all of the databases on the new server. The new server could have any IP/host name you want, and you could do testing there as well to make sure everything works on the new system.

Then, stop http on the old system, do a full replication to the new one, switch the old server to a new (temporary) host name and new IP address (either static or dynamic). Shut it down, then ‘move’ the IP information (IP address, host name, etc.) to the new server and reboot it. You’ll have a certain amount of downtime, but it makes for a pretty clean switch.