Installing the calendar system is fairly simple.
1) Setup (or have access to) MySQL version 3.3 or later on any platform. Create
a database and login for the calendar application to use.
2) Run the calendar.sql script against your database to create the tables.
3) Copy the "calendar" folder to your web server in an appropriate location.
If you're already running Apache or some other web server to host sites, the
"calendar" folder does not need to be under an existing site.
4) Setup (or have access to) Tomcat version 5.5 or later. (Actually, this
package works just fine under Tomcat 4.1 or later, but the instructions
below on editing the configuration files are 5.5-specific. If you're
comfortable configuring Tomcat, making the configuration below work on 4.1
or 5.0 shouldn't be difficult.)
5) Setup Tomcat to host the "calendar" folder as a webapp. If you're already
familiar with Tomcat, skip to step 6. If you've never used Tomcat before
or if it's only installed for this one application, the following instructions
should get you going. If you have problems, see:
http://jakarta.apache.org/tomcat/tomcat-5.5-doc/config/index.html
a) Rename the "server.xml" file in Tomcat's "conf" folder to something else
as a backup (e.g. server.xml.old).
b) Create a new "server.xml" file with the following contents:
................................................................................
................................................................................
Replace the markers in the above text with appropriate values.
Specifically:
#SERVER_IP_ADDRESS# should be replaced with your web server's IP address.
#WEBSITE_NAME# should be replaced with your website address (e.g.
www.example.com).
#CALENDAR_FOLDER_PATH# should be replaced with the full path to the
"calendar" folder you copied to your web server in step 4.
#SYSTEM_LOG_DIRECTORY# should be replaced with the full path to a folder
where you'd like Tomcat to put its system-level log file. This is the
file where Tomcat status and error messages will appear.
#WEBSITE_LOG_DIRECTORY# should be replaced with the full path to a folder
where you'd like Tomcat to put the website usage log. This is the file
where the record of every hit to the website will be recorded.
#SERVER_PORT# should be replaced with the port number you want to run
your Tomcat server on. Normally, this should be port 80 but if you're
already running another webserver (Apache, IIS, etc), you'll need to
use another port such as 8080.
c) If Tomcat will be serving requests on its own and you don't need to
configure another web server to proxy connections to it, skip to step 6.
d) If the other web server is not Apache, you're on your own. Sorry.
e) If you are already running Apache and you want Apache to proxy requests to
Tomcat so it appears everything is running on one site with no port
numbers, add the following line to server.xml, just below the
"
................................................................................
Replace the markers in the above text with appropriate values.
Specifically:
#PROXY_PORT# should be some other port that's not already in use on your
web server. Try 8081. Remember this value -- you'll need it when you
configure Apache.
#WEBSITE_NAME# should be replaced with your website address (e.g.
www.example.com). This should be the same address you used in step 6b.
#SERVER_PORT# should be replaced with the port you chose in step 6b.
f) Reconfigure Apache to proxy connections to Tomcat using mod_proxy. See:
http://httpd.apache.org/docs-2.0/mod/mod_proxy.html
6) If it doesn't already exist, create a folder named "Catalina" (note the
capital "C") in Tomcat's "conf" folder.
7) Inside the "Catalina" folder, create a folder named with the name of your
website (e.g. "www.example.com"). This should be the same name you used in
step 5b.
8) Decide where on your website you want the calendar application to appear.
If you want it to be at the root of your site, create a text file named
"ROOT.xml" inside the website folder. If you want it to appear in a folder
(e.g. "http://www.example.com/jonescalendar/"), create an XML file with the
name of the directory you want (e.g. "jonescalendar.XML"). The case of the
folder name is important.
9) In the new XML file, put the following text:
................................................................................
................................................................................
Replace the markers in the above text with appropriate values.
Specifically:
#WEBSITE_FOLDER_NAME# should be replaced with nothing if the calendar
is to appear at the root of your website. Otherwise, it should be
replaced with the name of the folder (the same name you gave the XML
file).
#CALENDAR_FOLDER_PATH# should be replaced with the full path to the
"calendar" folder you copied to your web server in step 4.
#MYSQL_USERNAME# should be replaced with the login name for the calendar
database on your MySQL server.
#MYSQL_PASSWORD# should be replaced with the password for the calendar
database on your MySQL server.
#MYSQL_SERVER_NAME# should be replaced with the name of your MySQL
server. If your MySQL server is running on the web server, this should
be "localhost".
#MYSQL_PORT_NUMBER# should be replaced with the port number your MySQL
server uses. If you don't know what this is, use 3306.
#MYSQL_DATABASE_NAME# should be replaced with the name of the calendar
database on your MySQL server.
If you need more help with this part, see:
http://jakarta.apache.org/tomcat/tomcat-5.5-doc/config/context.html
10) Install the JavaMail API package from:
http://java.sun.com/products/javamail/
The JAR file can be placed in Tomcat's "common/lib" folder (which makes it
available to every Tomcat application) or in the calendar application's
"WEB-INF/lib" folder (which only makes it available to the calendar
application).
(The JavaMail file cannot be distributed with the Calendar package due to
Sun's licensing policies. If you find this annoying, feel free to join the
millions who have already complained to Sun about it.)
11) Install the JavaBeans Activation Framework package from:
http://java.sun.com/products/javabeans/jaf/index.jsp
The JAR file can be placed in Tomcat's "common/lib" folder (which makes it
available to every Tomcat application) or in the calendar application's
"WEB-INF/lib" folder (which only makes it available to the calendar
application).
(The JavaBeans Activation Framework file cannot be distributed with the
Calendar package due to Sun's licensing policies. If you find this
annoying, feel free to join the millions who have already complained to Sun
about it.)
12) Edit the "calendar.properties" file under the calendar application's
"WEB-INF" folder to provide appropriate values for the application settings
The values have comments next to them to indicate their purpose.
13) (Re)Start Tomcat (and restart Apache if necessary) and hit the calendar site
using your web browser. If everything is working correctly, you should see
a blank calendar grid for the current month. If not, check for errors in
the Apache and Tomcat log files.
14) Click the "Edit calendar" link in the upper-right corner of the calendar.
To login, use:
Email address: admin@example.com
Password: admin
When you login, you must change that email address and/or password before
you can proceed. This is for your own good.
15) That's it. Start populating your calendar with events and info.