Resin 1.1
FAQ
Reference
JavaDoc
Demo
Java Tutorial
Getting Started
Configuration
Servlet
JSP
XTP/XSL
JavaScript
JS Library
Resin Web Server
Unix Apache
Windows Apache
Unix Netscape
IIS
Other Servlets
Getting Started
Resin provides several configuration options. We suggest you use the httpd (Resin web server) option first to evaluate Resin. If you need to use an external web server, you can configure to work wit it. Resin has three major configuration options: a standalone web server, a servlet engine with an external web server, and configuration with a third party servlet engine. Resin's httpd executable starts the standalone web server. Resin's srun executable starts the Java half with an external web server.
Executable | Configuration
--- | ---
httpd | Standalone Web Server
srun | Apache/Netscape/IIS servlet engine
com.caucho.jsp.JspServlet | External servlet engine
If you have any trouble starting Resin, check the troubleshooting FAQ. If that page doesn't solve the problem, please write us so we can update our documentation.
Preconditions
Resin needs Java before it can run. It can use either JDK 1.1.x and JDK 1.2. Sun's JDK for Windows and Solaris can be found at http://java.sun.com. Sun also has links to some other ports of the JDK. Linux users should check out either the IBM JDK or the Blackdown JDK. The IBM JDK appears to be more stable, but only supports JDK 1.1.8.
Standalone Web Server
The easiest and fastest Resin configuration uses the Resin httpd. This configuration provides a Java HTTP server. We recommend you start with this before trying any other configuration. The server listens at port 8080 in the standard configuration.
Resin with Apache
A more sophisticated configuration combines Apache and Resin on Unix or Win32. It uses Apache to serve static content like html and images and Resin to serve JSPs and Servlets. This configuration allows you to increase reliability by load balancing across several machines. The Apache configuration uses two pieces: a C program extending Apache (mod_caucho) and Java program supporting servlets and JSP (srun.) The two pieces communicate with a special high-speed protocol. To configure Apache with Resin, you must configure both Apache and Resin. The Resin configuration is identical to Resin's httpd configuration. The Apache configuration tells Apache how to find Resin. On Unix, you'll run configure using --with-apache and then make:
unix> ./configure --with-apache=/usr/local/apache unix> make
Resin with Netscape
On unix, Resin can also be configured to run with Netscape. The idea is the same as for Apache. On Unix, you'll run configure using --with-netscape and then make. The argument to --with-netscape is the directory containing the netscape start and stop scripts, i.e. the parent of the config directory.
unix> ./configure --with-netscape=/usr/local/netscape/https-your-hostname unix> make
Resin with IIS
You can also combine IIS and Resin. IIS serves static content like html and images and Resin serves JSPs and Servlets. The IIS configuration requires two pieces: iis_srun.dll, an ISAPI extension which lets IIS talk to Resin, and srun, Resin's Java support. For this setup you must configure both IIS and Resin. The Resin configuration is identical to Resin's httpd configuration. The IIS configuration tells IIS how to find Resin.
Installing Resin as a servlet
Finally, you can install Resin as a servlet with a third party servlet engine like Locomotive, JRun, ATG, or CTOWorks. Most sites won't need this configuration because Resin's servlet engine is already one of the fastest, but this option is available if you already need to run another servlet engine. This configuration is the most compliated of all. You must configure three components: The web server The third party servlet engine Resin
Reference |  | Resin Web Server
Copyright © 1998-2000 Caucho Technology. All rights reserved. Last modified: Mon, 20 Mar 2000 14:57:58 -0800 (PST)