WebSphere HTTP Server - IIS and WebSphere

Author

IIS and WebSphere

Roelof

2004-01-24, 11:33 pm

Hi,

I have a Windows 2003 server with IIS and an ear application that works well
using port 9080 , WebSphere 5.1.

I have tried to make the application available through port 80 to no avail.

Does anyone know a guide or installation procedure for configuring
IIS/WebSphere. I have also messed up my IIS settings;
no default settings or settings made by webSphere installation procedure
should be presumed.

Thanks in advance,

Roelof

Waydaws

2004-06-15, 5:48 pm

Roelof wrote:
> Hi,
>
> I have a Windows 2003 server with IIS and an ear application that works well
> using port 9080 , WebSphere 5.1.
>
> I have tried to make the application available through port 80 to no avail.
>
> Does anyone know a guide or installation procedure for configuring
> IIS/WebSphere. I have also messed up my IIS settings;
> no default settings or settings made by webSphere installation procedure
> should be presumed.
>
> Thanks in advance,
>
> Roelof
>
>
>
>
I just did it. It does work, but does something a little...strange. In
my case, I installed it on two nodes of a front end Load balanced
"cluster." The install is the same. I wasn't successfully in getting
it to work on it's own site, so I went with letting it install to the
default site.

Off the top of my head this is what I did:

First, of course, I installed it on the machine designated for WAS, and
also installed the iis plugin. You'll need this because you have to
generate your server.xml file which you'll need to copy to your remote
iis machines. So on the WAS server you install pretty much everything,
except plugin for ibm webserver (since you're not using it), and this
includes the Microsoft iis plugin.

Second on your remote IIS server(s), it's best if you install it using
the install CD, instead of just manually configuring it. Then just
select the plugin for iis only. (You'd be wise to install it to the
same path on your frontend webserver nodes, as your middle tier WAS
machine. Otherwise you're going to have to edit your server.xml file
to account for differences in installations paths before copying it to
the remote frontend webserver nodes.)

After you install it, you'll want to correct the weird thing it does:
that is, it adds the sePlugins and ibmWAS virtual directory in all
virtual directories and all websites on the box. (I have mostly separate
websites, but found the same issue with virtual directory webs.) You
*could* leave it, but wait until you see what happens if there is an
error condition. It will screw up all your sites, not just one.

To fix this I found it easiest to go though the metabase xml file and
remove the entries from all but default site. I actually found the
metabase edit utility from the iis 6 resource kit, handy for doing this,
but it'd be easy using the metabase.xml file directly too. (Oh, by the
way, I've enabled "allow direct metabase edit" on my nodes so the change
takes place immediately without restart.)
While you're at it, you might want to check the filters key of each site
where you shouldn't have the sePlugin and ibmWAS folders. There should
be no WAS plugin listed. Of course there is a global filter key where
it does (I assume) belong. I did leave it there.

That done, you still need to configure it to run. Using the IIS
Management Console go to Service Extension and add on called, say
iisWASPlugin, browse to the the folder with iisWASPlugin.dll and set it
to Allowed.

What else? Mmmm. I think that was it. I might have ended up restarting
IIS (maybe not), but if you do it with iisadmin service, you'll have
to go into your application pools and restart them all individually
(assuming you're using separate application pools for each of your
non-static sites).

Try it with snoop first, if http://servername/snoop works, try your app.

Hope I haven't forgotten anything. I'm not at work and can't look at
the setup right now.