Manage a proxy server cluster
We can use either the console, or wsadmin.sh to manage a proxy server cluster .
The main reason for creating a proxy cluster is to make it easier to administer multiple proxy servers. For example, if your proxy servers are members of a proxy server cluster, we can specify configuration settings for that proxy server cluster, and the settings are automatically applied to all of the proxy servers in that cluster. Creating a proxy server cluster also enables you to simultaneously start and stop all of the proxy servers in that cluster.
Avoid trouble:
- A proxy server cluster does not have some of the same functionality that an application server cluster has. For example, because there is no data replication among members of a proxy cluster. failover between proxy servers in the cluster is not supported. If a proxy server is down, all active connections owned by the proxy server go away and then incoming requests fail. Both proxy servers and proxy clusters, on the other hand, support the high availability and failover of backend servers, such that the proxy server can detect if a backend server is down and then forward the requests to a server that has the session replicated.
- When a proxy server is part of a proxy server cluster, the only HTTP proxy server setting that can be set at the proxy server level is Local outbound TCP address. The other HTTP proxy server settings must be set at the proxy cluster level.
gotcha
Complete one or more of the following tasks to use the console to manage the proxy server clusters.
- In the console, click Servers > Clusters > Proxy server clusters.
- Select the proxy server clusters and click either Start or RippleStart to start one or more proxy server clusters.
- Start launches the server process of each member of the cluster by calling the node agent for each server to start the servers. After all servers are running, the state of the cluster changes to running. If the call to a node agent for a server fails, the server does not start.
- RippleStart combines stopping and starting operations. It first stops and then restarts each member of the cluster. For example, the cluster contains 3 cluster members named server_1, server_2 and server_3. When you click RippleStart, server_1 stops and restarts, then server_2 stops and restarts, and finally server_3 stops and restarts. Use the RippleStart option instead of manually stopping and then starting all of the application servers in the cluster.
- Select the proxy server clusters and click either Stop or ImmediateStop to stop one or more proxy server clusters.
- Stop halts each server in a manner that allows the server to finish existing requests and allows failover to another member of the cluster. When the stop operation begins, the cluster state changes to partially stopped. After all servers stop, the cluster state becomes stopped.
- ImmediateStop stops the server quickly without regard to existing requests. The server ignores any current or pending tasks. When the stop operation begins, the cluster state changes to partially stopped. After all servers stop, the cluster state becomes stopped.
- Click the name of the proxy server cluster to access the Configuration tab to change the configuration settings.
- Click New, and type the name for the cluster in the Cluster name field to create a new proxy server cluster,
- Click Delete, and then click OK to delete an existing proxy server cluster.
- To add new members to a proxy server cluster, click the name of an existing proxy server cluster, and click Cluster members > New. Type the name for the proxy server in the Member name field.
Results
You have successfully modified a proxy server cluster.
Related tasks
Create a proxy server cluster using wsadmin
Proxy server cluster collection
Proxy server cluster member collection
Proxy cluster member templates collection
Proxy cluster member template settings
Create a proxy cluster: Basic proxy cluster settings
Create a proxy cluster: Create first proxy cluster member
Create a proxy cluster: Create additional proxy cluster members
Create a proxy cluster: Summary settings