2 System Requirements

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

• Hardware Requirements

  • Servers

  • Administration Console

• Supported Configurations

Hardware Requirements

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

Servers

Processing and Signaling Servers can be deployed on the following CPU architectures:

• Intel x86

• Intel 64-bit Xeon

• Sun 64-bit SPARC

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

• 200 MB of free disk space for the installation

In addition, the following are required for specific servers:

• 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 "Configuring SDR Logging" under "Viewing Service Broker SDRs" in Oracle Communications Service Broker System Administrator's Guide for more information.

• 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 can be deployed on the following CPU architectures:

• Intel x86

• Intel 64-bit Xeon

• Sun 64-bit SPARC with 32-bit JVM

The Web Administration Console server can be deployed on the following CPU architectures:

• Intel x86

• Intel 64-bit Xeon

• Sun 64-bit SPARC with 32-bit or 64-bit JVM

The following are the recommendations for each physical server 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 on or two milliseconds is critical for proper functioning of the system. If you do not synchronize server clocks, the system may display unexpected behavior.

Supported Configurations

Service Broker can be used with the following operating systems:

• Oracle Enterprise Linux 5.4

• Red Hat Enterprise Linux 5.0

• Sun Solaris 10

The JDKs are bundled with Service Broker. The Java version used is 1.6.

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

• Microsoft Explorer

• Mozilla Firefox

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

Note:

The stand-alone Administration Console is not available on the 64-bit Solaris operating system.

Table 2-1 Supported Platform Configurations and Corresponding Install File Names

Operating System	CPU and JVM	Install File name
Oracle Enterprise Linux 5.4 or Red Hat Enterprise Linux 5.0	CPU: Intel x86 JVM: HotSpot 32 bit and JRockit 32 bit	ocsb500-linux_x86.zip
	CPU: Intel Xeon 64 bit JVM: HotSpot 64 bit and JRockit 64 bit	ocsb500-linux_x64.zip
Sun Solaris 10	CPU: Sun SPARC 64 bit JVM: HotSpot 32 bit and JRockit 32 bit	ocsb500-sparc.zip
	CPU: Sun SPARC 64 bit JMV: HotSpot 64 bit and JRockit 64 bit	ocsb500-sparc_64.zip