Deploying DuraCloud from Binaries

The steps below outline how to start up a DuraCloud instance from the binary distribution.

1. Download the binary distribution from the downloads page
2. Install Tomcat application server (versions 5.5.x and 6.0.x are known to work)
3. Install ActiveMQ and configure it to [SOMEHOST]:61617.  Since the ActiveMQ broker is a shared service it can be installed on any host or an existing broker can be used.
4. Deploy the web applications
   
   1. Take the 4 .war files included in the binary distribution and copy them into the "webapps" directory under your tomcat installation.
   2. Start tomcat, as part of the startup process, tomcat will unpack the wars and deploy them
5. Start up the OSGi container
   
   1. Unpack the osgi-container zip file from the distribution package
   2. Create an empty directory which will serve as the execution directory for the services
   3. Create a BUNDLE_HOME environment variable pointing at the full path to the new execution directory
   4. From a command prompt, step down into the runner directory under the unpacked osgi-container directory

   5. Make the run.sh script executable

      chmod +x run.sh
      

   6. execute run.sh
      
      • Note: Errors of the type "ClassNotFoundException: org.apache.jasper.servlet.JspServlet" can be safely ignored
   7. Wait a few moments for startup to complete. Then hit enter to get a prompt and type "ss". You should see a list of 50 bundles which are in either the ACTIVE or RESOLVED states.
6. Initialize the DuraCloud applications
   
   1. Open the init.properties file found in the distribution package
   2. Edit the values that are contained in brackets "[...]" to be appropriate for your environment. This is the step where most problems tend to show up, so feel free to ask questions regarding what values need to be included in this file.
   3. A few notes on editing this file:
      
      • The value of [host] will almost certainly be: localhost
      • You will need to have your own Amazon S3 account in order to connect. The "username" and "password" in the init.properties file, in the case of Amazon, refer to the Access Key ID and the Private Access Key that are used to make API connections to Amazon Web Services.
      • You probably want to comment out (using '#') the section starting with 'durastore.storage-acct.1', unless you also want to create a Rackspace CloudFiles account.

      • The version number below is currently, 2.2.0

        duraservice.primary-instance.services-admin-context=org.duracloud.services.admin_[VERSION]
        

      • Even though they are not in brackets, you will probably want to update the values of duraservice.service-storage.space-id and duraservice.service-storage.service-xml-id. I'd recommend these values:

        duraservice.service-storage.space-id=duracloud-2-3-0-service-repo
        duraservice.service-storage.service-xml-id=duracloud-2-3-0-service-repo.xml
        

      • The security user settings at the bottom allow you to indicate the username and password users accounts that can access your local DuraCloud, you'll use these credentials to log in to DuraCloud after initialization

   4. Execute the app-config jar, passing in the init.properties file as a parameter

      java -jar app-config.jar init.properties
      

   5. The very last line of output from the execution of the app-config process should be "success". If that's not the case, look at the output more closely to determine what error may have occurred.
7. Add services
   
   1. At this point, the applications are deployed and initialized. Point your browser to http://localhost:8080/duradmin and log in to DurAdmin.
   2. On the spaces tab, create a space called: duracloud-2-3-0-service-repo (assuming you took the naming suggestions above)
   3. Use the Add Items button to add all of the files included under the services directory in the distribution package to this new space.

This should be it. You should now be able to perform all space functions and deploy services