Pre-BUILD Requirements

• download vmware

• https://www.vmware.com/products/workstation-pro/workstation-pro-evaluation.html

• LSU has a way to get a license: https://software.grok.lsu.edu/Article.aspx?articleId=20512

• LSU OneDrive link to shared

• create a vmware machine

• choose ubuntu server 22.04 iso

• 100 GB on one file for disk size

• the vm must have network access (right click the vm, go to settings>network adapter, select "Bridged", then save)

• go through the os installation process

• set your username and password

• finish the OS installation

• when the installation finishes, you should accept the prompt to reboot the machine.

• when the vm boots, log in with you username and password you set.

network debugging

• try the "vmware-netcfg" command on the host machine if you have trouble connecting.
• you may need to change between bridged and host-only connections (
• check your network connection in the command line with
• ping www.google.com
• if you get bytes back you're connection is good.

enable shared folders on the virtual machine

• (right click the vm, go to settings, click the options tab, select "Always Enabled" for shared folders
• (select a path to the "shared" folder from LSU OneDrive, click save)
• I keep my path simple and put the files in a folder called 'shared'
• my path is /mnt/hgfs/shared within the vm, if you use a different path, change it in all commands that use '/mnt/hgfs/shared'

Begin Build

These commands should all be executed in sequence from within the vmware CLI:

• sudo apt -y update

• sudo apt -y upgrade

• sudo apt -y install apache2 apache2-utils

• sudo a2enmod ssl

• sudo a2enmod rewrite

• sudo systemctl restart apache2

• sudo usermod -a -G www-data `whoami`

• sudo usermod -a -G `whoami` www-data

• Log out of the vm (CTL-D) (this is neccessary for group settings to be applied)

• Log back in

• ls /mnt/hgfs/shared

• you should see the shared folders from LSU OneDrive. if you don't see the shared folder, run this command in the vmware cli:

If bad mount point '/mnt/hgfs/' no such file or directory:

• mkdir /mnt/hgfs/
• sudo vmhgfs-fuse .host:/ /mnt/hgfs/ -o allow_other -o uid=1000

Start the build:

• execute in the vmware cli after shared folders are connected:
• sh /mnt/hgfs/shared/scratch_1.sh the above command runs a script containing the following:

#!/bin/bash
sudo apt install -y lsb-release gnupg2 ca-certificates apt-transport-https software-properties-common
sudo add-apt-repository ppa:ondrej/php
sudo add-apt-repository ppa:ondrej/apache2
sudo apt update

Install php and postgresql:

• sh /mnt/hgfs/shared/scratch_2.sh

the above command runs the following script the :

#!/bin/bash
sudo apt -y install php8.3 php8.3-cli php8.3-common php8.3-curl php8.3-dev php8.3-gd php8.3-imap php8.3-mbstring php8.3-opcache php8.3-xml php8.3-yaml php8.3-zip libapache2-mod-php8.3 php-pgsql php-redis php-xdebug unzip
sudo a2enmod php8.3
sudo systemctl restart apache2
# set default php to the version we have insalled:
sudo update-alternatives --set php /usr/bin/php8.3
#install Postgresql
sudo apt install -y postgresql-common
sudo /usr/share/postgresql-common/pgdg/apt.postgresql.org.sh
sudo apt install -y postgresql-15

Edit the postgresql.conf file starting at line 687

• sudo nano +687 /etc/postgresql/15/main/postgresql.conf

change line 687 from

#bytea_output = 'hex'

change to

bytea_output = 'escape'

• sudo systemctl restart postgresql

Setting Up PostgreSQL Database and User for Drupal 10:

create up a drupal10 database and user

• sudo -u postgres psql

from within the postgres cli change to drupal10:

create database drupal10 encoding 'UTF8' LC_COLLATE = 'en_US.UTF-8' LC_CTYPE = 'en_US.UTF-8' TEMPLATE template0;
create user drupal with encrypted password 'drupal';

Grant privileges, Enable extension,Modify database setting

• sudo -u postgres psql

\c drupal10
GRANT ALL PRIVILEGES ON DATABASE drupal10 TO drupal;
GRANT CREATE ON SCHEMA public TO drupal;
CREATE EXTENSION pg_trgm;

• Modify database setting

ALTER DATABASE drupal10
SET bytea_output = 'escape';
\q

• sudo systemctl restart postgresql
• Editing pg_hba.conf for User Authentication in PostgreSQL

cp /mnt/hgfs/shared/pg_hba.conf /etc/postgresql/15/main/

• Adds the following authentication settings for PostgreSQL users and databases on localhost. Note: Do not copy the configurations below into the pg_hba.conf file, as the indentations are incorrect.

# Database administrative login by Unix domain socket
local	  all		           all			                                  md5
#local	  DATABASE		   USER			                                  METHOD

Install Composer

• sh /mnt/hgfs/shared/scratch_3.sh

scratch_3.sh contents:

#!/bin/bash
curl "https://getcomposer.org/installer" > composer-install.php
chmod +x composer-install.php
php composer-install.php
sudo mv composer.phar /usr/local/bin/composer
sudo mkdir /opt/drupal
sudo chown www-data:www-data /opt/drupal
sudo chmod 775 /opt/drupal
sudo chown -R www-data:www-data /var/www/

Configure apache server settings:

• sudo cp /mnt/hgfs/shared/ports.conf /etc/apache2/ports.conf
• Apache virtual host configuration
  • sudo cp /mnt/hgfs/shared/000-default-v1.conf /etc/apache2/sites-enabled/000-default.conf
  • sudo cp /mnt/hgfs/shared/000-default-v1.conf /etc/apache2/sites-available/000-default.conf
• Copy command above edits the default virtual host configuration file located in /etc/apache2/sites-available/ and /etc/apache2/sites-enabled/.

<VirtualHost *:80>
ServerName localhost
DocumentRoot "/opt/drupal"
<Directory "/opt/drupal">
  Options Indexes FollowSymLinks MultiViews
  AllowOverride all
  Require all granted
</Directory>
# Ensure some logging is in place.
ErrorLog "/var/log/apache2/localhost_error.log"
CustomLog "/var/log/apache2/localhost_access.log" combined
</VirtualHost>

Now We create a Drupal virtual host configuration file using

• Copy over configuration from shared folder:

• sudo cp /mnt/hgfs/shared/drupal-v1.conf /etc/apache2/sites-available/drupal.conf

• Or paste following to /etc/apache2/sites-available/drupal.conf:

sudo nano /etc/apache2/sites-available/drupal.conf

Alias /drupal "/opt/drupal"
DocumentRoot "/opt/drupal"
<Directory /opt/drupal>
   AllowOverride All
   Require all granted
</Directory>

• Later in the installation steps, when we create an Islandora Starter Site project, we need to edit the root directory in the Apache configuration files as shown below, We will copy over 000-default.conf and drupal.conf with updated root directories

Configuring and Securing Apache for Drupal Deployment

• sudo systemctl restart apache2
• sudo a2ensite drupal
• sudo a2enmod rewrite
• sudo systemctl restart apache2
• sudo chown -R www-data:www-data /opt/drupal
• sudo chmod -R 755 /opt/drupal

Add PDO extentions for postgresql and mysql:

• sh /mnt/hgfs/shared/PDO-extensions.sh The following shell script will execute the commands below:

sudo apt-get install php8.3-mysql
sudo apt-get install php8.3-pgsql
#For mariaDB
sudo apt-get install php8.3-mysqli
sudo add-apt-repository ppa:ondrej/php
sudo add-apt-repository ppa:ondrej/apache2
sudo apt update
sudo systemctl restart apache2

Make sure postgresql and apache2 are both active:

• sudo systemctl restart postgresql apache2
• sudo systemctl status postgresql apache2

install tomcat and cantaloupe

Install JAVA 17.0.1

• Create directory for Java installation:

sudo mkdir /usr/lib/jvm
cd /usr/lib/jvm

• Download and extract the Java archive:

sudo wget -O openjdk-17.0.1.tar.gz https://download.java.net/java/GA/jdk17.0.1/2a2082e5a09d4267845be086888add4f/12/GPL/openjdk-17.0.1_linux-x64_bin.tar.gz
sudo tar -zxvf openjdk-17.0.1.tar.gz
sudo mv jdk-17.0.1 java-17.0.1-openjdk-amd64

• Set executable permissions and create a symbolic link:

sudo chmod +x /usr/lib/jvm/java-17.0.1-openjdk-amd64/bin/java
sudo ln -s /usr/lib/jvm/java-17.0.1-openjdk-amd64/bin/java /usr/bin/java

• Verify the Java installation:

java --version

• Configure alternatives to manage different Java versions:

sudo update-alternatives --install /usr/bin/java java /usr/lib/jvm/java-17.0.1-openjdk-amd64/bin/java 1
update-alternatives --list java

The output should include a line similar to: "/usr/lib/jvm/java-11-openjdk-amd64/bin/java" note this path for later use as JAVA_HOME. it is the same as the path above without "/bin/java". "/usr/lib/jvm/java-117.0.1-openjdk-amd64"- Add Java_HOME in default environment variables

• Add JAVA_HOME to Default Environment Variables:

echo 'export JAVA_HOME=/usr/lib/jvm/java-17.0.1-openjdk-amd64' >> ~/.bashrc
echo 'export PATH=$JAVA_HOME/bin:$PATH' >> ~/.bashrc
source ~/.bashrc

Install Tomcat:

• create tomcat user:

• sudo addgroup tomcat

• sudo adduser tomcat --ingroup tomcat --home /opt/tomcat --shell /usr/bin choose a password ie: password: "tomcat" press enter for all default user prompts type y for yes

• install tomcat

• find the tar.gz here: https://tomcat.apache.org/download-90.cgi

• sh /mnt/hgfs/shared/scratch_4.sh

The following shell script will execute the commands below:

#!/bin/bash
cd /opt
#O not 0
sudo mkdir tomcat
sudo wget -O tomcat.tar.gz https://dlcdn.apache.org/tomcat/tomcat-9/v9.0.89/bin/apache-tomcat-9.0.89.tar.gz
sudo tar -zxvf tomcat.tar.gz
sudo mv /opt/apache-tomcat-9.0.89/* /opt/tomcat
sudo chown -R tomcat:tomcat /opt/tomcat

• Make sure to change the tomcat version in scrathc_4 in sudo mv /opt/apache-tomcat-9.0.89/* /opt/tomcat

scratch_5.sh (if the tomcat tarball link is different you must change the path in the script or run the commands in the scratch_5 alt section):

• sh /mnt/hgfs/shared/scratch_5.sh

• Copy environment variables that includes java home to tomcat/bin

//Make sure version of openjdk java is correct in JAVA_HOME:
sudo cp /mnt/hgfs/shared/setenv.sh /opt/tomcat/bin/
sudo chmod 755 /opt/tomcat/bin/setenv.sh
sudo cp /mnt/hgfs/shared/tomcat.service /etc/systemd/system/tomcat.service
sudo chmod 755 /etc/systemd/system/tomcat.service
sudo systemctl start tomcat
sudo systemctl enable tomcat
sudo systemctl status tomcat

Cantatloupe:

Install Cantaloupe 5.0.6

• sh /mnt/hgfs/shared/scratch_6.sh

• scratch_6.sh will perform bellow tasks:

  • install and unzip cantaloupe 5.0.6
  • copy the configurations into cantaloupe_config
  • Copy cantaloupe service syetem directory
  • Enables Cantaloupe

sudo wget -O /opt/cantaloupe.zip https://github.com/cantaloupe-project/cantaloupe/releases/download/v5.0.6/cantaloupe-5.0.6.zip
sudo unzip /opt/cantaloupe.zip
sudo mkdir /opt/cantaloupe_config

copy the configurations into cantaloupe_config

• sudo cp cantaloupe-5.0.6/cantaloupe.properties.sample /opt/cantaloupe_config/cantaloupe.properties
• sudo cp cantaloupe-5.0.6/delegates.rb.sample /opt/cantaloupe_config/delegates.rb

Copy cantaloupe service syetem directory, check the version of your cantaloup in cantaloupe.service

sudo cp /mnt/hgfs/shared/cantaloupe.service /etc/systemd/system/cantaloupe.service
sudo chmod 755 /etc/systemd/system/cantaloupe.service

Enable Cantaloupe

sudo systemctl enable cantaloupe
sudo systemctl start cantaloupe
sudo systemctl daemon-reload

• Configure Cantaloupe URL(Important)

sudo nano /opt/cantaloupe_config/cantaloupe.properties
base_uri = http://127.0.0.1:8182/iiif/2

• Restart and Check the status

sudo systemctl restart cantaloupe
sudo systemctl status cantaloupe

Installing fedora

• stop tomcat and create fcrepo directy

• sudo systemctl stop tomcat

• sudo mkdir -p /opt/fcrepo/data/objects

• sudo mkdir /opt/fcrepo/config

• sudo chown -R tomcat:tomcat /opt/fcrepo

• sudo -u postgres psql

• Create fcrepo database, user, password in postgresql or maridb: sudo -u postgres psql

create database fcrepo encoding 'UTF8' LC_COLLATE = 'en_US.UTF-8' LC_CTYPE = 'en_US.UTF-8' TEMPLATE template0;
create user fedora with encrypted password 'fedora';
\c fcrepo
grant all privileges on database fcrepo to fedora;
GRANT CREATE ON SCHEMA public TO fedora;
\q

• Adding fedora configurations:
• sudo sh /mnt/hgfs/shared/fedora-config.sh

fedora-config.sh contains:

#!/bin/bash
sudo cp /mnt/hgfs/shared/i8_namespaces.yml /opt/fcrepo/config/
sudo chown tomcat:tomcat /opt/fcrepo/config/i8_namespaces.yml
sudo chmod 644 /opt/fcrepo/config/i8_namespaces.yml

sudo cp /mnt/hgfs/shared/allowed_external_hosts.txt /opt/fcrepo/config/
sudo chown tomcat:tomcat /opt/fcrepo/config/allowed_external_hosts.txt
sudo chmod 644 /opt/fcrepo/config/allowed_external_hosts.txt

#fcrepo.properties - It's configured according to our needs:
sudo cp /mnt/hgfs/shared/fcrepo.properties /opt/fcrepo/config/
sudo chown tomcat:tomcat /opt/fcrepo/config/fcrepo.properties
sudo chmod 640 /opt/fcrepo/config/fcrepo.properties

#From our old build instructions
sudo cp /mnt/hgfs/shared/repository.json /opt/fcrepo/config/repository.json
sudo chown tomcat:tomcat /opt/fcrepo/config/repository.json
sudo chmod 644 /opt/fcrepo/config/repository.json

Adding the Fedora Variables to JAVA_OPTS, change setenv:

• sudo nano /opt/tomcat/bin/setenv.sh

• uncomment line 5, comment line 4 (CTL-c) shows line number

• sudo chown tomcat:tomcat /opt/tomcat/bin/setenv.sh

Edit and Ensuring Tomcat Users Are In Place

• cp /mnt/hgfs/shared/tomcat-users.xml /opt/tomcat/conf/

• Copied tomcat-users.xml file will update following to tomcat-users.xml:

• sudo nano /opt/tomcat/conf/tomcat-users.xml

 <role rolename="tomcat"/>
 <role rolename="fedoraAdmin"/>
 <role rolename="fedoraUser"/>
 <user username="tomcat" password="TOMCAT_PASSWORD" roles="tomcat"/>
 <user username="fedoraAdmin" password="FEDORA_ADMIN_PASSWORD" roles="fedoraAdmin"/>
 <user username="fedoraUser" password="FEDORA_USER_PASSWORD" roles="fedoraUser"/>

tomcat users permissions:

• 1- postgres privileges: We have given correct postgres privileges to fedora user in fcrepo database

• 2- tomcat-users permission:

sudo chmod 600 /opt/tomcat/conf/tomcat-users.xml
sudo chown tomcat:tomcat /opt/tomcat/conf/tomcat-users.xml

download fedora Latest Release:

• NOTE: You may want to check visit: https://github.com/fcrepo/fcrepo/releases choose the latest version and ajust the commands below if needed
• sh /mnt/hgfs/shared/fedora-dl.sh

The following shell script will execute the commands below to download fedora war file and will place it to catalina webapp directory:

#!/bin/bash
sudo wget -O fcrepo.war https://github.com/fcrepo/fcrepo/releases/download/fcrepo-6.5.0/fcrepo-webapp-6.5.0.war
sudo mv fcrepo.war /opt/tomcat/webapps
sudo chown tomcat:tomcat /opt/tomcat/webapps/fcrepo.war

Enable fedora endpoint:

• Start the server:

  • /opt/tomcat/bin/startup.sh

• Restart tomcat:

  • sudo systemctl start tomcat

Navigate to Fedora endpoint:

• Once tomcat starts up, Fedora REST API should be available at http://localhost:8080/fcrepo/rest.
• The username is fedoraAdmin and we defined the password before as FEDORA_ADMIN_PASSWORD (We set: "islandora").

Syn:

Download syn:

check here for link: https://github.com/Islandora/Syn/releases/ copy the link (if changed from syn-1.1.1) and replace the link in the command below:

• run the command:
• sh /mnt/hgfs/shared/syn-dl.sh

#!/bin/bash
sudo wget -P /opt/tomcat/lib https://github.com/Islandora/Syn/releases/download/v1.1.1/islandora-syn-1.1.1-all.jar
sudo chown -R tomcat:tomcat /opt/tomcat/lib
sudo chmod -R 640 /opt/tomcat/lib

Generating an SSL Key for Syn and Placing the Syn Settings:

• sudo sh /mnt/hgfs/shared/syn-config.sh
• The following shell script will execute the commands below:

#!/bin/bash
sudo mkdir /opt/keys
sudo openssl genrsa -out "/opt/keys/syn_private.key" 2048
sudo openssl rsa -pubout -in "/opt/keys/syn_private.key" -out "/opt/keys/syn_public.key"
sudo chown www-data:www-data /opt/keys/syn*
sudo mkdir /opt/syn
sudo cp /mnt/hgfs/shared/syn-settings.xml /opt/fcrepo/config/
sudo chown tomcat:tomcat /opt/fcrepo/config/syn-settings.xml
sudo chmod 600 /opt/fcrepo/config/syn-settings.xml

Adding the Syn Valve to Tomcat | Enable the Syn Valve for all of Tomcat:

• sudo nano /opt/tomcat/conf/context.xml

• Then add this line before the closing Context ():

   <Valve className="ca.islandora.syn.valve.SynValve" pathname="/opt/fcrepo/config/syn-settings.xml"/>

• sudo systemctl restart tomcat

Redhat logging:

sudo cp /mnt/hgfs/shared/fcrepo-logback.xml /opt/fcrepo/config/
sudo chmod 644 /opt/fcrepo/config/fcrepo-logback.xml
sudo chown tomcat:tomcat /opt/fcrepo/config/fcrepo-logback.xml

• Then alter your $JAVA_OPTS like above to include:

  • Before: export JAVA_OPTS="-Djava.awt.headless=true -Dfcrepo.config.file=/opt/fcrepo/config/fcrepo.properties -DconnectionTimeout=-1 -server -Xmx1500m -Xms1000m"
  • After: export JAVA_OPTS="-Djava.awt.headless=true -Dfcrepo.config.file=/opt/fcrepo/config/fcrepo.properties -Dlogback.configurationFile=/opt/fcrepo/config/fcrepo-logback.xml -DconnectionTimeout=-1 -server -Xmx1500m -Xms1000m"

• sudo nano /opt/tomcat/bin/setenv.sh

• Comment line 5 and uncomment line 6

installing blazegraph

Creating a Working Space for Blazegraph and install Blazegraph:

• sh /mnt/hgfs/shared/blazegraph-dl.sh

sudo mkdir -p /opt/blazegraph/data
sudo mkdir /opt/blazegraph/conf
sudo chown -R tomcat:tomcat /opt/blazegraph
cd /opt
sudo wget -O blazegraph.war https://repo1.maven.org/maven2/com/blazegraph/bigdata-war/2.1.5/bigdata-war-2.1.5.war
sudo mv blazegraph.war /opt/tomcat/webapps
sudo chown tomcat:tomcat /opt/tomcat/webapps/blazegraph.war

Configuring Logging and Adding Blazegraph Configurations:

• sh /mnt/hgfs/shared/blazegraph_conf.sh The following shell script will execute the commands below:

#!/bin/bash
#Configuring Logging
sudo cp /mnt/hgfs/shared/log4j.properties /opt/blazegraph/conf/
sudo chown tomcat:tomcat /opt/blazegraph/conf/log4j.properties
sudo chmod 644 /opt/blazegraph/conf/log4j.properties
#Adding a Blazegraph Configuration
sudo cp /mnt/hgfs/shared/RWStore.properties /opt/blazegraph/conf
sudo chown tomcat:tomcat /opt/blazegraph/conf/RWStore.properties
sudo chmod 644 /opt/blazegraph/conf/RWStore.properties
sudo cp /mnt/hgfs/shared/blazegraph.properties /opt/blazegraph/conf
sudo chown tomcat:tomcat /opt/blazegraph/conf/blazegraph.properties
sudo chmod 644 /opt/blazegraph/conf/blazegraph.properties
sudo cp /mnt/hgfs/shared/inference.nt /opt/blazegraph/conf
sudo chown tomcat:tomcat /opt/blazegraph/conf/inference.nt
sudo chmod 644 /opt/blazegraph/conf/inference.nt
sudo chown -R tomcat:tomcat /opt/blazegraph/conf
sudo chmod -R 644 /opt/blazegraph/conf

Specifying the RWStore.properties in JAVA_OPTS:

• sudo nano /opt/tomcat/bin/setenv.sh Comment line 6 and uncomment line 7:

• Before: export JAVA_OPTS="-Djava.awt.headless=true -Dfcrepo.config.file=/opt/fcrepo/config/fcrepo.properties -DconnectionTimeout=-1 -server -Xmx1500m -Xms1000m"

• After: export JAVA_OPTS="-Djava.awt.headless=true -Dfcrepo.config.file=/opt/fcrepo/config/fcrepo.properties -Dlogback.configurationFile=/opt/fcrepo/config/fcrepo-logback.xml -DconnectionTimeout=-1 Dcom.bigdata.rdf.sail.webapp.ConfigParams.propertyFile=/opt/blazegraph/conf/RWStore.properties -Dlog4j.configuration=file:/opt/blazegraph/conf/log4j.properties -server -Xmx1500m -Xms1000m"

• Comment line 6 and uncomment line 7

• sudo systemctl restart tomcat

Installing Blazegraph Namespaces and Inference:

• sudo curl -X POST -H "Content-Type: text/plain" --data-binary @/opt/blazegraph/conf/blazegraph.properties http://localhost:8080/blazegraph/namespace

If this worked correctly, Blazegraph should respond with "CREATED: islandora" to let us know it created the islandora namespace.

• sudo curl -X POST -H "Content-Type: text/plain" --data-binary @/opt/blazegraph/conf/inference.nt http://localhost:8080/blazegraph/namespace/islandora/sparql

If this worked correctly, Blazegraph should respond with some XML letting us know it added the 2 entries from inference.nt to the namespace.

installing solr

Check JAVA_HOME:

• sudo nano ~/.bashrc

export JAVA_HOME=/usr/lib/jvm/java-17.0.1-openjdk-amd64
export PATH=$JAVA_HOME/bin:$PATH

• source ~/.bashrc

download 9.x solr:

sh /mnt/hgfs/shared/solr-dl.sh

cd /opt
sudo wget https://www.apache.org/dyn/closer.lua/solr/solr/9.6.0/solr-9.6.0.tgz?action=download
sudo mv solr-9.6.0.tgz?action=download solr-9.6.0.tgz
sudo tar xzf solr-9.6.0.tgz solr-9.6.0/bin/install_solr_service.sh --strip-components=2

Install Solr:

run following as root to extract and install solr:

• sudo bash ./install_solr_service.sh solr-9.6.0.tgz -i /opt -d /var/solr -u solr -s solr -p 8983

Runnig the above command will do the following:

• extracted solr-9.6.0 to /opt
• symlink /opt.solr -> /opt/solr-9.6.0
• installed /etc/init.d/solr script
• installed /etc/default/solr.in.sh
• service solr installed

to customize solr startup configuration go to this directory /etc/default/solr.in.sh:

• SOLR_PID_DIR="/var/solr"
• SOLR_HOME="/var/solr/data"
• LOG4J_PROPS="/var/solr/log4j2.xml"
• SOLR_LOGS_DIR="/var/solr/logs"
• SOLR_PORT="8983"

Adjust Kernel Parameters:

• sudo su
• sudo echo "fs.file-max = 65535" >> /etc/sysctl.conf
• sudo sysctl -p

make sure solr is running:

• sudo systemctl status solr

• If it was not running:

  • cd /opt/solr-9.6.0
  • bin/solr start

• sudo systemctl status solr

Create Solr Core

• sudo mkdir -p /var/solr/data/islandora8
• sudo mkdir -p /var/solr/data/islandora8/conf
• cp /mnt/hgfs/shared/solr_9.x_config/* /var/solr/data/islandora8/conf/
• sudo chown -R solr:solr /var/solr
• cd /opt/solr-9.6.0
• sudo -u solr bin/solr create -c islandora8 -p 8983

We will configure index via gui after site installed

Crayfish microservices

Adding this PPA to your system:

• sudo add-apt-repository -y ppa:lyrasis/imagemagick-jp2

• sudo apt-get update

• sudo apt-get -y install imagemagick tesseract-ocr ffmpeg poppler-utils

• NOTE If you get the sudo: apt-add-repository: command not found, run sudo apt-get install software-properties-common in order to make the command available.

Cloning and Installing Crayfish:

• sh /mnt/hgfs/shared/crayfish_reqs.sh

It's running the following:

cd /opt
sudo git clone https://github.com/Islandora/Crayfish.git crayfish
sudo chown -R www-data:www-data crayfish
sudo -u www-data composer install -d crayfish/Homarus
sudo -u www-data composer install -d crayfish/Houdini
sudo -u www-data composer install -d crayfish/Hypercube
sudo -u www-data composer install -d crayfish/Milliner
sudo -u www-data composer install -d crayfish/Recast

Preparing Logging:

• sudo mkdir /var/log/islandora
• sudo chown www-data:www-data /var/log/islandora

moving config files over:

• sh /mnt/hgfs/shared/microservices-config.sh

Folowing command will move Crayfish Microservices Config files and Apache Config files over.

#!/bin/bash
#Homarus Configs
#sudo rm -r /opt/crayfish/Homarus/cfg
sudo mkdir /opt/crayfish/Homarus/cfg
sudo cp /mnt/hgfs/shared/homarus.config.yaml /opt/crayfish/Homarus/cfg/config.yaml

#houdini Configs
sudo cp /mnt/hgfs/shared/houdini.services.yaml /opt/crayfish/Houdini/config/services.yaml
sudo cp /mnt/hgfs/shared/crayfish_commons.yml /opt/crayfish/Houdini/config/packages/crayfish_commons.yml
sudo cp /mnt/hgfs/shared/monolog.yml /opt/crayfish/Houdini/config/packages/monolog.yml
sudo cp /mnt/hgfs/shared/security.yml /opt/crayfish/Houdini/config/packages/security.yml
#Hypercube Configs

sudo mkdir /opt/crayfish/Hypercube/cfg
sudo cp /mnt/hgfs/shared/hypercube.config.yaml /opt/crayfish/Hypercube/cfg/config.yaml

#Milliner Configs
sudo mkdir /opt/crayfish/Milliner/cfg/
sudo cp /mnt/hgfs/shared/milliner.config.yaml /opt/crayfish/Milliner/cfg/config.yaml

#Recast Configs
sudo mkdir /opt/crayfish/Recast/cfg
sudo cp /mnt/hgfs/shared/recast.config.yaml /opt/crayfish/Recast/cfg/config.yaml

#Permissions
sudo chown www-data:www-data /opt/crayfish/Homarus/cfg/config.yaml
sudo chmod 644 /opt/crayfish/Homarus/cfg/config.yaml
sudo chown www-data:www-data /opt/crayfish/Houdini/config/services.yaml
sudo chmod 644 /opt/crayfish/Houdini/config/services.yaml
sudo chown www-data:www-data /opt/crayfish/Houdini/config/packages/crayfish_commons.yml
sudo chmod 644 /opt/crayfish/Houdini/config/packages/crayfish_commons.yml
sudo chown www-data:www-data /opt/crayfish/Houdini/config/packages/monolog.yml
sudo chmod 644 /opt/crayfish/Houdini/config/packages/monolog.yml
sudo chown www-data:www-data /opt/crayfish/Houdini/config/packages/security.yml
sudo chmod 644 /opt/crayfish/Houdini/config/packages/security.yml
sudo chown www-data:www-data /opt/crayfish/Hypercube/cfg/config.yaml
sudo chmod 644 /opt/crayfish/Hypercube/cfg/config.yaml
sudo chown www-data:www-data /opt/crayfish/Recast/cfg/config.yaml
sudo chmod 644 /opt/crayfish/Recast/cfg/config.yaml
sudo chown www-data:www-data /opt/crayfish/Milliner/cfg/config.yaml
sudo chmod 644 /opt/crayfish/Milliner/cfg/config.yaml

• sudo systemctl reload apache2

ActiveMQ/Alpaca:

1. ActiveMQ:

The latest ActiveMQ manual installation:

cd /usr/share/
sudo wget https://archive.apache.org/dist/activemq/6.1.2/apache-activemq-6.1.2-bin.zip
sudo unzip apache-activemq-6.1.2-bin.zip
sudo mv apache-activemq-6.1.2 activemq

• Create directories:

sudo mkdir -p /var/lib/activemq
sudo mkdir -p /var/lib/activemq/conf

Create an ActiveMQ System User and Set Permissions:

cd /usr/share/activemq
sudo useradd -r activemq -d /var/lib/activemq -s /sbin/nologin
sudo chown -R activemq:activemq /var/lib/activemq
sudo chown -R activemq:activemq /usr/share/activemq

Set Up Service:

• sudo cp /mnt/hgfs/shared/activemq.service /etc/systemd/system/activemq.service
• reload systemd to recognize the new service sudo systemctl daemon-reload

Enable an start Service:

sudo systemctl enable activemq
sudo systemctl start activemq
sudo systemctl status activemq

Set manual ActiveMQ as default ActiveMQ:

add activemq bin directory to default environment variable:

sudo nano ~/.bashrc
export PATH=$PATH:/usr/share/activemq/bin
source ~/.bashrc

Create a symbolic link For ActiveMQ:

• sudo ln -s /usr/share/activemq/bin/activemq /usr/local/bin/activemq
• Check ActiveMQ Version to make sure it is installed and system can find the right service version:
• activemq --version

ActiveMQ ConfigurationL(Important)

ActiveMQ expected to be listening for STOMP messages at a tcp url. If not the default tcp://127.0.0.1:61613, this will have to be set:

• sudo nano /usr/share/activemq/conf/activemq.xml
• Inside the element, find the configuration for the STOMP transport connector and change the stomp url from 0.0.0.0 to 127.0.0.1:61613
• Keep the port and the rest.
• name="stomp" uri="stomp://127.0.0.1:61613"
  • 61623 is fcrepo dynamic stomp port we configured in fcrepo.properties

Note for Karaf:

Karaf is not been used to install latest Alpaca Microservices any more, We will install alpaca with a jar file in the following steps.

2. Alpaca:

Alpaca importance in islandora ecosystem:

• Alpaca integrates and manages various microservices in an Islandora installation, handling content indexing, derivative generation, message routing from Drupal, service integration with repositories and endpoints, and configuration management for seamless system functionality.

• Java middleware that handle communication between various components of Islandora.

• In more detail, Alpaca will connect to the ActiveMQ broker, handle HTTP requests, index content in Fedora and Triplestore, and generate derivatives using FITS, Homarus, Houdini, and OCR services based on the queues and URLs specified in the configuration file.

download alpaca.jar:

• Make a directory for Alpaca and download the latest version of Alpaca from the Maven repository. E.g.

mkdir /opt/alpaca
cd /opt/alpaca
curl -L https://repo1.maven.org/maven2/ca/islandora/alpaca/islandora-alpaca-app/2.2.0/islandora-alpaca-app-2.2.0-all.jar -o alpaca.jar

Copy alpaca.properties:

• Alpaca is made up of several services, each of these can be enabled or disabled individually.

• Next, we need to copy over the configuration file containing the necessary flags so Alpaca knows how to connect to all required services. This configuration file is named alpaca.properties and should be executed using the following command:

  • cp /mnt/hgfs/shared/alpaca.properties /opt/alpaca/

• Look at the example.properties file to see some example settings.

configuration:

• Common options:

# Common options
error.maxRedeliveries=4

• ActiveMQ options:
  • This defines the url to the ActiveMQ broker which you installed earlier.

# ActiveMQ options
jms.brokerUrl=tcp://localhost:61616

• This defines the login credentials (if required)

activemq.username=system
activemq.password=manager

• This defines how many messages to process simultaneously.

jms.connections=10

• Fedora indexer options:

This service manages a Drupal node into a corresponding Fedora resource.

• Bellow defines whether the Fedora indexer is enabled or not.

# Fcrepo indexer options
fcrepo.indexer.enabled=true

• These define the various queues to listen on for the indexing/deletion messages. The part after queue: should match your Islandora instance "Actions".

fcrepo.indexer.node=queue:islandora-indexing-fcrepo-content
fcrepo.indexer.delete=queue:islandora-indexing-fcrepo-delete
fcrepo.indexer.media=queue:islandora-indexing-fcrepo-media
fcrepo.indexer.external=queue:islandora-indexing-fcrepo-file-external

• This defines the location of your Milliner microservice.

fcrepo.indexer.milliner.baseUrl=http://localhost:8000/milliner

• These define the default number of concurrent consumers and maximum number of concurrent consumers working off your ActiveMQ instance. A value of -1 means no setting is applied.

fcrepo.indexer.concurrent-consumers=1
fcrepo.indexer.max-concurrent-consumers=1

• This property allows the concurrent consumers to process concurrently; otherwise, the consumers will wait to the previous message has been processed before executing.

fcrepo.indexer.async-consumer=true

• Triplestore indexer options: This service indexes the Drupal node into the configured triplestore

  • This defines whether the Triplestore indexer is enabled or not.

# Triplestore indexer options
triplestore.indexer.enabled=false

• These define the various queues to listen on for the indexing/deletion messages. The part after queue: should match your Islandora instance "Actions".

triplestore.index.stream=queue:islandora-indexing-triplestore-index
triplestore.delete.stream=queue:islandora-indexing-triplestore-delete

• This defines the location of your triplestore's SPARQL update endpoint.

triplestore.baseUrl=http://localhost:8080/blazegraph/namespace/islandora/sparql

• These define the default number of concurrent consumers and maximum number of concurrent consumers working off your ActiveMQ instance. A value of -1 means no setting is applied.

triplestore.indexer.concurrent-consumers=1
triplestore.indexer.max-concurrent-consumers=1

• This property allows the concurrent consumers to process concurrently; otherwise, the consumers will wait to the previous message has been processed before executing.

triplestore.indexer.async-consumer=true

• Derivative services(islandora-connector-derivative): This service is used to configure an external microservice. This service will deploy multiple copies of its routes with different configured inputs and outputs based on properties.

The routes to be configured are defined with the property derivative.systems.installed which expects a comma separated list. Each item in the list defines a new route and must also define 3 additional properties.

• This defines if the item service is enabled.

derivative.<item>.enabled=true

• This is the input queue for the derivative microservice. The part after queue: should match your Islandora instance "Actions".

derivative.<item>.in.stream=queue:islandora-item-connector.index

• This is the microservice URL to process the request.

derivative.<item>.service.url=http://example.org/derivative/convert

• These define the default number of concurrent consumers and maximum number of concurrent consumers working off your ActiveMQ instance. A value of -1 means no setting is applied.

derivative.<item>.concurrent-consumers=1
derivative.<item>.max-concurrent-consumers=1

• This property allows the concurrent consumers to process concurrently; otherwise, the consumers will wait to the previous message has been processed before executing.

derivative.<item>.async-consumer=true

• Customizing HTTP client timeouts: You can alter the HTTP client from the defaults for its request, connection and socket timeouts.
  • To do this you want to enable the request configurer.

request.configurer.enabled=true

• Then set the next 3 timeouts (measured in milliseconds) to the desired timeout. The default for all three is -1 which indicates no timeout.

request.timeout=-1
connection.timeout=-1
socket.timeout=-1

• Alter HTTP options: By default, Alpaca uses two settings for the HTTP component, these are * disableStreamCache=true * connectionClose=true

If you want to send additional configuration parameters or alter the existing defaults. You can add them as a comma separated list of key=value pairs.For example:

http.additional_options=authMethod=Basic,authUsername=Jim,authPassword=1234

These will be added to ALL http endpoint requests.

• Note: We are currently running Camel 3.7.6, some configuration parameters on the above linked page might not be supported.

Run Alpaca using configurations:

• java -jar alpaca.jar -c /opt/alpaca/alpaca.properties

Create alpaca.service to use syustemd:

sudo nano /etc/systemd/system/alpaca.service

[Unit]
Description=Alpaca service
After=network.target

[Service]
Type=forking
ExecStart=java -jar /opt/alpaca/alpaca.jar -c /opt/alpaca/alpaca.properties
ExecStop=/bin/kill -15 $MAINPID
SuccessExitStatus=143
Restart=always

[Install]
WantedBy=default.target

Alpaca will perform the following tasks:

• Connect to ActiveMQ:

  • Broker URL: tcp://localhost:61616
  • Maximum Redeliveries: 5
  • Number of connections: 10

• Handle HTTP Requests:

  • Custom HTTP client options with specific timeouts (all set to -1, meaning no timeout).

• Fedora Indexing:

  • Enable Fedora indexer.
  • Connect to queues for content, delete, media, and external file indexing.
  • Base URL for the Milliner service: http://127.0.0.1:8000/milliner/

• Triplestore Indexing:

  • Enable Triplestore indexer.
  • Base URL for Triplestore: http://127.0.0.1:8080/bigdata/namespace/kb/sparql
  • Connect to queues for indexing and deleting data.

• Generate Derivatives:

  • Enable and configure FITS, Homarus, Houdini, and OCR services for generating derivatives.
  • Each service connects to its respective queue and service URL.
  • Example: FITS service URL is http://localhost:8000/crayfits

• Concurrent Consumers:

  • Configure concurrent consumer settings for various indexers and derivative services (all set to -1, meaning default values will be used).

Extra notes:

• Configuration:

  • If we are installing everything on the same server, the provided example properties should be fine as-is. Simply rename the file to alpaca.properties and run the command mentioned above.

  • If Alpaca is running on a different machine, we will just need to update the URLs in the configuration file to point to the correct host for the various services.

• Alpaca Activity: We won't see much activity from Alpaca until our ActiveMQ is populated with messages from Drupal, such as requests to index content or generate derivatives.

Download and Scaffold Drupal, Create a project using the Islandora Starter Site:

install php-intl 8.3:

sudo apt-get install php8.3-intl

create islandora starter site project

• cd /opt/drupal
• sudo composer create-project islandora/islandora-starter-site:1.8.0
• cd /opt/drupal/islandora-starter-site

Install drush using composer at islandora-starter-site

• sudo chown -R www-data:www-data /opt/drupal/islandora-starter-site
• sudo chmod 777 -R /opt/drupal/islandora-starter-site
• sudo -u www-data composer require drush/drush
• sudo ln -s /opt/drupal/islandora-starter-site/vendor/bin/drush /usr/local/bin/drush
• ls -lart /usr/local/bin/drush

Configure Settings.php and add Flysystem's fedora and trusted host:

sudo nano web/sites/default/settings.php

$settings['trusted_host_patterns'] = [
 'localhost',
 'YOUR_IP_ADDRESS',
];

$settings['flysystem'] = [
 'fedora' => [
   'driver' => 'fedora',
   'config' => [
     'root' => 'http://127.0.0.1:8080/fcrepo/rest/',
   ],
 ],
];

Re-configure Apache root directories:

1. Re-configure drupal.conf:

• sudo cp /mnt/hgfs/shared/drupal.conf /etc/apache2/sites-enabled/drupal.conf

• Bellow is the lines that Changed in drupal.conf Apache configuration:

Alias /drupal "/opt/drupal/islandora-starter-site/web"
DocumentRoot "/opt/drupal/islandora-starter-site/web"
<Directory /opt/drupal/islandora-starter-site>

2. Re-configure 000-default.conf:

• sudo cp /mnt/hgfs/shared/000-default.conf /etc/apache2/sites-enabled/000-default.conf

• sudo cp /mnt/hgfs/shared/000-default.conf /etc/apache2/sites-available/000-default.conf

• Bellow is the lines that Changed in 000-default.conf Apache configuration:

DocumentRoot "/opt/drupal/islandora-starter-site/web"
<Directory "/opt/drupal/islandora-starter-site/web">

Then restart apache:

• sudo systemctl restart apache2

change permission on the web directory:

• sudo chown -R www-data:www-data /opt/drupal/islandora-starter-site/web
• sudo chmod -R 755 /opt/drupal/islandora-starter-site/web

Again, make sure you have already done followings:

• You should have granted all privileges to the user Drupal when created the table and databases before site install so that these are all permissions on user to create tables on database.
• You should have installed PDO extention before site install.

Install the site using composer or drush:

• 1. install using Composer:

  • sudo composer exec -- drush site:install --existing-config

• 2. Install with Drush:

  • sudo -u www-data drush site-install --existing-config --db-url="pgsql://drupal:drupal@127.0.0.1:5432/drupal10"

Change default username and password:

• sudo drush upwd admin admin

Add a user to the fedoraadmin role:(Optional)

for example, giving the default admin user the role:

1. Using Composer:

• cd /opt/drupal/islandora-starter-site
• composer exec -- drush user:role:add fedoraadmin admin

2. Using Drush:**

• cd /opt/drupal/islandora-starter-site
• sudo -u www-data drush -y urol "fedoraadmin" admin

Configure the locations of external services:

Some, we already configured in prerequsits, but we will make sure all the configurations are in place.

Check following configurations before moving forward:

• check if your services like cantaloupe, apache, tomcat, databases are available and working
• check if you have already configured the cantaloup IIIF base URL to http://127.0.0.1:8182/iiif/2
• check if you have already configured activemq.xml in name="stomp" uri="stomp://127.0.0.1:61613"

solr search_api installation and fiele size:

• sudo -u www-data composer require drupal/search_api_solr

Configurations:

1. Configure Cantaloupe OpenSeaDragon:

• In GUI:

• Navigate to http://[your-site-ip-address]/admin/config/media/openseadragon

• set location of the cantaloupe iiif endpoint to http://localhost:8182/iiif/2

• select IIIF Manifest from dropdown

• save

• In settings.php:

  • $settings['openseadragon.settings']['iiif_server'] = 'http://127.0.0.1:8182/iiif/2';

Configure Cantaloupe for Islandora IIIF:

• In GUI:
  • /admin/config/islandora/iiif
  • set location of the cantaloupe: http://127.0.0.1:8182/iiif/2
• In settings.php:
  • $settings['islandora_iiif.settings']['iiif_server'] = 'http://127.0.0.1:8182/iiif/2';

Configure ActiveMQ, islandora message broker sertting url:

• In GUI:

  • /admin/config/islandora/core
  • set brocker URL to tcp://127.0.0.1:61613

• In settings.php:

  • $settings['islandora.settings']['broker_url'] = 'tcp://127.0.0.1:61613';

• If activeMQ was not active check activemq.service:

  • sudo netstat -tuln | grep LISTEN
  • Check if 61613 is active and being listed to

Configure solr:

• Check for bellow configuration:

  • Check solr is availabe at port 8983: sudo netstat -tuln | grep LISTEN
  • Check solr is running if not run: sudo /opt/solr/bin/start
  • Then restart: sudo systemctl restart solr
  • Check if your solr core is installed!

• In GUI: Navigate to admin/config/search/search-api edit the existing server or create one:

  • backend: Solr
  • Solr Connector: Standard
  • Solr core: islandora8

• In settings.php:

  • Set search_api.server.default_solr_server backend_config.connector_config.host

    • $settings['search_api.server.default_solr_server']['backend_config']['connector_config']['host'] = '127.0.0.1';

  • Solr port: Set search_api.server.default_solr_server backend_config.connector_config.port

    • $settings['search_api.server.default_solr_server']['backend_config']['connector_config']['port'] = '8983';

  • Solr, core name: Set search_api.server.default_solr_server backend_config.connector_config.core

    • $settings['search_api.server.default_solr_server']['backend_config']['connector_config']['core'] = 'islandora8';

Check syn/jwt configuration

keys must be available at /opt/keys/syn_private.key

• Symlinking the private key to /opt/drupal/keys/private.key

  • sudo ln -s /opt/keys/syn_private.key /usr/local/bin/drush

• In GUI:

  • First, Navigate to /admin/config/system/keys/add
    • key type: JWT RSA KEy
    • JWT Algorithm: RSAASA-PKCXS1-v1_5 Using SHA-256(RS256)
    • Key Provider: file
    • File location: /opt/keys/syn_private.key
    • Save

• Then, Navigate to /admin/config/system/jwt

  • Select the key you justy created
  • Save configuration

Select default Flysystem:

visit /admin/config/media/file-system to select the flysystem from the dropdown.

Run the migrations command and Enabling EVA Views:

run the migration tagged with islandora to populate some taxonomies.

Run the migrations taged with islandora:

• cd /opt/drupal/islandora-starter-site
• composer exec -- drush migrate:import --userid=1 --tag=islandora

Enabling EVA Views:

• drush -y views:enable display_media

instrall group modules and dependencies:

• cd /opt/drupal/islandora-starter-site
• sudo -u www-data composer require digitalutsc/islandora_group
• sudo -u www-data composer require 'drupal/rules:^3.0@alpha'
• drush en -y islandora_group gnode rules

Rebuild Cache:

• drush cr

Group Configuration:

group type:

• Navigate to Groups -> create a group type

Groups role and group role permissions:

• Create specific roles:

  • Navigate to Groups>Grope Type> edit group role of created Group Type >

  • For administratiopn access we create roles for admin, and ensure each role has the appropriate admin permissions:

    • Admin individual with administration roles
    • Admin Outsider
    • Admin Insider

  • You can also create different roles for members, content creators, or other specific roles, and assign these roles to specific users.

• Assign role to the user:

  • In Drupal, navigate to Admin > People to manage user roles:

    • Assign the administrator role to your user.

    • You can also assign users as content creators for specific group types. This way, they will only have access to the group types and groups they are assigned to, and will not have access to other group types or groups within those types.

Assign islandora access To the group type we created:

• Navigate to configuration -> access controll -> select islandora_access for <GroupTypeName>

Create Group:

• Mavigate to Groups> Create Groups

Create field access terms for Repository Item Content type:

• Navigate to structure -> content types -> repository item -> manage fields -> create a access terms (name = access_terms) -> type is Reference -> Reference type: Taxonomy term, Vocabulary: Islandora Access

Create field access terms for each Media types :

• Navigate to structure -> mediatypes -> edit one of the media types -> edit -> manage fields -> create a field -> create a access terms field (name = access_terms) -> type is Reference -> Reference type = Islandora Access

  • Example: We craete field access terms for audio and machine name in list of fields is field_access_terms

• For each media type, we need to have field access terms. After creating field_access_terms for one media type (ex: audio) this can be re-used for other media types.

  • Example: After creating field_access_terms for one of the

Select islandora access for each nodes and media:

• Navigate to configuration -> access controll -> islandora access

• Select islandora_access for the repository items content type and all media types.

• Select islandora_access for the each media types.

set available content in group type:

• navigate to groups>group type> set avaialble content
• install each content one by one

Fix the destination for each media type (Important for media ingestion for each media types):

• Navigate Structure>Media types

• For each media type, edit the field where the type is file and set the Upload destination to Public files (for fedora-less system)

  • Example: for audio: field_media_audio_file
  • Image media type's field type is Image not file

Ensure you have set maxiumum file size

• upload size and max post size:
  • sudo nano /etc/php/8.3/apache2/php.ini
  • change post_max_size = 8M to post_max_size = 200M
  • change upload_max_filesize = 8M to upload_max_filesize = 200M
  • change max_file_uploads = 200 to an appropriate number (1000?)

restart apache and tomcat, daemon-reload, cache rebuild

• sudo systemctl restart apache2 tomcat
• sudo systemctl daemon-reload
• drush cr

re-islandora Workbench to be on V1.0.0:

Remove dev version and install V1 cause dev version is not determined by workbench anymore:

cd /opt/drupal/islandora-starter-site

• remove mjordan/islandora_workbench_integration from composer.json and update composer sudo composer update

Re-install and enable(Running command bellow will get V1 )

• sudo -u www-data composer require mjordan/islandora_workbench_integration
• drush en -y islandora_workbench_integration
• drush cr
• sudo systemctl restart apache2 tomcat postgresql
• sudo systemctl daemon-reload

enable rest endpoints for workbench then rebuild the cache:

• drush cim -y --partial --source=/opt/drupal/islandora-starter-site/web/modules/contrib/islandora_workbench_integration/config/optional
• drush cr -y

If you had issue with number of file uploads check apache setting at /etc/php/8.3/apache2/php.ini

• sudo nano /etc/php/8.3/apache2/php.ini
• max_file_uploads = ???

Fix postgresql mimic_implicite error:

mimic_implicite for postgresql error occures while creating new content, After groupmedia module installaion, causes the content not to be created in postgresql database. here are steps to resolve it:

Copy the fixed postgresql edited php files over:

• sudo cp /mnt/hgfs/shared/postgres-core-module-src-driver/Connection.php /opt/drupal/islandora-starter-site/web/core/modules/pgsql/src/Driver/Database/pgsql/
• sudo cp /mnt/hgfs/shared/postgres-core-module-src-driver/Select.php /opt/drupal/islandora-starter-site/web/core/modules/pgsql/src/Driver/Database/pgsql/
• drush cr
• sudo systemctl daemon-reload
• sudo systemctl restart apache2 postgresql
• sudo systemctl status apache2 postgresql

Configure default Flysystem:

Need to be decided later

Run workbench ingest:

After running our transformation tools, we are ready to ingest the data. To do this, follow the steps below:

1. Create custom fields:

Because we have custom fields that are not part of the default Drupal fields in the database tables, Workbench will throw an error stating "Headers require a matching Drupal fields name." Therefore, we need to create them using any of the methods below:

• On GUI (Slow process, not recommended):

  • Navigate to structure>Content types> Repository items> manage fields> add field

• Batch ingest fields with json configuration scrips:

  • Install the field_create Module:

    • sudo -u www-data composer require 'drupal/field_create:^1.0'

  • Enable modules: drush en field_create field_create_from_json

  • Create a JSON configuration script to define fields with specific data types:

  • Create fields:

    • Navigate to configurations>delvelopment>add fields programmatically> under Content dropdown> copy json configuration for creating fields> Click save Configuration

    • Then under Action tab select node from dropdown > Click Create fields now

      • if json configurations where correct it will show you message that says: Processed fields for node.

    • Json format for creating fields with different data types:

  • Example JSON syntax for creating fields:

{
 "field_name": { # Machine name of the field
   "name": "field_name", #Machine name of the field
   "label": "field name", #Enter name of the field without '_' as a field lable name
   "type": "text", # type of the field can be assigned in "type"
   "force": true,
   "bundles": {
     "islandora_object": { #islandora content type
       "label": "islandora object" #description for islandora content type
     }
   }
 }
}

2. now run the workbench to ingest our content to the server:

• cd islandora_workbench
• ./workbench --config LDLingest.yml