(this page is incomplete; it will be updated when Peregrine installator is implemented)

+

(this page is incomplete; it will be updated when Peregrine installer is implemented)

* Download .war from [http://ws1.grid.sara.nl:21501/artifactory/libs-releases/org/erasmusmc/data-mining/peregrine/peregrine-ws/0.1/peregrine-ws-0.1.war this location] (check the latest version in advance) and deploy to your application server.

* Download .war from [http://ws1.grid.sara.nl:21501/artifactory/libs-releases/org/erasmusmc/data-mining/peregrine/peregrine-ws/0.1/peregrine-ws-0.1.war this location] (check the latest version in advance) and deploy to your application server.

Line 235:

Line 237:

* Download and run install script. After that deploy the resulting .war file to application server

* Download and run install script. After that deploy the resulting .war file to application server

The list of obligatory packages, that you need to include into your project is:

peregrine-api (includes ontology-api and common-utils)

peregrine-normalizer

peregrine-tokenizer

You need to decide, what will be your ontology provider. There are several options[1]:

File source ontology (ontology-impl-file)

DB source ontology (ontology-impl-db)

You need to decide, whether you need to disambiguate text indexing results (usually, you do). If yes, you need to include peregrine-disambiguator project. Disambiguator layer can be used out of the box without special configuration.

You have to decide, what Peregrine interface implementation you want to use. By the time of writing this article, there is only one implementation available: peregrine-impl-hash