Team Site setup with IIS...

Guys,
Are there any documents, etc., describing how 'integrated' Team Site is with IIS?

We're in the process of evaluating Interwoven's CMS tool and we're interested in understanding what's required to setup new sites (or sub-sites) with the tool (with IIS web servers). Currently we have sort of a ISP web hosting model, where we have 100s of sub-sites (physically under wwwroot) all with their own site/content owners.

Any assistance is appreciated...

Doug

Find more posts tagged with

Comments

Migrateduser

I think it depends on how you are using IIS - for instance ASP or ASPX. It seems like there is not much experience in the Interwoven field with .NET but there were some posts here a while back if you want to search. I don't have a lot of experience with classic ASP either but from what I remember, each TeamSite area (workarea, staging, edition) that has a global.asa (and probably same for web.config) has to be registered in IIS as an application. This is no problem if you don't create workareas or editions frequently, but if you do you have to go configure IIS so that they preview correctly. Other than that I am not aware of any issues, other than that you also have to configure an ISAPI plug-in and do some configuration to virtualize virtual includes and such.

I assume each of your subsites would be a branch, and if they use shared resources you might have to configure the proxy to support that.

You might also check http://groups.yahoo.com/group/TeamSite50

nipper

Don't know what documentation you are looking for, but this is really pretty easy. The TeamSite Admin manual will be a good reference.

When you import a site into a Workarea, if you properly import it, with the docroot at the top of the Workarea, the site should start to work. This would likely be one of you sub-sites, not the wwwroot.

Things to watch for, check you content for fully qualified URLS i.e. //server/subsite/images/blah.gif That is bad and hard to get around (you can by it affects performance).
Absolute paths (/images/blah.gif) and relative paths (../blah.gif) work fine.

If you use server side includes, there is a module to load.

My best advice, give it the smoke test, turn it on & see if it smokes. :-)

HTH,

Andy