Configuring the HTTP Server IBM WebSphere By: Sha
Configuring the HTTP Server IBM WebSphere By: Shafqat Muzamil
Hope this would be helpful! Trust me :)
Configuring the HTTP Server:
The plugin-cfg.xml file on the HTTP Server machine (RPS) reads WebSphere's plugin-cfg.xml file to forward requests to WebSphere. Copy the existing plugin-cfg.xml file on the RPS machine to a safe backup location and replace it with the plugin-cfg.xml file from WAS_HOME\config\cells\plugin-cfg.xml.
You can find the location of the existing plugin-cfg.xml on the RPS machine as follows:
On an IBM Http Server machine —
Open IBM_HTTP_Server_HOME\conf\httpd.conf, and search for “plugin-cfg.xml” in it to discover the location of the plugin-cfg.xml file on the RPS machine.
On a Sun ONE (iPlanet) Web Server machine —
Open Sun_ONE_HOME\servers\https-machine.domain\config\magnus.conf, and search for “plugin-cfg.xml” in it to discover the location of the plugin-cfg.xml file on the RPS machine.
On a Microsoft IIS machine —
Open the Windows registry, expand HKEY_LOCAL_MACHINE > SOFTWARE > IBM > WebSphere Application Server > 184.108.40.206.Plugin Config. The key points to the plugin-cfg.xml file on the RPS machine.
If you experience any problem with the HTTP plug-in component—the component that sends requests from your HTTP server (for example, IBM HTTP Server, Apache, iPlanet, or IIS) to WebSphere—try doing the following to resolve the problem:
Review the file install_dir\logs\http_plugin.log for clues. Look up any error or warning messages in the message table.
Review the HTTP server’s error and access logs to see if the HTTP server is experiencing a problem. Following are the log files for each server:
IBM HTTP Server and Apache — access.log and error.log
iPlanet — access and error
Microsoft IIS — timedatestamp.log