Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

There are two ways to get up and running with the Giles Ecosystem: using Docker or installing it directly on your infrastructure. We recommend to use Docker for evaluation and testing purposes, but to install all components directly on your machines in production. 

...

  1. Unpack the war file (e.g. by changing its ending to ".zip" and unzipping it)
  2. Find the file WEB-INF/classes/config.properties and edit the following properties:
    • giles_files_tmp_dir: This should be an absolute path to the directory where you want Giles to stores its temporary files (files uploaded by users that haven't been processed yet).
    • If your Kafka server is not running on the same machine as Giles, or if it is running on a different port than the default port (9092), you have to change the property 

      kafka_hosts to reflect this.

    • All other properties can later be changed through the webapp itself.
  3. Find the file WEB-INF/classes/META-INF/persistence.xml and change it as follows:
    • There are three lines that start with <property name="javax.persistence.jdbc.url".  In each line, replace /path/to/giles/dbfiles/folder with the path to the folder that should store Giles' DB files. It should look something like this:

      Code Block
      languagexml
      <property name="javax.persistence.jdbc.url" value="/path/to/giles/db/folder/users.odb"/>

       Make sure to keep the file name at the end of each line.

  4. Find the file WEB-INF/spring/spring-security.xml and change the following lines:

    Code Block
    languagexml
    <beans:bean id="dataSource" class="org.springframework.jdbc.datasource.DriverManagerDataSource">
    	<beans:property name="driverClassName" value="com.mysql.jdbc.Driver" />
    	<beans:property name="url" value="jdbc:mysql://localhost:3306/giles" />
    	<beans:property name="username" value="" />
    	<beans:property name="password" value="" />
    </beans:bean>

    Change the values of username and password to the username of your DB user and its password. If you did not name the new DB giles, change the url property to reflect the database name (e.g. if you named the database gilesdb, then instead of jdbc:mysql://localhost:3306/giles, put jdbc:mysql://localhost:3306/gilesdb).
    If you are using PostgreSQL instead of MySLQ, make sure to replace the driver class name with org.postgresql.Driver.

  5. Now, generate a new war file from the unpacked and changed files and deploy it in your Tomcat. 

    Info

    If you are on a Unix-based operating system, you can do this for example by running the command jar -cvf giles.war . from inside the unpacked Giles folder.


  6. Once deployed, Tomcat should be accessible at http://your.server/giles.

Note

From version v0.5 onwards, Giles does no longer use ObjectDB as database backend. If you set up a new Giles installation (not an update with existing data), you probably still have to execute step 3, but your data will be stored in the relational database you specify (e.g. MySQL). Step 3 is still part of the set up process for backwards compatibility and data migration purposes.


Info
titleUpgrading to v0.5

If you are upgrading from an earlier version to version v0.5, you will have to migrate existing data as follows:

  1. Make sure Giles is running without exceptions.
  2. Reregister the other components with Giles (Nepomuk, Cassiopeia, Cepheus) under "Apps".
  3. Go to http://your.giles.server/giles-root/admin/migrate
  4. Enter the username of the user who's data you want to migrate. The username will be a combination of username and provider id. For example for GitHub: githubusername_github. Depending on how much data the user has uploaded, this might take a while.
  5. Once the migration is done for a user, you will see some statistics about how many objects were migrated.


Nepomuk

Nepomuk needs the following software to be installed:

...