Pre-installation
The purpose of this document is to give guidance to programmes regarding the requirements for IT service provider procurement. It contains recommendations which should help to manage the installation, setup and update of the service.
Target group
This document addresses in particular programme representatives.
Prerequisites
Hosting requirements
The details of hosting requirements are described in the document “Technical specifications” (please, find it HERE).
This document introduces a shortened list of the components to indicate the basic needs for starting the procurement.
We recommend to use a separate server environment for the Jems service isolated from unrelated services.
A server can be ordered from any service provider who is selected according to the public procurement law (if applicable).
Service | RAM | CPU | HD |
Webserver + App | 16 GB | 10 cores | 16 GB |
MinIO | 512 GB - depending on file upload usage | ||
Elastic | 16 GB | ||
MariaDB | 16 GB | 6 cores | 64 GB |
Totals | 32 GB | 16 cores | 128 GB Fast SSD/NVME 512 GB HDD (dedicated for MinIO) |
Software requirements
The details of software requirements are described in the “Installation instructions” (please find them HERE).
This document introduces a shortened list of the components to be installed for a successful Jems service deployment.
Linux platform (Kernel 4.x or higher) |
 |
OpenJDK Runtime Environment 11 |
 |
MariaDB 10.6.12 |
 |
Elasticsearch 7.17.9 |
 |
MinIO RELEASE.2021-08-05T22-01-19Z |
 |
MariaDB is critical component for Jems service, which is required for a proper feature functionalities which are not supported by MySQL!
Development requirements
The details of development requirements will be described in the “Build instructions” with the first release, where you will find information on how to get the sources and
build the Jems service.
Installation checklist
Definition of the content
The checkpoints mentioned below are recommendations. The checklist highlights important milestones and should be taken into account before installation and future service maintenance.
The checklist includes initial actions required to start up the service as well as the steps related to the service support. These steps should be considered when planning the time schedule for the system and service maintenance. Potentially, there is no need to arrange for the constant presence of the person responsible for maintenance.
Check point | Stage | Description |
| Initial | Find a service provider who can deliver the environment according to the listed prerequisites. See the hosting requirements. |
| Optional | Request service provider to mirror production on test environment. |
| Initial | Request service provider to provide an environment ready for the component’s installation. |
| Initial | Request service provider to issue SSL certificate to secure Jems service. |
| Initial | Service provider should provide support with installation of packages required by Jems service.* |
| Initial | Service provider should provide support with Jems service installation.* |
| Initial | Service provider should provide support with Jems service configuration based on system user manual.* |
| On demand | Request service provider to customize service based on programme requirements. See the development instructions. |
| Regular | Request service provider to ensure that environment is in the actual updated status. |
| Regular | Request service provider to automate backups and support restore on demand. |
| On demand | Request service provider to update Jems service component dependencies based on release notes. |
| On demand | Request service provider to update Jems service based on release notes. |
*Note: The signing of the licence agreement allows support with first-time installation within six months after receiving the installation package and instructions.