Deploying SIP applications to Liberty

Session Initiation Protocol (SIP) applications are Java applications that contain at least one SIP servlet. SIP applications are deployed the same way as other web applications.

Before you begin

Install the sipServlet-1.1 feature in your Liberty server. For more information, see Adding and removing Liberty features.

Configure the SIP container.

About this task

To deploy a SIP application, the application must be packaged in a web archive (WAR) file, a servlet archive (SAR) file, or an enterprise archive (EAR) file that contains a WAR or SAR file.

This task describes how to manually deploy a SIP application. Alternatively, you can deploy a SIP application to Liberty by using the developer tools, which automatically enable all configurations related to the application in the server.xml file. For more information, see WebSphere® Developer Tools > Developing SIP applications.

Procedure

Add your SIP application WAR, SAR, or EAR file to the Liberty server in one of the following ways:
  • Move the archive file to the folder for drop-in artifacts in the server configuration directory at wlp/usr/servers/server_name/dropins. Liberty server monitors the dropins folder for new applications and automatically installs the application with the default configuration.
  • Move the archive file to the folder for applications in the server configuration directory at wlp/usr/servers/server_name/apps. Then, install the SIP application in the Liberty server by configuring an application element in the server.xml file.

    The following example installs the appName.ear file. The context-root attribute specifies the entry point of the deployed application.

    <application id="appId" name="appName" type="ear" location="appName.ear" context-root="/sip289/"/>