|
Home > Archive > Microsoft Content Management Server > April 2005 > Web Entry Points
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]
|
|
| GregoryH. 2005-04-21, 5:49 pm |
| Good morning,
We are using MCMS 2002 sp1 Enterprise on a Windows 2003, IIS 6 server.
We are planning on using the above configuration as a MCMS single authoring
server.
I have "Map Channel Names to Host Header Names" set to YES.
If I have an IIS Web Entry Point for the public as http://www.XXXX.edu and
have it defined in Site Manager as a root channel "www.XXXX.edu", how then
can I have a second Web Entry Point for my content contributors so they can
create, edit, and approve content?
--
Thank you,
Gregory
| |
| jawadak@gmail.com 2005-04-21, 5:49 pm |
| We are just using another port Number with the same address in our
environment ... so it is
http://www.XXX.edu:88
you just have to be careful that there are no hardcoded links with
actual server name in the link like http://www.XXX.edu/....
This way the IP address remains the same and you can also block the
port to outside traffic or for some specific people using firewall
easily (Less management) ....
| |
| Glen Wells 2005-04-21, 5:49 pm |
| You should create one more IIS Web site, so that you have two: one of which
(Site A) is assigned the server's public IP address; the other (Site B) is
assigned an IP address accessible only from your internal network.
Using The MCMS Server Configuration Application, set both sites as Entry
Points. In the column "MCMS?", set Site A to "Yes - Read Only" and Site B to
"Yes - Read Write".
Both IIS sites will serve the content from MCMS, but only Site B will allow
authoring.
I hope that answers your question.
--
Glen Wells
www.cubik.co.uk
"GregoryH." <gregoryh@newsgroup.nospam> wrote in message
news:64E0EFA8-ADA4-4EFF-A301-7F782F91440D@microsoft.com...
> Good morning,
>
> We are using MCMS 2002 sp1 Enterprise on a Windows 2003, IIS 6 server.
>
> We are planning on using the above configuration as a MCMS single
> authoring
> server.
>
> I have "Map Channel Names to Host Header Names" set to YES.
>
> If I have an IIS Web Entry Point for the public as http://www.XXXX.edu and
> have it defined in Site Manager as a root channel "www.XXXX.edu", how then
> can I have a second Web Entry Point for my content contributors so they
> can
> create, edit, and approve content?
> --
> Thank you,
> Gregory
| |
| Stefan [MSFT] 2005-04-21, 5:49 pm |
| Hi Gregory,
setup a second website and use the name (e.g.) "authoring.xxx.edu".
Then use the solution listed here to map the second name to the same
channel:
http://download.microsoft.com/downl...6a/MCMS+2002+-+(complete)+FAQ.htm#477EA7E7-CA78-456B-BC4D-B3E3AE832ABE
Cheers,
Stefan
--
This posting is provided "AS IS" with no warranties, and confers no rights
New to MCMS?
Check out this book: Building Websites Using MCMS: http://tinyurl.com/6zj44
----------------------
"GregoryH." <gregoryh@newsgroup.nospam> wrote in message
news:64E0EFA8-ADA4-4EFF-A301-7F782F91440D@microsoft.com...
> Good morning,
>
> We are using MCMS 2002 sp1 Enterprise on a Windows 2003, IIS 6 server.
>
> We are planning on using the above configuration as a MCMS single
authoring
> server.
>
> I have "Map Channel Names to Host Header Names" set to YES.
>
> If I have an IIS Web Entry Point for the public as http://www.XXXX.edu and
> have it defined in Site Manager as a root channel "www.XXXX.edu", how then
> can I have a second Web Entry Point for my content contributors so they
can
> create, edit, and approve content?
> --
> Thank you,
> Gregory
| |
| GregoryH. 2005-04-22, 5:58 pm |
| Good morning,
Your input is requested. Which is the best scenario to use a single MCMS
license as an Authoring Server (only one server for creating, editing,
approving content and public visitors to view content) for www.XXXX.edu and
why?
1) One entry point (www.XXXX.edu)
* anonymous to all
* use a form for authorized users to login and use console
2) Two entry points (www.XXXX.edu)
* one IIS Web site anonymous to all
* second IIS Web site for authorized users (not using port 80)
3) Two entry points (www.XXXX.edu and author.XXXX.edu)
* one IIS Web site anonymous to all (www.XXXX.edu)
* second IIS Web site for authorized users (author.XXXX.edu)
We also use an MSDN developer MCMS license for creating, testing...but no
staging.
Thank you for your insight, and comments, I look forward to reading them.
GregoryH
"Stefan [MSFT]" wrote:
> Hi Gregory,
>
> setup a second website and use the name (e.g.) "authoring.xxx.edu".
> Then use the solution listed here to map the second name to the same
> channel:
> http://download.microsoft.com/downl...6a/MCMS+2002+-+(complete)+FAQ.htm#477EA7E7-CA78-456B-BC4D-B3E3AE832ABE
>
> Cheers,
> Stefan
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
>
> New to MCMS?
> Check out this book: Building Websites Using MCMS: http://tinyurl.com/6zj44
> ----------------------
>
>
> "GregoryH." <gregoryh@newsgroup.nospam> wrote in message
> news:64E0EFA8-ADA4-4EFF-A301-7F782F91440D@microsoft.com...
> authoring
> can
>
>
>
| |
| Stefan [MSFT] 2005-04-22, 5:58 pm |
| Hi Gregory,
depends on the scenario:
1) is the best if authors coming from the internet should update the site.
Integrated authentication does not work anyway over internet so you would
have to go either with basic or forms authentication. Then you can use this
but ensure that the form is SSL encrypted.
2) this is similar to 3) except that in one scenario you have a different
port and in the other a different name.
Whatever your authors prefer!
Both are good solutions if authors are coming from the intranet. It is more
secure as 1) as you can ensure that the read-write site can only be hit from
the intranet.
3) might need to implement the following solution as well if you need to
have host header mapping for MCMS:
http://blogs.technet.com/stefan_gos.../22/404067.aspx
Cheers,
Stefan
--
This posting is provided "AS IS" with no warranties, and confers no rights
New to MCMS?
Check out this book: Building Websites Using MCMS: http://tinyurl.com/6zj44
----------------------
"GregoryH." <gregoryh@newsgroup.nospam> wrote in message
news:15523D27-3DA4-48A5-BE19-2AC4675C325D@microsoft.com...
> Good morning,
> Your input is requested. Which is the best scenario to use a single MCMS
> license as an Authoring Server (only one server for creating, editing,
> approving content and public visitors to view content) for www.XXXX.edu
and[vbcol=seagreen]
> why?
>
> 1) One entry point (www.XXXX.edu)
> * anonymous to all
> * use a form for authorized users to login and use console
> 2) Two entry points (www.XXXX.edu)
> * one IIS Web site anonymous to all
> * second IIS Web site for authorized users (not using port 80)
> 3) Two entry points (www.XXXX.edu and author.XXXX.edu)
> * one IIS Web site anonymous to all (www.XXXX.edu)
> * second IIS Web site for authorized users (author.XXXX.edu)
>
> We also use an MSDN developer MCMS license for creating, testing...but no
> staging.
>
> Thank you for your insight, and comments, I look forward to reading them.
> GregoryH
>
>
> "Stefan [MSFT]" wrote:
>
http://download.microsoft.com/downl...6a/MCMS+2002+-+(complete)+FAQ.htm#477EA7E7-CA78-456B-BC4D-B3E3AE832ABE[vbcol=seagreen]
rights[vbcol=seagreen]
http://tinyurl.com/6zj44[vbcol=seagreen]
and[vbcol=seagreen]
then[vbcol=seagreen]
they[vbcol=seagreen]
|
|
|
|
|