Regular SLEE services must be installed using deployable units, or DUs. These are JAR files containing the service deployment descriptor, Service Building Block (SBB) component JAR files, and supporting libraries.
Each installed DU is identified by a unique URL, which can later be used to uninstall the DU, removing the service and its components from the SLEE.
When a SIP Servlet application’s SAR file is deployed, Rhino SIP Servlet automatically generates a container service for the SIP Servlet application, and packages it inside a DU, along with the original SAR file. The resulting DU is then installed in the SLEE.
The new SIP Servlet application DU is installed with the following default properties:
The DU’s URL is the
file:URL of the original SAR file.
The servlet application name is that defined in the SAR’s
sip.xmldeployment descriptor, or
The ServiceID of the container service is:
name=SIP Servlet Application: app-name,vendor=OpenCloud,version=1.0
These properties may all be overridden at deployment time — see Installing a SIP Servlet Application.
Once deployed, the new service can be managed with the normal Rhino SLEE management commands, such as
deactivateservice, and so on. Rhino SIP Servlet provides some additional commands that let services be addressed by their servlet application names instead of their SLEE
|This section assumes that the application is packaged as a SAR file.|
See the following procedures for deploying and undeploying SIP Servlet applications in Rhino SIP Servlet: