Abstract
This section presents a step-by-step execution of the process of extracting, compiling, and executing VIVO with the VTE.
Summary
Phase 1) Preparing VTE
This phase consists of preparing the VTE to accommodate the VIVO code.
Step | Description |
---|---|
a) Installing VTE | See also: Installing the Translation Ecosystem (TDB-Jena version) of Vivo-1.11.2-SNAPSHOT (ETV) |
b) Installing and initialize the VTE-config1- Select Git perspective 2- Choose Clone Git repository 3- Select Clone URI | |
4) Fill the GIT location | Git location: https://github.com/UQAM-VIVO/VTE-config |
5) Select Master branch | |
6) Be careful to select the correct directory. | |
7) Preview after VTE-config installation |
Phase 2) Uploading the VIVO code
Step | Description |
---|---|
a) Select Git Clone for cloning VitroFrom Git perspective, select the Git Clone Icon | |
b) Enter the URI of Vitro | |
c) Select the appropriate branch(ex.: sprint-i18n-whitespace) | |
d) Select the appropriate local destinationHere as well, you have to pay attention to the base directory (c:\VIVO-Trad-Ecosysteme\GIT\...) | |
e) Repeating the steps a) b) c) d)for the following repo: | |
f) ResultsAt the end of the steps, your VTE should look like this: |
Phase 3) Importing the code in the ETV
This phase allows the code to be imported in order to be compiled and executed.
Steps | Description |
---|---|
a) Setup importing1) Choose the Java perspective 2) Right-click on the mouse, scroll down the menu and select 'Import'. 3) Click Import | |
b) Select "Existing Maven Projects" | |
c) Select Maven Projects1) Select the root directory "C:\VIVO-Trad-ecosysteme\GIT" 2) Select projects | |
d) Import Overview |
Phase 4) Compiling and run
Steps | Description | ||
---|---|---|---|
a) Start compiling and installing VIVO | |||
b) Overview of the success of the compilation process | |||
c) Launching Solr and Tomcat | |||
d) Overview of the execution trace | |||
e) Accessing VIVOSee also: http://localhost:8080/vivo/ (note: it may take some time for the intial page to load as Vivo builds its database) |