This topic describes how to create a cluster of proxy servers, using the wsadmin command, that can route requests to applications in a cell. 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.
$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.
$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.
$AdminConfig save
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.