Example Hardware 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.