Use this page to view information about and change configuration settings for a cluster. A cluster consists of a group of application servers. If one of the application servers fails, requests are routed to other members of the cluster.
To view this administrative console page, click
.To define a new cluster, click New to start the Create a new cluster wizard.
Specifies a logical name for the cluster. The name must be unique among clusters within the containing cell.
This field indicates whether the cluster is partially started, started, partially stopped, stopped, or unavailable. If the status is unavailable, the node agent is not running in that node and you must restart the node agent before you can start the server.
After you click Start or Ripplestart to start a cluster, each server that is a member of that cluster launches if it is not already running. When the first member launches, the state changes to partially started. The state remains partially started until all cluster members are running. When all cluster members are running, the state changes to running and the status changes to started. Similarly, when you click Stop or ImmediateStop to stop a cluster, the state changes to partially stopped when the first member stops, and then changes to stopped when all cluster members are not running.
![]() |
Started | The server is running. |
![]() |
Partially stopped | The server is in the process of changing from a started state to a stopped state. |
![]() |
Stopped | The server is not running. |
![]() |
Unknown | The server status cannot be determined. |