• 1 reply
  • Latest Post - ‏2012-08-17T15:17:11Z by Scott Johnston
1 Post

Pinned topic HTTP Server 8.5 does not redirect requests to nodes in cluster on Linux

‏2012-08-17T13:57:49Z |
I have a web application on a Linux cluster using WebSphere 7.0. The application is deployed on server 1 and on server 2. The IBM Web Server is configured on server 1. Sending a web request to the web server without a port number directs the request to server 1 or 2 as expected.

I installed WebSphere 8.5 (trial version) and replicated the configuration of the 7.0 cluster. I can reach the application with server one or server two's port number. The HTTP server is running on server one. If I try to use the web server URL with the application context (no port number), I get a 404 error. The HTTP server looks like it is configured properly and is running. When I go to the web server URL (no context for the application) I do see the IBM HTTP server page as expected.

Any ideas why the HTTP server is not directing requests to the application on server one or server 2?
Updated on 2012-08-17T15:17:11Z at 2012-08-17T15:17:11Z by Scott Johnston
  • Scott Johnston
    Scott Johnston
    132 Posts

    Re: HTTP Server 8.5 does not redirect requests to nodes in cluster on Linux

    Thanks for writing in and explaining your scenario.

    My first thought is that the web server plug-ins either have not been installed or were not configured properly. Have you installed the Web Server Plug-ins for WebSphere Application Server v8.5? Have you installed the stand-alone version of the WebSphere Customization Toolbox and included the Web Server Plug-ins Configuration Tool (PCT)? Did you register the plug-ins location with the PCT and then create web server definitions for the web servers?

    Previously, the installation of the IBM HTTP Server also included the web server plug-ins and allowed for some the basic configuration during the installation process. With this arrangement, there was always a one-to-one mapping between a set of web server plug-ins and a web server installation.

    Starting with the release of WebSphere Application Server v8.0 and the switch to using IBM Installation Manager, there was a movement to cleanly separate "installation" from "configuration" which had a significant impact on the process for setting up a web server with an application server.

    With Installation Manager, IBM HTTP Server, Web Server Plug-ins, and the WebSphere Customization Toolbox are viewed as completely separate installation 'packages'. Nevertheless, Installation Manager can install all of them at one time (similar to the previous install technology). However, there is now the extra post-installation step to configure the web server plug-ins.

    Because the web server plug-ins are separate from the web server and they have their own configuration tool, there can now be a one-to-many mapping between the plug-ins and web servers. That is, the plug-ins can be installed once to a machine and can be separately configured to function with all the web servers on that machine. For those who prefer the previous model, the web server plug-ins still can be installed multiple time to the same machine to create the one-to-one mapping as well.

    The WebSphere Application Server Information Center has illustrations of several common/popular topologies with the step-by-step installation and configuration process mapped out. The article is located at this URL:

    There are other articles which go into more detail than I have time for in this response:

    Installing and Configuring Web Server Plug-ins
    - This article explains the process at a high level and has sub-topic articles that cater to specific topologies, such as: Multiple web servers and remote Application Servers (

    Implementing a web server:

    Administrator Best Practices: Plug-ins Configuring
    Hopefully, the information provided above or the article in the Information Center will help identify the issue. However, if you follow the steps outlined above and are still having a problem connecting to the application, then please write back and describe the situation in more detail.

    Scott Johnston
    WebSphere Application Server
    Installation and Configuration User Experience Lead