You can use either the administrative console, or the wsadmin
tool to manage a proxy server cluster .
Before you begin
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, you 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.
문제점 방지: - 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
About this task
Complete one or more of the following tasks to use the
administrative console to manage your proxy server clusters.
Procedure
- In the administrative console, click .
- Select the proxy server clusters and click either or 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, your 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 or 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 ,
and type the name for the cluster in the field to create a new proxy server
cluster,
- Click , and then click 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 . Type
the name for the proxy server in the field.
Results
You have successfully modified a proxy server cluster.