Website Setup & Info

ID #1071

How does Tomcat work at GeekISP?

Tomcat support at GeekISP is pretty straightforward. First of all, Tomcat is an optional, ala carte service. Please check the ala carte page for the latest prices. If you'd like to add Tomcat service for a particular domain, just email support requesting it.

When Tomcat is enabled, there are several options in how its set up. By default, we now map your entire domain onto Tomcat, but that's not strictly required - we could only map a portion of your URL space.

For instance if you wanted only JSP files to be served by Tomcat, that's very easy to do. If you were planning a mixed deployment (i.e. some files served by Tomcat, some by Apache), just tell us how you'd like it configured. We use mod_jk to forward requests from Apache to Tomcat, so any simple url mapping is possible. For instance:

Keep PHP files on Apache:
*.php
Send anything in the /myapp/ url to Tomcat:
/myapp/*

Any basic pattern like that is easy to support. While the above is possible, we do highly recommend that you devote your entire domain to Tomcat to simplify deployment. If you have a main site (example.com) and want to add a few apps in support of your existing site, it may be simpler to configure 'java.example.com' and deploy your apps there.

Deployment is done via WAR files automatically. Assuming you have a standard setup (i.e. all URLs are mapped to Tomcat) for your example.com domain, you would deploy files like so:

  • To setup an application to serve the '/' URL for your domain (i.e. the default app), drop a file named ROOT.war into your ~/www.example.com directory.
  • If you want another app to handle /myapp, just drop a WAR named myapp.war into ~/www.example.com.
  • Note that your 'htdocs' and 'cgi-bin' directories are not used in this case, since all files are served from the contents of the WAR files.

On the backend, we run a single shared Tomcat instance, but we have redundant configurations running across several web servers. Sessions are sticky, but not replicated. That means that after the first request is served, a user will only be connected to a single Tomcat backend unless a Tomcat server should go down.

Tags: -

Related entries:

Last update: 2008-02-01 08:28
Author: Dave Steinberg
Revision: 1.0

Digg it! Print this record Send to a friend Show this as PDF file
Propose a translation for Propose a translation for
Please rate this entry:

Average rating: 0 out of 5 (0 Votes )

completely useless 1 2 3 4 5 most valuable

You cannot comment on this entry