Knowledge Collection: Plug-in for WebSphere Application Server
This Knowledge Collection is a focused compilation of links to FAQs, How to, common problems and learning related to the Plug-in.
List of content for Plug-in
1. Understanding IBM HTTP Server plug-in Load Balancing in a clustered environment (1219567)
After setting up the HTTP plug-in for load balancing in a clustered IBM WebSphere environment, the request load is not evenly distributed among back-end WebSphere Application Servers.
2. Recommended values for Web server plug-in config (1318463)
In the Web server plug-in, what do the LoadBalanceWeight, MaxConnections, ConnectTimeout, ServerIOTimeout, IgnoreAffinityRequests, and GetDWLMTable options mean and what are the recommended settings for these options? What affect does Session Affinity have? How are connections handled during plug-in fail-over? What is the effect of using more than one Web server child process?
3. Web server plug-in policy for WebSphere Application Server (1160581)
It is possible to configure your web server plug-in to route requests to WebSphere Application Server V5.1, V6.0, V6.1 and V7.0 releases. This technote provides steps on how to verify what V5.1, V6.0, V6.1 and V7.0 plug-in versions are installed on local or remote web servers, and how to determine if the installation complies with supported configurations.
4. Understanding HTTP plug-in failover in a clustered environment (1219808)
After setting up the HTTP plug-in for load balancing in a clustered IBM WebSphere environment, the HTTP plug-in is not performing failover in a timely manner or at all when a cluster member becomes unavailable.
5. Error message definitions for WebSphere Application Server's webserver plugin component. (1381320)
User's may find errors reported in the http_plugin.log file from the plugin application. Message logged at the ERROR level are defined.
6. Modifying web server plug-in properties from the WebSphere Application Server administrative console (1460889)
How can I modify the web server's plug-in (plugin-cfg.xml) properties from the WebSphere Application Server administrative console?
7. IIS 7.0 - Configuring the WebSphere Application Server Web server plug-in for multiple Web sites (1366887)
Internet Information Services 7.0 (IIS), which ships with Microsoft Windows 2008 & Microsoft Windows Vista, allows multiple Web sites to be run within a single IIS server. Given this ability, can the WebSphere Application Server Web server plug-in be used with multiple IIS Web sites?
8. How do the properties ServerIOTimeout and PostBufferSize affect plug-in behavior? (1408884)
When ServerIOTimeout expires for a Post request, will plug-in mark down the server or retry the request?
9. Webserver Plugin configuration (1450051)
How should I configure my web server plug-in for the best results ?
10. "GSK_ERROR_BAD_CERT" error in WebSphere Application Server V7.0 plug-in (1433593)
The web server plug-in is unable to connect to the WebSphere Application Server V7.0 application server using HTTPS.
11. "Failed to stat plugin config file" error message in V5.0, V5.1, V6.0 or V6.1 plug-in trace (1165469)
Apache/IBM HTTP Server V1.3, V2.0 and V6.0 Web servers can be configured with IBM WebSphere Application Server V5.0 through V6.1 plug-in. Some customer cases have reported that overall performance degraded, and lots of
Failed to stat plugin config file errors were observed within the plug-in trace.
12. Merging plugin-cfg.xml files from multiple nodes (1139573)
Merging plugin-cfg.xml files from multiple nodes for releases of IBM WebSphere Application Server version 5 and version 6.
13. IIS 6.0 - Configuring the WebSphere Application Server Web server plug-in for multiple Web sites (1328944)
Internet Information Services 6.0 (IIS), which ships with Microsoft Windows 2003, allows multiple Web sites to be run within a single IIS server. Given this ability, can the WebSphere Application Server Web server plug-in be used with multiple IIS Web sites?
14. Webcast replay: WebSphere Plug-in Requests, Session Affinity, Load Balancing and Failover (7020055)
This WebSphere Support Technical Exchange is designed to outline the flow of plug-in request processing and explains key plug-in properties in the plugin-cfg.xml file related to failover, ESI cache and plug-in SSL enablement. The session also discusses the difference between session affinity and session persistence. Level of Difficulty: Beginner Presenter (s): Bob Richter Date: 28 October 2010
15. Potential limitations and considerations when downloading static content from the WebSphere Application Server (7015501)
There are some potential limitations and considerations that must be carefully weighed when deciding whether to serve static content from the WebSphere Application Server when esiEnable is set to true.
16. 7.0 Plug-in Install does not set PluginInstallRoot property (1394428)
Installation of the WebSphere Application Server 184.108.40.206 plug-in does not set the "pluginInstallRoot" Property in the plugin-cfg.xml file
17. HTTP Plug-in failures might prevent IBM HTTP Server from starting (1326077)
There are several reasons that could cause the HTTP plug-in to fail to load or fail routing requests to the WebSphere Application Server. These are the 2 possible errors that might occur: 1. The plug-in cannot use DNS to resolve the server hostnames listed in the plug-in configuration file. 2. The plug-in log file is larger then 2GB. If either of these errors occur, the failure will also prevent the IBM HTTP Server from starting.
18. Changes to plug-in properties are not being reflected in the global plugin-cfg.xml file (1441220)
You are attempting to update plugin-cfg.xml properties like ServerIOTimeout and ConnectTimeout for a particular WebSphere Application Server. You expect the function "Update Global Web server Plug-in configuration" to update the associated values in the global plugin-cfg.xml file located in the config/cells directory, however, this does not work.
19. "Manage keys and certificates" link for plugin-key.kdb is broken in the WebSphere Application Server administrative console (1426980)
You cannot manage plugin-key.kdb from the WebSphere Application Server administrative console. The "Manage keys and certificates" icon for plugin-key.kdb appears to be broken.
20. IIS 7.0 - Configuring the WebSphere Application Server Web server plug-in to serve custom error pages (1405555)
When the WebSphere Application Server Web server plug-in encounters a run-time error while processing a request, it will return a generalized Error page with one of the following error codes: 500 - INTERNAL SERVER ERROR This will be returned for most error conditions including but not limited to: failure to reach or receive a response from all back-end Application Servers within a cluster, failures encountered by the GSKIT during SSL related processing. 503 - SERVICE UNAVAILABLE This will be returned if all available Application Servers within a cluster have reached their MaxConnections value limit as defined in the plugin-cfg.xml. 413 - REQUEST ENTITY TOO LARGE This will be returned if a POST request's content-length exceeds the PostSizeLimit value as defined in the plugin-cf
21. IIS 7.x - File permissions for the WebSphere Application Server Web server plug-in (1443293)
In some cases, problems observed with the loading or run-time function of the WebSphere Application Server Web server plug-in for Internet Information Services (IIS) may be due to file permissions. What file permissions are required for the plug-in to function properly with IIS 7.x on Microsoft Windows Server 2008?
22. Webcast replay: WebSphere Application Server 6.1 Plug-in: Technical Overview (7014498)
This WebSphere Support Technical Exchange session discusses the workings of the WebSphere Application Server 6.1 plug-in with examples from the plugin-cfg.xml configuration file. This presentation also helps you understand the tuning aspects of plugin and debug plugin trace. It uses examples from actual traces to aid in debugging plug-in related problems. Level of Difficulty: Intermediate Presenter(s): Naveen Shetty and Steve Reid DATE: 09 December 2008
23 Changing the plugin-cfg.xml file dynamically without having to restart the Web server (1211601)
If the Web server and plug-in are on a UNIX system and you change the log level (for example, change the log level from Error to Trace or from Trace to Error) in the plugin-cfg.xml file, this change is not picked up dynamically. You must restart the Web server to pick up the changes. The following errors are in the Plugin_Home/logs/http_plugin.log file:
ERROR: ws_config_parser:handleLogEnd: Failed to open log file '/opt/IBM/WebSphere/Plugin/logs/sunwebserver/http_plugin.log', OS Err:13 If you restart the Web server, the changes are picked up.
Other Knowledge Collections for WebSphere Application Server
1. Knowledge Collection: Migrating from WebSphere Application Server (7008725)
2. Knowledge Collection: Migrating to (or from) WebSphere Application Server V8.5.5 (7008727)
3. Knowledge Collection: Migrating to WebSphere Application Server V7.0 (7013842)
4. Knowledge Collection: Java Message Service (JMS) for WebSphere Application Server (7020347)
5. Knowledge Collection: Migration planning for WebSphere Application Server (7008724)
6. Knowledge Collection: Migrating from other Application Servers to WebSphere Application Server (7008729)
7. Knowledge Collection: Why Migrate? (7008728)
Definition of a Knowledge Collection
A Knowledge Collection is a focused compilation of links to documents that share a common theme. Knowledge Collections are navigation aids that organize content to help users quickly find relevant information. Knowledge Collections are not designed to be an all-inclusive list of all documents dealing with the specific theme.]
|Application Servers||IBM HTTP Server||Java SDK||AIX, Linux, Solaris, Windows||7.0, 6.1, 6.0, 2.0|
|Application Servers||Runtimes for Java Technology||Java SDK|
More support for:
WebSphere Application Server
Software version: 6.1, 7.0, 8.0, 8.5
Operating system(s): AIX, HP-UX, IBM i, Linux, Solaris, Windows
Software edition: Advanced, Base, Developer, Enterprise, Express, Network Deployment, Single Server
Reference #: 7021301
Modified date: 04 April 2011