Alternate Configurations Oracle Fusion Middleware Online Documentation Library

Deployment Topologies for Communication Services 16-5

16.3.1.1 Runtime Processes

Oracle WebLogic Communication Services start scripts use default values for many JVM parameters that affect performance. For example, JVM garbage collection and heap size parameters may be omitted, or may use values that are acceptable only for evaluation or development purposes. In a production system, you must rigorously profile your applications with different heap size and garbage collection settings in order to realize adequate performance. See Oracle WebLogic Communication Services Administrator’s Guide for suggestions about maximizing JVM performance in a production domain. Because a typical Oracle WebLogic Communication Services domain contains numerous engine and servers, with dependencies between the different server types, you should generally follow this sequence when starting up a domain:

1. Start the Administration Server for the domain.

Start the Administration Server in order to provide the initial configuration. The Administration Server can also be used to monitor the startupshutdown status of each Managed Server. You generally start the Administration Server by using either the startWebLogic.shcmd script installed with the Configuration Wizard, or a custom startup script.

2. Start Managed Servers.

Next you can start managed servers using the startManagedWebLogic.shcmd script or a custom startup script.

16.3.1.2 Request Flow

Request Flow is described in JSR 289. This specification is an enhancement to the SIPServlet specification. For details on JSR 289, see: http:www.oracle.comtechnologytechjavastandardsjsr289index.html

16.3.1.3 Client Connections

The default HTTP network configuration for each Oracle WebLogic Communication Services instance is determined from the Listen Address and Listen Port setting for each server. However, Oracle WebLogic Communication Services does not support the SIP protocol over HTTP. The SIP protocol is supported over the UDP and TCP transport protocols. SIPS is also supported using the TLS transport protocol. To enable UDP, TCP, or TLS transports, you configure one or more network channels for an Oracle WebLogic Communication Services instance. A network channel is a configurable WebLogic Server resource that defines the attributes of a specific network connection to the server instance. Basic channel attributes include: ■ Protocols supported by the connection, ■ Listen address DNS name or IP address of the connection, ■ Port number used by the connection, ■ optional Port number used by outgoing UDP packets, ■ Public listen address load balancer address to embed in SIP headers when the channel is used for an outbound connection. You can assign multiple channels to a single Oracle WebLogic Communication Services instance to support multiple protocols or to utilize multiple interfaces available with multi-homed server hardware. You cannot assign the same channel to multiple server instances. 16-6 Oracle WebLogic Communications Server Administration Guide When you configure a new network channel for the SIP protocol, both the UDP and TCP transport protocols are enabled on the specified port. You cannot create a SIP channel that supports only UDP transport or only TCP transport. When you configure a network channel for the SIPS protocol, the server uses the TLS transport protocol for the connection. As you configure a new SIP Server domain, you will generally create multiple SIP channels for communication to each engine tier server in your system. Engine tier servers can communicate to SIP state tier replicas using the configured Listen Address attributes for the replicas. Note, however, that replicas must use unique Listen Addresses in order to communicate with one another.

16.3.1.4 Artifacts

Installation, configuration and deployment create the following artifacts for OWLCS.

16.3.1.4.1 .ear Files .ear files for deploying your applications are found in your

middleware home directory for example: MW_ HOMEas11gr1wlcs1communicationsapplications. They are typically easily-identified by their names for example: sdpmessagingdriver-smpp.ear for deploying SMPP driver.

16.3.1.4.2 Configuration Files Configuring components is accomplished through various

.xml files. They can be found in your middleware home directory for example: DOMAIN_HOMEconfigcommunications. They are typically easily-identified by their names for example: usermessagingdriver-smpp_Plan.xml for configuring SMPP.

16.3.1.4.3 Log Files Log activities are stored in log files. There are many log files, but of

special note are install, activity, error, and diagnostic logs. They are found in your middleware home directory for example: DOMAIN_HOMEserverswlcs_ server1logs.

16.3.1.5 Topology Components

Components of a highly available OWLCS topology are detailed below. Figure 16–4 shows details of the OWLCS hosts that support the topology. Figure 16–4 Host details for OWLCS ■ Section 16.3.1.5.1, SIP Containers ■ Section 16.3.1.5.2, Third-Party Load Balancer Deployment Topologies for Communication Services 16-7 ■ Section 16.3.1.5.3, Proxy Registrar ■ Section 16.3.1.5.4, Presence Services ■ Section 16.3.1.5.5, Presence Web Services ■ Section 16.3.1.5.6, Third-Party Call Control Web Services ■ Section 16.3.1.5.7, Aggregation Proxy ■ Section 16.3.1.5.8, Authentication Proxy ■ Section 16.3.1.5.9, File Transfer Service ■ Section 16.3.1.5.10, Messaging Services ■ Section 16.3.1.5.11, STUN Service ■ Section 16.3.1.5.12, DAR Configuration ■ Section 16.3.1.5.13, Oracle Communicator Client ■ Section 16.3.1.5.14, State Tier ■ Section 16.3.1.5.15, User Dispatcher ■ Section 16.3.1.5.16, Oracle RAC Database Figure 16–5 OWLCS High Availability detail

16.3.1.5.1 SIP Containers OWLCS extends the core WebLogic Server platform with a

SIP Container compliant with JSR 289. This enables the development of J2EE applications that processes SIP in addition to HTTP for any advanced communications application. The platform enables the development of complementary communications services that integrate with SIP-based IP-PBXs as well as other SIP Note: For more information on configuring these components, see Oracle Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter.