| Oracle® Communications WebRTC Session Controller Installation Guide Release 7.0 E40974-02 |
|
|
PDF · Mobi · ePub |
| Oracle® Communications WebRTC Session Controller Installation Guide Release 7.0 E40974-02 |
|
|
PDF · Mobi · ePub |
This chapter provides information about planning your Oracle Communications WebRTC Session Controller installation.
When planning a WebRTC Session Controller installation, you consider how many physical servers can handle your subscriber base and how many signaling and media server nodes to include in your cluster.
The difference between a WebRTC Session Controller development system and a WebRTC Session Controller production system is only the number of machines in the system. You install the same components in a test system that you install in a production system.
See "WebRTC Session Controller System Requirements" for information about required hardware and software.
The following section describes recommended Signaling Engine installation topologies.
Figure 2-1 shows simple Signaling Engine installation topology, a domain with a single Administration server. The Administration server hosts all of the Signaling Engine applications on a single machine.
While a simple single host configuration is sufficient for development and Proof of Concept (PoC) installations, for production systems, a robust, fault-tolerant system is required.
Figure 2-2 shows a fault tolerant Signaling Engine installation topology. In this topology, the Administration server is installed on a separate machine from the two independently hosted clustered Managed Servers. In addition, there are two separately hosted Replicas. The Managed Servers can be separated geographically for additional fault tolerance, and additional replicas can be added as required.
Each element in this topology illustration is described in Table 2-1.
Table 2-1 Description of the Elements in the Signaling Engine Server and Coherence Standard Installation Topology
| Element | Description and Links to Additional Documentation |
|---|---|
|
Signaling Engine Domain |
A logically related group of Java components (in this case, the Administration Server, Managed Signaling Engines, and other related software components). For more information, see " |
|
Administration Server |
The central control entity of a domain which maintains the domain's configuration objects and distributes configuration changes to Managed Servers. For more information, see " |
|
Cluster |
A collection of multiple Signaling Engine instances running simultaneously and working together. For more information, see " |
|
Machine |
Logical representation of the computer that hosts one or more WebLogic Server instances (servers). Machines are also the logical glue between Signaling Engine Managed Servers and the Node Manager; in order to start or stop a Managed Server with Node Manager, the Managed Server must be associated with a machine. |
|
Managed Server |
Host for your applications, application components, Web services, and their associated resources. For more information, see " |
WebRTC Session Controller Signaling Engine nodes are based on Oracle Coherence. Decide how to configure Oracle Coherence settings for your WebRTC Session Controller Signaling Engine topology, for example, how many nodes to add to the cluster when a node failure occurs. For more information, see "Configuring and Managing Coherence Clusters" in Administering Clusters for Oracle WebLogic Server.
Media Engine nodes are installed on certified bare metal servers. Additional nodes can be added as required to support greater volumes of media traffic. For more information see Oracle Communications Application Session Controller System Installation and Commissioning Guide.
|
 Copyright © 2013, 2014, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
