1) GCALDaemon supporting a Java Virtual Machine (VM) such as found in Sun's JDK or JRE, version 1.5
or higher. This can be obtained for free from java.sun.com.
You can verify your existing Java version with the following console command:
java -version
java version "1.6.0"
Java(TM) SE Runtime Environment (build 1.6.0-b105)
Java HotSpot(TM) Client VM (build 1.6.0-b105, mixed mode, sharing)
2) Download the latest installer from
.
3) Start the installer. Click on 'Ok', then 'Next' and 'I agree'.
Select the required program components, then click on 'Next' and 'Finish'.
4) Start Config Editor.
If you see something similar to the results displayed in the above illustration, your installation has succeeded.
5) Then you should read the setup guides about the synchronization.
If you use
or an iCal-compatible PDA/Mobile synchronizer
(BitPim, MyPhoneExplorer, etc) read the guide about the
synchronization.
If you use Mozilla Calendar,
or
read the guide about the
synchronization.
Some calendar applications ignore time-zone properties.
When your local time-zone settings are incorrect your events may be off by one or more hours.
To resolve this effect, please verify that the time-zones in your Google Calendar
settings and in the OS / local calendar application are the same.
If you have trouble with running, please read the next ('GCALDaemon ZIP installation') chapter hereinafter,
and verify the file paths in the config files.
1) Download the latest Windows-compatible ZIP file from
.
2) Unzip the program under your 'Program Files' directory,
or the localized program folder instead on a non-english OS
(Programmi, Programme, Archivos de Programa, etc).
3) Test the installation; start the 'config-editor.bat' BAT file.
If you see something similar to the results displayed in the above illustration, your installation has succeeded
(go to point 8).
If you have trouble with running,
you must edit and replace some absolute file paths in the configuration files and scripts
(go to point 4).
4) Edit and modify the 'GCALDaemon/bin/standalone-start.bat' application starter script.
@echo off
rem Run GCALDaemon
java -cp ../lib/commons-codec.jar;../lib/commons-lang.jar;../lib/commons-logging.jar;
../lib/gcal-daemon.jar;../lib/gdata-calendar.jar;../lib/gdata-client.jar;
../lib/ical4j.jar;../lib/logger.jar;../lib/commons-collections.jar;../lib/commons-io.jar;
../lib/shared-asn1.jar;../lib/shared-ldap.jar;../lib/rome.jar;../lib/commons-httpclient.jar;
../lib/jdom.jar org.gcaldaemon.standalone.Main
"C:/Program Files/GCALDaemon/conf/gcal-daemon.cfg"
5) Edit and modify the 'GCALDaemon/bin/sync-now.bat' synchronizer script.
@echo off
rem Run GCALDaemon once then quit
java -cp ../lib/commons-codec.jar;../lib/commons-lang.jar;../lib/commons-logging.jar;
../lib/gcal-daemon.jar;../lib/gdata-calendar.jar;../lib/gdata-client.jar;
../lib/ical4j.jar;../lib/logger.jar;../lib/commons-collections.jar;../lib/commons-io.jar;
../lib/shared-asn1.jar;../lib/shared-ldap.jar;../lib/rome.jar;../lib/commons-httpclient.jar;
../lib/jdom.jar org.gcaldaemon.standalone.Main
"C:/Program Files/GCALDaemon/conf/gcal-daemon.cfg" runonce
6) Edit and modify the 'GCALDaemon/conf/nt-service.cfg' Windows NT service configurator file
(don't include backslash characters).
# Main configurator file
wrapper.app.parameter.1=C:/Program Files/GCALDaemon/conf/gcal-daemon.cfg
7) Start the 'standalone-start.bat' BAT file.
If you see something similar to the results displayed in the above illustration, your installation has succeeded.
8) Then you should read the setup guides about the synchronization.
If you use
or an iCal-compatible PDA/Mobile synchronizer
(BitPim, MyPhoneExplorer, etc) read the guide about the
synchronization.
If you use Mozilla Calendar,
or
read the guide about the
synchronization.
Some calendar applications ignore time-zone properties.
When your local time-zone settings are incorrect your events may be off by one or more hours.
To resolve this effect, please verify that the time-zones in your Google Calendar
settings and in the OS / local calendar application are the same.
If you have trouble with the working, try to switch the application's log level
to DEBUG, in 'GCALDaemon/conf/logger-config.cfg':
# Valid log levels: DEBUG, INFO, WARN, ERROR or FATAL
log4j.category.org.gcaldaemon=DEBUG
Then open 'log/gcal-daemon.log' file with your text editor.
This log file helps you to identify bugs and configuration problems
(e.g. 'Invalid credentials' error message means
that the username/password you entered were invalid).
If you still have trouble with installation, move on to
and please share your experiences with the rest of us.
If you have feedback about current releases, this forum is the place to share them. Thank you!