> 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-process/installation/preconisations-materielles.md).

# Préconisations Matérielles

## Postes clients

Configuration requise pour l'application web Efalia Process, la console d'administration et le Designer (modélisateur).

| Application                        | Pré-requis                                                                                                                                    |
| ---------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
| **Application Web Efalia Process** | Un navigateur web récent (moins de 2 ans) : Chrome, Firefox, Edge, Opera… Il est nécessaire d'autoriser l'usage de JavaScript et des cookies. |
| **Console d'Administration**       | Un navigateur web récent (moins de 2 ans) : Chrome, Firefox, Edge, Opera… Il est nécessaire d'autoriser l'usage de JavaScript et des cookies. |
| **Designer (modélisateur)**        | Un navigateur web récent (moins de 2 ans) : Chrome, Firefox, Edge, Opera… Il est nécessaire d'autoriser l'usage de JavaScript et des cookies. |

## Serveur

Configuration minimale requise pour le serveur Efalia Process.

| Élément    | Version / valeur                                                                                                                              |
| ---------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
| **JDK**    | JDK 1.8.x                                                                                                                                     |
| **OS**     | Windows 2016, 2019 (mode container non pris en charge lors de l'installation), ou Linux supportant le JDK 1.8, ou macOS supportant le JDK 1.8 |
| **RAM**    | 2 Go minimum disponibles pour la JVM                                                                                                          |
| **CPU**    | 1 vCPU minimum disponible pour la JVM                                                                                                         |
| **Disque** | 500 Mo pour la JVM, plus un espace pour les documents équivalent à la taille des documents attendus multipliée par un facteur 1,5             |
| **SGBD**   | MySQL 5.x (version stable), ou Oracle 11G à 19C — mode transactionnel et encodage UTF-8                                                       |
| **Tomcat** | Tomcat 8.5 minimum (fonctionne avec Tomcat 9) — [tomcat.apache.org/download-80.cgi](https://tomcat.apache.org/download-80.cgi)                |
| **LDAP**   | LDAP v3 ou Active Directory                                                                                                                   |

{% hint style="info" %}
La capacité disque nécessaire aux documents dépend directement de la taille du projet : prévoir un espace équivalent à 1,5 fois la volumétrie documentaire attendue.
{% 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-process/installation/preconisations-materielles.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.
