Fedora CloudSync is distributed as a WAR file that you can drop into any Java servlet container. This guide will walk you through the installation process.

On this page:

Download the Latest Version

1.0.0 Beta 2 (Released July 26th, 2011)

• Download fcrepo-cloudsync-service-1.0.0-beta-2.war (15MB, md5 sha1 asc)
• Issues Addressed with this Release:
  • By default, does not perform SSL certificate validation on the DuraCloud or Fedora instances it is configured to work against. This can be changed by modifying the skipSSLHostnameVerification and skipSSLTrustCheck values in WEB-INF/svc-impl.xml after deployment.
• Known Issues with this Release:
  • Same as 1.0.0 Beta 1 (see below)

1.0.0 Beta 1 (Released June 4th, 2011)

• Download fcrepo-cloudsync-service-1.0.0-beta-1.war (15MB, md5 sha1 asc)
• Known Issues with this Release:
  • Managed datastreams not copied (copy tasks will only work against objects that do not contain managed datastreams)
  • Limited user input validation in UI
  • Task detail panels just show raw data
  • Completed Task ordering is ascending
  • Completed Task titles omit task name
  • Inability to login as user other than "admin"

Upgrade Instructions

Upgrading from 1.0.0 Beta 1 to 1.0.0. Beta 2

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:

1. Stop Tomcat
2. Delete the old WAR file and the directory it expanded into, in the webapps directory.
3. Put the new WAR file in the old WAR file's place
4. Start Tomcat

Install Instructions

Define CloudSync Home

This is the directory where CloudSync will keep all data files and logs. You have four options for defining it:

1. Don't define it. If undefined, CloudSync will create and use the .cloudsync directory in the home directory of the user the servlet container runs as. For this to work, the home directory of the servlet container user must exist.
2. Set the value of the CLOUDSYNC_HOME environment variable. If set, the directory will be created and used when CloudSync starts.
3. Set the value of the cloudsync.home system property. If set, the directory will be created and used when CloudSync starts.
4. Modify the war file (unzip it, then zip it again when finished) and modify the cloudsync.properties file in the WEB-INF/classes directory.

Deploy the WAR File

CloudSync is designed to be installed in the servlet container of your choice. It has been tested with Tomcat 6.

Refer to your servlet container documentation for instructions on deploying war files. This is usually just a matter of copying the WAR file into a certain directory. NOTE: You may wish to rename the WAR file (e.g. cloudsync.war) before deploying it so the application becomes available at a shorter URL than it would be otherwise.

Check the System Log

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.