|Version 3 (modified by robert@…, 6 years ago) (diff)|
This guide describes how to install this dbNP module. Installation can be done from source code or using a pre-built WAR file. The method using a WAR file is much easier. However, using the source code you can perform your own changes to the source code, before installation.
This dbNP module needs a working GSCF instance to connect with. You can install GSCF using instructions on https://trac.nbic.nl/gscf/wiki/QuickStartServer. GSCF and the module may be on the same server, but this is not required.
The dbNP module can be most easily installed in a tomcat container. See http://tomcat.apache.org/ for more information about setting up a tomcat container.
Finally, the module needs a functioning database. PostgreSQL and MySQL database are supported out of the box. If you want support for other databases, you should add the libraries required to the source code, and build a war. See next chapter for more information
Retrieving and adjusting source code
The mass sequencing module has been written in Grails (www.grails.org). You can obtain the source code from SVN using the following command
svn co https://trac.nbic.nl/svn/dbnp-metagenomics dbnp-metagenomics
Write access to the repository is only available to registered developers.
After checking out the source code, you can edit the code and make adjustments. When you are finished editing, use the grails command
to create a WAR package for installation. See also http://www.grails.org/Deployment for more information. See
Retrieving pre-build package
Go to https://trac.nbic.nl/dbnp-metagenomics/downloads and download the latest package for this module.
Installing the package
When you have obtained or created a WAR package, you should deploy the package to a tomcat container. You can do so by copying the WAR to the TOMCAT_HOME/webapps directory. See also http://www.grails.org/Deployment for more information.
Configuring the package
You can configure the package by editing the file
where [environment] will be the environment the war has been created for. Normally this will be 'prod'. If you have created your own package, the environment name might be different.
See Configuration for more information about the configuration.