Microsoft Content Management Server - One database, Authoring + Production servers.

Author

One database, Authoring + Production servers.

Alan Lakman

2004-02-27, 11:34 pm

I have read in some posts on the site that to enable real
time production of content one can have only one Database,
and two CMS servers. One server that can be used for
authoring (read+Write) and one server that can be strictly
used for displaying content (end user facing with read
only capacity)..

The concern that I have is, if we have it that way...
when we enable host headers on production server, how will
the authoring server behave. Will this setting be
reflected for the authoring server as well because they
are using the same database or is the host header setting
not stored in a database.

If it is stored in a dtabase how can we handle such a
situation???

Thanks for any ideas/thoughts..

Alan.

Stefan [MSFT]

2004-02-28, 5:34 am

Hi Alan,

your concern is right.
You would have to ensure that name resolution is different of authors then
for subscribers.
This can be achieved by either using different DNS servers or by using local
host files.

Another solution would be to use the following workaround on the authoring
system which allows to map different host header names to one channel:
http://download.microsoft.com/downl...6a/MCMS+2002+-+(complete)+FAQ.htm#477EA7E7-CA78-456B-BC4D-B3E3AE832ABE

Please be aware that the following hotfix needs to be installed: 824597

Cheers,
Stefan.

--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Alan Lakman" <anonymous@discussions.microsoft.com> wrote in message
news:368b01c3fdb2$6e2c9f50$a501280a@phx.gbl...
> I have read in some posts on the site that to enable real
> time production of content one can have only one Database,
> and two CMS servers. One server that can be used for
> authoring (read+Write) and one server that can be strictly
> used for displaying content (end user facing with read
> only capacity)..
>
> The concern that I have is, if we have it that way...
> when we enable host headers on production server, how will
> the authoring server behave. Will this setting be
> reflected for the authoring server as well because they
> are using the same database or is the host header setting
> not stored in a database.
>
> If it is stored in a dtabase how can we handle such a
> situation???
>
> Thanks for any ideas/thoughts..
>
> Alan.

2004-02-28, 7:34 am

Thanks v much for the reply.
But what do is it that needs to be doen in the localhost
files and how could you be setting something that is
different for an author and a subscriber in a localhost
file.(which file particularly? is it lmlhosts?)???
Thanks again ..
Alan

>-----Original Message-----
>Hi Alan,
>
>your concern is right.
>You would have to ensure that name resolution is
different of authors then
>for subscribers.
>This can be achieved by either using different DNS
servers or by using local
>host files.
>
>Another solution would be to use the following workaround
on the authoring
>system which allows to map different host header names to
one channel:
>http://download.microsoft.com/download/4/2/5/4250f79a-
c3a1-4003-9272-2404e92bb76a/MCMS+2002+-+(complete)
+FAQ.htm#477EA7E7-CA78-456B-BC4D-B3E3AE832ABE
>
>Please be aware that the following hotfix needs to be
installed: 824597
>
>Cheers,
>Stefan.
>

dwc

2004-02-28, 11:35 am

For the record, I think sharing a CMS database between your authoring server and your production server is a very bad idea. The host header issue is something I would steer clear of altogether. Also, you will run into more issues than just host header m
apping. For example, if you change the standard properties on a published posting, that posting is taken out of publication until the standard properties are approved. This is because the edit and live versions share their standard properties.

The Microsoft reccommended solution for a production environment is to have at least one authoring server and one publishing server each with their own database. Then you can automate content deployment from one server to the other with the MCMS Site Dep
loyment API, either in vbscript or in your application itself.

Stefan [MSFT]

2004-02-28, 1:34 pm

Hi Alan,

I talked about the "hosts" file.
You need to associate the IP address of the server you want to address with
the host header (DNS) name.

Cheers,
Stefan.

--
This posting is provided "AS IS" with no warranties, and confers no rights.

<anonymous@discussions.microsoft.com> wrote in message
news:385701c3fdf4$fe03df20$a501280a@phx.gbl...[color=darkred]
> Thanks v much for the reply.
> But what do is it that needs to be doen in the localhost
> files and how could you be setting something that is
> different for an author and a subscriber in a localhost
> file.(which file particularly? is it lmlhosts?)???
> Thanks again ..
> Alan
>
> different of authors then
> servers or by using local
> on the authoring
> one channel:
> c3a1-4003-9272-2404e92bb76a/MCMS+2002+-+(complete)
> +FAQ.htm#477EA7E7-CA78-456B-BC4D-B3E3AE832ABE
> installed: 824597

Trevor Grant

2004-02-28, 11:34 pm

Hi dwc

You have valid points. However, the recommended solution from MS does not
take into account sites that are mission critical and require information to
be updated the moment it becomes available, especially intranet apps.

Trevor

"dwc" <anonymous@discussions.microsoft.com> wrote in message
news:FC7BBE32-2FF5-475C-B3EF-0B8F757A5312@microsoft.com...
> For the record, I think sharing a CMS database between your authoring
server and your production server is a very bad idea. The host header issue
is something I would steer clear of altogether. Also, you will run into
more issues than just host header mapping. For example, if you change the
standard properties on a published posting, that posting is taken out of
publication until the standard properties are approved. This is because the
edit and live versions share their standard properties.
>
> The Microsoft reccommended solution for a production environment is to
have at least one authoring server and one publishing server each with their
own database. Then you can automate content deployment from one server to
the other with the MCMS Site Deployment API, either in vbscript or in your
application itself.