|
OpenInteract2::Manual::AdminApache is a Perl module for compiling and configuration Apache/mod_perl 1.x. SYNOPSIS This section of the OpenInteract2 manual will show you how to compile Apache and mod_perl for a two-server proxy setup, along with other information for configuring Apache. Apache and mod_perl really arent difficult to setup. As long as you have a standard C compiler (GCC!) and a little patience its really a piece of cake. APACHE 1.x OVERVIEW OpenInteract2 depends on a persistent Perl environment within a web server. Currently, the best alternative is mod_perl 1.x. mod_perl is extremely powerful, but this power can come at a price. Embedding Perl into Apache uses more resources (particularly memory) than just using Apache alone. A number of developers have experimented with various ways of minimizing the memory footprint of mod_perl, and one of the easiest and best performing methods is to use a proxy server. This is described in great detail in the mod_perl guide under the Choosing the Right Strategy heading. But well summarize here: Setup a plain Apache server with mod_proxy and mod_rewrite to listen to port 80 for your website. (We describe the build process below.) Tell this server to deal with static file requests (images, movies, PDFs, etc.) Proxy all other requests back to a heavier mod_perl server. Receive the information back from the mod_perl server and send to the client. The benefits of this are: Resource-hogging mod_perl processes do not serve static files -- if they did, youd need more of the processes. Since OI2 can run under a URL context you can segment your site to different application servers. For instance, you can say that everything under /oi goes back to your OI2 application server running under mod_perl and everything under /jsp goes to a Tomcat web container with your Java Server Pages. But to the user its all under one site -- nifty. The front-end proxy is able to feed data back to the client at whatever rate it needs without taking up many resources the entire time. For instance, users reaching your website with modems can tie up a web server process for much longer than users who are on some sort of broadband network. If the process is small its not such a big deal. Since they are separate, you can make changes to the (heavy) back-end and mask them by the (light) front-end. This is a great help when things are going wrong with the back-end and you dont want users to see nasty error pages. Also since they are separate, you can very easily move the back-end process to an entirely separate machine (or machines, using some sort of DNS or load-balancing manipulation) if the need arises. Running OpenInteract2 in this environment is strongly recommended, and it comes with configuration files that make it easier to do the Right Thing..
|
Windows Software
Albina Merfyn - I find this to be really easy to use. I can...
