How do I
install Apache JServ to work with my Apache Web Server on UNIX systems? |
|
This section guides you through the process of
installing and setting up the servlet engine on UNIX systems. Apache JServ, like the
Apache Web Server, comes with installation scripts that guide and help you during the
installation but sometimes is good to know how the installation process is done to do it
by hand or to debug installation scripts. |
How do I
install Apache JServ to work with my Apache Web Server on win32 systems? |
|
If you are reading this document on a win32 system and
you chose the typical installation, you probably don't need any other
instructions to install your servlet engine since the automatic installer did it for you.
Otherwise, this section gives you the information you need to install the package. |
How do I know my
Apache JServ is working? or How do I get runtime information from my Apache JServ? |
|
Apache JServ has a built in dynamic status handler that
is currently used to monitor configurations and proper installation. This section
introduces you to the Apache JServ Status handler and to its benefits and dangers. |
How do I add and
execute my servlets now that Apache JServ is installed? |
|
Now that your servlet engine is up and running, your web
server is able to execute Java servlets. This section shows you how to setup and run your
servlets using Apache JServ. Note: this is not a servlet tutorial, please see the
JavaSoft Servlet web site
for more info on servlets and links to other resources or the JavaSoft Java Tutorial which has a section
of servlets. |
How do I secure my
servlet environment? |
|
Many servlet environments need a high degree of
security. Apache JServ gives you the ability of protect you from outside intruders
(network attacks and untrusted servlet execution) as well as inside ones, partitioning
your servlets into restricted execution environments. This section show you how to secure
your servlet engine. |
How do I migrate
from 0.9.xx to 1.0? |
|
Apache JServ 1.0 is based on the 0.9 code but introduces
major improvements and hooks for future ones. The developer team tried to incorporate as
many hooks as possible in the 1.0 tree so that future updates will not force users to
change dramatically their configurations and setup. Unfortunately, this led to major
differences in the behavior and configuration of 1.0 compared to the 0.9 generation. This
section guides you through the migration process. |
Note: other howto's and instructions
for more complex behavior will be added in the future. |