|
Home > Archive > Microsoft Content Management Server > October 2004 > Site Deployment Best Practices
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 |
Site Deployment Best Practices
|
|
| Justin 2004-10-26, 2:46 am |
| Hi all,
AFAIK, there are two ways of deploying MCMS content between dev, authoring
and production servers.
a) point all servers to the one database thus all servers are syncronized
automatically.
b) create deployment scripts and copy the sdo file to each machine to copy
content.
My questions are :
1) what are the pros/cons of each method, how should I choose which way to
go?
2) for non-cms assets I read using Application Center is the recommended way
to deploy. I'm not sure if I need to go this far as non-cms assets wont be
deployed nearly so often. Can anyone give me any real-world advise on how to
deploy a medium size application? Just manually copy files?
Thanks
| |
| Justin 2004-10-26, 7:46 am |
| Hi,
Yes, I've got that document, but it doesn't really answer my question.
"Mei Ying [MVP]" <anonymous@discussions.microsoft.com> wrote in message
news:112901c4bb23$b0df4c10$a501280a@phx.gbl...[vbcol=seagreen]
> Hi
>
> Have you see this article?
> http://msdn.microsoft.com/library/en-
> us/CMS2002_GB/htm/mcms2002_perf_deploy_abstract_msdn_xugb.a
> sp?frame=true
>
> I'd personally recommend planned releases that do not
> involve App Centre for solutions that aren't massive. App
> centre does a lot more than copy files.
>
> HTH
> Mei Ying
> ---
> Blog: http://meiyinglim.blogspot.com
> Contact: meiyinglim@hotmail.com
> ---
> between dev, authoring
> are syncronized
> each machine to copy
> choose which way to
> the recommended way
> cms assets wont be
> world advise on how to
> files?
| |
| Stefan [MSFT] 2004-10-26, 7:46 am |
| Hi Justin,
for a load balanced production system you could point all front end servers
to one database to ensure that all web servers are always in sync.
To sync the files you can use Application Center, RoboCopy, Xcopy or your
own scripts.
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
--------------------------------
"Justin" <justin_dbd@nospam.nospam> wrote in message
news:O9JSrhxuEHA.3840@TK2MSFTNGP12.phx.gbl...
> Hi all,
>
> AFAIK, there are two ways of deploying MCMS content between dev, authoring
> and production servers.
>
> a) point all servers to the one database thus all servers are syncronized
> automatically.
> b) create deployment scripts and copy the sdo file to each machine to copy
> content.
>
> My questions are :
>
> 1) what are the pros/cons of each method, how should I choose which way to
> go?
> 2) for non-cms assets I read using Application Center is the recommended
way
> to deploy. I'm not sure if I need to go this far as non-cms assets wont be
> deployed nearly so often. Can anyone give me any real-world advise on how
to
> deploy a medium size application? Just manually copy files?
>
> Thanks
>
>
| |
| Mei Ying [MVP] 2004-10-26, 5:48 pm |
| Hi
Right, you wanted some honest feedback about each approach :-)
This has been discussed before in a separate thread: Have a look
here -http://groups.google.com.sg/groups?hl=en&lr=& selm=035701c2e8a5%2477fdba00%242f01280a%
40phx.gbl
--
regards
Mei Ying
---
Blog: http://meiyinglim.blogspot.com
Contact: meiyinglim@hotmail.com
---
"Justin" <justin_dbd@nospam.nospam> wrote in message
news:Oc7xy30uEHA.2536@TK2MSFTNGP11.phx.gbl...
> Hi,
>
> Yes, I've got that document, but it doesn't really answer my question.
>
> "Mei Ying [MVP]" <anonymous@discussions.microsoft.com> wrote in message
> news:112901c4bb23$b0df4c10$a501280a@phx.gbl...
>
>
| |
| Justin 2004-10-27, 2:47 am |
| Thanks for your help guys, I'm nearly there, but I still feel I'm missing
something.
What I considered is to have this configuration:
Server 1: MCMS Development, Development Sql Server
Server 2: MCMS Authoring/Staging
Server 3: MCMS Production
Server 4: Shared Sql Server for Servers 2 and 3
In this way I thought I could get the benefits of security, i.e. having
Server 3 as read-only while having the immediate publish capability that
would come from Server 2 and 3 using the same Sql Server instance... there
would be no need for SDO scripts etc.
Does that make sence, is this a legitimate configuration, or are there other
factors I've not thought of?
Thanks
"Justin" <justin_dbd@nospam.nospam> wrote in message
news:O9JSrhxuEHA.3840@TK2MSFTNGP12.phx.gbl...
> Hi all,
>
> AFAIK, there are two ways of deploying MCMS content between dev, authoring
> and production servers.
>
> a) point all servers to the one database thus all servers are syncronized
> automatically.
> b) create deployment scripts and copy the sdo file to each machine to copy
> content.
>
> My questions are :
>
> 1) what are the pros/cons of each method, how should I choose which way to
> go?
> 2) for non-cms assets I read using Application Center is the recommended
way
> to deploy. I'm not sure if I need to go this far as non-cms assets wont be
> deployed nearly so often. Can anyone give me any real-world advise on how
to
> deploy a medium size application? Just manually copy files?
>
> Thanks
>
>
| |
| Stefan [MSFT] 2004-10-27, 7:46 am |
| Hi Justin,
this is an appropiate configuration but be aware that there will be no
staging environment as the authored changes will go live asap.
In addition you should not use Moderators in this configuraton as pages
waiting for moderator approval do not have a live version.
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
--------------------------------
"Justin" <justin_dbd@nospam.nospam> wrote in message
news:eg3qJ19uEHA.2116@TK2MSFTNGP14.phx.gbl...
> Thanks for your help guys, I'm nearly there, but I still feel I'm missing
> something.
> What I considered is to have this configuration:
>
> Server 1: MCMS Development, Development Sql Server
>
> Server 2: MCMS Authoring/Staging
>
> Server 3: MCMS Production
>
> Server 4: Shared Sql Server for Servers 2 and 3
>
> In this way I thought I could get the benefits of security, i.e. having
> Server 3 as read-only while having the immediate publish capability that
> would come from Server 2 and 3 using the same Sql Server instance... there
> would be no need for SDO scripts etc.
>
> Does that make sence, is this a legitimate configuration, or are there
other
> factors I've not thought of?
>
> Thanks
>
>
> "Justin" <justin_dbd@nospam.nospam> wrote in message
> news:O9JSrhxuEHA.3840@TK2MSFTNGP12.phx.gbl...
authoring[vbcol=seagreen]
syncronized[vbcol=seagreen]
copy[vbcol=seagreen]
to[vbcol=seagreen]
> way
be[vbcol=seagreen]
how[vbcol=seagreen]
> to
>
>
|
|
|
|
|