Bare-metal
Linux Ubuntu or Debian
Overview
The Trust1Validation can be deployed on a Tomcat 9 server. Below you will find instructions on how you can deploy the Trust1Validation on a bare metal installation.
The utilities service is a play application that can be deployed on the same server.
The OS used to validate this deployment method, is Ubuntu 22.04 LTS
Trust1Validation Service
Installing Java
Tomcat 9 requires Java SE eight or later. We’ll set up OpenJDK 11.
Run the next instructions with sudo privileges, we will update the package registries first and then install OpenJDK 11:
As soon as the installation is done, confirm it by checking with the following command:
The output should be similar to this:
System consumer
Deploying Tomcat in a basic consumer context is considered unsafe practice. We’ll create a brand new system consumer and group with residence listing /decide/tomcat that may run the Tomcat service. To create this consumer run the following command:
Downloading and installing Tomcat
You can retrieve the Tomcat binaries from their downloads page.
We need the core package.
We will use wget to download the binaries. We will set the version as a variable since we will need it later on
Once the download is complete, extract the tar file to the /opt/tomcat directory::
For ease of use can make a symbolic link
Later, when upgrading Tomcat, unpack the new version and alter the symlink to that version.
Now we need to update the directory ownership to the consumer we've created before:
The shell scripts inside the Tomcat’s bin directory must be made executable:
These scripts are used to start, stop and manage the Tomcat instance.
Running as a service
Now we will set up a service so that Tomcat is automatically started on system boot.
Open your text editor and create a tomcat.service unit file in the /etc/systemd/system/ directory:
Paste the following configuration:
Modify the JAVA_HOME variable if the path to your Java installation is different.
Save and close the file and notify systemd that a new service file has been created:
Enable and start the Tomcat service:
Check the service status:
The output should show that the Tomcat server is enabled and running:
You can start, stop and restart Tomcat same as any other systemd service:
Trust1Validation deployment
Now we have a running tomcat server we want to deploy our service.
first up we remove the original ROOT application
Next up we will deploy our war file.
You can find the war file in filemage instance
Now restart the service to make sure the service is deployed and running
You can also verify everything with the Tomcat web application manager
For the manager make sure you've enabled a user in the /opt/tomcat/latest/conf/tomcat-users.xml which is needed to log in to the manager.
Now the service should be available on localhost:8080 and is ready to be exposed.
Fileopen limit
The fileopen limit can be troublesome on webservers causing 503 errors. To prevent this we increase the filopen limit to a more reasonable amount;
To view the current user limits set, add the “-a” option in the “ulimit” command:
You can change the limit of opened files by adding the following to /etc/security/limits.conf:
Then you can reload the configuration using sysctl -p on the shell. Check this article.
Just for completeness you can verify what is the current limit for opened files using: ulimit -n
Extra's
In case your server is protected by a firewall, you’ll want to open port 8080.
Trust1Validation Utilities
Overview
The digital trust service utilities is a extension on the digital trust service. This provide functionalities like PDF/A validation.
Installing Java
We’ll set up OpenJDK 11.
If java is already installed you do not need to do this step
Run the next instructions with sudo privileges, we will update the package registries first and then install OpenJDK 11:
As soon as the installation is done, confirm it by checking with the following command:
The output should look something like this:
System consumer
Deploying Play in a basic consumer context is considered unsafe practice. We’ll create a brand new system consumer and group with residence listing /decide/play that may run the Play service. To create this consumer run the following command:
Downloading and installing DSS utils
You can retrieve the DSS utils binaries from their our download page
We will use wget to download the binaries.
Once the download is complete, extract the tar file to the /opt/play directory::
Running as a service
Now we will set up a service so that DSS utils is automatically started on system boot.
Open your text editor and create a dssutils.service unit file in the /etc/systemd/system/ directory:
Paste the following configuration:
Save and close the file and notify systemd that a new service file has been created:
Enable and start the DSS utils service:
Check the service status:
The output should show that the Tomcat server is enabled and running:
You can start, stop and restart DSS utils same as any other systemd service:
Last updated
