Example of Writing and Retrieving Call State Data

16-4 Oracle WebLogic Communications Server Administration Guide

16.2.1 Single-node Topologies

Both the All-In-One Administration Server and All-In-One Managed Server Topologies are intended to provide an out-of-box experience in which Presence, Instant Messaging, Voice-Over-IP, Third Party Calling, and Presence and MessagingWeb Services work with an OWLCS client. These topologies are recommended for use in a test and evaluation environment, not in a production environment. They do not include High-Availability support. In an All-In-One Administration Server topology, the one and the only server the Administration Server runs in a single JVM. In an All-In-One Managed Server topology, the Managed Server runs in one JVM and the Administration Server runs in a separate JVM.

16.3 Oracle WebLogic Communication Services Enterprise Deployment Topology

This section describes the Oracle WebLogic Communication Services OWLCS high-availability topology: Enterprise Deployment. The following sections are included: ■ Section 16.3.1, Introduction to OWLCS Enterprise Deployment Topology ■ Section 16.3.2, Geographic Redundancy ■ Section 16.3.3, Failover

16.3.1 Introduction to OWLCS Enterprise Deployment Topology

OWLCS supports a multi-node deployment topology. A SIP Container cluster is defined as a set of SIP Container instances that share state related to the applications. A cluster consists of multiple nodes, with each node running one instance of OWLCS. A highly available OWLCS cluster provides the following: ■ Replication of objects and values contained in a SIP Application Session ■ Database backed location service data ■ Load balancing of incoming requests across OWLCS SIP nodes ■ Overload protection protects the server from malfunctioning in the event of overload and rejects traffic which cannot be handled properly. ■ Transparent failover across applications within the cluster. If an instance of an application fails, it becomes unresponsive and the session can fail over to another instance of the application, on another node in a cluster. Note: For more information on OWLCS as a scalable Presence deployment, see Appendix G, Deploying a Scalable Presence Deployment Note: For information on installing and configuring OWLCS Enterprise Deployment topology, see Oracle WebLogic Communication Services Installation Guide.