Use setAttribute to Modify Session Data in “No-Call” Scope
4.8 Mark SIP Servlets as Distributable
If you have designed and programmed your SIP Servlet to be deployed to a cluster environment, you must include the distributable marker element in the Servlets deployment descriptor when deploying the application to a cluster of engine tier servers. If you omit the distributable element, WebLogic Server does not deploy the Servlet to a cluster of engine tier servers. If you mark distributable in sip.xml it must also be marked in the web.xml for a WAR file. The distributable element is not required, and is ignored if you deploy to a single, combined-tier non-replicated WebLogic Server instance.4.9 Use SipApplicationSessionActivationListener Sparingly
The SIP Servlet 1.1 specification introduces SipApplicationSessionActivationListener, which can provide callbacks to an application when SIP Sessions are passivated or activated. Keep in mind that callbacks occur only in a replicated WebLogic Server deployment. Single-server deployments use no SIP data tier, so SIP Sessions are never passivated. Also, keep in mind that in a replicated deployment WebLogic Server activates and passivates a SIP Session many times, before and after SIP messages are processed for the session. This occurs normally in any replicated deployment, even when RDBMS-based persistence is not configured. Because this constant cycle of activation and passivation results in frequent callbacks, use SipApplicationSessionActivationListener sparingly in your applications.4.10 Session Expiration Best Practices
For a JSR289 application, the container is more intelligent in removing sessions. For example, there is no need to explicity call invalidate on a session or sipappsession. However, if setExpirs is used on a session and the application is of a JSR289 type then that call has no effect unless setInvalidateWhenReadfalse is called on the session.4.11 Observe Best Practices for Java EE Applications
If you are deploying applications that use other Java EE APIs, observe the basic clustering guidelines associated with those APIs. For example, if you are deploying EJBs you must design all methods to be idempotent and make EJB homes clusterable in the deployment descriptor. 4-6 Oracle WebLogic Server SIP Container Developer’s GuideParts
» Oracle Fusion Middleware Online Documentation Library
» Multiple Responses SIP Servlets Versus HTTP Servlets
» Receiving Responses SIP Servlets Versus HTTP Servlets
» Proxy Functions SIP Servlets Versus HTTP Servlets
» Servlet Request Message Body
» Servlet Response Message Body
» Application Management Role of a Servlet Container
» Sends a 200 response to the CANCEL request.
» Sends a 487 response to the INVITE request to be cancelled.
» Invokes a doCancel method on the SIP servlet. This allows the application to
» Utility Functions Role of a Servlet Container
» Overview of Converged Applications
» Assembling and Packaging a Converged Application
» Using the Converged Application Example
» Overview of Header Format APIs and Configuration Summary of Compact Headers
» Assigning Header Formats with WlssSipServletMessage
» Summary of API and Configuration Behavior
» Overview Generating SNMP Traps from Application Code
» Requirement for Accessing SipServletSnmpTrapRuntimeMBean
» Obtaining a Reference to SipServletSnmpTrapRuntimeMBean
» Overview of Developing Distributed Applications
» Applications Must Not Create Threads
» Servlets Must Be Non-Blocking
» Store all Application Data in the Session
» All Session Data Must Be Serializable
» Use setAttribute to Modify Session Data in “No-Call” Scope
» Mark SIP Servlets as Distributable
» Session Expiration Best Practices
» Observe Best Practices for Java EE Applications
» Application Composition Model Oracle Fusion Middleware Online Documentation Library
» Using the Default Application Router
» Configuring a Custom Application Router
» Session Key-Based Request Targeting
» Overview of SIP Servlet Security
» Role Mapping Features Oracle Fusion Middleware Online Documentation Library
» Using Implicit Role Assignment
» Important Requirements 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
» Specifying a Predefined Logging Level
» Customizing Log Records Enabling Message Logging
» Overview Specifying Content Types for Unencrypted Logging
» Example Message Log Configuration and Output
» Configuring Log File Rotation
» Diameter Protocol Packages Oracle Fusion Middleware Online Documentation Library
» File Required for Compiling Application Using the Diameter API
» Implementing a Diameter Application
» Sending Request Messages Sending Answer Messages
» Creating New Attributes Working with AVPs
» Working with Diameter Sessions Creating Converged Diameter and SIP Applications
» Overview of Profile Service API and Sh Interface Support
» Enabling the Sh Interface Provider
» Using a Constructed Document Key to Manage Profile Data
» Prerequisites for Listener Implementations
» Implementing ProfileListener Monitoring Profile Data with ProfileListener
» Overview of the Profile Service API
» Implementing Profile Service API Methods
» Mapping Profile Requests to Profile Providers
» Configuring Profile Providers Using the Administration Console
» Overview of Rf Interface Support
» Understanding Offline Charging Events
» Configuring the Rf Application
» Specifying the Session Expiration Sending Asynchronous Events
» Accessing the Rf Application Implementing Event-Based Charging
» Using the Accounting Session State
» Overview of Ro Interface Support
» Credit Authorization with Unit Determination
» Credit Authorization with Direct Debiting
» Determining Units and Rating
» Configuring the Ro Application
Show more