Behavior does not change following installation of the WebSphere Application Server V4.0.x Web server plug-in
 Technote (FAQ)
 
Problem
After installing a plugin fix, there is no change in the behavior of the WebSphere® Application Server v4.0.x plug-in. While it is possible that the fix does not work, it is also possible that the fix did not install properly due to the Web server configuration.
 
Cause
In some cases, Web server or WebSphere Application Server administrators change the default location of WebSphere plug-in files by manually editing the WebSpherePluginConfig directive in the Web server configuration file and then manually copying all corresponding files to a new location. In this case Plug-in e-fix installer does NOT update any plug-in files that were manually copied to a non-default location. Although e-fix installer returns a message that installation of the plug-in e-fix was successful, the old plug-in module will still be in use by the Web server.
 
Solution
When the Web server plug-in for WebSphere Application Server v4.0 is installed, the plug-in module, plug-in configuration directives and several aliases are added to Web Server configuration file by default.

The name of the Web Server configuration file depends on which Web Server you are using. For example, IBM HTTP Server uses httpd.conf, while iPlanet 6 uses magnus.conf.

The following directive examples are from IBM HTTP Server with WebSphere Application Server V4.0.x on Windows® platforms, but they generally apply for other platforms and Web Servers as well.

LoadModule ibm_app_server_http_module D:/WebSphere/AppServer/bin/mod_ibm_app_server_http.dll
Alias /IBMWebAS/ "D:/WebSphere/AppServer/web/"
Alias /WSsamples "D:/WebSphere/AppServer/WSsamples/"
WebSpherePluginConfig D:\WebSphere\AppServer\config\plugin-cfg.xml

Plug-in eFixInstaller looks for valid WebSphere® Application Server V4.0 product.xml and places all files that are included in the plug-in e-fix beneath

Install_Root\AppServer\ directory (usually in Install_Root\AppServer\bin\ directory).

In some cases, Web server or WebSphere Application Server administrators change the default location of WebSphere plug-in files by manually editing the WebSpherePluginConfig directive in the Web server configuration file and then manually copying all corresponding files to a new location. In this case Plug-in e-fix installer does NOT update any plug-in files that were manually copied to a non-default location. Although e-fix installer returns a message that installation of the plug-in e-fix was successful, the old plug-in module will still be in use by the Web server.

Administrators must manually copy updated Web server plug-in files to the location specified in the Web server configuration file in order for them to be loaded during startup. Similar rules also apply for Apache, iPlanet, and Internet Information Service Web Server plug-in.

Refer to technote #1078612 for a detailed description of how to verify which build of Web server plug-in is being used with WebSphere Application Server V4.0.x.

 
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Plug-in
Operating system(s): HP-UX
Software version: 4.0.7
Software edition:
Reference #: 1080250
IBM Group: Software Group
Modified date: Dec 6, 2004