<summarylist/>

Resin provides a fast servlet runner for O'Reilly WebSite Pro, allowing it to run servlets and JSP files.

To configure Resin with O'Reilly WebSite Pro, you must follow the following steps:

1. Configure WebSite Pro via its property sheet
2. Configure resin.conf with a text editor
3. Start httpd. You may want to run httpd as an NT service.

You should use resin1.x/bin/setup.exe to setup your configuration. If you use setup.exe, you can just skip to the next section.

If you don't use the supplied setup.exe program, here are the steps needed to setup WebSite Pro to run Resin:

1. Make sure Resin works via it's httpd.exe!
2. Stop WebSite Pro.
3. Copy isapi_srun.dll to the WebSite root directory, .
4. Using the WebSite property sheet, Mapping tab, Associations list, associate .jsp, .xml and .xtp with the above extension .
5. Using the WebSite property sheet, Mapping tab, Content types list, set the content type for .jsp, .xml, and .xtp to .
6. Add isapi_srun.dll to WebSite's API pre-load list. Use the registry editor and add the full pathname of isapi_srun.dll, typically , to the LoadLibrary string. This is located under HKEY_LOCAL_MACHINE\Software\Denny\WebServer\CurrentVersion. The variable name is LoadLibrary, and it is a semicolon-delimited string. Simply add to the end of the LoadLibrary string.

In order to browse the supplied documents and samples, we strongly recommend creating a virtual server and mapping its root to the Resin directory. When creating this virtual server with WebSite's New Identity Wizard, you can uncheck both CGI options in the New Identity Wizard. Then after it's finished, change the / mapping from to . To set the virtual server up:

1. On WebSite's property sheet, Identity Tab, click New... and step through the New Identity Wizard. For this example, we'll assume that you used as the URL prefix.

2. Create the following document mappings using the property sheet, Mapping tab, Document list. We'll assume the identity hostname is resin.foo.com and the URL prefix is .

   1. Map to the Resin subdirectory
   2. Map to
   3. Map to
   4. Map to

Make sure WebSite Pro is running, then:

1. Browse http://resin.foo.com/servlet/Hello and /foo.jsp. You should see a "cannot connect" error.
2. Start httpd.exe
3. Browse http://resin.foo.com//servlet/Hello and /foo.jsp. You should now see the servlet.

resin.conf should mirror the configuration of WebSite Pro. In other words, you need to configure the document root and any directory aliases.

For many users, you only need to change the attribute from 'doc' to something like 'c:\website\htdocs'. For more complicated configurations, you'll need to add path-mapping attributes.

<caucho.com> <http-server app-dir='c:\website\htdocs'> <servlet-mapping url-pattern='/servlet/*' servlet-name='invoker'/> <servlet-mapping url-pattern='*.xtp' servlet-name='com.caucho.jsp.XtpServlet'/> <servlet-mapping url-pattern='*.jsp' servlet-name='com.caucho.jsp.JspServlet'/> </http-server> </caucho.com>

From the Resin bin folder, you need to start httpd.exe to start the servlet runner.

Now browse http://localhost/test.jsp. You should get a 'file not found' message.

Create a test file 'C:\WebSite\htdocs\test.jsp'

<example> <%@ page language=javascript %> 2 + 2 = <%= 2 + 2 %>

Browse http://localhost/test.jsp again. You should now get

<results> 2 + 2 = 4 </results>

As a final test, change language to 'java' and refresh the page. Nothing should change.

1. First, check your configuration with the standalone httpd.sh.
2. Check . That will tell if the ISAPI extension is properly installed.
3. Each srun host should be green and the mappings should match your resin.conf.
4. If caucho-status fails entirely, the problem is in the installation.
5. Check that isapi_srun.dll is in
6. If caucho-status shows the wrong mappings, there's something wrong with the resin.conf.
7. If caucho-status shows a red servlet runner, then httpd.exe hasn't properly started.
8. If you get a "cannot connect to servlet engine", caucho-status will show red, and httpd.exe hasn't started properly.
9. If httpd.exe doesn't start properly, you should look at the logs in resin1.x/log. You should start to get more information.
10. If you get Resin's file not found, the WebSite configuration is good but the resin.conf probably points to the wrong directories.

The following configuration line arguments are recognized by httpd.exe and httpd.exe. When installed as a service, these argument will be used when the service starts.

<deftable>
-verboseWrite more verbose information to the log file
-resin_home <path>Sets the location of Resin
-java_home <path>Specify the JDK location
-msjavaUse Microsoft's JVM
-nojitDisable JIT compilation to help debugging
-classpath <cp>Add to the classpath
-J<arg>Set a Java command line argument, e.g. -J-nojit.
-D<foo=bar>Set a Java variable, e.g. -Dresin.home=here.
-installInstall as an NT service
-install-as <name>Install as an NT service with the specific name.
-removeRemove as an NT service
-remove-as <name>Remove as an NT service with the specific name. </deftable>