Microsoft Content Management Server

Author

Web Entry Points

Mark Carranza

2005-06-29, 5:52 pm

Hi, the documentation is slim on creating, configuring, and maintaining
multiple MCMS web entry points.

Ideally I'd like to have, on the same box (only one enterprise license):
1) intranet, read/write, windows auth
2) intranet, read only, windows auth
3) extranet, https, read only, forms/custom auth
Option 1) exists as the Default Web Site in IIS

If I understand correctly, I use IIS to create additional websites, and use
SCA to configure. Tried this on the developer box, developer license, no
extra stuff happens: no /NR, /NRConfig etc. virtual directories created... I
seem to remember this can't be done with the dev license, but wanted to
try--I want to understand this before making changes on the production box.

So at this point, I'm kind of lost and I have a bunch of questions:
1) do web entry points point to the same MSMS site, or different sites with
the same MCMS backend?
2) do I have to duplicate all the code, templates, etc., under new web entry
points in directories and/or virtual directories
3) how do I have a separate web.config for each entry point?
4) if there is documentation/explanation of the multiple entry point
concepts/construction, please, where is it?

Thanks!

Kyong Kwak

2005-06-29, 5:52 pm

(1) what do you mean by MCMS site? I'm guessing a different look and feel?
then no. use channels and map channel headers to host name. So.. under
channels you'd have N-many "sites" i.e. www.mysite1.com and www.mysite2.com

(2) you can put things in dlls and use the gac or duplicate them. yes.
(3) since each site has their own directory they also have separate web.config
(4) I'm not sure where it would be.. anyone?

IIS is doing it's usual thing by setting up websites and such. SCA is
saying, when a certain website is "CMS Enabled", let CMS be in the pipeline
of serving pages so that it can properly map the templates to the postings (
in the db ).

hope that helps!!

"Mark Carranza" wrote:

> Hi, the documentation is slim on creating, configuring, and maintaining
> multiple MCMS web entry points.
>
> Ideally I'd like to have, on the same box (only one enterprise license):
> 1) intranet, read/write, windows auth
> 2) intranet, read only, windows auth
> 3) extranet, https, read only, forms/custom auth
> Option 1) exists as the Default Web Site in IIS
>
> If I understand correctly, I use IIS to create additional websites, and use
> SCA to configure. Tried this on the developer box, developer license, no
> extra stuff happens: no /NR, /NRConfig etc. virtual directories created... I
> seem to remember this can't be done with the dev license, but wanted to
> try--I want to understand this before making changes on the production box.
>
> So at this point, I'm kind of lost and I have a bunch of questions:
> 1) do web entry points point to the same MSMS site, or different sites with
> the same MCMS backend?
> 2) do I have to duplicate all the code, templates, etc., under new web entry
> points in directories and/or virtual directories
> 3) how do I have a separate web.config for each entry point?
> 4) if there is documentation/explanation of the multiple entry point
> concepts/construction, please, where is it?
>
> Thanks!

Mark Carranza

2005-06-29, 5:52 pm

Thanks for response:

>the same MCMS site
I want multiple entry/read only/authentication options for the SAME content.

So, what you're saying (in part):
- web entry points have to have their own directories.
- for the SAME content, things like template .aspx files, have to have the
same path, using duplicated or virtual directories.

I'm going to download the eval MCMS, as the developer license, unless I'm
doing it wrong, doesn't create the connection to MCMS.

"Kyong Kwak" wrote:
[vbcol=seagreen]
> (1) what do you mean by MCMS site? I'm guessing a different look and feel?
> then no. use channels and map channel headers to host name. So.. under
> channels you'd have N-many "sites" i.e. www.mysite1.com and www.mysite2.com
>
> (2) you can put things in dlls and use the gac or duplicate them. yes.
> (3) since each site has their own directory they also have separate web.config
> (4) I'm not sure where it would be.. anyone?
>
> IIS is doing it's usual thing by setting up websites and such. SCA is
> saying, when a certain website is "CMS Enabled", let CMS be in the pipeline
> of serving pages so that it can properly map the templates to the postings (
> in the db ).
>
> hope that helps!!
>
>
> "Mark Carranza" wrote:
>

Kyong Kwak

2005-06-29, 5:52 pm

if you want www.site1.com and www.site2.com to be mapped to the same name..
see this:
http://download.microsoft.com/downl...6a/MCMS+2002+-+(complete)+FAQ.htm#477EA7E7-CA78-456B-BC4D-B3E3AE832ABE

then just have 1 website in iis.
I've never used the eval version so I can't say.. but the connection to MCMS
( I'm guessing from the iis perspective ) isn't automatically added. you
need to do that manually. ( along with adding /nr and /mcms and such )

"Mark Carranza" wrote:
[vbcol=seagreen]
> Thanks for response:
>
> I want multiple entry/read only/authentication options for the SAME content.
>
> So, what you're saying (in part):
> - web entry points have to have their own directories.
> - for the SAME content, things like template .aspx files, have to have the
> same path, using duplicated or virtual directories.
>
> I'm going to download the eval MCMS, as the developer license, unless I'm
> doing it wrong, doesn't create the connection to MCMS.
>
> "Kyong Kwak" wrote:
>

Stefan [MSFT]

2005-06-30, 7:48 am

There is no difference between developer edition and eval edition except the
expiration and the license screen.

--
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
----------------------

"Kyong Kwak" <kkwak_at_purposedriven.com@nospam.com> wrote in message
news:621B6BC2-49D4-48AB-8B39-09FB446A3E47@microsoft.com...[vbcol=seagreen]
> if you want www.site1.com and www.site2.com to be mapped to the same
> name..
> see this:
> http://download.microsoft.com/downl...6a/MCMS+2002+-+(complete)+FAQ.htm#477EA7E7-CA78-456B-BC4D-B3E3AE832ABE
>
> then just have 1 website in iis.
> I've never used the eval version so I can't say.. but the connection to
> MCMS
> ( I'm guessing from the iis perspective ) isn't automatically added. you
> need to do that manually. ( along with adding /nr and /mcms and such )
>
> "Mark Carranza" wrote:
>

Stefan [MSFT]

2005-06-30, 7:48 am

Hi Mark,

1) all web entry points would have to point to the same physical directory.
If different authentication modes are required you would have to point them
to different directories with the same content - except for the web.config
files which need to have different authentication configured.

2) as indicated you need to duplicatate the content if the authentication
type is different.
Or just place the web.config in the root of your template project and all
other stuff in subdirectories.
Then you can create virtual directories in the second web entry point to
point to the sub directories and only the web.config needs to be located
local.

3) see point 2

4) no there is no documentation available.

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
----------------------

"Mark Carranza" <removethis.markca.at.magenic.com.removethis> wrote in
message news:C01C7099-AD79-4BA4-BF72-B538AE98FC52@microsoft.com...
> Hi, the documentation is slim on creating, configuring, and maintaining
> multiple MCMS web entry points.
>
> Ideally I'd like to have, on the same box (only one enterprise license):
> 1) intranet, read/write, windows auth
> 2) intranet, read only, windows auth
> 3) extranet, https, read only, forms/custom auth
> Option 1) exists as the Default Web Site in IIS
>
> If I understand correctly, I use IIS to create additional websites, and
> use
> SCA to configure. Tried this on the developer box, developer license, no
> extra stuff happens: no /NR, /NRConfig etc. virtual directories created...
> I
> seem to remember this can't be done with the dev license, but wanted to
> try--I want to understand this before making changes on the production
> box.
>
> So at this point, I'm kind of lost and I have a bunch of questions:
> 1) do web entry points point to the same MSMS site, or different sites
> with
> the same MCMS backend?
> 2) do I have to duplicate all the code, templates, etc., under new web
> entry
> points in directories and/or virtual directories
> 3) how do I have a separate web.config for each entry point?
> 4) if there is documentation/explanation of the multiple entry point
> concepts/construction, please, where is it?
>
> Thanks!

Stefan [MSFT]

2005-06-30, 7:48 am

Hi Mark,

what do you mean with "doesn't create the connection to MCMS". Please
explain.

Thanks,
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
----------------------

"Mark Carranza" <removethis.markca.at.magenic.com.removethis> wrote in
message news:CCE86570-0258-4985-A3DB-66EBE9EB89D0@microsoft.com...[vbcol=seagreen]
> Thanks for response:
>
> I want multiple entry/read only/authentication options for the SAME
> content.
>
> So, what you're saying (in part):
> - web entry points have to have their own directories.
> - for the SAME content, things like template .aspx files, have to have the
> same path, using duplicated or virtual directories.
>
> I'm going to download the eval MCMS, as the developer license, unless I'm
> doing it wrong, doesn't create the connection to MCMS.
>
> "Kyong Kwak" wrote:
>