TeamSIte 6.5 and IIS 6.0

Hi All-

We are about to install TeamSite 6.5 in a Windows 2003 Server Enterprise Edition environment. Has anyone had any problems configuring IIS 6.0 for this.

Our operations group turns off the Default Web Site for the base builds of web servers. I assume we can just create the IW-Mount Web Site (documentation) and specify a port for it and voila?

Am I missing something?

Thanks,

Find more posts tagged with

Comments

jitendra

Hi,

I had tried installing TS 6.5 having created a new website with port setting as 90 (say).
When I specified the server configuration during the installation as 90, the installer didnot configure the new website created.
Instead it installed iw-mount on the default website and changed its port setting to 90.

I ended up having to manually export the default website configuration into a new website.

Hope that gives you some insight. Maybe some IW contact can confirm this or point out how it could be done.

Thanks
Jitendra

Adam Stoller

Did you choose port 90 for iwwebd or for the "customer web server" ?
Were you intending that TeamSite be logged into on port 90 or that when you previewed content that it was sent to port 90?
Which platform are you working on?

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

jitendra

It wasn't really a concern for me as to what shoudl be the "application login" or "preview" port. I just didnot want anything on 80 as I was temporarily running another application on 80. Hence I chose the customer webserver as 90. This was my development box - Windows 2003 Std Edition.

Jitendra

anthonyl

Just remember that IIS 6.0 is installed in lockdown config, you need to enable ISAPI filters (and .asp, .cgi etc if needed) manually.

Cheers,
Ant

Ottawa_IWOV

Thanks for the insights.

Is it possible for the TeamSite server to have a standalone ws (IIS) virtualize TeamSite content if it resides on another physical machine?

Thanks,

Migrateduser

The way you've phrased this is a little confusing to me. Do I understand that you want to run IIS on a separate machine and add a website on it that points at the Y: drive on the TeamSite server? If so, that's a fairly trivial thing to do. Just set up the website to point to the iwserver share on the TeamSite box by UNC. Then set up your customer_webserver section of iw.cfg to point to that box, something like this:


[iwwebd]
default_protocol=http
http_port=80
https_port=443
host=teamsiteserver.mydomain.com

[iwproxy]
iwproxy_host=localhost
customer_webserver_host=iisserver.mydomain.com
iwproxy_port=1080
customer_webserver_port=81

Now, what I don't understand is why you would want to do that...

A more typical (and useful scenario) would be to use some proxy remaps to redirect page views to one or more instances of an app server residing on a different server, but that doesn't sound quite like what you are talking about.

Ottawa_IWOV

Basically, the group we are working with want to minimize web server installations in their envrionemnt.

Ergo, we install TeamSite, and use a already available IIS installation to virtualize requests for viewing content in the backing store ...

Make sense?

Ottawa_IWOV

I completely understand your second scenario. Assuming I use the proxy remaps, is an IIS installation required on the TS machine?

Thanks,