2 System Requirements

This chapter describes the hardware and software requirements for Oracle Communications Service Broker.

Hardware Requirements

There are different hardware requirements on machines running servers and machines running the Administration Console. See "Servers" and "Administration Console" for details.

Servers

Servers can be deployed on the following CPU architectures:

• x86-64 bit

• Oracle Sun SPARC 64 bit

Each server should have redundant network interface cards.

The following are the recommendations for each physical server in a production system. These are guidelines only:

• Dual quad core processors with 16 GB of RAM

• 2 GB of free disk space for the installation

The following requirements apply to specific server types:

• Processing servers

  Extra disk space is required for processing servers if you store Service Detail Records (SDRs) in files on the server. In general, 10 GB is sufficient for handling SDRs. However, the actual disk space you need depends on the server's capacity, the amount of traffic, and how many SDR files are stored on the server.

  See information about configuring SDR logging in Oracle Communications Service Broker System Administrator's Guide.

• Signaling servers

  A Dialogic TDM signaling board and Dialogic software are required for signaling servers that run in a TDM-based network.

  See "Installing Dialogic Hardware and Software for TDM Networks" for more information.

Administration Console

The stand-alone Administration Console and Web Administration Console can be deployed on the following CPU architectures:

• x86-64 bit

• Oracle Sun SPARC 64 bit

The following are the recommendations for each physical computer that hosts an Administration Console. These are guidelines only:

• Quad core processors with 8 GB of RAM

• 300 MB of free disk space for the installation

Software Requirements

Service Broker requires the following software:

• Network Time Protocol (NTP) client

  Service Broker requires that all servers accurately synchronize their system clocks to a common time source, to within one or two milliseconds. Oracle recommends using an NTP client or daemon and synchronizing all Service Broker servers to a common NTP server.

  Caution:

  Synchronizing system clocks to within one or two milliseconds is critical for proper functioning of the system. If you do not synchronize server clocks, the system may display unexpected behavior.

• Service Broker relies upon a shared library of the underlying operating system to provide Stream Control Transmission Protocol (SCTP) support.

  If you are implementing a solution that uses Diameter over SCTP, you need to ensure that the operating system includes the following library:

  libsctp.so.1

  If needed, install the shared library on the operating system of each managed server host machine.

• The Oracle Universal Installer imposes additional system requirements and library dependencies. For example, it requires 500 MB of swap space to be available on the installation target system.

  For more information about the Oracle Universal Installer, see Oracle Universal Installer and OPatch User's Guide.

Supported Configurations

Service Broker can be used with the following operating systems:

• Oracle Enterprise Linux 5.5

• Red Hat Enterprise Linux 5.4 or 5.5

• Oracle Solaris 10

The JDKs are bundled with Service Broker. The Java version used is 1.6.0_30 and JRockit R28.2.0.

The Web Administration Console can be used with the following Web Browsers:

• Microsoft Internet Explorer

• Mozilla Firefox

Table 2-1 lists the supported combinations of CPU type and JVM, along with the name of the installer archive file for the combination.

Table 2-1 Supported Configurations and Corresponding Installation Archive

CPU	JVM	Installer Archive
x86-64 bit	Java JDK 64 bit and JRockit 64 bit	ocsb600-linux_x86-64.zip
Oracle Sun SPARC 64 bits	Java JDK 64 bit and JRockit 64 bit	ocsb600-sparc64.zip