Oracle Server E10293-02 Benutzerhandbuch

The SIP Container

2-4  Oracle Communication and Mobility Server Developer’s Guide

Each servlet defined in the deployment descriptor has one instantiation. Because 
servlets are run in a multi-threaded environment, only data that is common to all 
requests and responses, such as init parameters, are stored as member variables.

Each servlet, which includes a <servlet> and a <servlet-mapping> section in 
the deployment descriptor file (sip.xml) also has a <security-constraint> 
section. OCMS makes these servlets reusable through the Servlet Creation wizard in 
OCMS SCE, because these sections are created together with the servlet. 

In OCMS, the Servlet archive format (SAR) file is renamed to a Sip Servlet aRchive 
(SSR). The format of the two files are the same, the difference in naming is because of 
the requirement for a third-party application server for OCMS. Because the application 
server cannot process SAR files, the SIP AS checks for SSR files instead. This name 
change enables portability between different SIP application servers.

Listeners can be registered to listen on events and invoke a method. Each deployment 
descriptor can only have one defined listener of each type. Each of these listeners must 
be implemented by the developer. The different types of listeners are as follows:

■

SipApplicationSessionListener

: The listener for 

SipApplicationSession

 creation and invalidation. It can be used to ask for a 

session extension. The SipApplicationSessionListener interface must be 
implemented and the sip.xml updated.

■

SipSessionListener

: The listener for changes in active SipSessions in the SIP 

servlet application. The SipSessionListener interface must be implemented 
and configured in the sip.xml file.

■

SipSessionAttributeListener

: The listener for SipSession attribute 

changes. The SipSessionAttributeListener interface must be implemented.

■

TimerListener

: The timer service enables delayed actions for a servlet if the 

TimerListener

 interface has been implemented. Only one timer listener exists 

per application (sip.xml).

■

SipSessionActivationListener

: Objects that depend on a session can listen 

on their status about being active or passive if the 
SipSessionActivationListener

 interface is implemented.

When you deploy a SIP application through Oracle 10g 

Application Server Control or through the admin_client.jar 
command-line tool you must rename the Servlet archive file (SAR file) 
to WAR and list the WAR file in the application.xml just like a WAR 
archive. Also the WAR must contain a web.xml file, so that you can 
deploy it on OC4J.

For more information on packaging SAR files and deploying EAR 
files, see Oracle Communication and Mobility Server Administrator’s 
Guide.