.ear Files .ear files for deploying your applications are found in your Configuration Files Configuring components is accomplished through various

16-12 Oracle WebLogic Communications Server Administration Guide Figure 16–6 Geo-Redundancy In the preceding figure, Geo-Redundancy is portrayed. The process proceeds in this manner:

1. Call is initiated on a primary Cluster site, call setup and processing occurs

normally.

2. Call is replicated as usual to the sites SIP State Tier, and becomes eligible for

replication to a secondary site.

3. A single replica in the SIP State Tier then places the call state data to be replicated

on a JMS queue configured on a replica site.

4. Call is transmitted to one of the available engines using JMS over WAN.

5. Engines at the secondary site monitor their local queue for new messages. Upon

receiving a message, an Engine in the secondary site persists the call state data and assigns it the site ID value of the primary site.

16.3.3 Failover

Oracle’s High Availability solutions include failover support for all levels of your system. During failover, the functions of a component that is malfunctioning or non-operational are addressed by a standby or replacement component. This is done without manual intervention, and in most cases end users will not be able to detect that the system is taking failover actions. There are two main types of failover: Session Failover and Service Failover. Session Failover occurs when the session, connection, or power are interrupted. During Session Failover, ongoing calls or requests are handled by backup nodes, and users do not detect that the condition arose. The SIP Container provides services to upper-levels to help recover from session failure. The SIP protocol rebuilds state at certain pre-defined times for example, every hour. This is designed to protect unreliable networks. When Service Failover occurs such as when a node in a cluster of nodes goes down, the load is handled by other nodes in the cluster. If an individual request is being processed at the time, it will fail, but subsequent requests will be picked up by the functioning nodes.