Hello, My apologies if this has been answered before, I have searched the archives. I am evaluating Zope as a content management system for websites I run at a college. We currently run IIS and MS Exchange on an NT server. What I would like to know is this... Eventually I will want to start using Zope to serve the site/s but I imaging I will need to change the port number so it runs from http://www.ourhost.com/ rather than http://www.ourhost.com:8080/ But I am worried that if I change this it will cause the exchange system to fail many of our users access their e-mail using the Exchange webmail system at http://www.ourpost.com/exchange Does anyone else using IIS and exchange have some guidance they can offer. Very impressed with Zope so far! Phil
Hi Philip,
Eventually I will want to start using Zope to serve the site/s but I imaging I will need to change the port number so it runs from http://www.ourhost.com/ rather than http://www.ourhost.com:8080/ But I am worried that if I change this it will cause the exchange system to fail many of our users access their e-mail using the Exchange webmail system at http://www.ourpost.com/exchange
Zope does *not* have to run its own web server, ZServer. Zope is primarily an application server. As far as I know, most people use Apache as a web server, and configure it to pass the requests to Zope. Now I don't know how to do *that* in IIS (though I've already done it with Apache). So what I would do would be to keep running ZServer, create a virtual host for Zope, and another one for Exchange. So zope would be served via www.ourhost.com and exchange via exchange.ourhost.com -a change that won't be too hard on your users. You can have virtual hosts in IIS, just like in Apache. You can find the how-to on zope.org/documentation. Hope this helps, Dimitris @ Nuclear
Dimitris Andrakakis wrote:
Now I don't know how to do *that* in IIS (though I've already done it with Apache). So what I would do would be to keep running ZServer, create a virtual host for Zope, and another one for Exchange. So zope would be served via www.ourhost.com and exchange via exchange.ourhost.com -a change that won't be too hard on your users.
Or perhaps you can have IIS direct everything EXCEPT things under the /exchange path to Zope. I, too, know nothing about configuring IIS, so you will have to look to someone else on the list, or your own ingenuity, for that. --sam
participants (3)
-
Dimitris Andrakakis -
HIND, Philip -
Samuel D. Gendler