Starting and Stopping Servers

2-6 Oracle WebLogic Communications Server Administration Guide

2.5 Administration Server Best Practices

The Administration Server in a Oracle WebLogic Communication Services installation is required for configuring, deploying, and monitoring services and applications. Oracle recommends the following best practices for configuring Administration Server and Managed Server instances in your Oracle WebLogic Communication Services domain: ■ Run the Administration Server instance on a dedicated machine. The Administration Server machine should have a memory capacity similar to Managed Server machines, although a single CPU is generally acceptable for administration purposes. ■ Configure all Managed Server instances to use Managed Server Independence. This feature allows the Managed Servers to restart even if the Administration Server is unreachable due to a network, hardware, or software failure. See Oracle Fusion Middleware Managing Server Startup and Shutdown for Oracle WebLogic Server for more information. ■ Configure the Node Manager utility to automatically restart all Managed Servers in the Oracle WebLogic Communication Services domain. See Oracle Fusion Middleware Oracle WebLogic Scripting Tool for more information. Should an Administration Server instance or machine fail, remember that only configuration, deployment, and monitoring features are affected, but Managed Servers continue to operate and process client requests. Potential losses incurred due to an Administration Server failure include: ■ Loss of in-progress management and deployment operations. ■ Loss of ongoing logging functionality. ■ Loss of SNMP trap generation for WebLogic Server instances as opposed to Oracle WebLogic Communication Services instances. On Managed Servers, Oracle WebLogic Communication Services traps are generated even in the absence of the Administration Server. To resume normal management activities, restart the failed Administration Server instance as soon as possible.

2.6 Common Configuration Tasks

General administration and maintenance of Oracle WebLogic Communication Services requires that you manage both WebLogic Server configuration properties and Oracle WebLogic Communication Services container properties. These common configuration tasks are summarized in Table 2–1 . Note: If an Administration Server fails due to a hardware, software, or network problem, only management, deployment, and monitoring operations are affected. Managed Servers do not require the Administration Server for continuing operation; Java EE applications and SIP features running on Managed Server instances continue to function even if the Administration Server fails. Shared Configuration Tasks 2-7 Table 2–1 Common Oracle WebLogic Communication Services Configuration Tasks Task Description Section 3.1, Overview of SIP Container Configuration ■ Configuring SIP Container Properties using the Administration Console ■ Using WLST to perform batch configuration Chapter 6, Configuring SIP Data Tier Partitions and Replicas ■ Assigning Oracle WebLogic Communication Services instances to the SIP data tier partitions ■ Replicating call state using multiple SIP data tier instances Chapter 4, Managing Network Resources ■ Configuring WebLogic Server network channels to handling SIP and HTTP traffic ■ Setting up multi-homed server hardware ■ Configuring load balancers for use with Oracle WebLogic Communication Services Section 5.7, Configuring Digest Authentication ■ Configuring the LDAP Digest Authentication Provider ■ Configuring a trusted host list Section 8.7, Logging SIP Requests and Responses ■ Configuring logging Servlets to record SIP requests and responses. ■ Defining log criteria for filtering logged messages ■ Maintaining Oracle WebLogic Communication Services log files