Resin provides several configuration options. We suggest you use the Resin web server option first. If you need a specific feature of another web server, you can later configure Resin to work with that web server.
The Resin standalone web server starts listening to HTTP requests on port 8080 and listens on port 6802 for any Apache or IIS plugin. Resin can then be used for development or evaluation. The steps are:
Until you're ready to deploy the server, those are all the steps needed to get started with Resin.
Resin needs Java before it can run. It needs JDK 1.2 or a later JDK.
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.
Resin has a number of major configuration options, each with a separate page:
Theexecutable starts Resin for all configurations.
If you have any trouble starting Resin, check the FAQ at http://www.caucho.com/quercus/faq.
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.
On Unix (including Linux and MacOS-X):
For more details, see the Resin standalone configuration page.
If you are already using Apache for your web server, you can use Resin with Apache on Unix or Win32. This configuration uses Apache to serve html, images, PHP, or Perl, and Resin to serve JSPs and Servlets.
The Apache configuration uses two pieces: a C program extending Apache () and Java program supporting servlets and JSP ( .) 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:
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.
On Windows, the setup program should configure Netscape's obj.conf correctly.
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: , an ISAPI extension which lets IIS talk to Resin, and , 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.
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: , an ISAPI extension which lets IIS talk to Resin, and , Resin's Java support.
Configuration is identical to the IIS configuration.