Did anybody here get the sample snoop servlet to work with IIS 5/6?

[c***@cross-check.com]

OK quick and simple question. We have one Win2k Server running both IIS 5 and WebSphere Application Server express 6.xx (latest refresh packages).

This works - http://mydomain.com:9080/snoop

I don't want to type in the port 9080 and use the default HTTP port through IIS: http://mydomain.com/snoop

I installed the iisWASPlugin_http.dll from CD and it created the ISAPI filter and the virtual directory sePlugins within IIS.. I have no idea what to do from here though.. I was hoping that the sample 'snoop' servlet would just work magically after installing this plugin (obviously it's not that simple)... So now I'm reading up and there is a plugin-cfg.xml file I possibly need to configure? I pulled this up whcih was generated from install and it's just somewhat chinese to me (hence the title). Hopefully someone can tell me what to do to make this simple thing work. I'm sure once I see how it must be configured I can configure our other java servlets that we have working...

I tried adding a 'snoop' URI just trial and erroring:

**------generated plugin-cfg.xml-------**
<?xml version="1.0" encoding="ISO-8859-1"?>

<Config ASDisableNagle="false" AcceptAllContent="false" AppServerPortPreference="HostHeader" ChunkedResponse="false" FIPSEnable="false" IISDisableNagle="false" IISPluginPriority="High" IgnoreDNSFailures="false" RefreshInterval="60" ResponseChunkSize="64" VHostMatchingCompat="false">
<Log LogLevel="Error" Name="C:\Program Files\IBM\WebSphere\Plugins/logs/CCRPWEBDEV/http_plugin.log"/>
<Property Name="ESIEnable" Value="true"/>
<Property Name="ESIMaxCacheSize" Value="1024"/>
<Property Name="ESIInvalidationMonitor" Value="false"/>
<RequestMetrics armEnabled="false" loggingEnabled="false" rmEnabled="false" traceLevel="HOPS">
<filters enable="false" type="URI">
<filterValues enable="false" value="/snoop"/>
<filterValues enable="false" value="/hitcount"/>
</filters>
<filters enable="false" type="SOURCE_IP">
<filterValues enable="false" value="255.255.255.255"/>
<filterValues enable="false" value="254.254.254.254"/>
</filters>
<filters enable="false" type="JMS">
<filterValues enable="false" value="destination=aaa:topic=bbb"/>
</filters>
<filters enable="false" type="WEB_SERVICES">
<filterValues enable="false" value="wsdlPort=aaa:op=bbb:nameSpace=ccc"/>
</filters>
</RequestMetrics>
</Config>

[v***@hotmail.com]

Once you have completed the WebServer installation you need to get the configurewebserver.bat file and run it on the application server bin. Once you do this your webserver becomes a managed node.

After doing this you need to update the webserver plugin and then test the servlet

[v***@hotmail.com]

If you are using WAS 5 all you need to do is install the IIS and update the plugin file and make sure that the default listener port(80) for IIS is added in the virtual host of the server.

[c***@cross-check.com]

Just a couple hours before you replied to me I did finally figure out I had to go to "Environments" after reading through a RedBooks PDF.. and setup the virtual host name there and an IP address... I went ahead and did this then regenerated the plugin, and it worked!

Now I'm just trying to figure out how to map it to one of our own applications we have running.. Can you give some quick pointers with this? I guess the snoop servlet is part of the default application when I view the deployment descriptor of it.


P.S. We are using WebSphere version 6 with latest refresh packs

[v***@hotmail.com]

If you application is running on the same server as the one that snoop is running then you should be able to hit your application by hitting the /contextroot instead of /snoop.

If it is running on a different server then you need to edit the virtual host of that server by adding the webserver port and then updating the plugin

This should work.

[v***@hotmail.com]

Ok..for WAS 6.0

During the Application installation you need to map it to both the application server and the webservers and then finish the installation. This automatically configures the WebServer to take requests.

[c***@cross-check.com]

Ok, yes everything is on same server. We'll keep trying this though and let you know results tommorow. Our day is at an end right now.. Thank you for the help!

I really wish they would've explained step-by-step an example of setting up the Environment variables in WAS 6 for IIS to generate a correct plugin cfg..We had to dig deep to find this final info..

[n***@ahoo.com]

(I'm from the same company as Charlie, btw!)

On installing the application, I have selected both the Application server and the web server in the map Modules to servers step - and the installation completes with no warnings, but on looking in the log we get the following (names changed):

PLGC0052I: Plug-in configuration file generation is complete for the Web server ourserverOurNode01Cell.SERVER_node.SERVER.
PLGC0050W: Propagation of the plug-in configuration file is not supported for the remote Web server ourserverOurNode01Cell.SERVER_node.SERVER.
PLGC0053E: Plug-in configuration file is not created for the Web server ourserverOurNode01Cell.SERVER_node.SERVER.

There is no reference to the newly installed application in the generated plugin-cfg.xml.

Any clues?

[v***@hotmail.com]

I think you are using a webserver other than IHS. In this case though your plugin is updated in the local machine you need to move it to the remote webserver box manually.
Copy the plugin-cfg.xml file from your machine to the remote machine and bounce the Web Server.

Hope this helps!