1 WebRTC Session Controller Installation Overview

This chapter provides an overview of Oracle Communications WebRTC Session Controller installed components and of the WebRTC Session Controller installation process. Subsequent chapters describe installation steps in detail.

For more detailed WebRTC Session Controller overview information, see the discussion about system architecture in WebRTC Session Controller Concepts.

About WebRTC Session Controller Media Engine and Signaling Engine

WebRTC Session Controller comprises two main sub components:

WebRTC Session Controller Signaling Engine (Signaling Engine)
WebRTC Session Controller Media Engine (Media Engine)

Signaling Engine handles signaling services between Web browser clients, traditional Session Initialization Protocol (SIP) networks and the Media Engine, while Media Engine handles media streaming as well Traversal Using Relay Network Address Translation (TURN) functionality.

Although these two sub components work together as a single solution, and cannot be used independently, they employ completely different installation models. For instance, Signaling Engine is currently certified on a single operating system, while Media Engine supports a selection of bare metal servers. Likewise, Signaling Engine utilizes a graphical installer, while Media Engine is a command line driven installation. In addition, each component requires additional independent configuration and post installation steps. For those reasons, you must pay careful attention to the instructions contained in this guide.

Overview of the WebRTC Session Controller Installation Procedure

The installation procedure follows these steps:

Plan your installation. When planning your installation, you do the following:
- Determine the scale of your implementation, for example, a small test system or a large production system.
- Determine how many physical machines you need, and which software components to install on each machine.
- Plan the system topology, for example, how the system components connect to each other over the network.
See "Planning Your WebRTC Session Controller Installation" for more information.
Review system requirements. System requirements include:
- Hardware requirements, such as disk space
- System software requirements, such as operating system (OS) versions and OS patch requirements, and Java Virtual Machine (JVM) process requirements (such as memory settings)
- Information requirements, such as IP addresses and host names
See "WebRTC Session Controller System Requirements" for more information.
Perform pre-installation tasks including assigning IP addresses to network assets and installing necessary support software.

See "WebRTC Session Controller Pre-Installation Tasks" for more information.
Install WebRTC Session Controller Signaling Engine.

See "Installing WebRTC Session Controller Signaling Engine" for more information.
Configure a WebRTC Session Controller Signaling Engine domain.

See "Creating and Configuring a WebRTC Session Controller Signaling Engine Domain" for more information.
Perform Signaling Engine post-installation tasks.

See "WebRTC Session Controller Signaling Engine Post-Installation Tasks" for more information.
Install WebRTC Session Controller Media Engine.

See "Installing WebRTC Session Controller Media Engine" for more information.
Perform Media Engine post-installation tasks.

See "WebRTC Session Controller Media Engine Post-Installation Tasks" for more information.
Troubleshoot any installation issues.

See "Troubleshooting a WebRTC Session Controller Installation" for more information.

Ensuring a Successful Installation

The WebRTC Session Controller installation should be performed by qualified personnel. You must be familiar with both Signaling Engine and Media Engine software and the operating systems on which you are installing the software.

Follow these guidelines:

As you install each component; for example, the JDK and WebRTC Session Controller Signaling Engine, verify that the component installed successfully before continuing the installation process.
Pay close attention to the system requirements. Before you begin installing the software, make sure your system has the required base software. In addition, make sure that you know all of the required configuration values, such as host names and port numbers.
As you create new configuration values, write them down. In some cases, you might need to re-enter configuration values later in the procedure.

Planning the Network and Hardware Setup

Before you can install WebRTC Session Controller, you must gather some information about your system and decide on the directories in which to install the software. You need to know:

The network names or IP addresses of the machines on which you are going to install the following components:
- The Signaling Engine
- The Media Engine
For machines hosting Signaling Engine installations, the directory on each machine which will serve as your Middleware_home directory. This directory serves as a repository for common files that are used by WebRTC Session Controller products installed on the same machine, such as WebLogic Server and a Java Development Kit.

The files in the Middleware_home directory are essential to ensuring that software operates correctly on your system. They:
- Facilitate checking of cross-product dependencies during installation
- Facilitate Service Pack installation
Passwords for administrative users on all server types.

WebRTC Session Controller has been tested to run on specific hardware and software platforms. "WebRTC Session Controller System Requirements" outlines supported configurations in detail. Unless your installation has been specified differently in cooperation with Oracle, only those configurations are supported.

Directory Placeholders Used in This Guide

Table 1-1 lists placeholders that are used in this guide to refer to the directories that contain WebRTC Session Controller system components.

Table 1-1 Directory Placeholders

Placeholder	Directory
Central_inventory_location	The directory in which the Oracle inventory file lives. The Oracle inventory lists all Oracle software installed on a machine.
Domain_home	The location of a configured WebRTC Session Controller WebLogic domain.
Middleware_home	The storage location for common WebRTC Session Controller files.
Oracle_home	The storage location for common Oracle software files.
temp_dir	A temporary directory into which you extract the installation images for Signaling and Media engine.
WSC_home	The directory in which WebRTC Session Controller is installed.