There are currently two ways of installing MOLGENIS on the server. We use several building blocks to deploy MOLGENIS on servers. The configuration is based upon RPM's which are used in Ansible to configure the deployment.
The architecture of MOLGENIS is displayed in the following figure.
Add repositories
You need to add the repository to access the RPM's:
In the pg_hba.conf You need to update to these lines:
# TYPE DATABASE USER ADDRESS METHOD# "local" is for Unix domain socket connections onlylocal all all peer# IPv4 local connections:hostallall127.0.0.1/32md5# IPv6 local connections:hostallall::1/128md5# Allow replication connections from localhost, by a user with the# replication privilege.#local replication postgres peer#host replication postgres 127.0.0.1/32 ident#host replication postgres ::1/128 ident
In the postgres.conf you need to update these lines:
max_locks_per_transaction=1024
Restart the service.
Elasticsearch
Open elasticsearch.yml in the Elasticsearch config directory and set the following properties:
In the /etc/security/limits.conf update this line:
elasticsearch-nofile65536
Add this this file in /etc/sysctl.d/99-elasticsearch.conf with the following content.
vm.swappiness=1
Restart the service.
Configure Tomcat
After you install Apache Tomcat you first need to install MOLGENIS before you start the service.
Configure HTTPD
We use proxy passes to expose Tomcat through Apache. You can use this file as template to expose your MOLGENIS instance. Create the file in /etc/httpd/conf.d/