2 Offline Mediation Controller System Requirements

This chapter describes the software and hardware requirements for installing Oracle Communications Offline Mediation Controller.

Software Requirements

Offline Mediation Controller is installed on a Linux platform. You must install and connect all required software for optimal performance.

Important:

You must have the same version of Offline Mediation Controller running on the Administration Server and the Administration Client.

Supported Operating Systems

Table 2-1 lists operating systems that support Offline Mediation Controller.

Table 2-1 Offline Mediation Controller Operating Systems Requirements

Product	Version	Notes
Oracle Linux, x86-64 (64-bit)	5 UL3+	NA
Oracle Linux, x86-64 (64-bit)	6.3	Support added in Offline Mediation Controller 6.0 Patch Set 2.
Red Hat Enterprise Linux, x86-64 (64-bit)	5 UL3+	NA
Red Hat Enterprise Linux, x86-64 (64-bit)	6.3	Support added in Offline Mediation Controller 6.0 Patch Set 2.
Oracle Solaris for SPARC (64-bit)	10 Update 4+	NA
Oracle Solaris for x86 (64-bit)	10 Update 6+	NA
Windows (64-bit)	7	Support added in Offline Mediation Controller 6.0 Patch Set 1. Only supported for Administration Client.
Windows (64-bit)	8.1	Support added in Offline Mediation Controller 6.0 Patch Set 3. Only supported for Administration Client.

Additional Software Requirements

Table 2-2 lists software required for running Offline Mediation Controller.

Table 2-2 Offline Mediation Controller Software Requirements

Product	Version	Notes
Oracle Database 11g Server Enterprise Edition (for single or Oracle Real Application Clusters (RAC) installation)	11g Release 2	NA
Oracle Database 12c Server Enterprise Edition (for single or Oracle Real Application Clusters (RAC) installation)	12c Release 1	Support added in Offline Mediation Controller 6.0 Patch Set 1.
Oracle Java	1.6	NA
Oracle Java	1.7	Support added in Offline Mediation Controller 6.0 Patch Set 1.
Oracle Java	1.8	Support added in Offline Mediation Controller 6.0 Patch Set 3 (Offline Mediation Controller 6.0.0.3.2 and later patch levels).
Oracle Unified Directory	11.1.1.5.0	NA
Oracle Unified Directory	11.1.2.0.0	Support added in Offline Mediation Controller 6.0 Patch Set 1.

The Offline Mediation Controller Installer checks for all required software and displays errors if it detects any missing or unavailable components, or if there are any connectivity-related issues.

Hardware Requirements

The number and configuration of the machines that you employ for your Offline Mediation Controller installation depend on the scale and the kind of deployment you have planned according to your networks.

Administration Server, Administration Client, and Node Manager and the Oracle Unified Directory server can reside on the same device.

Table 2-3 provides the minimal hardware requirements for installing Offline Mediation Controller.

Table 2-3 Offline Mediation Controller Minimum Hardware Requirements

Component	Requirement
Hard disk	5 GB of free disk space
Processor	Oracle recommends using twin cores, each running at 1.5 GHz CPU.
Memory	A minimum of 4 GB physical memory and 4 GB swap. If you plan to have the database installed on the same server as Offline Mediation Controller, the minimum memory requirements increase to 6 GB physical memory and 6 GB swap.

Component

Requirement

Hard disk

5 GB of free disk space

Processor

Oracle recommends using twin cores, each running at 1.5 GHz CPU.

Memory

A minimum of 4 GB physical memory and 4 GB swap.

If you plan to have the database installed on the same server as Offline Mediation Controller, the minimum memory requirements increase to 6 GB physical memory and 6 GB swap.

Information Requirements

This section describes the information that you will be required to provide during the Offline Mediation Controller installation process. You define some of these configuration values when you install and configure Oracle Database and Oracle Unified Directory for Offline Mediation Controller during the pre-installation tasks.

Note:

Oracle recommends that you print the tables and record the values for future reference.

Oracle Unified Directory Connection Information

Table 2-4 lists the Oracle Unified Directory details that are required during Offline Mediation Controller installation.

Table 2-4 Oracle Unified Directory Connection information

Field	Description	Value	Sample Value
Host Name	The IP address or the host name of the machine on which Oracle Unified Directory is installed.	-	example.com
LDAP Listen Port	The port used by LDAP to send and receive data.	-	1389
Administration Connector Port	The port used for administration traffic with Oracle Unified Directory.	-	4444
Root User DN	The root user distinguished name (DN).	-	cn=Directory Manager
Password	The root user bind password for Oracle Unified Directory.	-	-
OUD Instance Path	The path to the directory where the Oracle Unified Directory instance is installed.	-	-
Directory Base DN	The base DN for Oracle Unified Directory.	-	dc=ocomcexample.com

Database Connection Information

Note:

The database information is required only when using the JDBC Distribution Cartridge (DC). The Oracle database stores call records it receives from the JDBC DC.

Table 2-5 lists database details that are required when using the JDBC DC.

Table 2-5 Database Connection information

Field	Description	Value	Sample Value
Hostname	The IP address or the host name of the machine on which the Oracle database is installed.	-	-
Port number	The listener port number assigned to the Oracle database service.	-	-
User name	The database user name. This user must have the following capabilities on the database: create user, grant any role, grant any privileges, select any table for Enterprise edition, and DBA for XE.	-	-
Password	The password for the database user.	-	-
Service Name	The name of the Oracle database service.	-	-

About Installing Multiple Administration Servers

The Administration Server is a daemon process that communicates through commands and log messages with the Administration Client. The Offline Mediation Controller system can have one or two Administration Servers (one primary and one backup server).

If you configure a Offline Mediation Controller system with two Administration Servers, the following considerations apply:

Each Administration Server must be installed on a supported Unix (Solaris) or Linux (Oracle/Red Hat Enterprise) platform workstation.

The primary and backup Administration Servers do not communicate with one another for automatic cutover. (You must manually effect cut-over from the primary to the backup Administration Server.)
Each Administration Server is aware of, and can independently control, the entire Offline Mediation Controller system, including all Node Managers and nodes.
Administration Clients connect to the system by using the IP address of a specific Administration Server. For this reason, an Administration Client cannot connect to multiple Administration Servers simultaneously. The Administration Client displays a list of currently configured Administration Servers for the Offline Mediation Controller system.

Using Multiple Node Managers on a Single Mediation Host

You can create multiple Node Managers on a single mediation host. Each Node Manager independently controls a different set of node chains. This feature allows you to create node chains under one Node Manager without affecting the operation of any node chains controlled by another Node Manager in the same Offline Mediation Controller system.

The use of multiple Node Managers also enables you to effectively partition a Offline Mediation Controller system into manageable pieces that have predictable resource requirements. If you create multiple Node Managers on the same Unix (Solaris) or Linux (Oracle/Red Hat Enterprise) host, you must start each one using a different UDP port number.

To administer node chains controlled by any Node Manager on an mediation host, you must connect from the Offline Mediation Controller client to the Administration Server associated with that Node Manager.