|Oracle® Communications Service Broker Installation Guide
Part Number E15181-01
This chapter describes the tasks you need to perform prior to installing Oracle Communications Service Broker:
This task is required only if you intend to run Service Broker in a TDM-based network.
To use Service Broker in a TDM-based network, you must install the following components on any Signaling Server that will run a Service Broker SS7 Signaling Server Unit (SSU):
Dialogic TDM signaling board (with a license button) and the card driver
Information about these is on the Dialogic Web site:
For information about Dialogic TDM signaling boards, see:
To download the Dialogic software, see:
The required software for a TDM system includes:
DSI MTP3 (needed only if the MTP3 stack is required on the host rather than on the board)
See the associated installation guides for information on installing and using the board and software.
You download the Service Broker software from the Oracle E-Delivery Web site:
To download the Service Broker software:
Use your Web browser to go to the Oracle E-Delivery web site and follow the instructions.
When prompted to select a product pack, select Oracle Communications Applications and select the platform for your system configuration.
See "System Requirements" for a description of supported configurations.
When selecting the media pack, select Oracle Communications Service Broker.
Download the installation file for your platform.
In this documentation, the installation file is referred to as install_file.
Oracle Universal Installer is delivered as ZIP file. To unpack the installation program:
Open a command line shell and navigate to the directory where you downloaded the installation file:
Unpack the installation ZIP file: Enter:
Example on an Intel x86 Linux system:
The installer setup file is unpacked to the following directory:
where OS is the operating system.
Example of unpacked install directory for Solaris 10 64-bit SPARC:
To help minimize packet loss, the operating system socket buffers need to be large enough to handle the garbage collection of incoming network traffic.
By default, Coherence attempts to allocate a socket buffer of 2 MB. If your operating system is not configured to allow for large buffers, Coherence will utilize smaller buffers. Most versions of Unix have a very low default buffer limit, which should be increased to at least 2 MB.
Coherence will display the following warning if the buffer size is not set to at least 2 MB:
UnicastUdpSocket failed to set receive buffer size to 1428 packets (2096304 bytes); actual size is 89 packets (131071 bytes). Consult your OS documentation regarding increasing the maximum socket buffer size. Proceeding with the actual value may cause sub-optimal performance.
It is safe to operate with the smaller socket buffer size, but it is recommended that you increase it to 2 MB.
To change the socket buffer size to 2 MB on a Linux or Solaris system:
Log in as root.
Open a command shell, if necessary.
Execute one of the following commands:
sysctl -w net.core.rmem_max=2096304
ndd -set /dev/udp udp_max_buf 2096304