Contents for Developing SIP Servlets with WebLogic SIP Server
Overview of SIP Servlets
What is a SIP Servlet?
Differences from HTTP Servlets
Multiple Responses
Receiving Responses
Proxy Functions
Message Body
ServletRequest
ServletResponse
SipServletMessage
Roles of a Servlet Container
Application Management
SIP Messaging
Utility Functions
Requirements and Best Practices for WebLogic SIP Server Applications
Overview of Developing and Porting Applications for WebLogic SIP Server 2.1
Avoid Thread Creation
Servlets Must Be Non-Blocking
Store all Application Data in the Session
All Session Data Must Be Serializable
Use setAttribute() to Persist All Changes to Session State
send() Calls Are Buffered
Mark SIP Servlets as Distributable
Observe Best Practices for J2EE Applications
Composing SIP Applications
Overview of SIP Application Composition
Application Composition Model
Managing Proxied Requests
Sample Composer Application
Troubleshooting Application Composition
Securing SIP Servlet Resources
Overview of SIP Servlet Security
WebLogic SIP Server Role Mapping Features
Using Implicit Role Assignment
Assigning Roles Using security-role-assignment
Important Requirement for WebLogic SIP Server 2.1
Assigning Roles at Deployment Time
Dynamically Assigning Roles Using the Administration Console
Assigning run-as Roles
Role Assignment Precedence for SIP Servlet Roles
Debugging Security Features
weblogic.xml Deployment Descriptor Reference
Developing SIP Servlets Using Eclipse
Overview
SIP Servlet Organization
Setting Up the Development Environment
Creating a WebLogic SIP Server Domain
Configure the Default Eclipse JVM
Creating a New Eclipse Project
Creating an Ant Build File
Building and Deploying the Project
Debugging SIP Servlets
Enabling Access Logging
Overview
Enabling Access Logging
Specifying a Predefined Logging Level
Customizing Log Records
Example Access Log Configuration and Output