online mediation controller - basic admin 3 - 1

Online Mediation Controller 3 - 1

Schedule: Timing Topic

<xx> minutes Lecture

<xx> minutes Practice

<xx> minutes Total

The Oracle JRockit JDK has specifically been designed for server-side usage and has a large

number of features for performance and troubleshooting analysis in run time.

Beyond the requirements mentioned in the slide a Signaling Server requires a Dialogic TDM

signaling board and Dialogic software for Signaling Servers that run in a TDM-based network.

Online Mediation Controller requires that all servers accurately synchronize their system

clocks to a common time source, to within one or two milliseconds. Oracle recommends using

an NTP client or daemon and synchronizing all Online Mediation Controller servers to a

common NTP server.



When installing using Silent Mode specify the necessary installation parameters in one of two

ways:

• By editing the parameters in the silentInstaller.sh installer file

• By editing an installation response file, *.rsp.

Online Mediation Controller acts as a front end for the Oracle Communications Billing and

Revenue Management product towards the network. When deployed with additional bundles,

Online Mediation Controller can support SIP and various variants of IN protocols.

oracle_home/ocsb61 – Base directory for the Online Mediation Controller installation.

oracle_home/ocsb61/admin_server – Contains binaries for the Administration Console, and

the start scripts and modules related to the Administration Console.

oracle_home/ocsb61/managed_server – Contains binaries for the Processing Server or

Signaling Server, and the start scripts and modules related to the server.

oracle_home/ocsb61/jrrt – Contains the Oracle JRockit JDK. This directory is created only if

you specified to install the Oracle JRockit JDK during the installation. Selecting Java JDK

would create a jdk directory.

oracle_home/brm – Contains a separate installation of Billing and Revenue Management.


Production Installs

The Online Mediation Controller installation process installs the Administration Console and a

single managed server. The best practice for creating a multi-server system is to copy the

contents of the managed server directory to a new directory for each server you want to add.

To create a multi-server domain on a single physical server:

1. Create a new server directory for each additional server. To simplify your directory structure,

you may choose to create the directories in the ocsb directory of the existing the Oracle home,

alongside the existing managed server directory.

For example: Oracle_home/ocsb/new_server_directory

2. Copy the contents of the installed server directory to each new server directory that you

added.

The default installed server directory is: oracle_home/ocsb61/managed_server


To deploy a multi-server system in a single Oracle home, you first run the installer to install

the initial managed server. You then add additional servers in the same home by copying and

pasting the managed server directory to additional locations.



The domain creation script creates Online Mediation Controller domains based on the

settings in property files in the Administration Console directory. By default, the setting that

controls security in the domain is enabled. Before you run the script, you must either disable

the setting or, if you want to retain security for the domain, set up the client and server

certificate keystores on the host system.

The following snippet of a shell script generates certificate keys, stores them in keystores,

generates certificate files (.cer) and places the files in the appropriate trusted storage:

keytool -genkeypair -dname "cn=Axia Server, ou=CGBU, o=Oracle, c=US" -alias server -

keypass pass1234 -keystore serverkeystore -storepass pass1234 –noprompt

keytool -exportcert -alias server -keystore serverkeystore -storepass pass1234 -rfc -file

server.cer

keytool -importcert -file client.cer -keystore servertruststore -storepass pass1234 -noprompt

keytool -importcert -file server.cer -keystore clienttruststore -storepass pass1234 -noprompt

Instructor Note:

The lab for this lesson has students disable client and server certificate keystores. The topic

of disabling is not covered in any detail here because of the experience they will have in labs.

The IP multicast address and port is the address on which managed servers and the

Administration Console exchange certain types of internal communication within the domain.

Unicast is also supported and can be used with well know IP addresses to group domains in a

cluster.


A production system should always be deployed as a set of at least two servers per domain. In

the slide two domains are represented, one domain for signaling, ssu_domain (signaling server

unit) and one for processing, pn_domain.

The domain configuration directory needs to be accessible to the Administration Console and

all managed servers in the cluster. In this example an NFS disk is used to give domain

configuration file system access to managed servers.

Each server is defined in the domain configuration by specifying its name and listening ports.

This is done automatically when you use the Administration Console to create a server for a

specific domain. The configuration is kept in provisioning.agent.config within the domain’s

initial.zip file.

The directory structures in the diagram represent only the critical parts of software installation

for each node.



The Administration Console provides the configuration interface for the Online Mediation

Controller domain. After creating the domain, you can start configuring it from the

Administration Console interface displayed in the slide.


The screen shot in the slide illustrates the Administration Console being used to add a

managed server.


Managed Servers apply the domain configuration to network traffic.

Degraded Mode service and Subscriber Profile are features that require persistent storage.

Use JMX MBean operations or the Administration Console to configure the data storage

through the following steps:

1. Configure the database connection or local file storage location for each managed server.

2. Specify the persistence mechanism each feature should use by installing the appropriate

persistence package. Using the Administration Console, expand Domain Management. Click

Packages and then the Install button. Persistence packages are found in the directory

oracle_home/ocsb/admin_console/modules. The screenshot in the slide illustrates installing a

persistence package.

The file initial.zip contains references to all modules for Processing Servers and Signaling

Servers. This must be referenced when starting a managed server.


After adding and configuring managed servers a number of other tasks will complete your

installation.

Interworking Modules provide connectivity between Online Mediation Controller and the

various service platforms and session control platforms in the network.

Signaling Server Units are components that enables connections to SS7-based networks and

IMS-based networks through standard software and hardware interfaces.

The Orchestration Engine takes each session through one or more applications, sequentially,

where each application in its turn supplies the service that the application was created for.


Answer: b

online mediation controller - basic admin 3 - 1

Documents