Active-Active Configuration
An active-active server cluster contains a minimum of two servers. Both servers actively run applications and services. Each server might host different applications or might host instances of the same application. If one server fails, then its processing load is transferred to the other server.
Active-active configuration is the most common server clustering strategy for servers other than the database server.
This topic is part of About Server Clustering.
Potential Port Conflicts
Some Siebel Server components, such as Siebel Connection Broker (SCBroker), Siebel Gateway, and Siebel Remote Synchronization Manager, listen on a configurable static port. When these components run in an active-active cluster, you must plan your port usage so there is no port conflict after failover.
For example, an active-active server cluster contains two computers, each running a Siebel Server. If one computer fails, then the other computer hosts two Siebel Servers. Siebel Servers include a number of services, such as Siebel Connection Broker, that use a dedicated port. If this port number was the same on both computers, then a port conflict occurs after failover.
Capacity Planning
Active-active clusters use all of the server platforms continuously. Consequently, they take better advantage of computing resources than active-passive clusters. When doing capacity planning, make sure that clustered servers have sufficient capacity to handle a failover. Because failovers are usually infrequent and normally last only a short time, some performance degradation is often acceptable.
An active-active server cluster contains a minimum of two servers. Both servers actively run applications and services. Each server might host different applications or might host instances of the same application. If one server fails, then its processing load is transferred to the other server.
Active-active configuration is the most common server clustering strategy for servers other than the database server.