> 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/modo-de-uso/proceso-cliente.md). # Client process As a JAVA application, we can design our own Java call, in which we must run: **On Windows:** ``` java -cp "lib/*;lib/Win/*" com.indra.mmdd.editran.main.EDItranSepaXmlMain [Parameters] ``` **On UNIX:** ``` java -cp "lib/*:lib/DirSO/*" com.indra.mmdd.editran.main.EDItranSepaXmlMain [Parameters] ``` In `lib/DirSO/*`, replace `DirSO` with the name of the lib subfolder corresponding to the operating system on which it is going to run: * AIX: `lib/AIX/*` * HP: `lib/HP/*` * Linux: `lib/Linux/*` * Sun: `lib/Sun/*` Where `[Parameters]` can be, depending on the number of arguments specified: **1 argument:** * `-h` for a general query of the usage mode, * `-v` to display in the log the version of the Converter being used, or * `` — being `` the path and name of the file containing the source data. In this mode of use, Editran/SEPA decides the transformation to be performed according to the source file extension. * It will assume that if the name of said file ends with the extension `.xml` the transformation to be performed is in the direction: **XML (ISO 20022) → Flat (versions 14 and 44)** The file generated by Editran/SEPA will in that case be in flat format and its name will be the same as that of the source file but without the extension `.xml`. * Likewise, if the source file has no extension `.xml`, Editran/SEPA assumes that the transformation it must perform is in the direction: **Flat (versions 14 and 44) → XML (ISO 20022)** The file generated by Editran/SEPA will in that case be in XML format and its name will be the same as that of the source file but adding the extension `.xml`. The XML file is the input in the case of an XML → Flat transformation or the one resulting from the execution in the case of a Flat → XML transformation. **3 arguments:** ` ` Where: * ``: path and name of the file containing the source data. * ``: path and name of the final already transformed file. * ``: is the format that the file obtained with the transformation will have. * When `P` Editran/SEPA will perform a transformation in the direction: **XML (ISO 20022) → Flat (versions 14 and 44)** * On the other hand, when `X` Editran/SEPA will generate an XML file: **Flat (versions 14 and 44) → XML (ISO 20022)** The XML file is the input in the case of an XML → Flat transformation or the one resulting from the execution in the case of a Flat → XML transformation. The APPENDIX details the possible error codes returned by the process. In addition, the user can consult in the file `out.log` more detailed and explicit information about each task, and its result, performed during the conversion process. This file is generated automatically in the folder `logs` of the SEPA installation. --- # 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/modo-de-uso/proceso-cliente.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.