This document provides instructions for installing caIntegrator Bioconductor.

Topics in this document include:

Overview

caIntegrator provides the capability to perform level 3 Should "level 3" be defined? copy number analysis using either caDNAcopy or caCGHcall.  Both of these tools are part of the Bioconductor suite and are implemented as caGrid services wrapping the R Bioconductor code.  One or both of these tools can be installed either on a separate server from caIntegrator or on the same server.&nbsp.What is this? It keeps appearing in the markup.

Be aware that the R processing associated with caDNAcopy and/or caCGHcall can be very CPU and memory intensive.

The current installation instructions only support installation on Linux platforms. Recommended configurations are given at the bottom.

Prerequisites

please check linksThe following software packages must be installed prior to beginning the instructions:

Install Dependent Packages

The caIntegrator Bioconductor installation also depends on several other packages that may not be installed on your system.  Summaries of these packages and how to install them follow.

Globus 4.0.3

Installed at /usr/local/ws-core-4.0.3

  1. Download
  2. Unpack tar file into /usr/local/ws-core.4.0.3
  3. Ensure that GLOBUS_LOCATION is set to /usr/local/ws-core-4.0.3

Apache Axis 1.4

Installs files into $CATALINA_HOME

  1. Download
  2. Unpack tar file in home directory
  3. Move axis-1_4/webapps/axis directory to $CATALINA_HOME/webapps
  4. Stop and restart Tomcat ($CATALINA_HOME/bin/shutdown.sh; $CATALINA_HOME/bin/startup.sh)
  5. Test Axis installation

ActiveMQ 4.0.2

Installed at /usr/local/incubator-activemq-4.0.2

  1. Download
  2. Unpack tar file into /usr/local/incubator-activemq-4.0.2
  3. Ensure that JMS_HOME is set to /usr/local/incubator-activemq-4.0.2
  4. Edit file $JMS_HOME/conf/activemq.xml
    1. Change line that reads "<broker useJmx="true">" to "<broker useJmx="true" persistent="false">"
    2. Replace line that reads "<transportConnector name="default" uri="tcp://localhost:61616" discoveryUri="multicast://default"/>" with " <transportConnector name="default" uri="tcp://localhost:61616"/>"
    3. Comment out or remove line that reads "<networkConnector name="default" uri="multicast://default"/>"
  5. Make main binary executable
    1. chmod 755 $JMS_HOME/bin/activemq
      ActiveMQ can be autostarted or started as part of the Bioconductor launch script (provided later in these instructions)

R 2.9.0

Installed at /usr/local/R-2.9.0

  1. Download
  2. Unpack tar file in home directory
  3. Configure, build, and install
  4. make Should this be here?
    When I printed this document off, there was a "made install prefix+/usr/local/R-2.90" here, but I see it's gone. Did you delete it? Just wanted to make sure I didn't do anything I shouldn't.(smile)

Dependent R packages (RCurl, SJava, RWebServices, RUnit, DNAcopy)

Installs files into $R_HOME

  1. $R_HOME/bin/R
  2. At the R prompts:
  3. Build SJava links missed by install:
  4. Build and test SJava/RWebServices installation (as per Bioconductor Installation Guide page 10)

Install caDNAcopy

This section installs the caDNAcopy grid in three pieces: base code, R web service, and caGrid service.  You may skip this section if you are only using caCGHcall.

caDNAcopy Base Code

I'm unclear about whether each of these are steps. If so they should be numbered, if not, perhaps they should stay bulleted.
Installs into R_HOME

  1. cd to your home directory
  2. svn checkout http://gforge.nci.nih.gov/svnroot/bioconductor
  3. cd bioconductor/trunk/services/caDNAcopy/R
  4. $R_HOME/bin/R CMD INSTALL caDNAcopy

caDNAcopy RWebService

steps?
Installs into /usr/local/bioconductor/caDNAcopy

caDNAcopy Grid Service

These are worded like steps, so it's clearer to me that they can be numbered.Are the indented bullets steps as well? If so, I'll "letter" them.
Installs into $CATALINA_HOME

  1. Download Bioconductor-caGrid-Services.tar.gz from https://gforge.nci.nih.gov/docman/view.php/175/19977/Bioconductor-caGrid-Services.tar.gz
  2. Unpack tar file in home directory
  3. Build and deploy caDNAcopy grid service
  4. Prepare Tomcat for Grid applications
  5. cd $GLOBUS_LOCATION
  6. Optionally, fix timeout value in caDNAcopy.jar to be 2 hours instead of 60 seconds

Install caCGHcall

This section installs the caCGHcall grid service in three pieces: base code, R web service, and caGrid service.  You may skip this section if you are only using caDNAcopy.

caCGHcall Base Code

Installs into R_HOME

caCGHcall RWebService

If these are steps, just number the first one and I'll finish them.
Installs into /usr/local/bioconductor/caCGHcall

caCGHcall Grid Service

Installs into $CATALINA_HOME

  1. Build and deploy caCGHcall grid service
  2. Prepare Tomcat for Grid applications
  1. Copy $JMS_HOME/lib/*.jar to $CATALINA_HOME/webapps/wsrf/WEB-INF/lib

Launch Bioconductor Services

This section describes how to start up all the pieces of the Bioconductor installation once they have been successfully installed. In the section following this one, you can find optional scripts that can automate the startup and shutdown of all processes.

Starting Bioconductor Services

As per Bioconductor Installation Guide page 11: Do you have a link for this?

  1. Start up Tomcat (shutdown if already running)
  2. Start up ActiveMQ
  3. Start up R worker for caDNAcopy (skip if only using caDNAcopy)
  4. Start up R worker for caCGHcall (skip if only using caCGHcall)

Optional Improvements

Scripts to startup/shutdown Bioconductor

These shell scripts can be used to automate the launch of Bioconductor. If these are used to automatically start the Bioconductor services at system startup, please ensure that all environment variables (as listed in sections above) are already defined. All three scripts should be placed in the same directory and must be set to be executable (chmod a+x). Also note that these scripts are intended to be used with the common logging setup that is described in the section following this one.

Setting up common logging

One disadvantage to having multiple separate processes for Bioconductor is that each process creates a separate log file by default. By using the following steps, the log files for Tomcat, ActiveMQ, and caDNAcopy/caCGHcall are placed into a single directory (/usr/local/bioconductor/logs). If the scripts in the above section are used, it further improves logging by placing all messages into a single log file (/usr/local/bioconductor/logs/bioconductor-combined.log).