Table of Contents
- Title and Copyright Information
- Preface
- 1 About Developing Applications for the Converged Application Server
- 2 Overview of SIP Servlet Application Development
- 3 SIP Servlet POJOs
-
4
Best Practices for SIP Applications
- Overview of Developing Distributed Applications for Converged Application Server
- Use the SIP Concurrency Utilities
- Treat MessageListener Implementations as Read-Only
- Local Data Structures Must Not Store Container-Managed Objects
- Servlets Must Be Non-Blocking
- All Session Data Must Be Serializable
- Mark SIP Servlets as Distributable
- Use SipApplicationSessionActivationListener Sparingly
- Observe Best Practices for Java EE Applications
- Optimizing Memory Utilization and Performance with Serialization
- 5 Composing SIP Applications
- 6 Developing Converged Applications
- 7 SIP Servlet Concurrency
- 8 Managing Client Initiated Connections
- 9 Back to Back User Agents
- 10 Forking SIP Requests, Dialog Termination, and Session Keep Alive
- 11 Using Compact and Long Header Formats for SIP Messages
- 12 Developing Custom Profile Service Providers
- 13 Using Content Indirection in SIP Servlets
-
14
Securing SIP Servlet Resources
- Overview of SIP Servlet Security
- Triggering SIP Response Codes
- Specifying the Security Realm
- Converged Application Server Role Mapping Features
- Using Implicit Role Assignment
- Assigning Roles Using security-role-assignment
- Assigning run-as Roles
- Role Assignment Precedence for SIP Servlet Roles
- Debugging Security Features
- weblogic.xml Deployment Descriptor Reference
- 15 Enabling Message Logging
- 16 Generating SNMP Traps from Application Code
-
17
Using the REST Interface
- Location Service RESTful Interface
-
REST Management for
MBeans
- NetworkAccessPointMBean
- SipServerBean
- Configure Server Debugging
- Retrieving Runtime Attributes