Configuration Guide

     Previous  Next    Contents    View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Overview of the WebLogic SIP Server Architecture

Goals of the WebLogic SIP Server Architecture

Load Balancer

Engine Tier

Data tier

Example of Writing and Retrieving Call State Data

RDBMS Storage for Long-Lived Call State Data

Geographically-Redundant Installations

Example Hardware Configurations

Alternate Configurations

Overview of WebLogic SIP Server Configuration and Management

Shared Configuration Tasks for WebLogic SIP Server and WebLogic Server

WebLogic SIP Server Configuration Overview

Diameter Configuration

Methods and Tools for Performing Configuration Tasks

Administration Console

WebLogic Scripting Tool (WLST)

Additional Configuration Methods

Editing Configuration Files

Custom JMX Applications

Common Configuration Tasks

Configuring Data Tier Partitions and Replicas

Overview of Data Tier Configuration

datatier.xml Configuration File

Configuration Requirements and Restrictions

Best Practices for Configuring and Managing Data Tier Servers

Example Data Tier Configurations and Configuration Files

Data Tier with One Partition

Data Tier with Two Partitions

Data Tier with Two Partitions and Two Replicas

Monitoring and Troubleshooting Data Tier Servers

Storing Long-Lived Call State Data in an RDBMS

Overview of Long-Lived Call State Storage

Requirements and Restrictions

Steps for Enabling RDBMS Call State Storage

Using the Configuration Wizard RDBMS Store Template

Modify the JDBC Datasource Connection Information

Configuring RDBMS Call State Storage by Hand

Configure JDBC Resources

Configure WebLogic SIP Server Persistence Options

Create the Database Schema

Using Persistence Hints in SIP Applications

Configuring Geographically- Redundant Installations

Overview of Geographic Persistence

Requirements and Limitations

Steps for Configuring Geographic Persistence

Using the Configuration Wizard Templates for Geographic Persistence

Installing and Configuring the Primary Site

Installing the Secondary Site

Configuring Geographical Redundancy by Hand

Configuring JDBC Resources (Primary and Secondary Sites)

Configuring Persistence Options (Primary and Secondary Sites)

Configuring JMS Resources (Secondary Site Only)

Understanding Geo-Redundant Replication Behavior

Call State Replication Process

Call State Processing After Failover

Removing Backup Call States

Monitoring Replication Across Regional Sites

Troubleshooting Geographical Replication

Configuring Engine Tier Container Properties

Overview of SIP Container Configuration

Using the Administration Console to Configure Container Properties

Locking and Persisting the Configuration

Configuring Container Properties Using WLST (JMX)

Managing Configuration Locks

Configuration MBeans for the SIP Servlet Container

Locating the WebLogic SIP Server MBeans

WLST Configuration Examples

Invoking WLST

WLST Template for Configuring Container Attributes

Creating and Deleting MBeans

Working with URI Values

Reverting to the Original Boot Configuration

Configuring NTP for Accurate SIP Timers

Enabling the Engine Tier Cache

Overview of Engine Tier Caching

Configuring Engine Tier Caching

Monitoring and Tuning Cache Performance

Upgrading a WebLogic SIP Server 2.2 Configuration to Version 3.0

About the Upgrade Process

Step 1: Install Software and Prepare Domain

Step 2: Use the WebLogic Server 9.2 Upgrade Wizard

Step 3: Edit the config.xml File to Specify WebLogic SIP Server Resources

Step 4: Relocate and Edit WebLogic SIP Server Configuration Files

Upgrade sipserver.xml and datatier.xml Files

Upgrade diameter.xml Files

Step 5: Perform Optional Upgrade Tasks

Improving Failover Performance for Physical Network Failures

Overview of Failover Detection

WlssEchoServer Failure Detection

Forced Shutdown for Failed Replicas

WlssEchoServer Requirements and Restrictions

Starting WlssEchoServer on Data Tier Server Machines

Enabling and Configuring the Heartbeat Mechanism on Servers

Tuning JVM Garbage Collection for Production Deployments

Goals for Tuning Garbage Collection Performance

Modifying JVM Parameters in Server Start Scripts

Using JRockit Deterministic Garbage Collection (WebLogic Real Time)

Tuning Garbage Collection with JRockit

Tuning Garbage Collection with Sun JDK

Avoiding JVM Delays Caused by Random Number Generation

  Back to Top       Previous  Next