Hi,

I am currently trying to gather informations about how to add a new communication tunnel between our WAS 6.1 server and an IIS 6 web server. We will be adding a new J2EE application soon on our WAS server and I will have to update (I think) the WAS plug-in that is installed on our IIS 6 server but I can't find any documentation in the IBM boulder web site on how to update configurations or how to update the tunnel between WAS and IIS.

So do I have to do something on the plugin side to make that plugin able to communicate with the WAS server ? And how this can be done ? Is their any wizard or tools that can make this easier on IT side ?

I've been able to update a file called plugin-cfg.xml but again I just don't know what to do next. Is this file contain everything I need and I just have to copy it witihin IIS plugin structure ?

Can you help me with this because right now I'm a bit confuse.

Thank you very much !

www-01.ibm.com/support/docview.wss?uid=s...

The above links had information for WAS IIS7 plug-in. Please go through it, that will give an idea on how to configure for IIS6.

If possible, move this question to 'WebSphere Application Server' section.

Thanks for the reply !

But I don't know if this is what I need. How doing this procedure will make the WAS plugin able to speak with the new Enterprise application ? Only copying and renaming directories and modifying a "logs" line in the "plugin-cfg.xml" file will make the plug-in working as it should ? I don't have to modify anything on the WAS side ? Is the "iisWASPlugin_http.dll" that do all the work and is able to differientiate all the Enterprise Application ?

Thanks again !!

P.S.: I don't know how to move this post to the right thread sorry.

When you add a new applicastion to your existing websphere application server

1. After successful installation of your new app.... Regenerate the plug-in configuration


2. Propagate the plug-in

when the above 2 steps are done, the follwing things will occur in the background:

• 1. Plugin-cfg.xml file will be updated


• 2. your new application context root will be added to plugin-cfg.xml


• 3. Virtual host along with the host aliases inside it, which you used while installing new app will be updated in plugin-cfg.xml

that means when the requests comes from your webserver with new application context root, it can find the information on where to route it based on the updated information available in the plugin-cfg.xml file.

These are the only steps required for a new application to be accessable from the webserver configured to work with websphere.

Let me know, if the procedure is clear to you.