Skip Headers
Oracle® Communication and Mobility Server Installation Guide
Release 10.1.3 for Linux x86 and Microsoft Windows (32-bit)

Part Number E05364-03
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

1 Product and Installation Overview

This chapter describes Oracle Communication and Mobility Server (OCMS), Oracle Communication and Mobility Server Service Creation Environment (OCMS SCE) and recommended topologies in the following sections:

Product Overview

OCMS is a carrier grade SIP (Session Initiation Protocol) and J2EE execution platform for applications needing to send or receive messages over a SIP enabled broadband network or cellular network. This platform is referred to as a SIP Application Server.

Examples of such applications are as follows:

OCMS can be deployed either for broadband or 3GPP IP Multimedia System (IMS) networks offering value-added services. OCMS Service Creation Environment (OCMS SCE) is a package for third-party developers on the Microsoft Windows operating system. OCMS Service Creation Environment (SCE) consists of tools and APIs for developers to create their own services using the OCMS platform.

OCMS SCE requires the installation of the third-party tool Eclipse. Eclipse is the development environment for creating projects, writing code, and for automatically deploying applications into OCMS.

New in this Release

This release of Oracle Communication and Mobility Server includes enhancements and new features. To read about new and improved features, see http://www.oracle.com/technology/products/ocms/otn_front.htm.

Installation Prerequisites

This section describes prerequisites for installing OCMS and for using specific OCMS functionality.

System Requirements

To install OCMS your system must meet the following requirements:

  • Red Hat Enterprise Linux AS/ES 3.0 (update 3), or 4.0 (update 1)

  • Recommended for development purposes only: Microsoft Windows 2000 with Service Pack 3 or above, Microsoft Windows Server 2003 (32-bit) with Service Pack 1 or above, or Microsoft Windows XP Professional with Service Pack 2

  • Java 2 Platform, Enterprise Edition Software Development Kit (JDK) 5.0, (JDK version 1.5). Oracle Application Server installation mode uses the JDK 1.5 (Update 6) from the installation of Oracle Application Server. Standalone developer mode bundles JDK 1.5 (Update 6) with the OCMS installation.

  • Oracle TimesTen In-Memory Database 6.0 is required when installing Subscriber Data Services and using applications that require the authentication and authorization features provided by OCMS. Oracle TimesTen is provided with the OCMS distribution.

    Refer to What Components are Installed for more information on Subscriber Data Services.

  • a LAN connection and an IP address and hostname

Note:

The listed operating systems are certified and supported for Oracle Communication and Mobility Server. Other operating systems have not been certified.

Shared Memory Requirement on Linux

Before installing OCMS on Linux, make sure that you have set shmmax to a reasonably large value, approximately 1 GB or higher. As root, you can query for the current value by entering the following command:

more /proc/sys/kernel/shmmax

To set the value to approximately 1 GB, enter the following commands as root:

  • /sbin/sysctl -w kernel.shmmax=1073741824

  • Edit file /etc/sysctl.conf. At the end of the file add the line: kernel.shmmax=1073741824

Editing the /etc/sysctl.conf file makes the shmmax change done by the /sbin/sysctl -w kernel.shmmax=1073741824 command consistent across a reboot.

In general, we recommend this value to be set to be half the size of your physical RAM. If you have less than 2 GB of physical RAM, set it to approximately 1 GB as described above.

Port Requirements

OCMS requires the use of ports for TCP and UDP communications for the SIP Container, Presence server, and, if installed, the Edge Proxy. You can have the InstallShield Wizard for OCMS assign default port numbers for the SIP Container and Edge Proxy ports, or use port numbers that you specify. The Presence port is not configurable during installation, but can be configured in the MBean browser. Refer to the Oracle Communication and Mobility Server Administrator Guide for information on how to reconfigure port numbers following installation.

During installation, the InstallShield Wizard for OCMS validates that the selected ports are available. If a port is in use by another application, the installation will not succeed, and a port conflict error message is displayed and logged in an ocmsinstall.log file.

Table 1-1 lists the default ports used by OCMS when you install the Edge Proxy application.

Table 1-1 Default Ports: Edge Proxy Installed

SIP Port Edge Proxy Port Presence Port

5070

5060

5081


Table 1-2 lists the default ports used by OCMS when you do not install the Edge Proxy application:

Table 1-2 Default Ports: Edge Proxy Not Installed

SIP Port Edge Proxy Port Presence Port

5060

N/A

5071


Checking if a Port is in Use

To check if a port is being used in Windows, you can run the netstat command as follows:

C:\> netstat -an | find "portnum"

Note that you need double quotes around the port number.

To check if a port is being used in Linux, you can run the netstat command as follows:

netstat -a | grep <portnum>

Installation Modes

Oracle Communication and Mobility Server can be installed in the following installation modes:

Table 1-3 lists requirements for each installation mode.

Table 1-3 Requirements for Installation Modes

Requirement Oracle Application Server mode Standalone Developer mode

Oracle Containers for J2EE (OC4J)

Required before installation

Not required. Included with the installation.

Eclipse WebTools 1.5

Required if installing OCMS SCE.

Required if installing OCMS SCE.

Java Development Kit (JDK) 1.5

Provided by Oracle Application Server.

Included.

Oracle TimesTen In-Memory Database

Required if installing Subscriber Data Services.

Required if installing Subscriber Data Services.


Oracle Application Server Mode (Release 10.1.3.2 or Higher)

The recommended installation mode installs OCMS into an Oracle Application Server Release 10.1.3.2 or higher environment. This installation mode allows OCMS to use OC4J features such as Oracle High Availability (HA), clustering, and replication.

Oracle Communication and Mobility Server is deployed with an OC4J container that you manage using the Oracle 10g Enterprise Manager Application Server Control console. The Application Server Control functions enable starting, stopping, restarting, deploying, undeploying, and redeploying applications

Additionally, the Application Server Control MBean browser enables you to configure and manage the OCMS components. Configuring the attributes of the OCMS MBeans (Managed Beans) enables you to execute such administrative tasks as configuring the DNS (Domain Name System), configuring and managing Presence, and the basic configuration (port, IP, and host address) of the OCMS SIP Server itself.

For more information on managing and configuring OCMS in an Oracle Application Server environment, refer to "Managing the SIP Server" in the Oracle Communication and Mobility Server Administrator's Guide.

For more information on features provided by Oracle Application Server, refer to Oracle Application Server Administrator's Guide.

Standalone Developer Mode

The standalone developer mode allows developers to develop and test SIP applications in a minimal installation environment, without an application server. This installation mode installs Oracle Containers for J2EE (OC4J).

Standalone developer mode is not typically recommended for production deployment because of limited management capabilities.

JBoss Application Server Mode (Release 4.0.5GA or Higher)

The JBoss Application Server mode allows developers to manage OCMS through JBoss Application Server.

What Components are Installed

The following applications are included in a typical installation:

The following applications must selected for installation in the custom installation flow:

For more description and configuration information on these features, refer to Oracle Communication and Mobility Server Administrator's Guide.

Typical and Custom Installations

You can install OCMS as a typical installation that includes a set of certain installation components (SIP Container, Subscriber Data Services, Application Router, Proxy Registrar, and Presence) or you can perform a custom installation of specific features. Certain components can only be installed through a custom installation.

OCMS provides a SIP Container, a Presence server, a Proxy Registrar, Presence Webservices, a STUN Server, an Application Router, an Edge Proxy, an Aggregation Proxy, Diameter libraries, and a tool for developing third party applications, OCMS Service Creation Environment. Refer to What Components are Installed for more information on these features. OCMS also provides a framework for applications requiring user authentication and authorization called Subscriber Data Services. In a typical installation, the SIP Container is installed with an Application Router, Subscriber Data Services, Proxy Registrar, and Presence.

Custom Installation Requirements

When you only plan to use certain OCMS functionality and do not require all the provided functionality, you can perform a custom installation. Table 1-4 lists requirements for installing OCMS applications in a custom installation.

Table 1-4 Application Requirements for Custom Installations

OCMS Application Requirements Dependencies Availability

SIP Container

None

None

All modes and supported platforms

Subscriber Data Services

Oracle TimesTen In-Memory Database

SIP Container

All modes and supported platforms

Proxy Registrar

(Subscriber Data Services Requirements)

SIP Container, Subscriber Data Services

All modes and supported platforms

Application Router

(Subscriber Data Services Requirements)

SIP Container, Subscriber Data Services

All modes and supported platforms

Presence

None

SIP Container

All modes and supported platforms

Presence Webservices

None

SIP Container

Standalone Developer and Oracle Application Server modes only, all Platforms

Aggregation Proxy

(Subscriber Data Services Requirements)

SIP Container, Subscriber Data Services

All modes and supported platforms

STUN Server

None

SIP Container

All modes and supported platforms

Service Creation Environment (SCE)

Eclipse with WebTools 1.5

None

All modes on Windows platform only

Diameter

"tar" and "gunzip" must be in $PATH

None

Standalone Developer and Oracle Application Server modes only, Linux platform only

Edge Proxy

None

None

Oracle Application Server mode only, all supported platforms


Oracle Times Ten In-Memory Database

Subscriber Data Services (and applications that depend on Subscriber Data Services including Proxy Registrar, Application Router, and Aggregation Proxy) require Oracle TimesTen In-Memory Database, with data access control enabled. The OCMS installer automatically creates a data source for Oracle Times Ten during installation and sets permsize to 256MB.