Page History

...

Code Block

language	bash
title	Example for Linux
linenumbers	true

export GIT_HOMEREPO=/opt/tomcat/GIT
export JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64
export SOLR=/opt/solr
export TOMCAT_HOME=/opt/tomcat
export VIVO_HOME=/opt/tomcat/vivo_i18n/home

...

Step

Action

1) Create VIVO home

Code Block

language	bash

sudo -i -u tomcat # for Linux user
mkdir -p $VIVO_HOME
cp -r $TOMCAT_HOME/GIT/vivo-uqam-i18n/vivo-project-i18n-config/vivo_i18n/home/* $VIVO_HOME/home/

2) Edit runtime.properties file

Make sure that attribute properties fit with current installation

Code Block

language	bash

sudo -u tomcat vi $VIVO_HOME/config/runtime.properties

Code Block

language	bash
title	runtime.properties

Vitro.defaultNamespace = http://<your-server-ip-address>:8080/vivo_i18n/individual/
...

rootUser.emailAddress = YOUR_ADRESS
rootUser.passwordChangeRequired = false
rootUser.password = YOUR-PASSWORD
...

vitro.local.solr.url = http://<server-ip-address>:8983/solr/vivocore_i18n
...
RDFService.languageFilter = true
languages.selectableLocales = en_US, de_DE

3) Edit applicationSetup.n3 for TDB data persistence

Code Block

language	text
title	applicationSetup.n3

# UNCOMMENT
:tdbContentTripleSource
    a   vitroWebapp:triplesource.impl.tdb.ContentTripleSourceTDB ,
        vitroWebapp:modules.tripleSource.ContentTripleSource ;
    # May be an absolute path, or relative to the Vitro home directory.
    :hasTdbDirectory "tdbContentModels" .

:sparqlContentTripleSource
    a   vitroWebapp:triplesource.impl.sparql.ContentTripleSourceSPARQL ,
        vitroWebapp:modules.tripleSource.ContentTripleSource ;
    # The URI of the SPARQL endpoint for your triple-store.
    :hasEndpointURI "http://localhost:3030/vivo/query" ;
    # The URI to use for SPARQL UPDATE calls against your triple-store. 
    :hasUpdateEndpointURI "http://localhost:3030/vivo/update" .

COMMENT
#:sdbContentTripleSource
#    a   vitroWebapp:triplesource.impl.sdb.ContentTripleSourceSDB ,
#        vitroWebapp:modules.tripleSource.ContentTripleSource .

#REPLACE
:application
    a   vitroWebapp:application.ApplicationImpl ,
        vitroWebapp:modules.Application ;
    :hasSearchEngine              :instrumentedSearchEngineWrapper ;
    :hasSearchIndexer             :basicSearchIndexer ;
    :hasImageProcessor            :iioImageProcessor ;
    :hasFileStorage               :ptiFileStorage ;
    :hasContentTripleSource       :tdbContentTripleSource ;
#    :hasContentTripleSource       :sdbContentTripleSource ;
#    :hasConfigurationTripleSource :tdbConfigurationTripleSource ;
    :hasConfigurationTripleSource :tdbConfigurationTripleSource ;
    :hasTBoxReasonerModule        :jfactTBoxReasonerModule .

4) Edit and configure VIVO installation setting file

Check that the file contains the following code:

Code Block

language	bash

cd $GIT_HOMEREPO/Vivo-installer-i18n
sudo -u tomcat cp example_settings_i18n_linux.xml settings_i18n_linux.xml
sudo -u tomcat vi settings_i18n_linux.xml

Code Block

language	xml
title	settings_i18n_uqam.xml

<settings xmlns="http://maven.apache.org/SETTINGS/1.1.0"
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.1.0 http://maven.apache.org/xsd/settings-1.1.0.xsd">
        <profiles>
                <profile>
                        <id>defaults</id>
                        <properties>
                                <app-name>vivo_i18n</app-name>
                                <vivo-dir>/opt/tomcat/vivo_i18n/home</vivo-dir>
                                <tomcat-dir>/opt/tomcat</tomcat-dir>
                                <default-theme>wilma</default-theme>
                        </properties>
                </profile>
        </profiles>
        <activeProfiles>
                <activeProfile>defaults</activeProfile>
        </activeProfiles>
</settings>

...

Step

Action

1) check the state of the Git directory before starting the compilation

make sure that all directories are present and are all at the same hierarchical level in Git directories

Code Block

language	bash
title	Command

cd $GIT_HOMEREPO
ls -al

Code Block

language	bash
title	Result

drwxrwxr-x ... Vitro
drwxrwxr-x  ... Vitro-languages
drwxrwxr-x  ... VIVO
drwxrwxr-x  ... Vivo-installer-i18n
drwxrwxr-x  ... VIVO-languages

2) start compiling

Before starting the compilation make sure you have correctly configured the settings_i18n_linux.xml file as described above. The -DskipTests option is optional.

Info
Assurez-vous que le fichier war est installé dans le répertoire approprié de tomcat

Code Block

language	bash
title	Command

cd Vivo-installer-i18n
mvn -s settings_i18n_linux.xml -DskipTests=true install

At the end you should see a compilation end looking like this:

Code Block

language	bash
title	Result

[INFO] 
[INFO] --- maven-dependency-plugin:2.10:unpack (install) @ vivo-installer-vivo ---
[INFO] Configured Artifact: org.vivoweb:vivo-installer-vivo:1.11.2-SNAPSHOT:war
[INFO] Unpacking /opt/tomcat/GIT/Vivo-installer-i18n/webapp/target/vivo.war to /opt/tomcat/webapps/vivo_i18n with includes "" and excludes ""
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for VIVO Installer for i18n 1.11.2-SNAPSHOT:
[INFO] 
[INFO] Vitro Home ......................................... SUCCESS [ 2.409 s]
[INFO] VIVO Home .......................................... SUCCESS [ 1.453 s]
[INFO] VIVO Languages for Home en_US ...................... SUCCESS [ 0.340 s]
[INFO] VIVO Languages for Home de_DE ...................... SUCCESS [ 0.036 s]
[INFO] VIVO Languages for Home es ......................... SUCCESS [ 0.034 s]
[INFO] VIVO Languages for Home pt_BR ...................... SUCCESS [ 0.027 s]
[INFO] VIVO Languages for Home en_CA ...................... SUCCESS [ 0.024 s]
[INFO] VIVO Languages for Home CORE ....................... SUCCESS [ 0.105 s]
[INFO] VIVO Installer for i18n ............................ SUCCESS [ 0.151 s]
[INFO] Vitro Install Home for i18n ........................ SUCCESS [ 1.382 s]
[INFO] Vitro Dependencies ................................. SUCCESS [ 0.447 s]
[INFO] Vitro API .......................................... SUCCESS [ 1.295 s]
[INFO] Vitro Web App ...................................... SUCCESS [ 0.882 s]
[INFO] Vitro Languages for Web App en_US .................. SUCCESS [ 0.313 s]
[INFO] Vitro Languages for Web App de_DE .................. SUCCESS [ 0.064 s]
[INFO] Vitro Languages for Web App es ..................... SUCCESS [ 0.042 s]
[INFO] Vitro Languages for Web App pt_BR .................. SUCCESS [ 0.051 s]
[INFO] Vitro Languages for Web App en_CA .................. SUCCESS [ 0.099 s]
[INFO] Vitro Languages for Web App CORE ................... SUCCESS [ 0.212 s]
[INFO] VIVO API ........................................... SUCCESS [ 0.379 s]
[INFO] VIVO Web App ....................................... SUCCESS [ 1.146 s]
[INFO] VIVO Languages for Web App en_US ................... SUCCESS [ 0.027 s]
[INFO] VIVO Languages for Web App de_DE ................... SUCCESS [ 0.104 s]
[INFO] VIVO Languages for Web App es ...................... SUCCESS [ 0.039 s]
[INFO] VIVO Languages for Web App pt_BR ................... SUCCESS [ 0.034 s]
[INFO] VIVO Languages for Web App en_CA ................... SUCCESS [ 0.026 s]
[INFO] VIVO Languages for Web App CORE .................... SUCCESS [ 0.085 s]
[INFO] VIVO WebApp Install dependencies for i18n .......... SUCCESS [ 0.002 s]
[INFO] VIVO Install Web App for i18n ...................... SUCCESS [ 4.094 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 15.851 s
[INFO] Finished at: 2020-09-23T14:50:52-07:00
[INFO] ------------------------------------------------------------------------

...

Step

Action

1) access the sample file

Extract the sample file from GitHub

Code Block

language	bash

git clone https://github.com/vivo-project/sample-data.git  -b branch_name_to_be_coming

2) build a translated file in the target language

This step consists of copying language files from the directory is in the target language and translating the content into the new language and associating the appropriate linguistic tag to it.

Warning
Notes: Make sure your file is in UTF-8 format.

Code Block

language	bash

cd $GIT_HOMEREPO/sample-data/i18n
cp sample-data-en_US.ttl sample-data-fr_CA.ttl
edit sample-data-fr_CA.ttl

#- sample change

Code Block

language	text
title	Change from

sample-data:n1246
rdfs:label "ENC 1114 -- Introduction to Rhetoric"@en-US ;
.

Code Block

language	text
title	Change to

sample-data:n1246
rdfs:label "ENC 1114 -- Intruction à la Rhétorique"@fr-CA ;
.

3) Install the files so that they are processed each time VIVO is started.

Code Block

language	text
title	Change to

cp sample-data.ttl sample-data-en_US.ttl sample-data-fr_CA.ttl $VIVO_HOME/rdf/abox/filegraph

...

Step 4) Editing the problematic file

several directory structures and files need to be set up to initialize the implementation of the linguistic context in VIVO.

Step

Action

1) Create directory structures in Vitro-languages and VIVO-languages

The demonstration is for the integration of the French Canadian fr_CA in Vitro-languages and VIVO-Languages

Code Block

language	bash
title	Preparing Vitro-languages

cd $GIT_REPO/Vitro-languages
mkdir -p fr_CA/webapp/src/main/webapp/i18n
cp en_US/webapp/src/main/webapp/i18n/all_en_US.properties fr_CA/webapp/src/main/webapp/i18n/all_fr_CA.properties

Step 5) If necessary reset the various VIVO's indexes and databases

...

Page tree

Versions Compared

Old Version 37

New Version 38

Key

1) Create VIVO home

2) Edit runtime.properties file

3) Edit applicationSetup.n3 for TDB data persistence

4) Edit and configure VIVO installation setting file

1) check the state of the Git directory before starting the compilation

2) start compiling

1) access the sample file

2) build a translated file in the target language

Step 4) Editing the problematic file

Step 5) If necessary reset the various VIVO's indexes and databases