SDM 90 Installation

Oracle® Communications Session
Delivery Manager
Installation Guide
Release 9.0
F52425-02
October 2022
Oracle Communications Session Delivery Manager Installation Guide, Release 9.0
F52425-02
Copyright © 2022, 2022, Oracle and/or its affiliates.
This software and related documentation are provided under a license agreement containing restrictions on
use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your
license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license,
transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse
engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is
prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If
you find any errors, please report them to us in writing.
If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related
documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S.
Government, then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software,
any programs embedded, installed, or activated on delivered hardware, and modifications of such programs)
and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end
users are "commercial computer software," "commercial computer software documentation," or "limited rights
data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental
regulations. As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation
of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated
software, any programs embedded, installed, or activated on delivered hardware, and modifications of such
programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and
limitations specified in the license contained in the applicable contract. The terms governing the U.S.
Government's use of Oracle cloud services are defined by the applicable contract for such services. No other
rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications.
It is not developed or intended for use in any inherently dangerous applications, including applications that
may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you
shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its
safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this
software or hardware in dangerous applications.
Oracle®, Java, and MySQL are registered trademarks of Oracle and/or its affiliates. Other names may be
trademarks of their respective owners.
Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are
used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc,
and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered
trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content, products,
and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly
disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise
set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be
responsible for any loss, costs, or damages incurred due to your access to or use of third-party content,
products, or services, except as set forth in an applicable agreement between you and Oracle.
Contents
About This Guide
My Oracle Support viii
Revision History
1 Pre-Installation Tasks
Check System Requirements 1-2
Check Cluster Requirements 1-3
Check Firewall Settings 1-3
Check that Work Orders are in a Committed State 1-7
Upgrade to a Supported Version of Linux 1-7
Upgrade Linux on Your Server 1-7
Check the File Descriptor Count on Your Linux System 1-9
Verify the Required SDM_localhost Entry is in the Hosts File 1-10
Disable the Default HTTP Daemon 1-11
Specify the System Locale 1-12
Set up Local Yum Repository 1-12
Resolve Any Oracle Linux 6 Installation Dependencies 1-13
Configure the NNCentral Account 1-17
Add the NNCentral Group and NNCentral User Account 1-17
Specify NNCentral User Privileges 1-17
Select the Installation Type for Session Delivery Manager 1-18
R226 Compliance 1-24
2 Create a Session Delivery Manager Installation Directory

Unzip the Tar File to Create the Session Delivery Manager Installation Directory 2-1
iii
3 Perform a New Session Delivery Manager Installation
Start the Standalone Installation 3-1
Start the Cluster Installation 3-2
4 Configure the Installed Session Delivery Manager Cluster

Configure a New Cluster 4-1
Add New Nodes to the Cluster 4-2
5 Upgrade Session Delivery Manager

Shut Down the Session Delivery Manager Server 5-1
Upgrade the Session Delivery Manager Standalone Server 5-2
Start the Session Delivery Manager Standalone Upgrade 5-2
Migrate Application Data on the Standalone Server 5-3
Upgrade the Session Delivery Manager Cluster 5-4
Start the Session Delivery Manager Cluster Upgrade 5-5
Migrate Application Data on the Master Cluster Node 5-5
Migrate Application Data on Each Cluster Replica Node 5-7
Transfer the Migrated Application Database Backup to the Replica Node Manually 5-9
6 Typical Installation
Start the Typical Installation 6-2
Configure R226 Compliance and Default User Account Passwords 6-2
Specify the Global ID for Northbound Trap Receivers 6-2
Configure Web Server Security 6-3
Configure Fault Management 6-6
Configure RMI Over SSL 6-7
Configuring OCSDM for IPv4 Support 6-8
Configuring OCSDM for IPv6 Support 6-9
7 Custom Installation
Start the Custom Installation 7-1
Configure RMI Over SSL - Custom Installation 7-8
Configure the Mail Server 7-8
iv
Configure Route Management Central 7-10
Configure Transport Layer Security Certificates 7-10
Configure Entity Certificates 7-10
Configure Trusted Certificates 7-11
About Creating a Report Manager Database Instance on the External Oracle Database 7-12
8 Easy Installation
Start the Easy Installation 8-1
Configure RMI Over SSL - Easy Installation 8-4
Complete the Easy Installation for a Standalone Server 8-4
Complete the Easy Installation for a Cluster 8-4
9 Headless Installation
Unzip the Tar File to Create the SDM Installation Directory 9-1
Specify the Setup Properties File 9-2
Start the Headless Installation 9-4
Configure RMI Over SSL - Headless Installation 9-5
10 Start the Session Delivery Manager Server

Start the Server after a Standalone Installation 10-1
Start the Server after a Cluster Installation 10-2
Check Server Processes 10-3
v
About This Guide
About This Guide

This document and other product-related documents are described in the Related
Documentation table.
Related Documentation
Table 1 Oracle Communications Session Delivery Manager Documentation

Library
Document Name Document Description

Administration Guide Provides the following administration
information:
• Implement OCSDM on your network as a
standalone server or high availability (HA)
server.
• Login to the OCSDM application, access
GUI menus including help, customize the
OCSDM application, and change your
password.
• Access the product plugin service through
the GUI to manage product plugin tasks,
including how product plugins are
uploaded and installed.
• Manage security, faults, and transport
layer security certificates for east-west
peer OCSDM server communication, and
southbound communication with network
function (NF) devices.
• Configure northbound interface
(destination) fault trap receivers and
configure the heartbeat trap for
northbound systems.
• Monitor OCSDM server health to detect
heartbeat messages and display the
server status to prevent health problems,
or view server disk utilization information
and server directory statistics.
• Maintain OCSDM server operations,
which includes database backup and
database restoration and performing
server cluster operations.
• Use available OCSDM server scripts, the
contents of fault trap notifications, and a
list of northbound notification traps
generated by the OCSDM server.
vi
About This Guide
Table 1 (Cont.) Oracle Communications Session Delivery Manager

Documentation Library
Document Name Document Description

Installation Guide Provides the following installation information:
• Do pre-installation tasks, which include
reviewing system requirements, adjusting
linux and firewall settings, completing
OCSDM server settings and configuring
your NNCentral account for security
reasons.
• Do the typical installation to perform the
minimal configuration required to run the
OCSDM server.
• Do the custom installation to perform
more advanced configurations including
the mail server, cluster management,
Route Manager, transport layer security
(TLS), and Oracle database configuration.
Release Notes Contains information about the administration
and software configuration of the OCSDM
feature support new to this release.
Security Guide Provides the following security guidelines:
• Use guidelines to perform a secure
installation of OCSDM on your server,
which includes methods for securing the
server, firewall settings, system support
for encryption and random number
generators (RNG), using HTTPS, and
password guidelines.
• Review Security Manager features that
are used to configure groups, users,
operations, privileges, and manage
access to the system.
• Follow a checklist to securely deploy
OCSDM on your network and maintain
security updates.
REST API Guide Provides information for the supported REST
APIs and how to use the REST API interface.
The REST API interface allows a northbound
client application, such as a network service
orchestrator (NSO), to interact with OCSDM
and its supported product plugins.
SOAP API Guide The SOAP API guide provides information for
the SOAP and XML provisioning Application
Programming Interface (API) client and server
programing model that enables users to write
client applications that automate the
provisioning of devices. The web service
consists of operations that can be performed
on devices managed by the SDM server and
data structures that are used as input and
output parameters for these operations.
vii
About This Guide
My Oracle Support
My Oracle Support (https://support.oracle.com) is your initial point of contact for all
product support and training needs. A representative at Customer Access Support
(CAS) can assist you with My Oracle Support registration.
Call the CAS main number at 1-800-223-1711 (toll-free in the US), or call the Oracle
Support hotline for your local country from the list at http://www.oracle.com/us/support/
contact/index.html. When calling, make the selections in the sequence shown below
on the Support telephone menu:
1. Select 2 for New Service Request.
2. Select 3 for Hardware, Networking, and Solaris Operating System Support.
3. Select one of the following options:
• For technical issues such as creating a new Service Request (SR), select 1.
• For non-technical issues such as registration or assistance with My Oracle
Support, select 2.
You are connected to a live agent who can assist you with My Oracle Support
registration and opening a support ticket.
My Oracle Support is available 24 hours a day, 7 days a week, 365 days a year.
Emergency Response
In the event of a critical service situation, emergency response is offered by the
Customer Access Support (CAS) main number at 1-800-223-1711 (toll-free in the US),
or call the Oracle Support hotline for your local country from the list at http://
www.oracle.com/us/support/contact/index.html. The emergency response provides
immediate coverage, automatic escalation, and other features to ensure that the
critical situation is resolved as rapidly as possible.
A critical situation is defined as a problem with the installed equipment that severely
affects service, traffic, or maintenance capabilities, and requires immediate corrective
action. Critical situations affect service and/or system operation resulting in one or
several of these situations:
• A total system failure that results in loss of all transaction processing capability
• Significant reduction in system capacity or traffic handling capability
• Loss of the system's ability to perform automatic system reconfiguration
• Inability to restart a processor or the system
• Corruption of system databases that requires service affecting corrective actions
• Loss of access for maintenance or recovery operations
• Loss of the system ability to provide any required critical or major trouble
notification
Any other problem severely affecting service, capacity/traffic, billing, and maintenance
capabilities may be defined as critical by prior discussion and agreement with Oracle.
viii
About This Guide
Locate Product Documentation on the Oracle Help Center Site

Oracle Communications customer documentation is available on the web at the Oracle Help
Center (OHC) site, http://docs.oracle.com. You do not have to register to access these
documents. Viewing these files requires Adobe Acrobat Reader, which can be downloaded at
http://www.adobe.com.
1. Access the Oracle Help Center site at http://docs.oracle.com.
2. Click Industries.
3. Under the Oracle Communications sub-header, click the Oracle Communications
documentation link.
The Communications Documentation page appears. Most products covered by these
documentation sets appear under the headings "Network Session Delivery and Control
Infrastructure" or "Platforms."
4. Click on your Product and then Release Number.
A list of the entire documentation set for the selected product and release appears.
5. To download a file to your location, right-click the PDF link, select Save target as (or
similar command based on your browser), and save to a local folder.
Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My
Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info
or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
ix
Revision History
Revision History
This section provides a revision history for this document.
Date Revision
April 2022 • Initial Release.
October 2022 • Includes updates for the SDM 9.0.1
Release.
x
1
Pre-Installation Tasks
Read and understand the summary of pre-installation tasks that need to be done before
installing Oracle Communications Session Delivery Manager. Each of these pre-installation
tasks are described in more detail in subsequent sections.
1. If you have a software version of OCSDM that is installed on your system that is older
than OCSDM, Release 7.5M3, you must upgrade to OCSDM, Release 7.5M3 before you
can install OCSDM, Release 8.x. From 8.x or 8.x.x Release, you can upgrade to OCSDM
9.0.
2. Once the OCSDM system is installed and operational, use the instructions in the Oracle
Communications Session Delivery Manager Administration Guide for more information
regarding the installation of service provider and enterprise product plugins.
3. Read and understand this guide to install OCSDM for the first time or when you upgrade
OCSDM from a previous version. You must do the OCSDM installation before you can
install Oracle Communications Report Manager. Refer to the flow diagram below for more
information:
Figure 1-1 Installing or upgrading OCSDM with Report Manager
4. Check to ensure your system meets the minimum requirements.

5. Shut down your OCSDM server and shut down all applicable server nodes (if you have
OCSDM deployed as a server cluster).
6. Upgrade the version of Linux on your server(s) on which OCSDM is running, if the
version of Linux is not supported with the release of OCSDM that you are installing.
1-1
Chapter 1
Check System Requirements
7. Open the appropriate ports on the network and system firewall.

8. If your system does not rely on DNS, edit the /etc/hosts file to specify a host name
for your system and verify that the required SDM_localhost entry is in the /etc/
hosts file.
9. Disable the default httpd daemon.
10. Specify your system locale to the US English language UTF-8 character encoding
method (LANG=en_US.UTF-8).
11. If any required Linux software libraries that are shared with OCSDM are missing,
you must install them using the yum program.
Note:
Your system may already have these software libraries.
12. Setup the nncentral group and user account to administer OCSDM server
operations on your Linux server.
13. Decide what type of installation for OCSDM that you want to do (Easy-Install,
Headless, Typical, and Custom) based on the setup options that are available for
each installation type.
14. Start the OCSDM installation.
Check System Requirements

Oracle has certified the following hardware and software server platforms as well as
client requirements for use with Oracle Communications Session Delivery Manager.
Note:
Other hardware configurations might work with Oracle Communications
Session Delivery Manager, but Oracle has verified the configurations listed
here.
Oracle Communications Session Delivery Manager Server Requirements

• CPU: 4-core 2.1 GHz processor or better
• 16 GB RAM minimum, 24 GB RAM recommended
• 300 GB hard drive minimum
Supported Operating Systems

Oracle supports the following installations of Oracle Communications Session Delivery
Manager:
• Oracle Linux 6.5 to 6.9 64-bit
1-2
Chapter 1
Check Cluster Requirements
Note:
OpenSSL 1.0.2e-fips or later must be installed on your Linux server in order to
use the HTTPS service on the Apache web server. Most Linux distributions
include OpenSSL as part of the OS installation. You can check the version on
your system by using the following command:
openssl version
OpenSSL 1.0.2e-fips 11 Jun 2017
Oracle supports the following installations of Oracle Communications Session Delivery

Manager with Oracle Communications Report Manager:
• Oracle Communications Report Manager for Oracle Fusion Middleware 12c is supported
on Oracle Linux 7.0 to 7.9 (64-bit).
• Oracle Database 19c with Oracle Fusion Middleware 12c is supported on Oracle Linux
8.0 to 8.6 (64 bit).
Client Requirements
• Oracle recommends Internet Explorer versions 11.900 and later, Mozilla Firefox versions
44 and later, or Google Chrome version 56 and later.
Note:
SDM 8.2.x and SDM 9.0 do not support Microsoft Edge.
• If the server is not part of your DNS domain, the hosts file on each client must be edited
to include the host name and IP address of the Oracle Communications Session Delivery
Manager server.
Language Requirements
On the Linux server, ensure that the US English language UTF-8 character encoding method
is specified.
Check Cluster Requirements

• All cluster nodes must reside at the same geographical location (be co-located).
• All cluster nodes must belong to the same IP network.
• No firewalls can exist between cluster nodes.
• Firewalls can exist between client browsers and the cluster nodes and product devices
managed by a product plugin if their logical ports are specified when you install the
cluster. Refer to the Check Firewall Settings section for more information.
Check Firewall Settings

When setting up Oracle Communications Session Delivery ManagerOracle Communications
Session Delivery Manager in your network, you may have a firewall between the clients
1-3
Chapter 1
(browsers, SOAP, REST etc.) and the OCSDM cluster, and a firewall between the
OCSDM cluster and other devices.
Figure 1-2 OCSDM in your Network with a Firewall between the clients
Session Delivery
Manager Cluster
Network Clients Network
C ons ole
LINK ACT LINK ACT LINK A
Alarm M gmt 0 M gmt 1 M gmt 2 S 0P0 S 0P1 S 1P0
Browser SBC
SOAP
No firewall between members of a cluster.

Uses RMI dynamic port allocation.
Note:
You cannot have firewalls between the servers in a cluster.
If firewalls exist on either side of the OCSDM cluster, ensure the ports listed in the
following table are open. If your operating system comes with a firewall, you need to
apply the same criteria. You must switch off the firewall in your operating system or
ensure these ports are available.
Table 1-1 Communication Between OCSDM Cluster and Network Clients
Port Number Protocol Service Configurable Affects Purpose

Firewall?
8443 TCP HTTPS N Y Apache port.
HTTPS port
for client/
server
communicatio
n.
1-4
Chapter 1
Table 1-1 (Cont.) Communication Between OCSDM Cluster and Network

Clients

Firewall?
8080 TCP HTTP N Y HTTP port for
client/server
communicatio
n.
Table 1-2 Communication Between OCSDM Cluster and Network Devices

Firewall?
161 UDP SNMP N Y SNMP traffic
between the
SDM server
and the device.
162 UDP SNMP N Y SNMP trap
reporting from
the device to
the OCSDM
server.
21 TCP FTP N Y Used for file
transfer.
22 TCP SFTP/SSH N Y Used for secure
file transfer
(such as Route
Manager and
LRT updates)
and SSH
sessions
between
OCSDM and
southbound
devices (For
example, SBC).
3001/ 3000 TCP ACP/ACLI N Y Used by
OCSDM to
communicate
with all versions
of a device.
Table 1-3 Communication Between OCSDM Servers in the Cluster

Firewall?
22 TCP SFTP N Y Used to transfer
files between
OCSDM
servers.
1-5
Chapter 1
Table 1-3 (Cont.) Communication Between OCSDM Servers in the Cluster

Firewall?
1098 TCP RMI N Y RMI
Communication
between host
members in a
cluster.
1099 TCP RMI Lookup N Y RMI registry
port. Used for
the RMI
communication
between host
members in a
cluster.
8005 TCP HTTP N Y Tomcat
shutdown port
used by the
shutdown
script. Can be
blocked on a
firewall
because it is
local to the
OCSDM server.
8009 TCP Apache N Y Tomcat port.
8088 UDP Coherence N Y Used by the
OCSDM
Coherence
REST
application to
handle HTTP
requests on
localhost and
port 8088.
9000 TCP Berkeley N Y Berkeley
database.
61616 TCP Apache N Y Message
broker.
Either port 8080 (HTTP) or port 8443 (HTTPS) must be open on the firewall,
depending on which port you select between the network client and OCSDM server.
Note:
Ports are assigned dynamically through Remote Method Invocation (RMI)
dynamic port allocation. If you are enabling and configuring iptables, all traffic
must be allowed between servers in the cluster. Communication between
clustered OCSDM servers must not be restricted.
1-6
Chapter 1
Check that Work Orders are in a Committed State
Check that Work Orders are in a Committed State

If you are upgrading from the previous version of Oracle Communications Session Delivery
Manager, you must check the status of scheduled work orders before you upgrade to
OCSDM Release 9.x.
All work orders must be in a Committed state before you upgrade to OCSDM Release 9.0
because the migration of existing work orders on a server running OCSDM Release 7.5m3 is
not provided when you upgrade to OCSDM Release 9.0. See your product plugin
documentation for more information about placing your work orders into a Committed state.
Upgrade to a Supported Version of Linux

Use this task if you have an unsupported version of Linux that needs to be upgraded to a
supported version of Linux so you can install Oracle Communications Session Delivery
Manager on your server.
Upgrade Linux on Your Server

Use this task if you need to upgrade the Linux server operating system on your server in
order to upgrade Oracle Communications Session Delivery Manager.
Note:
Ensure that the server is shut down before you do this task. See the Shut Down
Your System section for more information on shutting down the OCSDM server.
1. Login to the server as the nncentral user.

2. Change to the OCSDM software installation bin directory. For example:
cd /<sdm-install-directory>/AcmePacket/NNC<version>/bin
3. Run the backupdbcold.sh script.
Note:
The backupdbcold.sh -- help script provides all of the arguments that you can
use.
./backupdbcold.sh
• You can use the following arguments with this script:
1-7
Chapter 1
Upgrade to a Supported Version of Linux
– -d —Use this argument to select a local directory that you want to store
backup archives. For example:
./backupdbcold.sh -d/<sdm-install-directory>/AcmePacket/
<Directory>/
NNC<version>_ColdBackup_yyyy_mm_dd_<number>_all.tar
– -a, --all — Use this argument to run all backups and store them as a
single archive.
./backupdbcold.sh --all
– -c --core — Use this argument to backup the core application database

and store it as an individual archive.
./backupdbcold.sh --core
– -r --report — Use this argument to backup the reporting Oracle database

and repository and store as an individual archive.
./backupdbcold.sh --report
– -o --ocsdmdw — Use this argument to backup the (Oracle

Communications Session Delivery Manager Data Warehouse
(OCSDMDW) database and store as an individual archive.
./backupdbcold.sh --ocsdmdw
– -ep, --excludePlugins —Use this argument to exclude archived plugin zip

files from the resulting backup file. By default, the resulting backup file
contains all product plugin installation zip files which were previously
uploaded to OCSDM. You can override this behavior by entering this
command.
./backupdbcold.sh --excludePlugins
After the script runs, the output displays a section called Backup Results. The
output shows if the core OCSDM application database and reporting databases
are successfully backed up to the default DatabaseBackup directory. The
following example shows the directory on which the application database file was
backed up:
/<sdm-install-directory>/AcmePacket/DatabaseBackup/
NNC<version>_ColdBackup_yyyy_mm_dd_<number>_all.tar
Note:
If you do not have reporting configured on the OCSDM server, the output
shows that the reporting databases failed to be backed up.
4. Upgrade the server to a supported version of Linux. See Check System

Requirements for more information.
1-8
Chapter 1
Check the File Descriptor Count on Your Linux System
5. Repeat the steps above if you need to upgrade another Linux server on which Oracle
Communications Session Delivery Manager needs to run.
Check the File Descriptor Count on Your Linux System

The Oracle Communications Session Delivery Manager server requires that the Linux
system, on which it is installed and runs, have 20,000 file descriptors.
2. Use the ulimit -n command to view the number of file descriptors configured for your
Linux system.
ulimit -n
3. If the output displays a value of 20000 or greater, you are finished with this task. If the
output value is less than 20000, continue to the next step.
4. Navigate to the OCSDM installation bin directory.
For example:
5. Run the shutdownnnc.sh script. By default, the shutdownnnc.sh script detects whether
the existing installation is a standalone or clustered system and prompts you with the
option to shut down the entire cluster if no flag options are provided.
Note:
However, You can script an option ahead of time by adding -local for single
nodes and -cluster to shutdown an entire cluster.
./shutdownnnc.sh
Shutdown back-end server
Do you wish to shut down the entire cluster (Yes/No)? Yes
6. Login to the server as the root user.

7. Open the limits.conf file in the /etc/security/ directory to check if there is any line in the
file with soft nofile or hard nofile entries. For example:
/etc/security/limits.conf
#<domain> <type> <item> <value>
* soft nofile 20000

* hard nofile 20000
8. If there are no values after the nofile entries or these entries are less than 20000, enter
each entry as shown above.
9. Exit the shell.
1-9
Chapter 1
Verify the Required SDM_localhost Entry is in the Hosts File
11. Use the ulimit -n command again to view the number of file descriptors that you
configured (the command should now return a value of 20000).
12. If you have a cluster setup, repeat the previous steps for each cluster member.
Verify the Required SDM_localhost Entry is in the Hosts File

You must verify that the required SDM_localhost entry is in the /etc/hosts file that is
used for internal server communication within a cluster, or for any OCSDM server(s) in
your environment that do not rely on a domain name server (DNS).
Note:
The IP address that is used for the SDM_localhost entry on each OCSDM
cluster member must be registered on the network Domain Name Server
(DNS). If this entry is absent on the DNS server, DNS lookup timeouts occur,
which can cause database problems.

2. Enter the ifconfig command to view the Ethernet 0 (eth0) IP address on the
OCSDM server.
[my_linux_system]$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:21:F6:69:00:33

inet addr:10.138.222.189 Bcast:10.138.223.255
Mask:255.255.252.0
inet6 addr: fe80::221:f6ff:fe69:33/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:31991154 errors:0 dropped:0 overruns:0 frame:0
TX packets:10798060 errors:0 dropped:0 overruns:0
carrier:0
collisions:0 txqueuelen:1000
RX bytes:2842355697 (2.6 GiB) TX bytes:26025276531 (24.2
GiB)
Interrupt:163
3. View the /etc/hosts file to verify that there is a SDM_localhost entry and that
the IP address of this entry matches the eth0 interface.
The following example has the correct eth0 interface (shown in the previous
example) and SDM_localhost entry:
[my_linux_system]$ Vi /etc/hosts
10.138.222.189 acme189 SDM_localhost
4. If the /etc/hosts file does not include the eth0 IP address and SDM_localhost
entries, enter them in the /etc/hosts file using the following format:
1-10
Chapter 1
Disable the Default HTTP Daemon
Note:
The order in which this entry appears in the hosts file does not matter.
For example:
<eth0 IP address> <optional hostname(s)> SDM_localhost
Note:
SDM_localhost does not support IPv6 link-local addresses.
If you fail to add the SDM_localhost entry in the hosts file, the following message appears
during the OCSDM setup installation process:
Setup encountered an error and cannot continue!

INVALID_SERVICE_CONFIGURATION: /etc/hosts file is not configured
correctly. There should be one entry for SDM_localhost. Please refer to
the installation documents for proper syntax.
5. Restart the network service to initialize the changes that you made to the hosts file.
$ service network restart
Disable the Default HTTP Daemon

If your Oracle Communications Session Delivery Manager server is running a default HTTP
daemon (HTTPD) process, disable that process from restarting.
2. To discover if the HTTPD is installed or running:
service httpd status
The following message appears if the HTTPD is not installed. Continue to the next
sections.
httpd: unrecognized service
The following message appears if the HTTPD is installed but not running. Continue to the
next sections.
httpd is stopped
1-11
Chapter 1
Specify the System Locale
A message similar to the following appears if the HTTPD is installed and running:
httpd (pid 5644) is running...
3. If the HTTPD is running, stop the HTTPD:
service httpd stop
4. Disable the HTTPD from restarting when the system reboots:
chkconfig httpd off
5. Verify that the HTTPD is not running:
service httpd status
Note:
If your are using Oracle Linux 7 or later, use the following command:
systemctl status httpd
Specify the System Locale

You must specify the system location to LANG=en_US.UTF-8 (United States English
language) in order for Oracle Communications Session Delivery Manager to install
properly.
2. Ensure that the US English language UTF-8 character encoding method
(LANG=en_US.UTF-8) parameter is specified in the i18n (Internationalization) file
in the /etc/sysconfig/i18n directory. This file specifies the current language
settings.
Set up Local Yum Repository

If your SDM server has no direct internet connection, you have two options to install
dependencies: either set up a local yum repository on the SDM server or set up a local
yum server on another machine on the same subnet as your SDM server.
1. To set up a local yum repository on the SDM server, follow the instructions in
Creating a Local Yum Repository Using an ISO Image.
2. To set up a local yum server on the same subnet as your SDM server, follow the
instructions in step 1 on the machine that will function as your yum server, and
then follow the instructions in Setting up a Local Yum Server Using an ISO Image.
1-12
Chapter 1
Resolve Any Oracle Linux 6 Installation Dependencies

Resolve any Oracle Linux 6.5, 6.6, 6.7, 6.8, and 6.9 software library dependencies before you
install OCSDM so that the OCSDM installation process runs properly. The following table
describes the Oracle Linux 6 software library packages shared with Oracle Communications
Session Delivery Manager:
Library Description
apr The Apache Portable Runtime (APR) supporting
library is for the Apache web server that provides
a set of application programming interfaces (APIs)
that map to the underlying operating system (OS).
The APR provides emulation where the OS does
not support a particular function to make a
program portable across different platforms.
apr-util The APR Utility Library (APR-Util) provides a
predictable and consistent interface for underlying
client library interfaces. This API assures
predictable if not identical behavior regardless of
which libraries are available on a given platform.
compat-expat1 Expat is a stream-oriented parser for XML
documents. You register handlers with the parser
before starting the parse and these handlers are
called when the parser discovers the associated
structures in the document being parsed. A start
tag is an example of the kind of structures for
which you may register handlers.
libxslt The package contains extensible style sheet
language transformations (XSLT) libraries. These
are useful for extending libxml2 libraries that are
used to manipulate XML files to support XSLT
files.
libaprutil The APR database binding library for the Apache
web server.
libGL OpenGL-based programs must link with the libGL
library that implements the GLX interface as well
as the main OpenGL API entry points.
libX11 The X.Org stack, which provides an open source
implementation of the X Window System for the C
language X interface. See the X.Org Foundation
for more information.
libXxf86vm X11 XFree86 video mode extension library
provides an interface to the XFree86-
VidModeExtension extension, which allows client
applications to get and set video mode timings in
extensive detail. It is used by the xvidtune program
in particular.
alsa-lib Advanced Linux Sound Architecture (ALSA) library
package used by programs (including ALSA
Utilities ) requiring access to the ALSA sound
interface.
If you are missing any shared software libraries in your Oracle Linux environment, run the
"yum" program. Yum is the primary tool for getting, installing, deleting, querying, and
1-13
Chapter 1
managing Oracle Linux software packages from official software repositories, as well
as other third-party repositories.
1. Login to your Oracle Linux system on which OCSDM is to be installed as the root
user.
2. Install the Oracle Linux software on your linux system using the "yum" program.
For example:
yum install -y apr

Resolve any of the following software library dependencies for Oracle Linux 7.0 upto
7.9 before you install OCSDM so that the OCSDM installation process runs properly.
The following table describes the Oracle Linux 7 software library packages shared with
Oracle Communications Session Delivery Manager.
Library Description
apr The Apache Portable Runtime (APR)
supporting library is for the Apache web server
that provides a set of application programming
interfaces (APIs) that map to the underlying
operating system (OS). The APR provides
emulation where the OS does not support a
particular function to make a program portable
across different platforms.
predictable and consistent interface for
underlying client library interfaces. This API
assures predictable if not identical behavior
regardless of which libraries are available on a
given platform.
language transformations (XSLT) libraries.
These are useful for extending libxml2 libraries
that are used to manipulate XML files to
support XSLT files.
libaprutil The APR database binding library for the
Apache web server.
libGL OpenGL-based programs must link with the
libGL library that implements the GLX interface
as well as the main OpenGL API entry points.
libX11 The X.Org stack, which provides an open
source implementation of the X Window
System for the C language X interface. See
the X.Org Foundation for more information.
VidModeExtension extension, which allows
client applications to get and set video mode
timings in extensive detail. It is used by the
xvidtune program in particular.
1-14
Chapter 1
Library Description
alsa-lib Advanced Linux Sound Architecture (ALSA)
library package used by programs (including
ALSA Utilities ) requiring access to the ALSA
sound interface.
If you are missing any shared software libraries in your Oracle Linux environment, run the
"yum" program. Yum is the primary tool for getting, installing, deleting, querying, and
managing Oracle Linux software packages from official software repositories, as well as other
third-party repositories.
1. Login to your Oracle Linux system on which OCSDM is to be installed as the root user.
2. Install the Oracle Linux software on your linux system using the "yum" program. For
example:
yum install -y apr-util

Resolve any of the following Oracle Linux 8.0 or later software library dependencies before
you install OCSDM so that the OCSDM installation process runs properly. The following table
describes the Oracle Linux 8 software library packages shared with Oracle Communications
Session Delivery Manager.
Library Description
apr The Apache Portable Runtime (APR) supporting
library is for the Apache web server that provides
a set of application programming interfaces (APIs)
that map to the underlying operating system (OS).
The APR provides emulation where the OS does
not support a particular function to make a
program portable across different platforms.
predictable and consistent interface for underlying
client library interfaces. This API assures
predictable if not identical behavior regardless of
which libraries are available on a given platform.
language transformations (XSLT) libraries. These
are useful for extending libxml2 libraries that are
used to manipulate XML files to support XSLT
files.
libaprutil The APR database binding library for the Apache
web server.
libGL OpenGL-based programs must link with the libGL
library that implements the GLX interface as well
as the main OpenGL API entry points.
libX11 The X.Org stack, which provides an open source
implementation of the X Window System for the C
language X interface. See the X.Org Foundation
1-15
Chapter 1
Library Description
VidModeExtension extension, which allows client
applications to get and set video mode timings in
extensive detail. It is used by the xvidtune program
in particular.
alsa-lib Advanced Linux Sound Architecture (ALSA) library
package used by programs (including ALSA
Utilities ) requiring access to the ALSA sound
interface.
xorg-x11-utils xorg-x11-utils is shipped with common Linux
distributions. The xorg-x11-utils package is
designed for, X.Org X11 X client utilities. The xorg-
x11-utils package is a collection of client utilities
which can be used to query the X server for
various information
libnsl libnsl package contains the libnsl library. The libnsl
package contains the public client interface for
NIS(YP) and NIS+. It replaces the NIS library that
used to be in glibc. It includes IPv6 support.
libapr-1.so.0 libapr-1.so.0 is a dependency of the Apache
Portable Runtime (APR) which is for the Apache
web server that provides a set of application
programminginterfaces (APIs) that map to the
underlying operating system (OS).
libXtst libXtst is a package in Ubuntu which provides an X
Window System client interface to the Record
extension to the X protocol. The Record extension
allows X clients to synthesise input events, which
is useful for automated testing.
libasound.so.2 This is a system library
libXtst.so.6 libXtst.so.6 is from the libXtst package in Ubuntu
which provides an X Window System client
interface to the Record extension to the X
protocol. The Record extension allows X clients to
synthesise input events, which is useful for
automated testing.
libXi.so.6 libXi.so.6is from the libXi package which provides
an X Window System client interface to the
XINPUT extension to the X protocol. The Input
extension allows setup and configuration of
multiple input devices, and hotplugging of input
devices (to be added and removed on the fly).
If you are missing any shared software libraries in your Oracle Linux environment, run
the "yum" program. Yum is the primary tool for getting, installing, deleting, querying,
and managing Oracle Linux software packages from official software repositories, as
well as other third-party repositories.
1. Login to your Oracle Linux system on which OCSDM is to be installed as the root
user.
1-16
Chapter 1
Configure the NNCentral Account
2. Install the Oracle Linux software on your linux system using the "yum" program. For
example:
yum install -y apr-util
Configure the NNCentral Account

For security reasons, you must create an NNCentral user account named nncentral and an
NNCentral group named nncentral on the server to administer Oracle Communications
Session Delivery Manager related server operations. You also must specify limited sudo
privileges for the nncentral user and nncentral group. After the Oracle Communications
Session Delivery Manager installation, all the installed files are owned by the nncentral
account. The main Oracle Communications Session Delivery Manager process has to run as
a sudo user in order to have access to port 162.
Add the NNCentral Group and NNCentral User Account

The nncentral group and user account must be added to administer Oracle Communications
Session Delivery Manager server operations on your Linux server.
2. Add the nncentral group
groupadd nncentral
3. Add the nncentral user account.
useradd -m -g nncentral -d /home/nncentral -s /bin/bash nncentral
4. Set the password for the nncentral user.
passwd nncentral
5. If you are prompted to enter a new password, reenter the password that you entered in
step 4.
The following message displays:
passwd: all authentication tokens updated successfully.
Specify NNCentral User Privileges

You must specify limited privileges for an NNCentral user on the Linux server, so this user
can administer Oracle Communications Session Delivery Manager operations on the server.
You must use visudo to make edits to the sudoer configuration file.
Note:
This file can only be edited using Linux visual text editor (vi editor) commands.
1-17
Chapter 1
Select the Installation Type for Session Delivery Manager

2. Execute visudo.
# visudo
3. Press i to enter insert mode and begin adding text.

4. Add the following line to specify NNCentral user privileges in the sudoer
configuration to give the NNCentral user the limited authority to run Oracle
Communications Session Delivery Manager:
Note:
The placeholder <my-sdm-install-directory> is the name of the
directory where you installed SDM and the command line as shown
below is not valid without modification. Also, the entire entry must be
entered on the same line. Take notice also that the example below may
wrap as it is shown, depending on how you are viewing this document
(HTML or PDF).
nncentral ALL=/<my-sdm-install-directory>/AcmePacket/NNC*/jre/bin/
java * -Dlog4j.configuration*=* -cp *
com.acmepacket.ems.server.services.snmp.TrapRelay.TrapRelay *
5. Press Esc to return to command mode.

6. Press :wq to save your changes and exit visudo.
Note:
If you want to quit without saving your changes, press :q!.
7. Ensure that the sudoer configuration for the nncentral user is specified.
grep nncentral /etc/sudoers

Choose from the following installation types for Oracle Communications Session
Delivery Manager based on the setup options that are available for each installation
type.
• Typical Installation—Specify the most common setup properties to get a basic
Oracle Communications Session Delivery Manager installation running on the
server, which includes configuring passwords for the default user accounts, the
global identifier, web server security, and the SNMP Trap Relay port for Fault
Manager.
• Custom Installation—Configure the mail server, manage clusters, Route Manager,
configure the Report Manager database instance, and Transport Layer Security
(TLS) certificates.
1-18
Chapter 1
• Easy Installation— Specify the minimum number of properties to get started. The majority
of the settings are defaulted.
• Headless Installation—Specify the options supported in the Easy Installation through a
file.
The following table describes each setup option and in which installation type this setup
option is available:
Setup Option Typical Custom Easy Installation Headless

Installation Installation Installation
Admin Password Yes Yes Yes Yes
R226 Compliance Yes Yes Yes Yes
LI Admin Password Yes Yes Yes Yes
Global Identifier Yes Yes Yes Yes
HTTPS Apache Yes Yes No No
User
Group
Port Number
HTTPS Server Yes Yes Yes Yes
Name
Certificate Alias Yes Yes No No
Name
Truststore Yes Yes Yes Yes
Password
1-19
Chapter 1

RMI over SSL Yes Yes Yes Yes
N
o
t
e
:
T
h
e
R
M
I
o
v
e
r
S
S
L
s
e
t
u
p
o
p
t
i
o
n
i
s
a
v
a
i
l
a
b
l
e
f
r
o
m
t
h
e
1-20
Chapter 1

S
D
M
9
.
0
.
1
r
e
l
e
a
s
e
o
n
w
a
r
d
s
.
HTTPS Private Key Yes Yes No No

File [Path]
HTTPS Certificate Yes Yes No No
File [Path]
HTTPS Yes Yes No No
Intermediate
Certificate File
[Path]
Web Server File Yes Yes No No
Size Limit [GB]
Enable TLS Yes Yes No No
versions 1.1 and
1.2
Trap Relay Port Yes Yes No No
Number
Fault Configuration Yes Yes Yes Yes
Sudo Password
Mail Server DNS No Yes No No
Name
Mail Server Secure No Yes No No
Protocol
Mail Server Port No Yes No No
Mail Server From No Yes No No
Mail Server User No Yes No No
ID
1-21
Chapter 1

Mail Server Login No Yes No No
Required
Extra Mail Server No Yes No No
Properties
Cluster Member IP No Yes Yes Yes
Address
SFTP Username No Yes No No
SFTP Password No Yes Yes Yes
Route Set Number No Yes No No
of Backups
SAML Responder No Yes No No
Username
Password
Connection
Timeout
SAML Certificate No Yes No No
Alias Name
SAML Certificate No Yes No No
File [Path]
SBI TLS Entity No Yes No No
Certificate
Common Name
Certificate Org Unit
Certificate Org
Certificate City or
Locality
Certificate State or
Province
Certificate County
Code
Certificate Key
Size
Certificate Validity
(Days)
Generate No Yes No No
Certificate Signing
Request (Path)
Export Entity No Yes No No
Certificate (Path)
1-22
Chapter 1

Import Signed No Yes No No
Entity Certificate
(Path)
SBI TLS Trusted No Yes No No
Certificate Alias
Name
SBI TLS Trusted No Yes No No
Certificate Import
File (Path)
Oracle DB No Yes No No
OCSDMDW
OCSREMDW
Password
Oracle DB No Yes No No
OCSDMDW Oracle
Home (Path)
The following table describes the parameters that can be configured in the Easy Installation
and Headless Installation.
Setup Option Default Value Configurable

Admin Password N/A Yes
R226 Compliance N/A Yes
LI Admin Password N/A Yes
Global Identifier (Product Mode) Yes
HTTPS Server Name N/A Yes
Truststore Password N/A Yes
RMI over SSL - Truststore N/A Yes
password
Fault Configuration Sudo N/A Yes
Password
Cluster Member IP Address N/A Yes
SFTP Password N/A Yes
HTTPS Apache User nncentral No
HTTPS Apache Group nncentral No
HTTPS Apache Port 8443 No
Number
Certificate Alias Name nncentral No
HTTPS Private Key File N/A No
[Path]
HTTPS Certificate File N/A No
[Path]
HTTPS Intermediate N/A No
Certificate File [Path]
Web Server File Size Limit 2 GB No
[GB]
Enable TLS versions 1.1 Yes No
and 1.2
1-23
Chapter 1
Setup Option Default Value Configurable

Trap Relay Port Number 162 No
R226 Compliance
Upon initial installation, the Oracle Communications Session Delivery Manager can be
configured to enable or disable R226 compliance. When R226 compliance is set to
enabled on OCSDM, the Lawful Intercept and SIPREC features and their attributes
are hidden from view and are not configurable.
When R226 compliance is disabled, the Lawful Intercept and SIPREC features and
their attributes can be seen and configured by users with the appropriate permissions.
Note:
Once R226 compliance has been enabled, it cannot be revoked without a
complete reinstallation of the OCSDM. However, if R226 compliance is
disabled, you can enable it at any time.
1-24
2
Create a Session Delivery Manager
Installation Directory
Use this task to unzip the tar file containing the Oracle Communications Session Delivery
Manager software application image and create the OCSDM installation directory called
AcmePacket.
Unzip the Tar File to Create the Session Delivery Manager

Installation Directory
1. Get information about the software files that you need to do the Oracle Communications
Session Delivery Manager server installation. See the Session Delivery Manager
Software Distribution Media section in the Oracle Communications Session Delivery
Manager Release Notes, Release 9.0 for more information.
2. Download the appropriate tar.gz (application image) file from the Oracle customer portal
to a directory on the server where you want to install OCSDM.
3. Login to your server as the root user.
4. Navigate to the directory where you want to install OCSDM on the server.
cd /<directory>
5. Extract the tar.gz file.

For example:
tar -xzvf NNC<version>OracleLinux65_64bit.tar.gz
or
or
The OCSDM (AcmePacket) software installation directory is created. For example:
6. Before you begin your installation, ensure that you are certain what type of installation
that you want to do (Typical, Custom, Easy, or Headless). Refer to the Select Installation
Type for Session Delivery Manager section for more information.
2-1
3
Perform a New Session Delivery Manager
Installation
Use this chapter to perform a new standalone or cluster Oracle Communications Session
Delivery Manager server installation.
Complete the following tasks before you begin this installation:
1. Complete all applicable tasks in the Pre-Installation Tasks chapter.
2. Configure the NNCentral account. Refer to the Configure the NNCentral Account section
3. You must unzip the tar file to create the OCSDM installation directory, which contains the
installation program used to run the installation. Refer to the Create a Session Delivery
Manager Installation Directory section for more information.
4. Ensure that this installation is the type of installation that you want to do. Refer to the
Select Installation Type for Session Delivery Manager section for more information.
Start the Standalone Installation

2. Navigate to the Oracle Communications Session Delivery Manager installation bin
directory.
For example:
3. Run the setup application with the setup.sh script.
./setup.sh
Note:
A warning message appears if you have less than the recommended minimum
physical memory. Proceeding without the recommended minimum physical
memory may result in performance degradation.
WARNING:
This process may take several minutes to complete. Interrupting the setup.sh
process risks corrupting the system.
3-1
Chapter 3
Start the Cluster Installation
4. Complete the OCSDM installation and press Enter to continue to the setup, where
you can select your OCSDM installation type. Depending on the OCSDM
installation type you choose, refer to the Typical Installation, Custom Installation,
Easy Installation, or Headless Installation chapter for more information.
Start the Cluster Installation

You can install a high-availability (HA) cluster of OCSDM servers to ensure reliable,
continuous data and operations by masking both planned and unplanned downtime
and preventing single points of failure without compromising availability.
1. Login to your server as root user.
directory.
For example:
3. Run the setup.sh script.
./setup.sh
Note:
A warning message appears if you have less than the recommended
minimum physical memory. Proceeding without the recommended
minimum physical memory may result in performance degradation.
WARNING:
This process may take several minutes to complete. Interrupting the
setup.sh process risks corrupting the system.
4. Complete the OCSDM installation and press Enter to continue to the setup, where
you can select your OCSDM installation type. Depending on the OCSDM
installation type you choose, refer to the Typical Installation, Custom Installation,
5. Repeat the previous steps on each server node in the cluster.
6. After the each cluster node is complete, refer to the Configure the Installed
Session Delivery Manager Cluster chapter for more information on associating the
cluster nodes that you installed with each other so that they can function together
as a cluster.
3-2
4
Configure the Installed Session Delivery
Manager Cluster
After you have installed an Oracle Communications Session Delivery Manager standalone
server or cluster of OCSDM servers, use the following sections to configure them.
An OCSDM cluster is comprised of multiple server nodes (members), each of which can be a
candidate node for your file systems, databases or applications. Each cluster node monitors
the health of other cluster nodes. If a node fails, another node in the cluster takes over
services for the failed node. For example, when an interruption or failure occurs in a critical
application on a node, a high-availability cluster combats this disruption by switching
application operations to another node within the cluster to quickly and seamlessly prevent a
complete system failure.
Note:
In an OCSDM cluster, the R226 compliance value for each node must be the same
or the cluster cannot start up. As each node of the cluster starts up, if there is any
mismatch on this value, the cluster startup fails. Cluster nodes that fail due to a
mismatch of R226 compliance value require a complete OCSDM re-installation.
Configure a New Cluster

When configuring the Oracle Communications Session Delivery Manager cluster, add all
other nodes each time you run setup.sh. For example, if you are setting up a cluster with
nodes A, B, and C. When running setup.sh on node A, add nodes B and C; when running
setup.sh on node B, add nodes A and C; and when running setup.sh on node C, add nodes A
and B.
Note:
When configuring or modifying the master cluster server, all cluster replica nodes
must be shut down.

For example:
4-1
Chapter 4
3. Run the setup.sh script.
./setup.sh
Note:
WARNING:
4. Select option 2, Custom. Press Enter to continue.
[ ] 1 - Typical : Runs through most common set up options.

(Recommended) [Default]
[X] 2 - Custom : Allows manual customization. (Advanced users)
[ ] 3 - Quit : Finish and quit setup.
5. From the Customize Configuration menu (after you have started the custom
installation), Select option 6, Cluster management. Press Enter to continue.
6. When you are prompted, enter Yes to continue.
7. Select option 1, Configure and manage members in cluster. Press Enter to
continue.
8. When you are prompted, enter Yes to continue.
See additional sections in this chapter to perform other management operations
on the cluster.
Add New Nodes to the Cluster

1. Select option 1, Add a new member. Press Enter to continue.
2. When you are prompted, enter the IP address of the node you are adding to the
cluster. For example
Provide the IP address of the Host requiring membership to cluster.

Member IP address [ ]
Please enter the sftp username Username [nncentral]
Please enter the SFTP passwordPassword []
4-2
Chapter 4
Note:
Do not enter the domain name server (DNS) name or the fully qualified domain
name (FQDN) for the node.
3. Enter the SFTP username, password, confirm password, and for each cluster.
These credentials are stored in the nnc_sftp.ini file which is later used for pulling or
transferring the RMI certificate across the clusters.
4. Repeat steps to add additional nodes to the cluster.
5. When done adding nodes, select option 3, Apply new cluster configuration. Press
Enter to continue.
6. Select option 3, Quit out of cluster configuration. Press Enter to continue.
7. If this system is not part of the cluster, select option 2, No. Otherwise, select option 1,
Yes. Press Enter to continue.
8. If you selected Yes, enter the nncentral user name and nncentral password which other
nodes of the cluster can use to SFTP files from this system. See the Configure the
NNCentral Account section if you need to configure an nncentral account.
Note:
The master server node in the OCSDM cluster must be started and fully
operational before you can start the replica nodes.
If you need to change cluster member IP addresses after a successful OCSDM cluster
deployment, you must backup the OCSDM database, reinstall the cluster (with the new
cluster member IP addresses), and restore the database backup and start each cluster
member node.
4-3
5
Upgrade Session Delivery Manager
Use the tasks in this chapter to shut down the Oracle Communications Session Delivery
Manager server and either upgrade a standalone OCSDM server or OCSDM server cluster.
Ensure that you complete the following tasks before you begin this installation:
Shut Down the Session Delivery Manager Server

You can shut down the existing Oracle Communications Session Delivery Manager software
version running on your system to install a new version of the software, restore a database or
apply a software patch. If you are upgrading an OCSDM cluster, use these steps to shut
down each server node in the cluster.
1. Login to your server as the nncentral user.
For example:
3. Run the shutdownnnc.sh script. By default, the shutdownnnc.sh script detects whether
the existing installation is a standalone or clustered system and prompts you with the
option to shut down the entire cluster if no flag options are provided.
Note:
However, You can script an option ahead of time by adding -local for single
nodes and -cluster to shutdown an entire cluster.
./shutdownnnc.sh
Shutdown back-end server
Do you wish to shut down the entire cluster (Yes/No)? Yes
5-1
Chapter 5
Upgrade the Session Delivery Manager Standalone Server
Note:
If you are running any version of OCSDM prior to Release 7.5M3, you cannot
install OCSDM Release 9.x. Ensure that you are currently running OCSDM,
Release 7.5M3 or later. After 7.5M3, you can install OCSDM 8.x. You can
upgrade to OCSDM 9.0 from OCSDM 8.x or 8.x.x.
Note:
It is recommended that you take a cold DB back up of the system before
proceeding with upgrade.
Use the following summary of tasks to upgrade your OCSDM standalone server:
1. You must unzip the tar file to create the OCSDM installation directory, which
contains the installation program used to run the installation. Refer to the Create a
Session Delivery Manager Installation Directory section for more information.
2. If you are upgrading Report Manager, the Oracle Database and Oracle BI
Publisher must be running before you upgrade OCSDM so that Report Manager
database data is migrated.
3. Start the installation.
Start the Session Delivery Manager Standalone Upgrade
Note:
The previous release of Oracle Communications Session Delivery Manager
must manage at least one device to be upgraded successfully.

For example:
3. Run the setup application with the setup.sh script. The setup application
determines that a migration of the application data needs to occur from the current
release and that specific plugin(s) need to be installed based on the product
devices (SBCs, E-SBCs, or both) OCSDM managed in the previous release.
./setup.sh
5-2
Chapter 5
Note:
WARNING:
4. The data migration tool automatically detects the previous release. When you are
prompted, select that you have a standalone system and use the following section to
complete your upgrade.
Migrate Application Data on the Standalone Server

Migrate the application data on the master node (member) of the cluster system.
1. Enter 1 to proceed with database migration.
Setup has detected that database migration needs to be performed.

The migration process involves backing up the existing database and then
performing various operations to migrate the database to the current
version.
Depending on size of the existing database and the operations to be
performed,
this process may take up to an hour to complete, however you can cancel
and
rollback the process at any time by pressing the <a> key followed by
<enter>.
Note that database migration MUST be performed before setup can continue.
[X] 1 - Proceed with database migration [Default]
[ ] 2 - Cancel and exit setup
Please select an option [1] 1
2. Enter Yes to migrate data from the previous Oracle Communications Session Delivery
Manager installation.

Do you want to continue Yes/No? Yes
Pressing a key anytime during the process aborts the current migration. You cannot be
able to launch the target version of Oracle Communications Session Delivery Manager
until setup is re-run and database migration is performed.
3. When you are prompted, specify the directory path on your server where you
downloaded the requested product plugin(s). Once the directory path(s) to the product
plugin(s) are provided, the migration process continues migrating application data to
SDM 9.x.
5-3
Chapter 5
Upgrade the Session Delivery Manager Cluster
4. Press Enter and continue to the setup, where you can select your OCSDM
installation type. You must re-enter the setup parameters that you used when you
previously setup OCSDM. Refer to the Typical Installation, Custom Installation,
Note:
Ensure that you are currently running OCSDM, Release 7.5M3. If you are
running any version of OCSDM prior to Release 7.5M3, you cannot install
OCSDM Release 8.x. After installing OCSDM 8.x, you can upgrade to
OCSDM 9.0 from OCSDM 8.x or 8.x.x.
Note:
It is recommended that you take a cold DB backup from the master node
before proceeding with upgrade.
Use following summary of tasks to upgrade your OCSDM server cluster:

1. See the Session Delivery Manager Software Distribution Media section in the
Oracle Communications Session Delivery Manager Release Notes for more
information about the names and descriptions of the software files that you need to
do this upgrade.
2. Download the OCSDM application image file to each OCSDM server cluster node
in the same base directory in which the previous software was initially installed.
3. You must unzip the tar file on each node to create the OCSDM installation
directory, which contains the installation program used to run the installation. Refer
to the Create a Session Delivery Manager Installation Directory section for more
information.
4. If you are upgrading Report Manager, the Oracle Database and Oracle BI
Publisher must be running before you upgrade OCSDM so that Report Manager
database data is migrated.
5. Start the installation on the master cluster node and migrate the application data
from the previous release to this master cluster node.
6. Continue the installation on the master node.
7. Migrate the application data from the previous release to each cluster replica
node.
8. With the introduction of OCSDM, Release 8.0, you must select one server to start
in the cluster only (which in this case is the master node). Once this server is
started and operational, you can start the other server(s) in the cluster.
5-4
Chapter 5
Start the Session Delivery Manager Cluster Upgrade
Note:
The previous release of Oracle Communications Session Delivery Manager must
manage at least one device to be upgraded successfully.
1. Login to the master cluster server node as the root user.

For example:
3. Run the setup application with the setup.sh script. The setup.sh application determines
that a migration of the application data needs to occur from the current version to 9.x. If
you are migrating from OCSDM Release 7.5M3, specific plugin(s) may need to be
installed based on the product devices (SBCs, E-SBCs, or both).
./setup.sh
Note:
WARNING:
4. The data migration tool automatically detects the previous release. When you are
prompted, select that you have a clustered system and use the following section to
complete your upgrade.
Migrate Application Data on the Master Cluster Node

Transfer the application data on the master node (member) of the cluster system.
1. Enter 1 to transfer application data from the previous Oracle Communications Session
Delivery Manager installation.

version.
5-5
Chapter 5

performed,
this process may take up to an hour to complete, however you can
cancel and
rollback the process at any time by pressing the <a> key followed
by <enter>.
Note that database migration MUST be performed before setup can
continue.
2. When prompted, enter Yes to transfer application data from the previous OCSDM
installation.

3. When you are prompted, specify the directory path on your server where you
downloaded the requested product plugin(s). Once the directory path(s) to the
product plugin(s) are provided, the migration process continues migrating current
application data to the new release. During this process, the setup application
asks you if you want to transfer a backup of the migrated database (DB) to other
members of the cluster. If you answer yes, a backup is done and transferred to the
targeted members of the server cluster.
4. Enter 1 to copy the transferred database to other cluster nodes.
Your existing setup is configured for a clustered environment.

Setup on all
other nodes in your cluster will require the migrated database
archive just
created. Setup can now attempt to copy this archive via SFTP to
other cluster
nodes.
Note that if you skip this step, you must manually copy the
migrated database
archive to all other nodes in the cluster, as this archive will be
required
during setup on the other cluster nodes
[X] 1 - Copy the migrated database archive to other cluster
nodes [Default]
[ ] 2 - Do not copy the migrated database archive
5. When prompted, enter Yes to continue.

6. Enter the username, password, and folder path for the SFTP credentials for each
cluster node when prompted.
Provide SFTP credentials for cluster node 2.2.2.2:

username: [] myuser
password: [] xxxxx
5-6
Chapter 5
remote folder path: [ ] /home/myuser

remote folder path: [/home/myuser]
For example, a successful application data transfer shows information similar to the
following:
cluster node: 2.2.2.2

destination file: /home/myuser/ColdBackup_2012_02_13_112911_db.tar.gz
result: SUCCEEDED
cluster node: 3.3.3.3
destination file: /home/otheruser/ColdBackup_2012_02_13_112911_db.tar.gz
result: SUCCEEDED
Press <enter> to continue
Database migration is now complete.
Press <enter> to continue with setup
7. Press Enter and continue to the setup, where you can select your OCSDM installation
type. You must re-enter the setup parameters that you used when you previously setup
OCSDM. Refer to the Typical Installation, Custom Installation, Easy Installation, or
Headless Installation chapter for more information.
8. Once you have completed the setup on the master node, go to the Migrate Application
Data on Each Cluster Replica Node section to complete the cluster upgrade on the
replica nodes in the cluster.
Migrate Application Data on Each Cluster Replica Node

Transfer the application data to each replica node (member) of the cluster system.
Pre-requisites: Ensure that you have shut down the server, downloaded and unzipped the
application image file, and started the setup application on the replica node before starting
this task.
1. Enter 1 to continue importing the database backup.

version.
performed,
this process may take up to an hour to complete, however you can cancel
and
rollback the process at any time by pressing the <a> key followed by
<enter>.
Note that database migration MUST be performed before setup can continue.
5-7
Chapter 5
2. Enter Yes to continue.

3. Enter 1 to continue.
Your existing setup is configured for a clustered environment. For

your
existing environment, setup must be run on cluster node 1.1.1.1
prior
to running setup on any other cluster node (including this one).
When setup
is run on cluster node 1.1.1.1, a migrated master database archive
file will be produced.
If you have already run setup on 1.1.1.1 and either allowed setup to
automatically copy the database archive file to this node, or have
copied this
file manually, please select option [1] below. Otherwise, please
select
option [2] below to cancel setup. Then run setup on 1.1.1.1 before
running setup again on this node.
[X] 1 - Specify location of migrated master database archive
file [Default]

5. Enter the full path to the database backup and enter yes to continue the import
process.
Enter migrated master database archive file path:

[ ] /home/myuser/ColdBackup_2012_02_13_112911_db.tar.gz
[/home/myuser/ColdBackup_2012_02_13_112911_db.tar.gz]
backing up existing database....done
restoring the migrated master database...done
Restore migrated master database archive succeeded
Press <enter> to continue with setup
6. Press Enter to continue the Typical Installation and later the Custom Installation of
Oracle Communications Session Delivery Manager (depending on your installation
requirements of Oracle Communications Session Delivery Manager). These
installation(s) must be completed to use the current Oracle Communications
Session Delivery Manager software version on this replica node system.
7. Press Enter and continue to the setup, where you can select your OCSDM
installation type. You must re-enter the setup parameters that you used when you
previously setup OCSDM. Refer to the Typical Installation, Custom Installation,
5-8
Chapter 5
8. Repeat the previous steps if you need to transfer application data on another replica
node (member) of the cluster system.
Transfer the Migrated Application Database Backup to the Replica Node

Manually
Use this task if you opted not to copy the migrated database archive when you migrated
application data on the master cluster node when upgrading OCSDM from a previous
release.
1. Log into the replica node, shut it down and do a backup of the application database (also
known as a cold backup). See the Backup Databases on a Shutdown Server section in
the Session Delivery Manager Server Database Maintenance chapter of the Oracle
Communications Session Delivery Manager Administration Guide for more information.
2. Migrate the application data on this replica node from the backed up application
database. See the Migrate Application Data on Each Cluster Replica Node section in this
chapter for more information.
3. Repeat the previous steps for any remaining cluster node.
5-9
6
Typical Installation
The following tasks are accomplished in the Typical installation to specify the most common
setup properties to get a basic Oracle Communications Session Delivery Manager installation
running on the server.
1. The setup program loads and installs the appropriate product plugins (if you are
upgrading OCSDM from a previous version).
Note:
If you are installing OCSDM for the first time, the appropriate product plugins
must be installed after the OCSDM server installation. See the Manage Product
Plugins chapter in the Oracle Communications Session Delivery Manager
Administration Guide for more information.
2. Configure R226 Compliance. For more information on R226 compliance, see "R226
Compliance" section.
3. Configure passwords for the default user accounts.
Note:
Verify that you have the correct sudo password before you do this task.
4. Configure the global identifier.

5. Configure HTTP or HTTPS (default) on the Apache web server.
6. Configure the SNMP Trap Relay port for Fault Manager.
7. Configure RMI over SSL to secure the RMI ports 1099 and 1098 using SSL connections.
Note:
RMI over SSL support is available from the SDM 9.0.1 release onwards.
Note:
Once you have accomplished the applicable tasks, and the required configuration of
the NNCentral account in the "Pre-Installation Tasks" chapter, you are ready to
begin this installation. We recommend that you record all the setup parameters that
you configure in this chapter. You will need to use them again the next time you
upgrade OCSDM and run the Typical installation.
6-1
Chapter 6
Start the Typical Installation
Start the Typical Installation

• Select option 1, Typical. Press Enter to continue.
[X] 1 - Typical : Runs through most common set up options.

[ ] 2 - Custom : Allows manual customization.
(Advanced users)
[ ] 3 - Easy-Install : Prompts user for minimal setup option
values.
Configure R226 Compliance and Default User Account

Passwords
You must configure R226 compliance and passwords for the admin and LIadmin user
groups before starting the Oracle Communications Session Delivery Manager
application. Identical credentials must be configured during installation on all nodes of
a clustered deployment.
Note:
If you set R226 compliance to enabled, you can no longer create LIadmin
user groups and are not prompted to provide an LIadmin password. For
more information on R226 compliance, see "R226 Compliance".
1. Select option 1, R226 compliance and Default user account passwords. Press
Enter to continue.
2. Enter Yes or No when prompted Do you want to enable R226 compliance?.
You are prompted for a confirmation when enabling this feature since it cannot be
undone without a complete re-installation.
3. Enter the admin password and confirm by re-entering it.
4. Enter the LIadmin password and confirm by re-entering it.
Specify the Global ID for Northbound Trap Receivers

The OC SDM global identifier configuration installation option must be configured
on an Oracle Communications Session Delivery Manager cluster server to create a
unique global identifier (ID). The Global ID is used to identify a cluster from which
northbound traps originate. The traps are generated by OCSDM alarms that can be
OCSDM or device alarms. OCSDM forwards the alarms it has in its Fault Management
system to a northbound client. When an administrator receives the SNMP trap fault
6-2
Chapter 6
Configure Web Server Security
notification on their northbound system, the originating device can be determined by viewing
the global ID contained in the SNMP trap fault notification.
Note:
The global identifier must be the same for all nodes in a clustered system.
1. Select option 2, OC SDM global identifier configuration. Press Enter to continue.

2. Enter a global unique identifier for the system and press Enter. For example:
Enter global identifier: [ ] OCSDM

This task is used to configure the server to run in either HTTPS or HTTP mode, configure
Apache web server parameters, and optionally configure the size of files being uploaded to
the web server for the secure functioning of the web server and Oracle Communications
Session Delivery Manager.
Note:
This section does not discuss the importation or deletion of Transport Layer security
certificates for east-west peer OCSDM server communication, and for southbound
communication with network function (NF) devices. These actions are handled in
the Custom Installation when using the OCSDM setup installation program. Refer to
the Configure Transport Layer Security Certificates section for more information.
1. Select option 3, Web Server configuration. Press the Enter key to continue.
2. Option 1 (HTTP/HTTPS configuration) is selected by default to configure the your web
server parameters. Press Enter to continue.
[X] 1 - HTTP/HTTPS configuration - Setup HTTP or HTTPS configuration

[Default]
[ ] 2 - Security configuration - Options below can be used to modify the
Web server security configurations of OCSDM
a. We highly recommend that you keep HTTPS mode (default) as the system running
mode for your system to create secure web connections. If you need HTTP
(unsecured) select option 2. Press Enter to continue.
6-3
Chapter 6
Note:
OpenSSL 1.0.2e-fips or later must be installed on your linux server in
order to use the HTTPS service on the Apache web server to
support the options of running HTTPS with Transport Layer Security
(TLS) 1.0, 1.1, and 1.2.
[X] 1 - HTTPS mode [Default]

[ ] 2 - HTTP mode
b. Accept the default nncentral user as the Apache user.
Note:
You cannot use the value root for the Apache user.
Apache User [nncentral]
c. Accept the default nncentral group as the Apache group.
Note:
You cannot use the value root for either the Apache group name.
Apache Group [nncentral]
d. Enter an Apache port number or accept the default port of 8443 (secure
HTTPS).
Note:
Port 8080 is the port number for unsecured HTTP.
Apache Port Number (1024-65535) [8443]
e. Enter the DNS name of the server.
Server name [] myserver1
6-4
Chapter 6
Note:
The specified DNS server name must match the common name (CN) of the
certificate.
f. (For HTTPS configuration only) If your certificate is signed by a certificate authority,

select option 2, No, when prompted about creating a self-signed certificate. Press
Enter to continue. If your certificate is not signed, continue to sub-step g.
i. Enter the absolute path to the private key file.
Private key file []
ii. Enter the absolute path to the certificate file.
Certificate file []
iii. If there are intermediate certificates, select option 1. Press Enter to continue.
Then enter the absolute path to the certificate chain file. Otherwise, select the
default option 2.
Are there intermediate certificates?

[ ] 1 - Yes
[X] 2 - No [Default]
g. If you want to create a self signed certificate, select option 1, Yes. Press Enter to
continue.
h. Accent nncentral as the certificate alias name.
Certificate alias name [nncentral]
i. Specify a truststore password that provides write protection to the truststore where
X.509 certificates are kept. X.509 certificates are used in many internet protocols,
including TLS/SSL, which is the basis for HTTPS.
Truststore password []
The upper-level the security configuration is complete and the main web server menu
returns. If you do not need to adjust the default maximum file size for files that are
uploaded to the web server, your web server configuration is complete.
3. (Optional) Select option 2, Security configuration to update the Apache HTTP Daemon
(HTTPD) server configuration files, if you need to change the default value set by Oracle
Communications Session Delivery Manager for files that can be uploaded to the web
server. Press the Enter key to continue.
[ ] 1 - HTTP/HTTPS configuration - Setup HTTP or HTTPS configuration

[Default]
[X] 2 - Security configuration - Options below can be used to modify the
6-5
Chapter 6
Configure Fault Management
a. Select option 1, Modify web server file directive size limit

[Default].
[X] 1 – Modify web server file directive size limit [Default]

[ ] 2 - Enable TLS versions 1.1 and 1.2 (HTTPS)
[ ] 3 – Cancel out and do not apply changes
b. Press Enter to continue.

c. You are next prompted to enter the upload file size limit in gigabytes (GB). The
default size limit is 2 gigabytes.
Web server File Size Limit in GB (2-100) [2]
If the entered value exceeds the file-size limit, an error message displays and
prompts you to re-enter the value.
4. (Optional) By default, Transport Layer Security (TLS) 1.0 is used for HTTPS.
Select option 2, Security configuration if you want to enable TLS versions 1.1
and 1.2 to be used for HTTPS instead.
[ ] 1 - HTTP/HTTPS configuration - Setup HTTP or HTTPS

configuration [Default]
[X] 2 - Security configuration - Options below can be used to
modify the Web server security configurations of OCSDM
a. Select option 2, Enable TLS versions 1.1 and 1.2 (HTTPS).
[ ] 1 – Modify web server file directive size limit [Default]

[X] 2 - Enable TLS versions 1.1 and 1.2 (HTTPS)


By default,OCSDM fault management listens on port 162 for SNMP traps generated
by devices. Linux port numbers that are below 1000 are restricted to specific user
privileges. For this reason, a fault management setting for configuring the sudo
password on the system is required to be specified during the installation that is
restricted to enabling a trap listener to listen on port 162 and forward device traps from
OCSDM to its main northbound trap receiver(s).
1. Select option 4, Fault Management configuration. Press Enter to continue.
6-6
Chapter 6
Configure RMI Over SSL
2. Select option 1, Configure SNMP trap settings. Press Enter to continue.
[X] 1 - Configure SNMP trap settings [Default]

[ ] 2 - Quit out of fault management configuration
3. Either enter the port number that your server will listen on for SNMP traps or press Enter
to accept the default port of 162.
Note:
You cannot use a port number reserved for Oracle Communications Session
Delivery Manager components.
Enter the port number that Trap Relay should listen on: (1-65535) [162]
4. The system requires the entry of the sudo password to support internal components that
require sudo user privileges. If prompted (you entered a port below 1024 in the previous
step), enter the sudo password. Then re-enter the sudo password to confirm.
5. Select option 5, RMI over SSL setup option. Press Enter to continue.
The RMI over SSL setup option is available from the SDM 9.0.1 release onwards.
Next Step
See Configuring OCSDM for IPv4 Support .
Configure RMI Over SSL

Configure RMI over SSL to secure the RMI ports 1099 and 1098 using SSL connections.
1. Note:
Support for RMI over SSL is available from the SDM 9.0.1 release.
Select option 5, RMI Over SSL. Press Enter to continue.

2. You are prompted to provide the certificates using any one of the options:
a. Upload CA Certificate [Default].
b. Self-signed certificate
3. Enter 1 to select the first option - Upload CA Certificate [Default]. This option allows
you to use the CA signed certificates. Provide the information as listed in the table.
a. Private Key file - Complete file path of the CA signed private key file of type X.509
certificate.
b. Certificate file - Complete file path of the CA signed certificate file of type X.509
certificate.
c. Certificate alias name with the default value “nncentral”.
d. Trust store password - Password that provides write protection to the truststore
where the X.509 certificates are kept. The X.509 certificates are used in many
6-7
Chapter 6
Configuring OCSDM for IPv4 Support
internet protocols, including TLS/SSL. Trust store password must be at least 6

characters.
The uploaded certificates are used to generate the truststore by using a
keytool command and if the certificate uploaded is invalid, the execution of
keytool command fails and an error is shown at the end of this option
workflow. The certificates generated are stored under the location /
AcmePacket/NNC90_1/ssl/RMI/ and is configured at the JVM level to establish
RMI calls over SSL.
4. Enter 2 to select the option Self-Signed. Provide information as listed below:
a. Certificate alias name [rminncentral] - Certificate alias name with default
value “nncentral”.
b. Trust store password - Password which provides write- protection to the
truststore where the X.509 certificates are kept. The X.509 certificates are
used in many internet protocols, including TLS/SSL. The Trust store password
must be at least 6 characters.
After you provide the information, the server private key, server CSR file,
server certificate file and trust store certificates are generated using the
openssl and keytool’ command. All certificates generated are stored under
the location /AcmePacket/NNC90_1/ssl/RMI/. The generated truststore
certificate and password are configured at the JVM level to establish the RMI
calls over SSL.

This procedure is applicable only for releases - SDM 8.2.2 to SDM 8.2.3. Starting with
SDM release 8.2.2 to 8.2.3, if you have not enabled IPv6 on the system that has
OCSDM running, you will need to make the following modifications in the server.xml
file.
The server.xml file is located in the AcmePacket/<NNC version>/Apache/tomcat/
conf/ directory.
1. In the server.xml file, find this line:
<Connector protocol="AJP/1.3"
address="::"
port="8009"
2. In this line, for the address attribute which is currently address="::"', modify the
value as address="0.0.0.0". After modification it should look as below:
address="0.0.0.0"
port="8009"
3. You need to make the changes for SDM versions from 8.2.2 to 8.2.3, if IPV6 is not
enabled.
Start the Oracle Communications Session Delivery Manager server.
6-8
Chapter 6

This procedure if applicable for SDM 8.2.3 and later versions.
Starting from SDM version 8.2.3 and later, if IPv6 is enabled on the system that has OCSDM
running, you will need to modify the server.xml file located in the AcmePacket/<NNC
version>/Apache/tomcat/conf/ directory as shown below
1. Open the server.xmlfile.
2. In the server.xml file, find this line:
address="0.0.0.0"
port="8009"
3. In this line, for the address attribute which is currently address="0.0.0.0"', modify the
value as address="::". After modification it should look as shown below:
address="::"
port="8009"
Start the Oracle Communications Session Delivery Manager server.
6-9
7
Custom Installation
The custom installation options are for more advanced users.
Note:
The feature RMI over SSL has been introduced in the SDM 9.0.1 release.
If you are installing SDM 9.0, the first four steps of the custom installation are
identical to the steps of the typical installation. If you are installing SDM 9.0.1, the
first five steps of the custom installation are identical to the steps of the typical
installation.
The first four steps of the custom installation are identical to the steps of the typical
installation. The following custom options are displayed:
• Mail server configuration
• Cluster management—See the Configure the New Cluster section in the Typical
Installation chapter and the Session Delivery Manager Server Cluster Maintenance
chapter in the Oracle Communications Session Delivery Manager Administration Guide
• Route Manager configuration
• Transport layer security (TLS) configuration
• Oracle Database configuration
Note:
Once you have accomplished the applicable tasks, and the required configuration of
the NNCentral account in the Pre-Installation Tasks chapter, you are ready to begin
this installation. We recommend that you record all the setup parameters that you
configure in this chapter. You will need to use them again the next time you upgrade
OCSDM and run the Custom installation.
Start the Custom Installation

directory.
For example:
7-1
Chapter 7
Start the Custom Installation
./setup.sh
Note:
WARNING:
4. Select option 2, Custom. Press Enter to continue.

[X] 2 - Custom : Allows manual customization.
(Advanced users)
[ ] 3 - Easy-Install : Prompts user for minimal setup option
values.

The following main custom installation options appear:
[X] 1 - R226 compliance and Default user account passwords

[Default]
[ ] 2 - Global identifier
configuration
[ ] 3 - Web Server
configuration
[ ] 4 - Fault Management configuration
[ ] 5 - RMI Over
SSL
[ ] 6 - Mail Server
configuration
[ ] 7 - Cluster
management
[ ] 8 - Route Manager Central
configuration
[ ] 9 - SAML Single sign on
configuration
[ ] 10 - SBI TLS
configuration
[ ] 11 - Oracle DB OCSDMDW configuration. Please drop this DB, if
it already exists.
[ ] 12 - Quit setup
7-2
Chapter 7
Configure R226 Compliance and Default User Account Passwords
Please note:
• Support for RMI over SSL is available from the SDM 9.0.1 release onwards.
• Starting from SDM 8.2.2 version, you must enable IPV6 on the system where
OCSDM is running. For more information, see Configuring OCSDM for IPv4 Support.
• Option 8, SAML Single sign on configuration for importing self-signed certificates into
the Route Manager certificates file (cacerts), is not supported in this release.

Passwords
You must configure R226 compliance and passwords for the admin and LIadmin user groups
before starting the Oracle Communications Session Delivery Manager application. Identical
credentials must be configured during installation on all nodes of a clustered deployment.
Note:
If you set R226 compliance to enabled, you can no longer create LIadmin user
groups and are not prompted to provide an LIadmin password. For more
information on R226 compliance, see "R226 Compliance".
1. Select option 1, R226 compliance and Default user account passwords. Press Enter
to continue.
You are prompted for a confirmation when enabling this feature since it cannot be undone
without a complete re-installation.

The OC SDM global identifier configuration installation option must be configured on an
Oracle Communications Session Delivery Manager cluster server to create a unique global
identifier (ID). The Global ID is used to identify a cluster from which northbound traps
originate. The traps are generated by OCSDM alarms that can be OCSDM or device alarms.
OCSDM forwards the alarms it has in its Fault Management system to a northbound client.
When an administrator receives the SNMP trap fault notification on their northbound system,
the originating device can be determined by viewing the global ID contained in the SNMP trap
fault notification.
Note:
The global identifier must be the same for all nodes in a clustered system.
1. Select option 2, OC SDM global identifier configuration. Press Enter to continue.
7-3
Chapter 7
2. Enter a global unique identifier for the system and press Enter. For example:
Enter global identifier: [ ] OCSDM

This task is used to configure the server to run in either HTTPS or HTTP mode,
configure Apache web server parameters, and optionally configure the size of files
being uploaded to the web server for the secure functioning of the web server and
Oracle Communications Session Delivery Manager.
Note:
This section does not discuss the importation or deletion of Transport Layer
security certificates for east-west peer OCSDM server communication, and
for southbound communication with network function (NF) devices. These
actions are handled in the Custom Installation when using the OCSDM setup
installation program. Refer to the Configure Transport Layer Security
Certificates section for more information.
1. Select option 3, Web Server configuration. Press the Enter key to continue.
2. Option 1 (HTTP/HTTPS configuration) is selected by default to configure the your
web server parameters. Press Enter to continue.
[X] 1 - HTTP/HTTPS configuration - Setup HTTP or HTTPS

[ ] 2 - Security configuration - Options below can be used to
a. We highly recommend that you keep HTTPS mode (default) as the system
running mode for your system to create secure web connections. If you need
HTTP (unsecured) select option 2. Press Enter to continue.
Note:
OpenSSL 1.0.2e-fips or later must be installed on your linux server in
order to use the HTTPS service on the Apache web server to
support the options of running HTTPS with Transport Layer Security
(TLS) 1.0, 1.1, and 1.2.
[X] 1 - HTTPS mode [Default]

[ ] 2 - HTTP mode
b. Accept the default nncentral user as the Apache user.
7-4
Chapter 7
Note:
You cannot use the value root for the Apache user.
Apache User [nncentral]
c. Accept the default nncentral group as the Apache group.
Note:
You cannot use the value root for either the Apache group name.
Apache Group [nncentral]
d. Enter an Apache port number or accept the default port of 8443 (secure HTTPS).
Note:
Port 8080 is the port number for unsecured HTTP.
Apache Port Number (1024-65535) [8443]
e. Enter the DNS name of the server.
Note:
The specified DNS server name must match the common name (CN) of the
certificate.
f. (For HTTPS configuration only) If your certificate is signed by a certificate authority,

select option 2, No, when prompted about creating a self-signed certificate. Press
Enter to continue. If your certificate is not signed, continue to sub-step g.
i. Enter the absolute path to the private key file.
Private key file []
ii. Enter the absolute path to the certificate file.
Certificate file []
7-5
Chapter 7
iii. If there are intermediate certificates, select option 1. Press Enter to

continue. Then enter the absolute path to the certificate chain file.
Otherwise, select the default option 2.
Are there intermediate certificates?

[ ] 1 - Yes
[X] 2 - No [Default]
g. If you want to create a self signed certificate, select option 1, Yes. Press Enter
to continue.
h. Accent nncentral as the certificate alias name.
Certificate alias name [nncentral]
i. Specify a truststore password that provides write protection to the truststore

where X.509 certificates are kept. X.509 certificates are used in many internet
protocols, including TLS/SSL, which is the basis for HTTPS.
The upper-level the security configuration is complete and the main web
server menu returns. If you do not need to adjust the default maximum file size
for files that are uploaded to the web server, your web server configuration is
complete.
3. (Optional) Select option 2, Security configuration to update the Apache HTTP
Daemon (HTTPD) server configuration files, if you need to change the default
value set by Oracle Communications Session Delivery Manager for files that can
be uploaded to the web server. Press the Enter key to continue.
[ ] 1 - HTTP/HTTPS configuration - Setup HTTP or HTTPS

[X] 2 - Security configuration - Options below can be used to
a. Select option 1, Modify web server file directive size limit

[Default].


c. You are next prompted to enter the upload file size limit in gigabytes (GB). The
default size limit is 2 gigabytes.
Web server File Size Limit in GB (2-100) [2]
7-6
Chapter 7
If the entered value exceeds the file-size limit, an error message displays and
prompts you to re-enter the value.
4. (Optional) By default, Transport Layer Security (TLS) 1.0 is used for HTTPS. Select
option 2, Security configuration if you want to enable TLS versions 1.1 and 1.2 to be
used for HTTPS instead.
[ ] 1 - HTTP/HTTPS configuration - Setup HTTP or HTTPS configuration

[Default]
[X] 2 - Security configuration - Options below can be used to modify the
a. Select option 2, Enable TLS versions 1.1 and 1.2 (HTTPS).



By default,OCSDM fault management listens on port 162 for SNMP traps generated by
devices. Linux port numbers that are below 1000 are restricted to specific user privileges. For
this reason, a fault management setting for configuring the sudo password on the system is
required to be specified during the installation that is restricted to enabling a trap listener to
listen on port 162 and forward device traps from OCSDM to its main northbound trap
receiver(s).
1. Select option 4, Fault Management configuration. Press Enter to continue.
2. Select option 1, Configure SNMP trap settings. Press Enter to continue.
[X] 1 - Configure SNMP trap settings [Default]

[ ] 2 - Quit out of fault management configuration
3. Either enter the port number that your server will listen on for SNMP traps or press Enter
to accept the default port of 162.
Note:
You cannot use a port number reserved for Oracle Communications Session
Delivery Manager components.
Enter the port number that Trap Relay should listen on: (1-65535) [162]
7-7
Chapter 7
Configure RMI Over SSL - Custom Installation
4. The system requires the entry of the sudo password to support internal
components that require sudo user privileges. If prompted (you entered a port
below 1024 in the previous step), enter the sudo password. Then re-enter the
sudo password to confirm.
5. Select option 5, RMI over SSL setup option. Press Enter to continue.
The RMI over SSL setup option is available from the SDM 9.0.1 release onwards.
Next Step
See Configuring OCSDM for IPv4 Support .
Configure RMI Over SSL - Custom Installation

Configure RMI over SSL to secure the RMI ports 1099 and 1098 using SSL
connections.
1. Select option 5, RMI Over SSL. Press Enter to continue.
2. You are prompted to provide the certificates using any one of the options:
a. Uploading the CA signed trusted certificates (Default).
b. Self-signed certificate
For more information on how to proceed with the steps, see Configure RMI
Over SSL.
Configure the Mail Server
Note:
If you want Session Delivery Manager products to send out emails, you can
setup the mail server credentials to enable the sending of emails to a
targeted Microsoft Exchange and Gmail server.
1. Select option 5, Mail Server configuration. Press Enter to continue.
[X] 5 - Mail Server configuration
2. Select option 1, Configure mail server. Press Enter to continue.
[X] 1 - Configure mail server [Default]
3. Select option 1, Configure mail server host. Press Enter to continue.
[X] 1 - Configure mail server host
4. Enter the DNS name of your mail server.
Provide the DNS name.

Host name [] mail.example.com
7-8
Chapter 7
Configure the Mail Server
5. Select option 1, Mail server secure protocol. Press Enter to continue.
[X] 1 - Mail server secure protocol
6. Select your mail server's secure protocol.

Valid secure protocols are:
• starttls
• ssl
Note:
Customers may select none, but Oracle recommends all customers select
starttls or ssl.
7. Select option 1, Mail server port. Press Enter to continue.
[X] 1 - Mail server port
8. Choose a port number or press Enter to select the default port 465.
9. Select option 1, Configure mail from. Press Enter to continue.
[X] 1 - Configure mail from
10. Enter the address you want used for the From address.
For example, if sending to Microsoft Exchange account, mailadmin@acmepacket.com. If

sending to a Gmail account, mailadmin@gmail.com.
Provide the mail from.

Mail from [ ] mailadmin@example.com
11. Select option 1, Configure mail user. Press Enter to continue.
12. Enter the mail user id.
Provide the mail user id.

Mail user [] user@example.com
13. Select option 1, Configure mail logon required. Press Enter to continue.
14. Select either true or false.
Mail logon required true/false [false]
a. If you set the mail logon required to true, select option 1, Configure mail logon user
password. Press Enter to continue.
[X] 1 - Configure mail logon user password
7-9
Chapter 7
Configure Route Management Central
b. Enter the mail logon user password.
Mail logon user password []
15. Select option 1, Extra mail properties. Press Enter to continue.
[X] 1 - Extra mail server properties [Default]
16. Enter the extra mail server properties you want to configure.
The format for entering multiple mail server properties is:
property1:value1;property2:value2;property3:value3
17. Select option 2, Apply new mail server configuration. Press Enter to continue.
18. Select option 2, Quit out of mail server configuration. Press Enter to continue.
Configure Route Management Central

1. Select option 7, Route Manager Central configuration. Press Enter to continue.
2. Set the maximum number of route set backups.
Please enter the maximum number of route set backups per route set/
backup type combination
# of backups (1-500) [10]
Configure Transport Layer Security Certificates

The transport layer security (TLS) feature provides a single secure sockets layer (SSL)
keystore of entity or trusted certificates that provide support for all applications,
product plugins, and their respective network functions that run on Oracle
Communications Session Delivery Manager.
Note:
This section does not discuss the importation or deletion of HTTPS
certificates for the web service. Refer to the Configure Web Server Security
section for more information.
Configure Entity Certificates

1. Select option 9, SBI TLS configuration. Press Enter to continue.
2. Select option 1, Entity Certificate. Press Enter to continue.
3. Select option 1, Create Entity Certificate. Press Enter to continue.
4. Enter the certificate details.
• Common name
• Organization unit
7-10
Chapter 7
Configure Transport Layer Security Certificates
• Organization
• City or locality
• State or province
• Country code
• Key size
• The number of days during which this certificate is valid
After creating an Entity Certificate, new options appear.
5. Select the action you wish to perform.
• View Entity Certificates
• Export Entity Certificate
• Generate Certificate Signing Request (CSR)
• Import Signed Entity Certificate
• Delete Entity Certificates
• Return to Main Menu
6. If you select the option to export the certificate, import a certificate, or generate a CSR,
provide the absolute path to the file.
7. When finished configuring the entity certificate, select option 6, Quit and back to Main
Menu. Press Enter to continue.
Configure Trusted Certificates

1. Select option 9, SBI TLS configuration. Press Enter to continue.
2. Select option 2, Trusted Certificate. Press Enter to continue.
3. Select option 1, Import Trusted Certificate. Press Enter to continue.
4. Enter the alias name for the certificate.
5. Enter the full path to the certificate
For example:
Enter full path of the certificate to be imported: [ ] /etc/ssl/certs/

server.crt
6. Select the action you wish to perform.

• Import Trusted Certificate
• List all Certificates
• View Certificate detail
• Delete Trusted Certificate
• Return to Main Menu
7. If you select the option to view or delete a certificate, provide the alias of the certificate.
8. When finished configuring trusted certificates, selection option 5, Quit and back to Main
Menu. Press Enter to continue.
7-11
Chapter 7
About Creating a Report Manager Database Instance on the External Oracle Database
About Creating a Report Manager Database Instance on the

External Oracle Database
If you are using Oracle Communications Report Manager with Oracle Communications
Session Delivery Manager, option 10 (Oracle DB OCSDMDW configuration) in the
Custom Installation is used to specify the Oracle home path (ORACLE_HOME) and
the credentials of the Oracle database user instance (OCSREMDW).
For more information about creating the OCSDMDW database instance, see the
Create a Report Manager Database Instance chapter in the Oracle Communication
Report Manager Installation Guide.
7-12
8
Easy Installation
The Easy-Install option is provided for an Oracle Communications Session Delivery Manager
(OCSDM) server installation that has specific, simplified setup options.
The Easy-Install option can be used to deploy an OCSDM instance with basic configuration
options to run Oracle Communications Session Element Manager and Oracle
Communications Route Manager. Additional installation steps are required for Report
Manager and a more comprehensive set of options is offered for the Typical and Custom
installation options in the setup program.
Note:
We recommend that you record all the setup parameters that you configure in this
chapter. You will need to use them again the next time you upgrade OCSDM and
run the Easy Install.

Start the Easy Installation

directory.
For example:
./setup.sh
8-1
Chapter 8
Configure R226 Compliance and Default User Account Passwords
Note:
WARNING:
3. Complete the OCSDM installation and press Enter to continue.

4. Select option 3, Easy-Install. Press Enter to continue.

[ ] 2 - Custom : Allows manual customization.
(Advanced users)
[X] 3 - Easy-Install : Prompts user for minimal setup option
values.

Passwords
You must configure R226 compliance and passwords for the admin and LIadmin user
groups before starting the Oracle Communications Session Delivery Manager
application. Identical credentials must be configured during installation on all nodes of
a clustered deployment.
Note:
If you set R226 compliance to enabled, you can no longer create LIadmin
user groups and are not prompted to provide an LIadmin password. For
more information on R226 compliance, see "R226 Compliance".

You are prompted for a confirmation when enabling this feature since it cannot be
undone without a complete re-installation.
8-2
Chapter 8

The OC SDM global identifier configuration installation option must be configured on an
Oracle Communications Session Delivery Manager cluster server to create a unique global
identifier (ID). The Global ID is used to identify a cluster from which northbound traps
originate. The traps are generated by OCSDM alarms that can be OCSDM or device alarms.
OCSDM forwards the alarms it has in its Fault Management system to a northbound client.
When an administrator receives the SNMP trap fault notification on their northbound system,
the originating device can be determined by viewing the global ID contained in the SNMP trap
fault notification.
• The OCSDM global identifier is selected by default. Choose from the following options to
enter the global ID:
• If you want to retain the default global ID, press Enter. For example:
Enter global identifier: [OCSDM]
• If you want to enter another global ID for the system, enter the global ID and press
Enter. For example:
Enter global identifier: [OCSDM] OCSDM-Boston

This task is used to configure the server to enter the name of the web server and assign a
truststore password for write protection of a self-signed HTTPS certificate.
In the Easy Install, HTTPS mode is selected for you as the default system running mode to
create secure web connections on your system and you are only required to enter the web
server name and optionally enter a truststore password.
1. Enter the DNS name of the server.
2. No truststore password is selected by default. Choose from the following options:

• Specify a truststore password that provides write protection to the truststore where
X.509 certificates are kept. X.509 certificates are used in many internet protocols,
including TLS/SSL, which is the basis for HTTPS.
• Press Enter to continue the installation.

By default,OCSDM fault management listens on port 162 for SNMP traps generated by
devices. Linux port numbers that are below 1000 are restricted to specific user privileges. For
this reason, a fault management setting for configuring the sudo password on the system is
required to be specified during the installation that is restricted to enabling a trap listener to
8-3
Chapter 8
Configure RMI Over SSL - Easy Installation
listen on port 162 and forward device traps from OCSDM to its main northbound trap
receiver(s).
1. Enter the sudo password.
2. Re-enter the sudo password to confirm the sudo password that you set.
If you are doing a standalone installation, go to the Start the Server after Standalone
Installation section. If you are doing a cluster installation go to the Configure the
Cluster and Start the Server Installation section.
Configure RMI Over SSL - Easy Installation

A self-signed certificate option is provided to configure the RMI over SSL.
1. Select RMI over SSL option in the installation workflow.
The option RMI over SSL is available only from the SDM 9.0.1 release onwards.
2. Provide the truststore password using which the server private key, server CSR
file, server certificate and trust store certificates are generated and stored under
the location /AcmePacket/NNC90_1/ssl/RMI/.
The default value nncentral is used for the certificate alias name, you are not
prompted to enter it.
Complete the Easy Installation for a Standalone Server

1. At the Cluster management part of the easy installation, No (option 2) is selected
for you by default, press Enter.
2. At the next prompt, enter yes and press Enter to finish the easy installation.
Complete the Easy Installation for a Cluster

1. At the Cluster management part of the easy installation, when you are asked if
this server is to be a member of a cluster, select Yes (option 1) by entering 1 and
press Enter.
2. When prompted to continue, type Yes.
3. When prompted, enter the IP address(es) of each cluster member separated by a
comma and press Enter. For example:
10.10.10.2, 10.10.10.3
Please enter the sftp password for member IP [XX.XX.XX.XX]
Password []
Please confirm the password
Confirm password []
4. When prompted, enter the Secure File Transfer Protocol (SFTP) password, which
is the clear-text nncentral user password and press Enter. Refer to the Configure
the NNCentral Account section in the Pre-installation Tasks chapter for more
information.
5. Re-enter the SFTP password to confirm it.
8-4
9
Headless Installation
The Headless Installation of Oracle Communications Session Delivery Manager is a fast,
simplified installation process that runs without the setup application. Use the tasks in this
chapter to specify the user_setup.properties file and run a setup script that points to this file.
When you run the setup script, OCSDM is installed on your server.
Unzip the Tar File to Create the SDM Installation Directory

Unzip the tar file to create the Oracle Communications Session Delivery Manager
(AcmePacket) software installation directory.
1. Download the appropriate tar.gz file from the Oracle customer portal.
2. Save the tar.gz file to the directory on your server where you want to install OCSDM.
4. Navigate to the directory where you want to install OCSDM on the server.
cd /<directory>
5. Extract the tar.gz file.

For example:
or
or
9-1
Chapter 9
Specify the Setup Properties File
The OCSDM software installation directory is created. For example:

You can edit the user_setup.properties file, which has pre-defined server installation
inputs that you specify. The headless installation setup script points to and uses this
file later to install OCSDM on your server.
Note:
After you complete the Headless Installation and decide to run the Typical or
Custom Installation, any changes that you make in these installations are not
propagated to the user_setup.properties file. The changes you made in the
Typical or Custom Installation need to be added to the user_setup.properties
file to keep this file current in the event that you need to use this file again in
a future headless installation.
1. Navigate to the setup folder in the OCSDM installation directory.
$ AcmePacket/NNC<version>/conf/setup
2. In the setup directory, you can edit the user_setup.properties setup file with
your inputs by using a built-in text editing program such as nano, vi, or emacs. The
following example shows how to access and show the contents of the
user_setup.properties file.
$ vi user_setup.properties
1 # Password value for default admin user (e.g.
ADMIN_PASSWORD=admin)
2 ADMIN_PASSWORD=abc123
3
4 # Password value for default LIadmin user (e.g.
LI_ADMIN_PASSWORD=LIadmin)
5 LI_ADMIN_PASSWORD=abc123
6
7 # Value for toggling R226 compliance (valid values are enabled/
disabled) (e.g. R226_COMPLIANCE=enabled)
8 R226_COMPLIANCE=enabled
9
10 # Global configuration value (e.g. GLOBAL_CONFIG_ID=OCSDM)
11 GLOBAL_CONFIG_ID=OCSDM
12
13 # Server name for HTTPS configuration (must match CN or Common
Name value of the certificate)
14 SERVER_NAME=name.server.com
15
16 # Password value for Trust Store (e.g.
TRUST_STORE_PASSWORD=abc123)
17 TRUST_STORE_PASSWORD=abc123
9-2
Chapter 9
18
19 # Support for RMIOverSSL is available from the SDM 9.0.1 release
onwards.
20 # Password value for RMIOverSSL (e.g.
RMI_TRUST_STORE_PASSWORD=example123).
21 # The parameter can be used from SDM 9.0.1 release onwards
22 # RMI_TRUST_STORE_PASSWORD=abc123
23
24 # Password value for sudo user 'nncentral' (e.g.
SUDO_PASSWORD=abc123)
25 # SUDO_PASSWORD=abc123
26
27 # Password value for SFTP user 'nncentral' (e.g.
SFTP_PASSWORD=abc123)
28 SFTP_PASSWORD=abc123
29
30 # Comma-separated list of cluster member IP addresses
31 #(e.g for SDM.9.0.1 onwards :-
CLUSTER_MEMBERS=IP-1:sftpPwd,IP-2:sftpPwd, [...] IP-N:sftpPwd )
32 # CLUSTER_MEMBERS=
10.10.10.2:abc123,10.10.10.3:abc123,10.10.10.4:abc123
33 # OR
34 #( e.g for SDM 9.0 :- e.g. CLUSTER_MEMBERS=IP-1, IP-2, [...] IP-N )
35 # CLUSTER_MEMBERS=10.10.10.2,10.10.10.3,10.10.10.4
The following table describes each input used to configure your OCSDM server:
ADMIN_PASSWORD Input a clear-text password value for the OCSDM

administrator user.
LI_ADMIN_PASSWORD Input a clear-text value desired for an OCSDM

lawful intercept (LI) administrator user.
R226_COMPLIANCE Specify whether R226 compliance is enabled or

disabled on the OCSDM. This value is case-
sensitive.
GLOBAL_CONFIG_ID Input the unique global identifier (ID) for the

product, which is used by northbound devices to
determine the source of northbound traps. For
example, OCSDM-Boston.
SERVER_NAME The DNS name of the host server on which

OCSDM is being installed for the HTTPS
configuration. For example, name.server.com.
TRUST_STORE_PASSWORD The clear-text trust store password for web server

security. HTTPS is the default.
RMI_TRUST_STORE_PASSWORD The clear-text trust store password value for a self-

signed certificate for RMI over SSL
9-3
Chapter 9
Start the Headless Installation
Note:
This is available from the SDM 9.0.1
release onwards.
SUDO_PASSWORD The clear-text nncentral sudo password, which is

required to support internal components that
require Linux sudo user privileges. By default,
OCSDM fault management listens on port 162 for
SNMP traps generated by devices. Linux port
numbers that are below 1000 are restricted to
specific user privileges. For this reason, a fault
management setting for configuring the sudo
password on the system is required to be specified
during the installation that is restricted to enabling a
trap listener to listen on port 162 and forward
device traps from OCSDM to its main northbound
trap receiver(s).
SFTP_PASSWORD The clear-text nncentral user password.
CLUSTER_MEMBERS (Optional for cluster setup)

• For SDM 9.0.1 release: The comma-separated
list of cluster member IP addresses:sftpPwd.
For example:
10.10.10.2:abc123,10.10.10.3:abc123
• For SDM 9.0 release: The comma-separated
list of cluster member IP addresses. For
example: 10.10.10.2, 10.10.10.3, 10.10.10.4
Note:
If you are doing a standalone installation,
enter the pound symbol (#) to omit the
CLUSTER_MEMBERS= entry. For example:
22 # CLUSTER_MEMBERS=
3. Save the inputs you made to the user_setup.properties file in the text editor.
Start the Headless Installation

directory.
9-4
Chapter 9
Configure RMI Over SSL - Headless Installation
For example:
cd <sdm-install-directory>/AcmePacket/NNC<version>/bin
3. Run the setup application with the setup.sh script with the headless syntax and the full
path to the user_setup.properties file that you specified for this installation. For
example:
./setup.sh --headless /home/AcmePacket/NNC<version>/conf/setup/

user_setup.properties
Note:
WARNING:
Configure RMI Over SSL - Headless Installation

The OCSDM Headless installation option provides a simplified way of setting up basic
configuration with default values for SDM installation.
Note:
The RMI over SSL setup option is supported from the SDM.9.0.1 release onwards.
By default, a self-signed certificate option has been configured for RMI over SSL.
1. In the AcmePacket/NNC90_1/conf/setup/user_setup.properties file, provide
RMI_TRUST_STORE_PASSWORD.
2. Update the user_setup.properties file for the below line:
SDM 9.0 release: # Comma-separated list of cluster member IP addresses

(e.g. IP-1, IP-2, […] IP-N)
CLUSTER_MEMBERS=10.10.10.2, 10.10.10.3, 10.10.10.4
SDM 9.0.1 release onwards:

# Comma-separated list of cluster member IP addresses (e.g.
CLUSTER_MEMBERS=IP-1:sftpPwd,IP-2:sftpPwd, [...] IP-N:sftpPwd)
CLUSTER_MEMBERS=10.10.10.2:abc123,10.10.10.3:abc123,10.10.10.4:abc123
9-5
10
Start the Session Delivery Manager Server
Use the tasks in this chapter to start Oracle Communications Session Delivery Manager
server(s) after a standalone or cluster. You can also use this chapter to check the status of
OCSDM server processes to make sure the server(s) are running properly.
Start the Server after a Standalone Installation

1. Once the installation completes, switch to the nncentral user from the root user. For
example:
[root@myserver bin]# su nncentral

directory.
For example:
3. Start OCSDM with the startnnc.sh script.
./startnnc.sh
After all services have started, the system is ready for use. Do not attempt to log in until
the console has indicated that the web servers are up. If you are upgrading from 7.5M3,
the plugin service management system automatically uploads the plugins from the path
you identified earlier, and installs them. The console displays the number of services
started. For example:
Starting Back-End server now

27 of 27 services have started...
Starting Apache servers...
Servers and services started successfully. Web client access ready.
4. Once the system is started, you can begin using OCSDM by entering the server host
name or IP address, and port number in your web browser navigation bar.
For example:
https://example.com:8443
5. In the login page, enter the administrator login name and password that you configured in
the Configure User Account Passwords section.
Next Steps
• Check OCSDM server processes.
10-1
Chapter 10
Start the Server after a Cluster Installation
Start the Server after a Cluster Installation

Use this task if you are starting the OCSDM server after the cluster installation.
Note:
If you are migrating from SDM 7.5M3 to SDM 8.x, ensure that the application
data migration from SDM 7.5M3 to SDM 8.x has successfully completed
before starting the cluster. The migration to OCSDM 9.0 is from OCSDM 8.x
or 8.x.x.
1. Once the installation completes, switch to the nncentral user from the root user on
any cluster node. For example:
[root@myserver bin]# su nncentral

directory.
For example:
3. Start OCSDM with the startnnc.sh script.
./startnnc.sh
After all services have started, the system is ready for use. Do not attempt to log in
until the console has indicated that the web servers are up. If you are upgrading
from 7.5M3, the plugin service management system automatically uploads the
plugins from the path you identified earlier, and installs them. The console displays
the number of services started. For example:
Starting Back-End server now

27 of 27 services have started...
Starting Apache servers...
Servers and services started successfully. Web client access ready.
4. Once the system is started, you can begin using OCSDM by entering the server
host name or IP address, and port number in your web browser navigation bar.
For example:
https://example.com:8443
5. Once this server has started on this node and it is operational, you can start the
other server node(s).
6. Enter the administrator login name and password that you configured in the
Configure User Account Passwords section.
10-2
Chapter 10
Check Server Processes
Next Steps
• Check OCSDM server processes.
Check Server Processes

After the startnnc.sh script has completed, you can verify that Oracle Communications
Session Delivery Manager is up and running by entering the report process status command
on the system. Depending on your hardware specifications it may take a few minutes for
Oracle Communications Session Delivery Manager to start.
1. Execute the report process status command on the server.
ps -eaf | grep Acme
When Oracle Communications Session Delivery Manager is successfully running, you

should see:
• Several httpd processes
• Three or more Java processes
2. If the above processes are running and you still cannot connect to your server, check the
firewall settings of your server and network. See Firewall Settings in chapter 1.
10-3

SDM 90 Installation

Uploaded by

Copyright:

Available Formats

SDM 90 Installation

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SDM 90 Installation

Uploaded by

Copyright:

Available Formats

Oracle® Communications Session

Copyright © 2022, 2022, Oracle and/or its affiliates.

2 Create a Session Delivery Manager Installation Directory

4 Configure the Installed Session Delivery Manager Cluster

5 Upgrade Session Delivery Manager

10 Start the Session Delivery Manager Server

About This Guide

Table 1 Oracle Communications Session Delivery Manager Documentation

Document Name Document Description

Table 1 (Cont.) Oracle Communications Session Delivery Manager

Document Name Document Description

Locate Product Documentation on the Oracle Help Center Site

Access to Oracle Support

Figure 1-1 Installing or upgrading OCSDM with Report Manager

4. Check to ensure your system meets the minimum requirements.

7. Open the appropriate ports on the network and system firewall.

Check System Requirements

Oracle Communications Session Delivery Manager Server Requirements

Supported Operating Systems

Oracle supports the following installations of Oracle Communications Session Delivery

Check Cluster Requirements

Check Firewall Settings

LINK ACT LINK ACT LINK A

Alarm M gmt 0 M gmt 1 M gmt 2 S 0P0 S 0P1 S 1P0

No firewall between members of a cluster.

Table 1-1 Communication Between OCSDM Cluster and Network Clients

Port Number Protocol Service Configurable Affects Purpose

Table 1-1 (Cont.) Communication Between OCSDM Cluster and Network

Port Number Protocol Service Configurable Affects Purpose

Table 1-2 Communication Between OCSDM Cluster and Network Devices

Port Number Protocol Service Configurable Affects Purpose

Table 1-3 Communication Between OCSDM Servers in the Cluster

Port Number Protocol Service Configurable Affects Purpose

Table 1-3 (Cont.) Communication Between OCSDM Servers in the Cluster

Port Number Protocol Service Configurable Affects Purpose

Check that Work Orders are in a Committed State

Upgrade to a Supported Version of Linux

Upgrade Linux on Your Server

1. Login to the server as the nncentral user.

3. Run the backupdbcold.sh script.

• You can use the following arguments with this script:

– -c --core — Use this argument to backup the core application database

– -r --report — Use this argument to backup the reporting Oracle database

– -o --ocsdmdw — Use this argument to backup the (Oracle

– -ep, --excludePlugins —Use this argument to exclude archived plugin zip

4. Upgrade the server to a supported version of Linux. See Check System

Check the File Descriptor Count on Your Linux System

6. Login to the server as the root user.

* soft nofile 20000

Verify the Required SDM_localhost Entry is in the Hosts File

1. Login to the server as the root user.

eth0 Link encap:Ethernet HWaddr 00:21:F6:69:00:33

<eth0 IP address> <optional hostname(s)> SDM_localhost

Setup encountered an error and cannot continue!

$ service network restart

Disable the Default HTTP Daemon

service httpd status

httpd: unrecognized service

httpd (pid 5644) is running...