This week's book giveaway is in the Testing forum. We're giving away four copies of Data Structures the Fun Way: An Amusing Adventure with Coffee-Filled Examples and have Jeremy Kubica on-line! See this thread for details.
I have a basic query regarding the 'propogation of plugin-cfg.xml' file.
As per my understanding we install the Application Server first and then the Web Server. While installing the HTTP Server Plugin later, we specify the 'webserver name' to be configured. And once its all done a 'plugin-cfg.xml' file is generated in the location we specified during the definition of webserver.
In the httpd.conf file we have a directive called WebSpherePluginConfig which has the location of plugin-cfg.xml file. Its like an indirection.
What exactly do they mean to say, 'proprogation of plugin config file from application server to web server?', when anyways the HTTP Server reads the httpd.conf file to get the location of plugin-cfg.xml file through the directive.
Can anyone explain? It may look like trivial but i don't get the concept.
Modifying the plugin config file is not a one-time thing. Any time you deploy a new application or change settings such as virtual hosts, this file will have to be rebuilt to show the changes. WebSphere does this for you when you select the option to "regenerate the plugin file".
Propagating the plugin file just means moving it to the location defined in your httpd.conf file. If your web server is on the same system as the app server and you defined the location as the same location where WebSphere is generating the plugin, you may not have to do anything at all to propagate it.
However, in a clustered configuration, generally one or more web servers are not on the same systems as the app servers. This means that when configuration changes occur, the plugin file will have to be "propagated" to the systems upon which the web servers are running.