Oracle WebLogic Server SIP Container Base Platform Topologies 7-5
data to the RDBMS after the call dialog has been established, and retrieves or deletes the persisted call state data as necessary to modify or remove the call state. See
Section 4.4, Storing Long-Lived Call State Data In A RDBMS .
7.5 Geographically-Redundant Installations
Oracle WebLogic Server SIP Container can be installed in a geographically-redundant configuration for customers who have multiple, regional data centers, and require
continuing operation even after a catastrophic site failure. The geographically-redundant configuration enables multiple Oracle WebLogic Server SIP
Container installations complete with engine and SIP data tier clusters to replicate call state transactions between one another. If the a particular sites installation were to
suffer a critical failure, the administrator could choose to redirect all network traffic to the secondary, replicated site to minimize lost calls. See
Section 4.6, Using Geographically-Redundant SIP Data Tiers.
7.6 Example Hardware Configurations
Oracle WebLogic Server SIP Containers flexible architecture enables you to configure engine and SIP data tier servers in a variety of ways to support high throughput
andor provide high availability.
7.7 Alternate Configurations
Not all Oracle WebLogic Server SIP Container requirements require the performance and reliability provided by multiple servers in the engine and SIP data tier. On a
development machine, for example, it is generally more convenient to deploy and test applications on a single server, rather than a cluster of servers.
Oracle WebLogic Server SIP Container enables you to combine engine and SIP data tier services on a single server instance when replicating call states is unnecessary. In a
combined-tier configuration, the same Oracle WebLogic Server SIP Container instance provides SIP Servlet container functionality and also manages the call state for
applications hosted on the server. Although the combined-tier configuration is most commonly used for development and testing purposes, it may also be used in a
production environment if replication is not required for call state data.
Figure 7–2 shows an example deployment of multiple combined-tier servers in a production
environment.
7-6 Oracle WebLogic SIP Server Container Administrators Guide
Figure 7–2 Single-Server Configurations with SIP-Aware Load Balancer
Because each server in a combined-tier server deployment manages only the call state for the applications it hosts, the load balancer must be fully SIP aware. This means
that the load balancer actively routes multiple requests for the same call to the same Oracle WebLogic Server SIP Container instance. If requests in the same call are not
pinned to the same server, the call state cannot be retrieved. Also keep in mind that if a Oracle WebLogic Server SIP Container instance fails in the configuration shown in
Figure 7–2 , all calls handled by that server are lost.
8
Upgrading Deployed SIP Applications 8-1
8
Upgrading Deployed SIP Applications
The following sections describe how to upgrade deployed SIP Servlets and converged SIPHTTP applications to a newer version of the same application without losing
active calls:
■
Section 8.1, Overview of SIP Application Upgrades
