1 Product and Installation Overview

1.1.1 New in this Release

This release of Oracle WebLogic Communication Services includes enhancements and new features. To read about new and improved features, see Oracle Technology Network.

1.2.1 System Requirements

To install OWLCS your system must meet the following requirements:

• Oracle RDBMS Server 11.1.0.7 or Oracle RDBMS Server 10.2.0.4.

  Note:

  Oracle Database 10g Express Edition (10.2.0.1) may be used, but it is not a production Oracle database, and may only be used in a development environment.

• 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.

  Note:

  For a list of supported platforms, see Oracle WebLogic Communication Services Administrator's Guide.

• JRockit SDK 1.6

  Note:

  When you start Oracle Universal Installer (runInstaller or setup.exe) you can specify -jreLoc <jdk path> so that Oracle Universal Installer will not prompt you to provide a jdk. For example: setup.exe -jreLoc c:\jdk1.6.5

1.2.2 Port Requirements

OWLCS requires the use of ports for TCP and UDP communications. See Oracle WebLogic Communication Services Administrator's Guide for information on how to reconfigure port numbers following installation.

Table 1-1 lists the default ports used by OWLCS.

1.4.1 All-in-One Administration Server

All OWLCS components are deployed on an Administration Server within a domain on a physical machine. There are no managed servers. Configuration and management of OWLCS components is done using the same Administration Server.

All-in-One Administration Server is not meant to be a production environment, rather a test and evaluation environment. It does not include High Availability functionality.

1.4.2 All-in-One Managed Server

All OWLCS components are deployed on a Managed Server within a domain on a physical machine. An Administration Server installed on the same domain is used to configure and manage OWLCS components.

All-in-One Managed Server could be used in a production environment when high availability is not required. It does not include High Availability functionality.

1.4.3 Enterprise Deployment Topology

This is the minimal recommended HA topology for Enterprise Deployment for OWLCS. OWLCS components are separated as SIP Infrastructure, Services and Presence components. Each group of components is deployed within its own domain on two different machines.

Enterprise Deployment Topology is meant for production enterprise installations.