> For the complete documentation index, see [llms.txt](https://documentation.efalia.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.efalia.com/produit/efalia-egov/installation.md).

# Installation

Procédure d'installation d'Efalia eGov : prérequis techniques (Apache, Tomcat, PostgreSQL, Elasticsearch, ActiveMQ), architecture et sécurité.

Le but de ce document est de décrire la procédure d'installation de Efalia Egov.

Nous allons détailler les prérequis techniques des différents composants nécessaires au bon fonctionnement de Efalia eGov :

* La machine de déploiement (facultative)
* Le(s) serveur(s) applicatif(s) hébergeant le progiciel, contenant principalement :
  * Apache
  * Tomcat
  * Postgresql
  * Elasticsearch
  * ActiveMQ (Service de messagerie applicative JMS)

En fonction de la charge attendue, les différents services pourront être répartis sur plusieurs serveurs

{% hint style="info" %}
Il est recommandé mais non obligatoire d'installer les composants Apache, Tomcat, Elasticsearch, ActiveMQ et de base de données sur un système Debian 12 64bits (système de base, sans composant additionnel hormis « Serveur SSH » et « Utilitaire usuels du système »). Différentes configuration types vous sont proposées en Annexe B. L'application est également qualifiée sur CentOS 7 et 8, ainsi que Ubuntu 18/20/22.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://documentation.efalia.com/produit/efalia-egov/installation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
