> 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/ibm-editran-v5.3-iseries-en/editran-ff/installation-and-requirements/installed-modules.md). # Installed modules The modules that make up the Editran/XAdES product are arranged in the following directory tree: 1. XAdES/bin: Contains the scripts to start start\_xades.sh and to stop the server stop\_xades.sh, The command file XAdES/bin/start\_xades\_sh starts the java ThreadPooledServer server. This process will appear in the rest of the document referred to as the Editran/XAdES Java Server. In the file, the following variables are set, which the user must modify to adapt them to their installation: DIR\_XADES = installation path MEM\_INI= initial memory allocated, in MB MEM\_MAX= maximum memory allocated, in MB \#JAVA\_HOME= the version of Java they have is indicated in quotes, and all scripts where necessary should be reviewed to indicate it. An example could be: DIR\_XADES = “/XAdES” MEM\_INI=1024 MEM\_MAX=1024 JAVA\_HOME="/usr/lpp/java/J8.0\_64" The command file XAdES/bin/stop\_xades.sh stops the server. In the same way as in the startup file, it must be edited to give the correct value to the DIR\_XADES variable. In our example: ![](https://2621858476-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F80nfuaOloGPZthms7LSJ%2Fuploads%2Fgit-blob-392748209c1e9b8a4879c410d996d634f34aeb79%2Fimage%20\(121\).png?alt=media)DIR\_XADES = “/XAdES” When running sh ./start\_xades.sh it is important to check in the log that it has started correctly, especially the first time the product is installed. (With qsh, run sh ./start\_xades.sh in the corresponding directory, in our example XAdES/bin and * [x] check in XAdES/logs/out.log that it has started correctly. The client that will launch from Editran/FF the signature and verification requests for the received files and the subsequent user process after receipt for these transmissions. 2\. XAdES/conf: Includes the configuration files of Editran/XAdES. There are 3 different configuration files: * [x] xades.properties: Configuration of the Editran/XAdES Java server. It is explained how it should be configured in point 3. * [x] Log4j.properties: Configuration of the application log. * [x] FicheroKeyStores.txt: File that stores the physical keystores with which signing is desired. It is explained how it should be configured in the section. 3\. XAdES/crl: Stores certificate revocation lists in case there is no Internet connection. 4\. XAdES/lib: Contains the Java libraries that implement the server for signing and verifying XAdES-EPES signatures. 5\. XAdES/logs: In this directory the Java server log files will be created. 6\. XAdES/plantillas: The templates used as a model to create XAdES signatures. The templates store the optional parameters used by Editran/XAdES to perform the signature with a specific format. 7\. XAdES/rsc: This is the directory where the resources required by the server reside, such as schemas for validating the XML format of the signatures. Among these resources is the template schema, plantillafirma.xsd, necessary in case the templates need to be modified. 8\. XAdES/rsc/truststore: A TrustStore.pfx file is provided in the /rsc/truststore/ folder with several CAs already included. This store is of PKCS12 type but contains no keys, only certificates that are public, so no major security measures are required either. A script has been included for handling the TrustStore file, gestor\_truststore.sh, which makes it easier to add and delete the CAs that we consider the product should accept and, in addition, allows the password of this file to be changed (default “password”). Example of correct startup: 21/06/2021 13:46:33,846 510 INFO \[main] servers.ThreadPooledServer main - Starting Editran Signature Services Server v3.0.0 21/06/2021 13:46:33,878 542 INFO \[Thread-6] servers.ThreadPooledServer openServerSocket - InetAddress: /127.0.0.1 21/06/2021 13:46:33,879 543 INFO \[Thread-6] servers.ThreadPooledServer openServerSocket - Port: 7760 21/06/2021 13:46:33,880 544 INFO \[Thread-6] servers.ThreadPooledServer openServerSocket - LocalSocketAddress: /127.0.0.1:7760 --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.editran.onesait.com/documentacion-editran/ibm-editran-v5.3-iseries-en/editran-ff/installation-and-requirements/installed-modules.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.