Difference between revisions of "DataMiner Installation"

From Gcube Wiki
Jump to: navigation, search
(Created page with '__TOC__ ==Introduction== DataMiner is a service providing state-of-the art DataMining algorithms and ecological modelling approaches under the Web Processing Service (WPS) stand…')
 
Line 74: Line 74:
  
 
   http://goo.gl/rtbHpW
 
   http://goo.gl/rtbHpW
 +
 +
==Related Links==
 +
* [http://onlinelibrary.wiley.com/doi/10.1002/cpe.3435/abstract Description of the Parallel Processing approach used by DataMiner]
 +
 +
* [http://onlinelibrary.wiley.com/doi/10.1002/cpe.3030/abstract Description of the Cloud Computing mechanisms used by DataMiner]
 +
 +
* [http://gcube.wiki.gcube-system.org/gcube/index.php/How-to_Implement_Algorithms_for_the_Statistical_Manager Implementing new algorithms]
 +
 +
* [http://gcube.wiki.gcube-system.org/gcube/index.php/Statistical_Manager_Algorithms list of Algorithms potentially available on the service]
 +
 +
 +
==Related Experiment==
 +
* [http://www.sciencedirect.com/science/article/pii/S0304380013003980 Predicting the habitat of a marine species]
 +
 +
* [http://www.sciencedirect.com/science/article/pii/S0304380015001222 Identifying the habitat of a rare species]
 +
 +
* [http://www.tandfonline.com/doi/abs/10.1080/15481603.2014.959391#.VVRY0fntlBc Calculating the similarity between two maps]
 +
 +
* [http://wiki.i-marine.eu/index.php/IOTC_Area_Predictive_analysis Signal processing and forecasting of fisheries data]
 +
 +
* [http://www.sciencedirect.com/science/article/pii/S0304380015002392 Application of clustering analysis to identify species commonness]

Revision as of 15:11, 27 July 2015

Introduction

DataMiner is a service providing state-of-the art DataMining algorithms and ecological modelling approaches under the Web Processing Service (WPS) standard. In this guide, we show how administrators and site-managers can install DataMiner on top of SmartGears service installations.

Prerequisites

See the SmartGears GHN requirements

Installation

Here I report the passages required to build a fully working development-environment DataMiner installation from scratch.

1 - Install a SmartGears-enabled tomcat service, possibly on the 80 port or with a redirect to the 80 port. Use devsec as starting scope.

2 - Download the official 52 WAR application from the following link and put it under webapps:


 http://build.dev.52north.org/jenkins/view/Processing/job/52n-wps_GIT-DEV_nightly_builds/lastSuccessfulBuild/org.n52.wps$52n-wps-webapp/artifact/org.n52.wps/52n-wps-webapp/3.3.2-20150523.010021-9/52n-wps-webapp-3.3.2-20150523.010021-9.war


3 - Substitute the 52n-wps-server-3.3.2-X.jar with the corresponding jar on our Maven gcube-externals repository:


 (Repository: "gCube Externals")
 <dependency>
   <groupId>rapidminer-custom</groupId>
   <artifactId>52n-wps-server</artifactId>
   <version>3.3.2</version>
 </dependency>


4 - add the following maven library along with its dependencies to the wps/WEB-INF/lib/ folder of the wps application:


 (Repository: "gCube Snapshots")
 <dependency>
   <groupId>org.gcube.dataanalysis</groupId>
   <artifactId>dataminer</artifactId>
   <version>1.0.0-SNAPSHOT</version>
 </dependency>


5 - create a folder named "persistence" under wsp/

6 - create a folder named "ecocfg" under wsp/

7 - copy all the files available at this SVN link into the ecocfg folder:


 https://svn.d4science.research-infrastructures.eu/gcube/trunk/data-analysis/DataMinerConfiguration/cfg


8 - copy the PARALLEL_PROCESSING folder at this SVN link into the ecocfg folder (thus creating the PARALLEL_PROCESSING folder under ecocfg):


 https://svn.d4science.research-infrastructures.eu/gcube/trunk/data-analysis/DataMinerConfiguration/PARALLEL_PROCESSING


9 - copy the following xml file into the wps/config folder:


 https://svn.d4science.research-infrastructures.eu/gcube/trunk/data-analysis/DataMinerConfiguration/wpscfg/wps_config.xml


10 - substitute the hostname and the port inside the following tag of the previous xml file, with the correct indication of the hostname of the machine and of the port (80) of the tomcat:


 <Server protocol="http" hostname="localhost" hostport="8080" includeDataInputsInResponse="false" computationTimeoutMilliSeconds="3600000" cacheCapabilites="false" webappPath="wps" repoReloadInterval="0.0" minPoolSize="10" maxPoolSize="20" keepAliveSeconds="1000" maxQueuedTasks="100">


11 - a reference example of configured and working wps application can be found at this link:

 http://goo.gl/rtbHpW

Related Links


Related Experiment