<title>Getting Started</title>

<summarylist/>

<p/>Resin provides several configuration options.  We suggest you use the
<a href='httpd.xtp'>httpd</a> (Resin web server) option first to
evaluate Resin.  If you need to use an external web server,
you can configure to work with it.

<p/>Resin has two major configuration options:
<ul>
<li>a standalone web server
<li>a servlet engine with an external web server
</ul>

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

<deftable>
<tr><th>Executable<th>Configuration
<tr><td>httpd<td>Standalone Web Server
<tr><td>httpd<td>Apache/Netscape/ISAPI servlet engine
<tr><td>com.caucho.server.http.HttpServer<td>Resin main java class.
</deftable>

<p>If you have any trouble starting Resin, check the <a
href='../faq/index.xtp'>troubleshooting FAQ</a>.  If that page doesn't
solve the problem, please write us so we can update our documentation.

<section title='Preconditions'>

<p/>Resin needs Java before it can run.  It can use either JDK
1.1.x and JDK 1.2.

<p/>Sun's JDK for Windows, Solaris, and Linux can be found at
<a href='http://java.sun.com'>http://java.sun.com</a>.  Sun also has
links to some other ports of the JDK.

<p/>Linux users can also check out the <a href='http://www.ibm.com'>IBM
JDK</a>.  Currently, however, the IBM is currently less stable
than the Sun JDK.

</section>

<section title='Standalone Web Server'>

The easiest and fastest Resin configuration uses the
<a href='httpd.xtp'>Resin httpd</a>.  This configuration provides a
Java HTTP server. We recommend you start with this
before trying any other configuration.

<center>
<ct:img src='httpd.gif'/>
</center>

<p/>The server listens at port 8080 in the standard configuration.

</section>

<section title='Resin with Apache'>

A more sophisticated configuration combines Apache and Resin on <a
href='cse-apache-unix.xtp'>Unix</a> or <a
href='cse-apache-win.xtp'>Win32</a>.  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.

<p/>The Apache configuration uses two pieces: a C program extending
Apache (<var/mod_caucho/>) and Java program supporting servlets and
JSP (<var/srun/>.)  The two pieces communicate with a special high-speed
protocol.

<center>
<ct:img src='apache_srun.gif'/>
</center>

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.

<p/>On Unix, you'll run configure using --with-apache and then make:
<example>
unix> ./configure --with-apache=/usr/local/apache
unix> make
</example>

</section>

<section title='Resin with Netscape'>

On unix, Resin can also be configured to
<a href='cse-netscape.xtp'>run with Netscape</a>.  The idea is
the same as for Apache.

<p/>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.

<example>
unix> ./configure --with-netscape=/usr/local/netscape/https-your-hostname
unix> make
</example>

<p/>On Windows, the setup program should configure Netscape's obj.conf
correctly.

</section>

<section title='Resin with IIS'>

You can also combine <a href='cse-iis.xtp'>IIS and Resin</a>.  IIS
serves static content like html and images and Resin serves JSPs and
Servlets.   The IIS configuration requires two pieces:
<var/isapi_srun.dll/>, an ISAPI extension which lets IIS talk to
Resin, and <var/srun/>, Resin's Java support.

<center>
<ct:img src='iis_srun.gif'/>
</center>

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.

</section>

<section title="Resin with O'Reilly WebSite">

You can also combine <a href='cse-oreilly-website.xtp'>WebSite and Resin</a>.
WebSite serves static content like html and images and Resin serves JSPs and
Servlets.   The WebSite configuration requires two pieces:
<var/isapi_srun.dll/>, an ISAPI extension which lets IIS talk to
Resin, and <var/srun/>, Resin's Java support.

<center>
<ct:img src='iis_srun.gif'/>
</center>

<p/>Configuration is identical to the IIS configuration.

</section>

<!--
<section title='Installing Resin JSP 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.

<center>
<ct:img src='appserver.gif'/>
</center>

This configuration is the most compliated of all.  You must configure
three components:
<ol>
<li>The web server
<li>The third party servlet engine
<li>Resin
</ol>

</section>

-->