> 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/publico-editranff-v6.2-windows-en/comandos/proceso-java-editran-signature-services-para-firmas-xades.md). # Editran Signature Services Java process for XAdES signatures All functionality related to XAdES signature modes is carried out through the package *Editran Signature* *Services* delivered with the product. To use this service, it is necessary to have a 32-bit Java 8 or higher installation with the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy File extension (from Release 1.8.0\_151 it is included by default), both on the server machine and on each of the signing workstations. Under the installation directory is the following directory structure: XAdES * **bin**: contains a series of batch files. * ***configuration\_xades.bat***: by default the Java process *Editran Signature Services* for XAdES signatures starts on 127.0.0.1 on port 7760, the truststore in XAdES\rsc\truststore is used. If you want to configure different values for these parameters or the workstation on which the service will be started requires a proxy for Internet access, it will be executed and the new values will be written. * ***truststore\_manager.bat:*** batch script to manage the CA certificate store *XAdES\rsc\truststore\truststore.pfx* included in the installation. It allows you to query, add, and delete the stored certificates, as well as change the password that protects it. **If the password is changed, then *****XAdES\bin\configuration\_xades.bat***** must be run afterward to update the new value in the configuration.** * ***obten\_dn.bat***batch for querying and obtaining the certificate data needed for the profiles. This batch is useful when configuring the product and collecting the data from certificates that are not installed on the machine but are available in files with extensions .*p12* or *.pfx*, if they are certificates for signing (those of local users), or .cer if they are certificates whose signatures are going to be verified (those of remote users). * ***start\_xades.bat***batch script to start the Java process *Editran Signature Services* for XAdES signatures. It must be edited and the XAdES path value must be properly configured in: *set XADES\_PATH=C:\EditranFF.600\XAdES* On the signing workstations, from *UserFF.exe* the process starts automatically. **When you install the product and run *****UserFF.exe*****, check in XAdES\logs\out.log that the service has started.** On the server workstation, the process can be started: 1. Manually by running start\_xades.bat 2. Automatically: a shortcut to start\_xades.bat will be created, and it will be dragged to the Windows Startup folder. 3. By installing it as a Windows Service (see the wrapper section of this chapter). **Once the process has started, the success of the operation should be checked in XAdES\logs\out.log.** * ***stop\_xades.bat:*** batch script to stop the Java process *Editran Signature Services* for XAdES signatures. It must be edited and the XAdES path value must be properly configured in: *set XADES\_PATH= C:\EDItranFF.600\XAdES* When UserFF.exe is closed, the Java process *Editran Signature Services* stops automatically. * **conf**: contains the configuration files related to the Java process *Editran Signature Services.* Edit log4j.properties to modify the information level in the log file, the number of log files you want to keep, the maximum size, the name, etc. * **crl** * **doc** * **lib** * **logs**: contains the out.log log file with all the information related to the Editran Signature Services Java process for XAdES signatures: whether the process is running and the characteristics and result of each signature and signature verification performed. * **templates**: contains the templates delivered with the product with different sets of parameters for signing in each of the modes. They can be modified and others added as long as they comply with the XAdES\rsc\plantillafirma.xsd schema proprietary to Editran/FF. * **policies**: contains the General State Agency policy file, according to which the templates in the directory *templates* which have EPES-AGE in their name. * **rsc**: contains *truststore\truststore.pfx*, the store with the CA certificates of all the certificates that will be used to sign or whose signatures will be verified. The store can be viewed and modified with *“XAdES\bin\truststore\_manager.bat”*. If it is detected that in *truststore.pfx* some CA certificate is missing (verification result “The CA is not trusted”), it can be added using this utility. * **utils** * **wrapper**: contains the elements necessary to install *Editran Signature Services* as a Windows service on the server workstation. The service can only be installed this way if it is to be used exclusively to perform the first automatic signature and to verify signatures. **On client workstations, the process cannot be installed this way because Windows services cannot request the password of the certificates during signing.** The following steps will be performed: 1. In XAdES\wrapper\conf of the XAdES directory, edit the file *wrapper.conf* and properly configure the XAdES installation path in: *# Execution directory* *wrapper.working.dir=C:\EditranFF.600\XAdES* * **2**. Optional: check whether the service will work before installing it by running the batch **SignatureServiceTest.bat** from this directory. If no error message appears, the service will work correctly. 3. Install the Windows Service ***Editran Signature Services*** by running the batch ***InstallSignatureService.bat*** from this directory. 4. Configure a user with appropriate permissions in the Service Login ***Editran Signature Services.*** When it is necessary to uninstall the service, run UninstallSignatureService.bat. --- # 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/publico-editranff-v6.2-windows-en/comandos/proceso-java-editran-signature-services-para-firmas-xades.md?ask=&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.