Resin provides a fast servlet runner for Netscape, allowing Netscape to run servlets, JSP and XTP files.
To configure Resin with Netscape, you must follow the following steps:
To compile and installon Unix, you'll need to run configure 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.
If you need finer control over the Netscape configuration, you can use the following arguments to ./configure. Resin needsand .
Making caucho_nsapi will automatically change your obj.conf file. For reference, here are the changes:
Note: Versions prior to iPlanet 6 put thein obj.conf.
Note: The caucho-status is optional and probably should be avoided in a production site. It lets you ask plugin module about the Caucho status, valuable for debugging.
Restart Netscape. Now browse http://localhost/caucho-status. It should return a table indicating that the servlet runner is stopped.
Browse http://localhost/test.jsp. It should return a message like:
In Resin 1.2, you can distribute requests to multiple machines. All requests in a session will go to the same host. In addition, if one host goes down, Resin will send the request to the next available machine.
In addition, you can specify backup machines. The backup only will serve requests if all primaries are down.
See the http config section for more details.
By default, Resin will look in resin1.2/doc for JSP files and resin1.2/doc/WEB-INF/classes for servlets and beans. To tell Resin to use Netscape's document area, you configure the. Change from 'doc' to something like '/usr/local/netscape/doc'.
Installing Resin with Netscape modifies Netscape's obj.conf file. For most users, the default installation will be fine. More sophisticated users will need to modify the obj.conf file.
Now you need to start the servlet engine.
Now browse http://localhost/test.jsp. You should get a 'file not found' message.
Create a test file '/usr/local/netscape/htdocs/test.jsp'
Browse http://localhost/test.jsp again. You should now get
A better way to run the servlet engine in a production environment is to use the start and stop scripts. These scripts add extra reliability to the server. If Resin should ever exit, it will automatically be restarted.
To start the servlet runner, use
To stop it, use
On Windows, the setup program should configure the obj.conf. Except that you don't need to compile the plugin on windows, the configuration is identical.