Developers who are already familiar with writing SIP Servlet applications need not change anything just to use Rhino SIP Servlet. They can continue to develop and test servlet applications using their existing tools, IDEs, and so on.
Developers new to SIP Servlet should review the SIP Servlet 1.1 specification (JSR 289) to get started and experiment with Rhino SIP Servlet’s example applications.
Package as a "SAR" file
SIP Servlet applications are packaged as a SAR (SIP Servlet ARchive) file, which like other SLEE or Java EE archive file types, is a JAR file containing the application’s classes, resources and a deployment descriptor, sip.xml.
The SAR file layout looks like this:
WEB-INF/sip.xml # Deployment descriptor WEB-INF/classes/... # Application classes (servlets, listeners etc) WEB-INF/lib/... # Third-party libraries (jar files)
Deploy with console or Ant commands
Once an application has been packaged as a SAR file, it can be installed into Rhino SIP Servlet using the install-ss (console) or <​sipservlet:install> (Ant) commands. See Application Deployment in the Installation and Administration Guide.
Unlike many other servlet containers, a newly-deployed Rhino SIP Servlet application is not automatically activated. Instead, it is deployed as a SLEE service, which requires an extra activation step before the SLEE will begin firing events to the service.
You can activate the service using standard rhino-console commands, or the <​sipservlet:activate> Ant task.
