|
Home > Archive > Microsoft Content Management Server > September 2006 > MCMS 2002 Server Recommended Architecture
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 |
MCMS 2002 Server Recommended Architecture
|
|
|
| Hi
We are in the process of setting up a new environment for a new MCMS
site we are creating and I would appreciate any advice on our server
setup.
We are going to use:
Windows Server 2003
SQL Server 2005
MCMS 2002 SP2
Visual Studio 2005
..Net Framework 2.0
What we are currently thinking is to have a separate Development
Server, Authoring Server, Production Server and SQL Server. The
Production Server would be in the DMZ and the Development, Authoring
and SQL Servers would be internal network only. We were also thinking
that the Authoring Server and Production machines would share the same
MCMS database with the Authoring Server having read/write access and
Production only having read access. This way when a posting is approved
on the Authoring server it will be immediately available in the
Production/Live site.
Can anyone tell me what are the pros and cons of this setup?
We are also considering either having another separate server for
UAT/Staging or sharing this on either the Development server or
Authoring server. Can anyone make suggestions on this as well.
What is the recommended setup for a MCMS site?
Thanks for any advice.
| |
| Mei Ying [MVP] 2006-09-29, 1:32 am |
| Hi
Take a look at this thread that discusses one important consideration:
http://groups.google.com.sg/group/m...8c?dmode=source
You would probably want to be careful with applying changes to parts of the
content that aren't version. As long as production and staging share the
same database, you will face the same problem outlined in the thread.
regards
Mei Ying
"ni232" <ni232@hotmail.com> wrote in message
news:1159453726.298732.224370@m73g2000cwd.googlegroups.com...
> Hi
>
> We are in the process of setting up a new environment for a new MCMS
> site we are creating and I would appreciate any advice on our server
> setup.
>
> We are going to use:
> Windows Server 2003
> SQL Server 2005
> MCMS 2002 SP2
> Visual Studio 2005
> .Net Framework 2.0
>
> What we are currently thinking is to have a separate Development
> Server, Authoring Server, Production Server and SQL Server. The
> Production Server would be in the DMZ and the Development, Authoring
> and SQL Servers would be internal network only. We were also thinking
> that the Authoring Server and Production machines would share the same
> MCMS database with the Authoring Server having read/write access and
> Production only having read access. This way when a posting is approved
> on the Authoring server it will be immediately available in the
> Production/Live site.
>
> Can anyone tell me what are the pros and cons of this setup?
>
> We are also considering either having another separate server for
> UAT/Staging or sharing this on either the Development server or
> Authoring server. Can anyone make suggestions on this as well.
>
> What is the recommended setup for a MCMS site?
>
> Thanks for any advice.
>
|
|
|
|
|