This article will help you to understand how requests traverse various WebSphere Application Server topologies.

Stand-alone server environment

In a stand-alone server environment, a web server can be remote to the application server machine or local, but there can only be one defined to WebSphere Application Server. The web server always resides on an unmanaged node.

  • Remote web server
    In this scenario, the application server and the web server are on separate machines. The web server machine can reside in the internal network, or more likely, will reside in the DMZ. Use this configuration for a production environment. See figure below:
    How-Requests-Traverse-Various-WebSphere-Application-Server-Topologies
  • Local web server
    In this scenario, a stand-alone application server exists on machine A. The web server and web server plug-in are also installed on machine A. This topology is suited to a development environment or for internal applications. See figure below:
    How-Requests-Traverse-Various-WebSphere-Application-Server-Topologies

Distributed server environment

Web servers in a distributed server environment can be local to the application server or remote. The web server can also reside on the deployment manager system. You have the possibility of defining multiple web servers and the web servers can reside on managed or unmanaged nodes.

  • Remote web server
    The deployment manager and the web server are on separate machines. The web server machine can reside in the internal network, or more likely, it resides in the DMZ. Use this configuration for a production environment.Note that this scenario and the process are almost identical to the process outlined for a remote web server in a stand-alone server environment. The primary difference is that the script that defines the web server is run against the deployment manager, and you will see an unmanaged node created for the web server node. In figure below, the node is unmanaged because there is no node agent on the web server system.
    How-Requests-Traverse-Various-WebSphere-Application-Server-Topologies
  • Local to a federated application server
    In this scenario, the web server is installed on a machine that also has a managed node. Note that this scenario functions the same if the deployment manager were installed on Machine B.
    How-Requests-Traverse-Various-WebSphere-Application-Server-Topologies

If you find any missing point in here, please let us know in comment section or tweet us at @techienotecom. To get more articles like this, subscribe to our RSS feeds.

How Requests Traverse Various WebSphere Application Server Topologies
Tagged on:         

One thought on “How Requests Traverse Various WebSphere Application Server Topologies

  • November 26, 2015 at 5:13 am
    Permalink

    Hi,

    Very nice website for was. Keep the good work.

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

Notify me of followup comments via e-mail. You can also subscribe without commenting.

Recommend on Google