This chapter describes Oracle WebLogic Communication Services (OWLCS), and recommended topologies in the following sections:
For information about the features and capabilities of Oracle WebLogic Communication Services, see Oracle WebLogic Communication Services Administrator's Guide.
This release of Oracle WebLogic Communication Services includes enhancements and new features. To read about new and improved features, see Oracle Technology Network.
This section describes prerequisites for installing OWLCS and for using specific OWLCS functionality.
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.
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:
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.5OWLCS 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.
| Port | Port Number |
|---|---|
|
SIP |
5060 |
|
SIPS |
5061 |
|
Admin Server HTTP |
7001 |
|
Admin Server HTTPS |
7002 |
|
Managed Server HTTP |
8001 |
|
Managed Server HTTPS |
8002 |
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 UNIX) you can run the netstat command as follows:
netstat -a | grep portnum
Installation and configuration of Oracle WebLogic Communication Services is accomplished by using the following installers and tools: Repository Creation Utility (RCU), OWLCS Base Platform Installer, OWLCS Installer, WebLogic Server (WLS) Configuration Wizard. The following chapters detail the steps you must take to install and configure these components.
Oracle WebLogic Communication Services can be installed in the following installation modes:
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.
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.
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.