|
Home > Archive > Microsoft Content Management Server > August 2004 > Split CMS implementation over 3 machines?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Split CMS implementation over 3 machines?
|
|
| Ciaran 2004-08-13, 7:48 am |
| We are currently planning a CMS implementation project, and the client
was recommended (by someone else) to split CMS over three boxes: one
for IIS web server, one for 'CMS', and the third for SQL Server, to
house the content repository. We are familiar with a 2 box approach,
where IIS/CMS reside on one machine, and SQL Server on another, but
not with this three-box approach. Our understanding was that since CMS
integrates ISAPI filters with IIS in order to get at the calls that it
should handle, that they need to be integrated together.
Is it possible to split IIS from CMS components in such a way? What
would be the circumstances under which this might be suitable (or not
suitable)?
How would we set up IIS and CMS in order to function in this way?
thanks,
Ciaran
| |
| Stefan [MSFT] 2004-08-13, 7:48 am |
| Hi Cirian,
MCMS needs to be on the IIS server.
MCMS is actually the web server - so there is no way to split it from IIS.
If you need such a 3-tier achitecture you could implement it by using
WebServices to communicate from the front end IIS server to the IIS server
on the CMS box - but I would not recommend it.
Cheers,
Stefan.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
MCMS FAQ:
http://download.microsoft.com/downl...6a/MCMS+2002+-+(complete)+FAQ.htm
MCMS Blog: http://blogs.msdn.com/stefan_gossner/category/4983.aspx
MCMS Sample Code:
http://www.gotdotnet.com/community/...t+S
erver
MCMS Whitepapers and other docs:
http://blogs.msdn.com/stefan_gossne...2/07/41859.aspx
--------------------------------
"Ciaran" <ciaran.fletcher@ie.fujitsu.com> wrote in message
news:fc1e9738.0408130057.3a72fd03@posting.google.com...
> We are currently planning a CMS implementation project, and the client
> was recommended (by someone else) to split CMS over three boxes: one
> for IIS web server, one for 'CMS', and the third for SQL Server, to
> house the content repository. We are familiar with a 2 box approach,
> where IIS/CMS reside on one machine, and SQL Server on another, but
> not with this three-box approach. Our understanding was that since CMS
> integrates ISAPI filters with IIS in order to get at the calls that it
> should handle, that they need to be integrated together.
>
> Is it possible to split IIS from CMS components in such a way? What
> would be the circumstances under which this might be suitable (or not
> suitable)?
> How would we set up IIS and CMS in order to function in this way?
>
> thanks,
> Ciaran
| |
| Spencer Harbar [MVP] 2004-08-13, 7:48 am |
| MCMS is effectively the web server (or part of it).
The whole idea of the dynamic compilation of templates and content at
runtime means that the "content server" elements of MCMS must be on the IIS
box.
It sounds like the third party doesn't understand MCMS's architecture.
Unless you are using web services (additional bespoke development time and
effort) you need IIS and MCMS on the same box(es).
hth
Spence
www.mcmsfaq.com
"Ciaran" <ciaran.fletcher@ie.fujitsu.com> wrote in message
news:fc1e9738.0408130057.3a72fd03@posting.google.com...
> We are currently planning a CMS implementation project, and the client
> was recommended (by someone else) to split CMS over three boxes: one
> for IIS web server, one for 'CMS', and the third for SQL Server, to
> house the content repository. We are familiar with a 2 box approach,
> where IIS/CMS reside on one machine, and SQL Server on another, but
> not with this three-box approach. Our understanding was that since CMS
> integrates ISAPI filters with IIS in order to get at the calls that it
> should handle, that they need to be integrated together.
>
> Is it possible to split IIS from CMS components in such a way? What
> would be the circumstances under which this might be suitable (or not
> suitable)?
> How would we set up IIS and CMS in order to function in this way?
>
> thanks,
> Ciaran
| |
| Ciaran 2004-08-13, 5:51 pm |
| Spence,
I agree completely. I have had other input that suggested that if you
staged the site into flat HTML, then you could have this on IIS, and
use the CMS and SQL boxes for Content production, but like you say,
that removes all the dynamic elements, and is not suitable for the
particular solution.
Many thanks to you and Stefan,
Ciaran
"Spencer Harbar [MVP]" <spence@harbar.net> wrote in message news:<uO1ygeRgEHA.3916@TK2MSFTNGP11.phx.gbl>...[vbcol=seagreen]
> MCMS is effectively the web server (or part of it).
> The whole idea of the dynamic compilation of templates and content at
> runtime means that the "content server" elements of MCMS must be on the IIS
> box.
>
> It sounds like the third party doesn't understand MCMS's architecture.
> Unless you are using web services (additional bespoke development time and
> effort) you need IIS and MCMS on the same box(es).
>
> hth
> Spence
> www.mcmsfaq.com
>
>
>
>
> "Ciaran" <ciaran.fletcher@ie.fujitsu.com> wrote in message
> news:fc1e9738.0408130057.3a72fd03@posting.google.com...
|
|
|
|
|