WebSphere Application Server Version 6.1 Feature Pack for Web Services
             Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows, z/OS

             Personalize the table of contents and search results

Creating a proxy server cluster using the wsadmin command

This topic describes how to create a cluster of proxy servers, using the wsadmin command, that can route requests to applications in a cell.

Before you begin

The cluster includes the machines and nodes that are going to belong to the proxy server cluster. You need to have WebSphere Application Server V6.1 installed. Consider how requests are routed to the proxy server cluster (for example, using domain name server (DNS), Load balancer, or the proxy server). Before you create a cluster, start the deployment manager.

About this task

Create a proxy server cluster, as follows:

Procedure

  1. Start the wsadmin utility.
  2. Create an empty cluster with no members, by typing:
    $AdminTask createCluster {-clusterConfig {-clusterName <name_of_cluster> -clusterType PROXY_SERVER}}
    Or, to create a cluster and add a specified proxy server to that cluster, type:
    $AdminTask createCluster { -clusterConfig {{<name_of_cluster> true PROXY_SERVER}} -convertServer
         {{<node_name> <name_of_proxy_server> "" "" ""}}}
    This proxy server serves as the template for all subsequent members that are added to the cluster.
  3. Add one member at a time to the cluster, as follows:
    $AdminTask createClusterMember {-clusterName <name_of_cluster> -memberConfig  
          {-memberNode <node_name> -memberName <name_of_proxy_server>}}
    If no members exist in the cluster, the first member that is added serves as the template for subsequent members that are added to the cluster.

    When a proxy server is added to a cluster, proxy-specific configuration settings for it can only be configured using the wsadmin scripting client.

  4. Save the configuration changes, as follows:
    $AdminConfig save
  5. Start the proxy server cluster so that request routing is enabled, as described in Starting clusters using scripting.
  6. Configure requests to route to the proxy server. For DNS-based routing, associate the logical name of the site with the IP addresses of the proxy server cluster members in DNS.

    For Load balancer routing, configure the IP addresses of the cluster members as the target of the virtual cluster.

    For Edge proxy or IBM HTTP Server with WebSphere Application Server plug-in-based routing, generate the plug-in configuration file for the proxy server cluster, and configure the Edge proxy or the WebSphere Application Server plug-in with this information.

Results

The proxy server cluster is created with the members and is enabled for routing traffic.

What to do next

Monitor the traffic. See Monitoring the proxy server with PMI for more information.



In this information ...


IBM Redbooks, demos, education, and more


Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

IBM Suggests
Task topic    

Terms of Use | Feedback

Last updated: Nov 25, 2008 2:35:59 AM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.wsfep.multiplatform.doc/info/ae/ae/tjpx_proxycluster.html