I'm writing to find out is using ISAPI filter is a viable solution for our
scenario below:

We have just upgraded/migrated from a CMS2001-Site Stager-SunONE UNIX web
server environment to a CMS2002 Authoring-Deployment Script-CMS2002
Production environment for our university web presence.  Under the UNIX
environment we were able to set up virtual servers that maintained the
aliased URL that our customer wanted.  However in the new CMS environment,
we are only able to set up IIS redirects where users can enter the aliased
URL, but the actual URL based on the CMS channel hierarchy gets displayed in
the address bar.

I read in Building Websites with Microsoft Content Management Server where
setting up host headers in CMS required the channel names to be the same as
the URL desired.  Also mentioned was the use of an ISAPI filter as another
option.  Unfortunately changing the channel names is to the FQDN is not a
feasible option for a few reasons: (1) we have almost 150 sites hosted on
our CMS system (it seems like using host header names for CMS is an all or
nothing option where all the channels need to be converted to FQDNs), (2)
our channel hierarchy goes as deep as 4 levels/directories,  and (3) there
is code in our templates to implement branding for our colleges whose
structure is mimicked in our channel hierarchy

If I used an ISAPI filter, is it still necessary to have the channel name
the same as the host header name?  Is rewriting the domain name of a CMS
hosted site possible with ISAPI filters?

Thanks in advance,
Ernest

[ Post a follow-up to this message ]

Hi Ernest,

when using the ISAPI filter you can rewrite the FQDN to the channel name.

Cheers,
Stefan


"leongek" <eleong@hsc.usf.edu> wrote in message
news:%23yjdaLyOHHA.4484@TK2MSFTNGP02.phx.gbl...
>
> I'm writing to find out is using ISAPI filter is a viable solution for our
> scenario below:
>
> We have just upgraded/migrated from a CMS2001-Site Stager-SunONE UNIX web
> server environment to a CMS2002 Authoring-Deployment Script-CMS2002
> Production environment for our university web presence.  Under the UNIX
> environment we were able to set up virtual servers that maintained the
> aliased URL that our customer wanted.  However in the new CMS environment,
> we are only able to set up IIS redirects where users can enter the aliased
> URL, but the actual URL based on the CMS channel hierarchy gets displayed
> in the address bar.
>
> I read in Building Websites with Microsoft Content Management Server where
> setting up host headers in CMS required the channel names to be the same
> as the URL desired.  Also mentioned was the use of an ISAPI filter as
> another option.  Unfortunately changing the channel names is to the FQDN
> is not a feasible option for a few reasons: (1) we have almost 150 sites
> hosted on our CMS system (it seems like using host header names for CMS is
> an all or nothing option where all the channels need to be converted to
> FQDNs), (2) our channel hierarchy goes as deep as 4 levels/directories,
> and (3) there is code in our templates to implement branding for our
> colleges whose structure is mimicked in our channel hierarchy
>
> If I used an ISAPI filter, is it still necessary to have the channel name
> the same as the host header name?  Is rewriting the domain name of a CMS
> hosted site possible with ISAPI filters?
>
> Thanks in advance,
> Ernest
>

[ Post a follow-up to this message ]

So if using the ISAPI filter, it is necessary to set your channel names as
FQDN also?

And also if using host headers in CMS (by setting the Map Channel Names to
Host Header in SCA), every channel must be named as a FQDN?


"Stefan Goßner [MSFT]" <stefang@online.microsoft.com> wrote in message
news:uMksyQ6OHHA.3544@TK2MSFTNGP03.phx.gbl...
> Hi Ernest,
>
> when using the ISAPI filter you can rewrite the FQDN to the channel name.
>
> Cheers,
> Stefan
>
>
> "leongek" <eleong@hsc.usf.edu> wrote in message
> news:%23yjdaLyOHHA.4484@TK2MSFTNGP02.phx.gbl... 
>
>

[ Post a follow-up to this message ]

Hi,

no that is not necessary.
As the ISAPI filter can rewrite the FQDN to any other name you can use any
other name for the channel name.

Cheers,
Stefan


"leongek" <eleong@hsc.usf.edu> wrote in message
news:ujYhCq9OHHA.4484@TK2MSFTNGP02.phx.gbl...
> So if using the ISAPI filter, it is necessary to set your channel names as
> FQDN also?
>
> And also if using host headers in CMS (by setting the Map Channel Names to
> Host Header in SCA), every channel must be named as a FQDN?
>
>
> "Stefan Goßner [MSFT]" <stefang@online.microsoft.com> wrote in message
> news:uMksyQ6OHHA.3544@TK2MSFTNGP03.phx.gbl... 
>
>

[ Post a follow-up to this message ]