|Oracle® Communications Service Broker Installation Guide
Part Number E23522-02
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
The following Software related to the Dialogic Distributed Signaling Interface (DSI):
DSI MTP3 (needed only if the MTP3 stack is required on the host rather than on the board)
Information about Dialogic products is on the Dialogic Web site:
See the associated installation guides for information on installing and using the board and software.
You download the Service Broker software from the Oracle software delivery Web site:
To download the Service Broker software:
In a web browser, navigate to the Oracle software 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.
Select Oracle Communications Service Broker media pack and click Continue.
Follow the instructions to complete the download of the Service Broker media pack.
When the download completes, extract the contents of the media pack.
The Service Broker media pack contains installation archives that are named after the system configuration for which it is intended. See "System Requirements" for a list of the archive file names.
The installation files for each supported operating system are delivered in their own archive file. To unpack the archive:
Open a command line shell and navigate to the directory to which you extracted the Service Broker media pack.
Unpack the installation archive appropriate for your target system, in the form:
Where install_file is the path and name of the installation archive file. Example on an Intel x86 Linux system:
The installer setup files are unpacked to the following directory:
where operating_system is your 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.
Service Broker uses Oracle Coherence as its in-memory data grid caching manager. By default, Coherence attempts to allocate a socket buffer of 2 MB. If your operating system is not configured to allow buffers this large, Coherence will utilize smaller buffers. Most versions of Unix have a very low default buffer limit, which you should increase 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 Oracle recommends 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.
Run the command appropriate for your operating system:
sysctl -w net.core.rmem_max=2096304
sysctl -w net.core.wmem_max=2096304
The first command sets the read memory size, and the second sets the write memory size.
ndd -set /dev/udp udp_max_buf 2096304
In Linux, add the rmem_max and wmem_max name-value pairs as shown in the previous step to /etc/sysctl.conf to make the configuration change permanent.