Deploying Active Web in tomcat or jetty
Active Web
|
Deploying Active Web in tomcat or jetty |
Active Web |
|
Active Web is no longer a supported component of PROIV; and is only available as a standalone WAR (Web Application Archive) file. To run an active web page, a servlet or web application container is required. Tomcat and Jetty are examples of commonly used Servlet containers.
Tomcat and Jetty offer multiple ways of deploying the WAR file, however for a default install of both containers the simplest mechanism to deploy Active Web is by copying the WAR file into the webapps directory.
By default, Tomcat creates a new directory in the webapps directory, with the same name as the WAR file, and extracts the WAR file into the directory (Depending on the configuration, removing the WAR file may result in the new directory being deleted). Jetty, on the other hand, extracts the WAR file into a temporary directory, usually located in the system temp directory.
You (Active Web user) have to actually add your application pages, and therefore the best method of deployment is to extract the ActiveWeb archive manually into a webapps subdirectory of your choice. The name of the subdirectory is the context path used by the servlet container, and determines how the ActiveWeb application is accessed using an URL.
For example, extracting the WAR file to /home/tomcat/webapps/ActiveWeb - by default, requires a URL of http://myhost:8080/ActiveWeb/index.xsp to access the ActiveWeb application.
If the WAR file is extracted to a directory called ROOT (Tomcat) or root (Jetty) then the context path is not required to access the application. The URL would then be http://myhost:8080/index.xsp.
It is possible to configure both Tomcat and Jetty to use different paths as the root application, but that is beyond the scope of this document.
Topic ID: 150181