Getting Started


Resin
FAQ
Reference Guide
JavaDoc
Demo
Tutorial

Getting Started
Configuration
EJB
IDE
Topics
JSP
XTP/XSL

Resin Web Server
Unix Apache
Windows Apache
Unix Netscape
IIS
WebSite
Other Servlets

Getting Started

Reference Guide

Resin Web Server

Preconditions
Standalone Web Server
Resin with Apache
Resin with Netscape
Resin with IIS
Resin with O'Reilly WebSite

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 with it.

Resin has two major configuration options:

a standalone web server
a servlet engine with an external web server

Resin's httpd executable starts both the standalone web server or the servlet engine. The protocol used depends on the <http> and <srun> configuration in the resin.conf.

Executable	Configuration
httpd	Standalone Web Server
httpd	Apache/Netscape/ISAPI servlet engine
com.caucho.server.http.HttpServer	Resin main java class.

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, Solaris, and Linux can be found at http://java.sun.com. Sun also has links to some other ports of the JDK.

Linux users can also check out the IBM JDK. Currently, however, the IBM is currently less stable than the Sun JDK.

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

On Windows, the setup program should configure Netscape's obj.conf correctly.

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: isapi_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.

Resin with O'Reilly WebSite

You can also combine WebSite and Resin. WebSite serves static content like html and images and Resin serves JSPs and Servlets. The WebSite configuration requires two pieces: isapi_srun.dll, an ISAPI extension which lets IIS talk to Resin, and srun, Resin's Java support.

Configuration is identical to the IIS configuration.

Reference Guide

Resin Web Server