Steps to propogate WebSphere 6.0.2.x IIS Plug-in config on stand-alone server?

What are the proper steps to update the IIS 6 plug-in config file on a WebSphere 6.0.2.x installation where WebSphere and IIS 6 co-exist on the same server? I've been able to update the config by jumping into some wizards, but am looking for the proper / best practice steps.
LVL 16
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.


If the WebServer and Application Server exists on the same machine the plug-in configuration file does not need to be propagated to the server when it is regenerated. The file is
generated directly in the location the Web server reads it from.
The plug-in configuration file is automatically generated. Because this is a local
installation, you dont have to propagate the new plug-in configuration to the Web

You can follow the below steps to Configure the webserver with a standalone application server exists on machine A.
Local Web server

Assume the application server is already installed and configured. Perform the
following tasks:
1. Install the Web server on Machine A.
2. Install the Web server plug-in on Machine A by doing the following:
a. Select Local installation.
b. Enter a name for the Web server definition. The default is webserver1.
c. Select the location for the plug-in configuration file. By default, the location
under the config directory in the profile for the standalone application
server will be selected. For example, when the name specified for the Web
server definition in the previous step is webserver1, the default location for
the plug-in file is:
During installation, the following tasks are performed:

a. Create the plug-in configuration file and places it in the location specified.
b. Update the Web server configuration file with the plug-in configuration,
including the location of the plug-in configuration file.
c. Update the WebSphere Application Server configuration to define the new
Web server.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
jessc7Author Commented:
Thanks dipinci. So when a new virtual host or application is added, is there anything that needs to be done to update the IIS plugin? Say we add a virtual host for SSL, or install a new app with its own context root. Are there steps we need to take to update the plugin config?
When you add a new configuration in the WebSphere Virtual host and install new app the plugin will get updated. This plugin is pointed to <profile_home>/config/cells/<cell_name>/nodes/webserver1_node/servers/we
bserver1/plugin-cfg.xml as I have explained earlier.

Introduction to Web Design

Develop a strong foundation and understanding of web design by learning HTML, CSS, and additional tools to help you develop your own website.

jessc7Author Commented:
Is there a way to verify where the plugin is looking for its config file? Is there a setting somewhere I can reference to make sure it is pointed to the /AppServer location? Thanks!
jessc7Author Commented:
I found the file to confirm the location:

<drive>:\Program Files\IBM\WebSphere\Plugins\bin\<server>\plugin-cfg.loc

So just to verify, any time I make changes that impact the plugin through the WebSphere Admin console, all I have to do in the in the Admin console is save the changes, and the plugin-cfg.xml file is automatically updated to reflect the new changes?
You are right,  open the plugin-cfg.loc file in a text editor, which will provide you the location of plugin-cfg.xml.

I guess you have provide WebSphere Application Server as local and webserver definition name as webserver1 during the plugin installation.Then the plugin file should be pointed to   <profile_home>/config/cells/<cell_name>/nodes/webserver1_node/servers/webserver1/plugin-cfg.xml
jessc7Author Commented:
dipinci, I've been told its best practice to still perform the following steps from the Admin Console:

Servers -> Web Servers -> Select the web server -> Click Generate Plug-ing

Any thoughts?
Yes its a best practise to perform Generate Plugin-in. IBM also recommends the same.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Java App Servers

From novice to tech pro — start learning today.