CloudSync Project
CloudSync 1.1.x (Current Release)
CloudSync 1.0.x
...
On this page:
Table of Contents |
---|
...
...
This upgrade just requires a straight WAR file replacement. No changes to the content of CLOUDSYNC_HOME
are needed.
Upgrading will depend on the servlet container you're using. For example, if using Tomcat:
webapps
directory....
See Downloads for the latest WAR file.
This is the directory where CloudSync will keep all data files and logs. You have four options for defining it:
It is recommended that you allocate at least 128 MB of heap and 128 MB of PermGen memory for use by CloudSync when running in a dedicated servlet container. In a shared container, you should find out what these values are set to currently, and increase them by at least 128 MB each.
This can be done in a variety of ways, depending on the servlet container. In Tomcat, one way to control it is to set the CATALINA_OPTS
environment variable before starting up the container.
For example, in Unix:
No Format |
---|
export CATALINA_OPTS="-Xms128m -Xmx128m -XX:MaxPermSize=128m"
|
In Windows:
No Format |
---|
set CATALINA_OPTS=-Xms128m -Xmx128m -XX:MaxPermSize=128m
|
CloudSync is designed to be installed in the servlet container of your choice. It has been tested with Tomcat 6.
...
CloudSync's main logfile can be found in $CLOUDSYNC_HOME/systemlogs/cloudsync.log. If you're having trouble starting or using the service, this file often contains details that will help you resolve the problem.
Upgrading from one of the beta releases will require a re-installation due to significant database changes.