Added by Megan Forbes, last edited by Aron Roberts on Jan 26, 2010  (view change)

Labels:

Enter labels to add to this page:
Wait Image 
Looking for a label? Just start typing.

Overview

This page describes the process for installing and setting up CollectionSpace v0.4. You may choose to download pre-built deployments and war files and simply deploy them (Option #1), or you may choose to check the source code out of our Source Code Repository and build the system from scratch (Option #2).

For more information about this release, see http://www.collectionspace.org/current_release

Option #1: Deploying CollectionSpace

Step 1: Download and deploy the servers.

See Deploying the CollectionSpace Service Layer for instructions. For Step 1, follow "Step 1 approach 1: Download pre-built and pre-configured domains (recommended)"
On This Page

Step 2: Download and deploy the Application and User Interface layers

  1. Open a command prompt and type the following. You can also use a tool like WinSCP. You can use anonymous credentials with FTP, or use your repository credentials with SFTP.
    If you wish to connect via sftp, which will protect your password in transmission, you can do so by substituting sftp for ftp in line 1, above. You will not need to enter the binary command on line 3; sftp always uses binary mode.
  2. Copy the two .war files into JBoss's server/cspace/deploy folder.

Step 3: Configure the Application layer

  1. In the JBoss-based two-server deployment of a CollectionSpace system, unzip ui-specs.zip within the $JBOSS_HOME/server/cspace/conf folder.
  2. Create a properties file called chain.properties to configure the Application Layer.
    • Either in the JBoss-based two-server deployment of a CollectionSpace system, create the chain.properties file within the $JBOSS_HOME/server/cspace/conf folder.
    • Or in Tomcat, create the chain.properties file in the classpath for your web server; e.g. within the $TOMCAT_HOME/shared/classes folder.
  3. Define the following properties in the chain.properties file:

    Example (from the App/UI layer from the Mercury 0.4 release, running on the Mercury 0.4 staging slice):

    (Note that the file ../cspace-ui/html/findedit.html is contained within the cspace-ui-exp.war file, and is not a discrete file within the filesystem.)

(Optional) Copy the test data from the UI Layer source code checkout into the folder you created:
  • Copy the UI Specification files into the schemas folder:

Option #2: Build from Source

  1. Build and deploy the Services layer.
  2. Build and deploy the Application layer.
  3. Build and deploy the User Interface layer.
  4. Integrate