Deployment
From Wesip
From Wesip
Deployment of converged applications is similar to that of the web applications. The components, directory structure and access rules are the same as well with the only difference that separate deployment descriptors are used for HTTP and SIP (web.xml and sip.xml). Another significant difference is that when the application is packaged the extension of the resulting file is sar instead of war.
A typical converged application directory structure would look like this
The deployment descriptors for web and sip servlets
/WEB-INF/web.xml /WEB-INF/sip.xml
The servlets and utility classes
/WEB-INF/classes/mySipServlet.class /WEB-INF/classes/myHttpServlet.class /WEB-INF/classes/utilityBar.class /WEB-INF/classes/utilityFoo.class ....
The group of libraries required by the application
/WEB-INF/lib/libraryBar.jar /WEB-INF/lib/libraryFoo.jar ....
The static resources, configuration files and jsp pages
/aJspPage.jsp /anHTMLFile.jsp /aConfigurationFile.props /anAnnoucementFile.wav ....
This directory structure would be typically packaged to a file called something like myApplication.sar which would be used for deployment following the container deployment procedures that apply (i.e. copying it into container applications folder)