Moving entire Fortress installation

jsiegmund · Post by **jsiegmund** » Mon Jul 14, 2008 9:42 am

Hello,

we're currently in the process of migrating our entire serverpark to new servers. I have to design a plan for migrating the Fortress environment to it's new location.

Currently both front and back-end apps are setup on the same machine and hosted at port 80; a fairly regular setup I think.

In the new situation; the back-end and front-end will be devided. The back-end will be served by a SQL server in our own network, the front-end will be hosted by a server in our DMZ (so we can connect to it globally via https). Maybe the front-end will run on a different port as well, I'm not quite sure about that yet (is that nescessary to make it available at fortress.company.com?).

What's the best way of migrating everything and offcourse update the clients with the new addresses? Moving the databases isn't that hard. Can I setup Fortress on the front-end again after I've manually moved the databases to the new SQL Server instance?

Please advice on this

Beth · Post by **Beth** » Mon Jul 14, 2008 10:10 am

You will want to use the same instructions that are used for Vault: Moving Vault (Server and Database) to a new machine. Just make sure that you move the sgvault, sgdragnet, and sgmaster databases for Fortress.

For installing in a DMZ, you will most likely want to install Fortress under a custom account that has access to both the DMZ machine and the SQL machine.

is that necessary to make it available at fortress.company.com?

No, that isn't a requirement. Your users could use an IP address to connect. Or you could make some complex name such as XYZ123ABC.company.com if you are concerned about outsiders randomly checking fortress.company.com (sort of like setting the password to "password," it's common enough to make a good guess). Or you could use some other external IP address that is only on your firewall/router that would then forward it to the appropriate area.

jsiegmund · Post by **jsiegmund** » Tue Jul 15, 2008 1:12 am

Beth wrote:
is that necessary to make it available at fortress.company.com?
No, that isn't a requirement. Your users could use an IP address to connect. Or you could make some complex name such as XYZ123ABC.company.com if you are concerned about outsiders randomly checking fortress.company.com (sort of like setting the password to "password," it's common enough to make a good guess). Or you could use some other external IP address that is only on your firewall/router that would then forward it to the appropriate area.

Hi Beth, thanks for the link to the KB article, I should have searched a bit better I guess

. As for above quote; I think you misunderstood my question.

On our webserver there will be multiple webapplication made available to our employees, one of them is fortress. Now I would like those apps to be available via https://fortress.company.com and http://otherapp.company.com; so that the users have something easy to remember. That means I'll have to forward those addresses like following:

https://fortress.company.com --> https://serverip/Fortress
https://otherapp.company.com --> http://serverip/Otherapp

But I don't know if that's possible in IIS; maybe I have to run both apps on different ports so the forwarding is like this:
https://fortress.company.com --> https://serverip:10001
https://otherapp.company.com --> https://serverip:10002

This might be more of an IIS based question, but perhaps you guys have some experience in setting up server systems like this.

Beth · Post by **Beth** » Tue Jul 15, 2008 7:54 am

Both ways you mention are possible. You could either make each have it's own website in IIS and give each a different port, or you could use host headers so that it knows that https://fortress.company.com goes to https://serverip/Fortress. Which method you use is a matter of preference.