Configuring and Managing WebLogic SIP Server

Overview of the WebLogic SIP Server Architecture

Goals of the WebLogic SIP Server Architecture

Load Balancer

Engine Tier

Data tier

Example Hardware Configuration

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

Configuration Implementation

Diameter Configuration

Understanding Staging Modes for the sipserver Application

Startup Sequence for a WebLogic SIP Server Domain

Methods and Tools for Performing Configuration Tasks

Administration Console

Upgrade Utility

WebLogic Scripting Tool (WLST)

Additional Configuration Methods

Editing Configuration Files

Custom JMX Applications

Administration Server Best Practices

Adding threads to weblogic.admin.RMI and weblogic.admin.HTTP

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

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)

ConfigManagerRuntimeMBean Usage and Reference

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

Configuring Diameter Sh Client Nodes and Relay Agents

Overview of Diameter Protocol Configuration

Steps for Configuring Diameter Client Nodes and Relay Agents

Installing the Diameter Domain

Creating Network Channels for the Diameter Protocol

Configuring Two-Way SSL for Diameter TLS Channels

Configuring Diameter Sh Client Nodes

Configuring Diameter Relay Agents (Optional)

Example Domain Configuration

Configuring an HSS Simulator

Capacity Planning for WebLogic SIP Server Deployments

Introduction to Capacity Planning

Determining Performance Goals

Basic Hardware Configuration and Throughput Values

Throughput Values for WebLogic SIP Server Instances

Sample Deployment Scenarios

Small Deployment

Medium Deployment

Large Deployment

Managing WebLogic SIP Server Network Resources

Overview of Network Configuration

Configuring Load Balancer Addresses

Multiple Load Balancers and Multihomed Load Balancers

Configuring Network Channels for SIP or SIPS

Reconfiguring an Existing Channel

Creating a New SIP or SIPS Channel

Configuring SIP Channels for Multi-Homed Machines

Configuring TCP and TLS Channels for Diameter Support

Configuring Engine Servers to Listen on Any IP Interface (0.0.0.0)

Configuring Unique Listen Address Attributes for Data Tier Replicas

Production Network Architectures and WebLogic SIP Server Configuration

Overview

Single-NIC Configurations with TCP and UDP Channels

Static Port Configuration for Outbound UDP Packets

Multihomed Server Configurations Overview

Multihomed Servers Listening On All Addresses (IP_ANY)

Multihomed Servers Listening on Multiple Subnets

Understanding the Route Resolver

IP Aliasing with Multihomed Hardware

Load Balancer Configurations

Single Load Balancer Configuration

Multiple Load Balancers and Multihomed Load Balancers

Network Address Translation Options

IP Masquerading Alternative to Source NAT

Example WebLogic SIP Server Network Configuration

Overview

Example Network Topology

WebLogic SIP Server Configuration

Load Balancer Configuration

NAT-based configuration

maddr-Based Configuration

rport-Based Configuration

Logging SIP Requests and Responses

Overview of SIP Logging

Using the Template Logging Servlet

Deploying the Template Logging Application

Using the Logging Servlet Implementation in Other Applications

Defining Logging Servlets in sip.xml

Configuring the Logging Level and Destination

Specifying the Criteria for Logging Messages

Using XML Documents to Specify Logging Criteria

Using Servlet Parameters to Specify Logging Criteria

Specifying Content Types for Unencrypted Logging

Managing Logging Performance

Enabling Log Rotation and Viewing Log Files

trace-pattern.dtd Reference

Adding Tracing Functionality to SIP Servlet Code

Order of Startup for Listeners and Logging Servlets

Avoiding and Recovering From Server Failures

Failure Prevention and Recovery Features

Overload Protection

Redundancy and Failover for Clustered Services

Automatic Restart for Failed Server Instances

Managed Server Independence Mode

Directory and File Backups for Failure Recovery

Backing up config.xml

Automated config.xml Archiving

Automatic Backup of config.xml at Server Startup

Backing Up the sipserver Application

Backing Up the Diameter Application

Backing Up Server Start Scripts

Backing Up Logging Servlet Applications

Backing Up Security Data

Backing Up the WebLogic LDAP Repository

Backing Up SerializedSystemIni.dat and Security Certificates

Backing Up Additional Operating System Configuration Files

Restarting a Failed Administration Server

Restarting an Administration Server on the Same Machine

Restarting an Administration Server on Another Machine

Restarting Failed Managed Servers

Configuring SNMP

Overview of WebLogic SIP Server SNMP

Browsing the MIB

Configuring SNMP

SNMP Port Binding for WebLogic SIP Server

Understanding and Responding to SNMP Traps

Files for Troubleshooting

Trap Descriptions

connectionLostToPeer

Description

Recovery Procedure

connectionReestablishedToPeer

Description

Recovery Procedure

dataTierServerStopped

Additional License FAQs

overloadControlActivated, overloadControlDeactivated

Description

Recovery Procedure

Additional Overload FAQs

replicaAddedToPartition

Description

Recovery Procedure

replicaRemovedFromPartition

Additional Shutdown FAQs

Upgrading Deployed SIP Applications

Overview of SIP Application Upgrades

Requirements and Restrictions for Upgrading Deployed Applications

Steps for Upgrading a Deployed SIP Application

Assign a Version Identifier

Defining the Version in the Manifest

Appending the Version to the Archive Name

Appending the Version to the context-root (Enterprise Applications)

Deploy the Updated Application Version

Undeploy the Older Application Version

Roll Back the Upgrade Process

Accessing the Application Name and Version Identifier

Upgrading Software and Converged Applications

Overview of System and Application Upgrades

Requirements for Upgrading a Production System

Upgrading to a New Version of WebLogic SIP Server

Configure the Load Balancer

Configure the New Engine Tier Cluster

Define the Cluster-to-Load Balancer Mapping

Duplicate the SIP Servlet Container and Data Tier Configuration

Upgrade Engine Tier Servers and Target Applications to the New Cluster

Upgrade Data Tier Servers

Upgrading a Deployed Production Application (Compatible Session Data)

Upgrading a Deployed Production Application (Incompatible Session Data)

Configure the Load Balancer

Configure the New Engine Tier Cluster

Define the Cluster-to-Load Balancer Mapping

Migrate Engine Tier Servers and Target Applications to the New Cluster

Applying Patches Using InstallPatch

Overview of the InstallPatch Utility

Required Environment for the InstallPatch Utility

Syntax for Invoking the InstallPatch Utility

Example InstallPatch Commands

Editing the MANIFEST Classpath in GUI Mode

Troubleshooting the InstallPatch Utility

Upgrading a WebLogic SIP Server 2.0.x Configuration to Version 2.2

About the Upgrade Program

Steps for Upgrading an Existing Configuration

Required Environment for the UpgradeConfig Utility

UpgradeConfig Reference

Improving Failover Performance for Physical Network Failures

Overview of Failover Detection

WlssEchoServer Failure Detection

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

Tuning Garbage Collection with JRockit

Tuning Garbage Collection with Sun JDK

Avoiding JVM Delays Caused by Random Number Generation