 |
Saké System Requirements
In order to run Saké on your web server,
you must have a server that is capable of hosting a servlet
container. If you are looking for recommendations, you're
in the right place.
If you are looking for the
simplest, cheapest servlet container that you could use, then
Jakarta
Tomcat is an excellent choice. Tomcat is the official reference
implementation of the Java Servlet API, and it is very actively
developed. As of this writing, the best choice for production
environments is version 3.3.1 of Tomcat. Version 4.0 and 4.1 both
contain a broken classloader that is not capable of properly loading
the classes in the Saké jar file into memory, even if you manually
unpack the jar file. Version 3.3.1 is very stable and robust though,
and we have seen no problems with it at all. The version 3.3.1
release of Tomcat allows you to do the simple version of the Saké
installation, so you can be up and running in minutes by grabbing
a copy of Java, Tomcat, and then Saké. We have tested Saké running
under Tomcat on
If you are a Windows user and
prefer a point-and-click solution then we recommend the JRun
servlet runner, from Macromedia.
JRun is the servlet runner that we used when we originally developed
Saké. It has changed ownership many times since then, but it is
still a very nice servlet container. Saké doesn't make any use
of any of the bells and whistles that have been tacked on to the
JRun project over the years, but if you are planning a architecture
around JSP and Servlets in general then you may be interested
in this full-featured product.
The following is a list of
system configurations that have been tested and verified compatible
with Saké. This is not an exhaustive compatibility list, this
is a list of configurations that we have specifically tested and
that are known to work correctly. Many configurations listed here
will work fine. If you have configured Saké on a configuration
not listed here, please let us know about it. We are always interested
in learning about new configurations.
|
Tested Configurations
|
|
Operating System
|
HTTP Server
|
Servlet Container
|
|
|
|
|
|
This is an excellent combination, and installation for
Tomcat is very, very simple. Saké is currently maintained
in our lab primarily using this combination, on a RedHat
7.3 server. Version 4.0 and 4.1 of Tomcat have problems
loading classes to run Saké, but version 3.3.1 includes
all of the functionality that Saké needs.
|
 |
|
|
|
|
|
See above. Mac OSX is a beautiful operating system from
head to toe and we are proud to support it.
|
|
|
|
|
|
|
See above.
|
|
|
|
|
|
|
Saké was developed using this combination. Specific installation
instructions for JRun are available here.
Allaire, the makers of JRun, recommend against using JRun's
embedded web server for production environments. For production
environments, JRun is more properly used as a plug-in
for a standalone web server such as Apache. JRun is a
very simple and robust servlet runner that is very easy
to configure.
|
|
|
|
|
|
|
Basically the same configuration as above, but with JRun
3.0 and Windows 2000. Saké development continued for a
while under this configuration.
|
|
|
|
|
|
|
Install with JRun as described here,
then create an alias for the Saké templates directory,
as described here.
|
|
|
|
|
|
|
ServletExec is a servlet runner on par with JRun. We
recommend JRun over ServletExec because it provides a
simpler and smoother installation and configuration procedure,
but Saké will run equally well with ServletExec. Install
with ServletExec as described here,
then create an alias for the Saké templates directory,
as described here.
Note that as of this writing, the Windows version of ServletExec
required version 1.3.4 of Apache specifically. ServletExec
version 2.1 was not compatible with Apache version 1.3.9.
By the time you read this, new versions of ServletExec
may have eliminated this issue.
|
|
|
|
IIS
(v4.0)
|
|
| Install with
JRun as described here, then create an alias for the Saké
templates directory in IIS with the IIS administration application.
|
|
|
|
|
|
| This configuration
works, but is not recommended. Servlet support in iPlanet
is relatively new and not extremely sophisticated, compared
to a more robust product like JRun. |
|
|
|
|
|
| See above.
|
|
|
|
|
|
| Install with
JRun as described here,
then create an alias for the Saké templates directory, as
described here.
|
|
|
|
|
|
| This is a
pretty popular configuration at universities. No real problems. |
The following is a list of configurations that are
specifically NOT recommended for use with Saké.
|
Known Problem
Configurations
|
|
Operating
System
|
HTTP
Server
|
Servlet
Runner
|
|
Any
|
|
|
|
Apache JServ implements the Java
Servlet Development Kit 2.0 from Sun, even though
newer JSDK versions have been available for some time
and are widely supported elsewhere. Saké requires a servlet
runner compliant with JSDK2.1 for more sophisticated session
management features. (The current version is 2.2) The
JServ project has been terminated, in favor of the newer
Jakarta Tomcat project. Tomcat is a promising project
that will bring support for the 2.2 Servlet API to Apache
via open and free software.
Apache JServ is also discouraged because
it is very poorly documented and extremely tedious to
install, with a wide host of incompatibility issues. You
need specific, and not current, versions of Apache, Java
and the Java Servlet Development Kit in order to get JServ
working. Our technical support staff does not maintain
a familiarity with Apache JServ for these reasons. If
you must use Apache JServ for some reason, we will of
course do our best to support you, but we are far more
familiar with JRun and ServletExec.
|
|
|
Any
|
Any
|
|
| Jakarta
Tomcat is fully-compatible with Saké, but versions 4.1 and
4.0 include a broken classloader that can't even load the
classes from Saké's jar file, much less run them. We strongly
recommended Tomcat, but at the time of this writing version
3.3.1 is the best option. Version 3.3.1 will understand
Saké's WAR file distribution just fine. |
|
|
