xml and xslt
resin installation quick start
You can start using Resin by simply expanding the archive, and starting Resin with a Java command line.
The Resin web server starts listening to HTTP requests on port 8080 and listens on port 6800 for load balancer or cluster messages. Resin can then be used for development or evaluation. The steps are:
Once you've made sure Resin is working, you'll want to add some content to the default web site:
You can easily create virtual hosts by creating content in the directory:
Permanent content locations
Eventually, you'll want to move your content and configuration into a more permanent location:
Running Resin as a daemon
In a deployment environment, Resin will run as a background daemon. The previous steps ran Resin in the foreground, which is convenient for development since the logging output goes to the console. When running as a daemon, Resin detaches from the console and continues running until told to stop.
Until you're ready to deploy the server, those are all the steps needed to get started with Resin.
Resin 3.1 needs Java before it can run. It needs JDK 1.5 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.
The easiest and fastest Resin configuration uses the Resin as the primary or only web server. 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 default configuration and can be changed to the HTTP port 80 during deployment.
Unix (including MacOS-X)
For more details, see the Resin Web Server configuration page.
If you are already using Apache for your web server, you can use Resin with Apache. 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
unix> ./configure --with-apache=/usr/local/apache unix> make unix> make install
For more details, see the Resin with Apache configuration page.
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.
For more details and troubleshooting steps, see the Resin with IIS configuration page.