![]() |
||
What role are you playing? Viewer ~ Publisher ~ Admin |
Before installing Calendar Central, you must have already installed Java and Perl on your server.
Install Java
If you are not already doing Java development, you will probably want to install the Java Runtime Environment, JRE. This is available for almost all platforms. The best source for the JRE is at www.JavaSoft.com. Click here to go straight the the JRE section on JavaSoft's site. If you have a server that is not supported by JavaSoft, give us a call and we will help you locate a Java runtime for your systemIf you are a development shop, you may have already installed the full JDK (Java Development Kit), version 1.1.3 or greater. The JDK comes with the JRE, so your set.
Install Perl
Perl 5.x is required to run Calendar Central. A good source for a pre-compiled Windows NT version is at ActiveState. You can go straight to http://www.ActiveState.com/software/default.htm and get the latest version.
If you are installing on Windows NT, there may be a few extra steps needed for the web server to run Perl as a CGI. There's a good FAQ on ActiveState's site to help you out.
The following assumes you have correctly installed the Java runtime (JRE or JDK version 1.1.3 or greater) and Perl 5.x on your server. It also assumes a basic familiarity with URLs, HTML, and CGI. If you don't know what these mean, don't worry, just email us with any questions at support@iRenaissance.com, or call 919.380.7815. We'll work it out together.
The first thing you need to decide is where to put Calendar Central. It should probably be a directory off your main web site directory. Put the compressed tar file (or zip file) for Calendar Central in that main directory. When you uncompress and extract the tar file (or unzip the zip file), you will end up with a subdirectory called "cc". cc will contain the complete application for the applet, server, and database.
classpath
You should not have a classpath environment variable. Previous version of Java
required this. Java 1.1.x does not.
Change to the cc directory and start the server with the following command ( there
are two parameters).
CAUTION: Make sure Calendar Central is not already running.
jre -cp . irServer PortNumberToListenOn irCom.pl
Fill in the port number the server will listen on. irCom.pl is the name of the CGI script used for server
communications. If you're on a Unix system, append an ampersand, '&', on the end of the command to create a
background process.
Update "irCom.pl" to match your current system. This is the CGI Perl script the applet uses to communicate
with the server. There are a few variables at the top of the script. Refer to the script for instructions. Make
sure the port number in the script matches the port number the server is listening on.
irCom.pl should have file permissions set as an executable for all.
Some systems expect Perl scripts to end in ".cgi". You may rename "irCom.pl" to "irCom.cgi".
Make sure you use the same name for all installation instructions.
Create your own HTML page for the Calendar Central applet. You may copy and edit the example page,
CalendarCentral.html.
A. BASE HTML tag
Update the BASE HTML tag to use your server's IP address plus the path plus
a slash, '/', on the end. You must use IP addressing for the codebase of the applet in order to work with many
firewalls.
B. codebase applet parameter
Update the codebase applet parameter to use your servers IP address. This should be the
same as the CODEBASE HTML tag. Make sure you append the slash, '/'. You must use IP addressing for the
codebase of the applet in order to work with many firewalls.
C. "port" applet parameter
Update the "port" applet parameter to be the same as the port number the server is listening on.
D. "communicationsCGI" applet parameter
Update the path for the communicationsCGI parameter. This should be the path and filename that will be
appended to the base URL. For example, if the URL for the CGI is "http://208.207.20.45/cc/irCom.pl" then
the cummunicationsCGI parameter should be set to "cc/irCom.pl". Do NOT put
a '/' on the front.
Note: If you changed the name of irCom.pl, use the new name for step D above.
Start the viewer. We recommend you start the Classic View first (HTML view). The format is:
http://yourDomain/cgi-bin/irCom.pl?db
Basically, you have to run the CGI Perl script, irCom.pl, and pass it the name of the database,
db. Your CGI format may be different.
If you see the contents of the Perl script instead of the calendar, your server doesn't know that it should
execute the Perl script. Please see the FAQ
for enabling CGI Perl scripts for your web server.
Once your know the Perl CGI is running, kick off the Java Viewer:
http://yourDomain/cc/CalendarCentral.html
Back to Getting Started.
irServer.class
The server application. Type "java irServer" for options. irCom.pl
The Perl CGI the applet uses to talk to the Java server. irCCApplet.class
The Calendar Central Applet. CalendarCentral.html
The example HTML file which brings up the applet. irCCAdmin.class
An administrative applet which lists the members that have accessed the server in the last hour. It requires the same HTML page setup as irCCApplet.class . templates
This directory is where the sample HTML templates are located.
Problem: The server reports a problem when started.
- You do not have all the files AND subdirectories in the cc directory. This is most likely caused by copying the directory without copying the subdirectories.
Problem: The applet does not load at all.
- You have not specified the BASE or CODEBASE correctly.
Problem: The applet's graphics do not load.
- You did not append a slash, '/', to the BASE and CODEBASE.
Problem: The applet has loaded, but I don't see the calendar view.
- The server is not running.
- You did not specify the same port number: a) when you started the server, and b) when you updated irCom.pl, and c) when you updated the applet's port parameter in the HTML file.
- You have not specified BASE or CODEBASE correctly. Pull up the Java console in Netscape (Explorer doesn't have one). Look at the URL for the CGI. If it is not correct, the BASE and CODEBASE are not correct.
- You have renamed "irCom.pl" to something else and did not update the communicationsCGI applet parameter to match the new name.
- irCom.pl is not set to be executable by all.