Messaging Oracle WebLogic Communication Services

2 Shared Configuration Tasks 2-1 2 Shared Configuration Tasks The following sections provide an overview of the configuration tasks that are common to both Oracle WebLogic Communication Services and Oracle WebLogic Server. These topics are included: ■ Section 2.1, Shared Configuration Tasks for Oracle WebLogic Communication Services and Oracle WebLogic Server ■ Section 2.2, Oracle WebLogic Communication Services Configuration Overview ■ Section 2.3, Methods and Tools for Performing Configuration Tasks ■ Section 2.4, Starting and Stopping Servers ■ Section 2.5, Administration Server Best Practices ■ Section 2.6, Common Configuration Tasks

2.1 Shared Configuration Tasks for Oracle WebLogic Communication Services and Oracle WebLogic Server

Oracle WebLogic Communication Services is based on the Oracle WebLogic Server 10g Release 3 application server, and many system-level configuration tasks are the same for both products. This guide addresses only those system-level configuration tasks that are unique to Oracle WebLogic Communication Services, such as tasks related to network and security configuration and cluster configuration for the engine and SIP data tiers. HTTP server configuration and other basic configuration tasks such as server logging are addressed in Oracle WebLogic Server documentation. See Oracle Fusion Middleware Getting Started With Installation for Oracle WebLogic Server to get started.

2.2 Oracle WebLogic Communication Services Configuration Overview

The SIP Servlet container, SIP data tier replication, and Diameter protocol features of Oracle WebLogic Communication Services are implemented in the Oracle WebLogic Server 10g Release 3 product as custom resources. A pair of custom resources, sipserver and datatier, implement the engine tier SIP Servlet container functionality and SIP data tier replication functionality. In production deployments, both resources are generally installed. Specialized deployments may use only the sipserver resource in conjunction with a SIP-aware load balancer, as described in Section 15.7, Alternate Configurations . Another custom resource, diameter, provides Diameter base protocol functionality, and is required only for deployments that utilize one or more Diameter protocol applications.