> For the complete documentation index, see [llms.txt](https://docs.editran.onesait.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.editran.onesait.com/documentacion-editran/documentacion-editran-editran-sepa-v3-open-en/requisitos-e-instalacion/modulos-instalados.md).

# Installed modules

The modules that make up the Editran/SEPA product are organized according to the following tree:

1. **SEPA**: Contains the directory tree, the user manual and the file `public.key` necessary for the proper functioning of the Editran/SEPA license.
2. **SEPA/conf**: Contains the configuration of the additional parameters of Editran/SEPA, the log, and the configuration of the entities to be converted.
3. **SEPA/doc**: Contains the Javadoc documentation necessary for, if desired, using the Editran/SEPA module as a library.
4. **SEPA/lib**: Contains the Java libraries that implement the conversion functionality as well as the schemas that the XML formats must comply with. Within this folder there are subfolders distinguishing each Operating System where the corresponding libraries for each one are included.
5. **SEPA/logs**: In this directory the log file generated by the program will be stored.
6. **SEPA/scripts**: Contains example scripts such as those that must be incorporated into the pre-issue or post-receipt user processes when the client wants to use Editran/SEPA from Editran/G and also a script to use Editran/SEPA independently. It includes scripts for each of the Operating Systems on which Editran/SEPA can be used. It also includes scripts for the XML Separate functionality (requires specific license, see chapter [it is essential to have the corresponding license (see section](#9-separador-ficheros-planos-y-xml)). In turn, the subfolder `/utils` includes two procedures: one to pad records with spaces until they reach a fixed length (intended for files with line breaks in which the length of each line is variable) and another to insert line breaks at a fixed length (intended for files that do not have any line breaks).


---

# 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://docs.editran.onesait.com/documentacion-editran/documentacion-editran-editran-sepa-v3-open-en/requisitos-e-instalacion/modulos-instalados.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.