You can download any stable or pre-release version from OpenCGA GitHub Releases. You will find a tar.gz file with the name of opencga and the version, for instance, to download OpenCGA 2.0.0-rc3 you have to go to GitHub Release page at https://github.com/opencb/opencga/releases/tag/v2.0.0-rc3 and download the file opencga-2.0.0-rc3.tar.gz from the Assets section:
Building from Source
Prerequisites
In order to build OpenCGA from source code you must first get the source code of OpenCGA from GitHub, most of the dependencies - including OpenCB dependencies - will be fetched from Maven Central Repository, however, in some scenarios, OpenCB dependencies will need to be built from GitHub source code. Compiling and building processes are carried out by Apache Maven. The following tools are required for successful build:
OpenCGA as any other software has dependencies, some of them come from other OpenCB projects such as CellBase while others are third-party dependencies such as MongoDB. All OpenCGA stable releases are always merged and tagged at master branch (users are encouraged to use latest stable release for production), you can find all releases at OpenCGA Releases. We guarantee that all the dependencies needed for building stable releases are deployed at Maven Central Repository, this is true for both OpenCB and third-party dependencies. Therefore for building a stable release you only need to clone OpenCGA repository itself since all the dependencies will be fetched form Maven Central repository.
This is different for development branches. Active OpenCGA development is carried out at develop branch, in this branch third-party dependencies will be still fetched from Maven Central Repository but this is not true for OpenCB dependencies since it is very likely they are still in development and therefore they are not deployed. Keep in mind that we only guarantee that develop compiles and that bugs are expected, use this branch for development or for testing new functionalities. So, for building develop branch you may require to download and install the following OpenCB repositories in this order:
As you can see one of our rules is that develop branch of all major applications such as OpenCGA and CellBase always depend on develop branches. So, if you really want to build develop the you can clone and build dependencies by executing:
## Clone develop brancgitclone-bdevelophttps://github.com/opencb/java-common-libs.gitgitclone-bdevelophttps://github.com/opencb/biodata.gitgitclone-bdevelophttps://github.com/opencb/cellbase.gitgitclone-bdevelophttps://github.com/opencb/oskar.git## Now you can execute the following command in each of the folders the specified order abovemvncleaninstall-DskipTests
Clone and Build OpenCGA
You can clone OpenCGA from GitHub by executing:
## Latest stable versiongitclone-bmasterhttps://github.com/opencb/opencga.git## Develop branch, for this to work remember to clone and build OpenCB dependencies (see above)gitclone-bdevelophttps://github.com/opencb/opencga.git
Building with Maven
OpenCGA allows to customise many variables in the configuration files, in order to make easier the building and configuration of OpenCGA we rely on Maven Properties that can be defined in file ~/.m2/settings.xml. During the building all these properties will be injected automatically in the configuration files so users do not have to manually change all configuration values. Note this is only possible when building OpenCGA from source code, if you download the binary version you will have to manually set up all configuration variables.
An example of that file can be found in the README and below. The description of each property can be found below:
OPENCGA.CATALOG.DB.HOSTS: This property should be configured with the host and port of the MongoDB installation. By default, for development purposes, we have it set with "localhost:27017".
OPENCGA.CATALOG.DB.USER: This property should only be set if the MongoDB needs authentication. In this case, this property will contain the user name with permissions for the database. *This can be left empty in any case. The admin will be able to set this credentials using the command line.
OPENCGA.CATALOG.DB.PASSWORD: This property should only be set if the MongoDB needs authentication. In this case, this property will contain the password of the user with permissions for the database. *Like in the user property, this can be left empty. The admin will be able to set this credentials using the command line.
OPENCGA.INSTALLATION.DIR: This property is extremely important when using Tomcat to deploy the webservices. This property will have to point to the final OpenCGA installation directory after everything has been built. This property will be used by Tomcat to locate the configuration files. If this is not properly set, none of the webservices will work. Default: /opt/opencga.
OPENCGA.USER.WORKSPACE: In Catalog, users are allowed to build their own directory structure, upload their own files, run analysis, etc. This path should be pointing to a physical location where Catalog will be storing those files and directory structure. By default, we normally put it in a folder called "sessions" within the installation directory (file:///opt/opencga/sessions/).
OPENCGA.STORAGE.VARIANT.DB.HOSTS:
OPENCGA.STORAGE.VARIANT.DB.USER:
OPENCGA.STORAGE.VARIANT.DB.PASSWORD:
OPENCGA.ANALYSIS.EXECUTION.MANAGER: OpenCGA Catalog allows users to run jobs. This property indicates how the jobs will be launched. At the moment we only support two types: LOCAL to run the jobs locally in a thread or SGE to run the jobs using Sun Grid Engine. More queuing systems will be supported soon.
OPENCGA.CLIENT.HOST: This property should be pointing to the URL where the webservices will be available. For development purposes, the default is http://localhost:8080/opencga/. This property is read by the command line opencga.sh in order to communicate with the webservices.
OPENCGA.CELLBASE.REST.HOST: URL to be used for Variant Annotation.
After creating this and configuring a default profile, you can build OpenCGA by executing the following command from the root of the cloned repository:
$mvncleaninstall-DskipTests
The first time this command can take some minutes since it has to fetched and store locally all the dependencies, the next builds will be much faster. After successful building, user should find the following file structure under a build folder:
