> 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/sepa/requirements-and-installation/installation.md). # Installation
Software download Enter the website and select Resources. Go to IBM iSeries and in the section **Additional Modules** download the Editran SEPA software.
Package installation As400/Java * Unzip the EDItranSepaXml.tar file in the installation folder created for this purpose, e.g. /editransepa, leaving the following directory structure from this one: \|-conf \|-bin \|-lib \|-logs * First we should check that the start.sh and stop.sh files have execute permissions. * Next, edit the start.sh file and set the following variables: PWD=/ editransepa (installation path, where it has been unzipped) IP="0.0.0.0" (IP on which the server starts) PORT="7774" (PORT on which the server is listening) JAVA\_HOME="/QOpenSys/QIBM/ProdData/JavaVM/jdk60/32bit" (Java installation path) * Then edit the stop.sh file by setting the following variables PWD=/ editransepa (installation path, where it has been unzipped) * Once this is done, the application can be started by running the command: ./start.sh To check that the Server has started correctly once the command has been executed, edit the logs/out.log file, and it should contain the following traces (the port and IP should show the ones configured in the file): 17/04/2012 11:16:40,013 8530 INFO \[main] servers.ThreadPooledServer main - Starting Server 17/04/2012 11:16:40,031 8548 INFO \[Thread-3] servers.ThreadPooledServer openServerSocket - Port:7775 17/04/2012 11:16:40,033 8550 INFO \[Thread-3] servers.ThreadPooledServer openServerSocket - LocalSocketAddress\:/192.168.172.88:7775 17/04/2012 11:16:40,035 8552 INFO \[Thread-3] servers.ThreadPooledServer openServerSocket - InetAddress\:/192.168.172.88 * To stop the process: ./stop.sh The files EDItranSepaXml.tar and EDItranSepaXml.rar are available to test a possible installation from scratch. There is a server log file in which you can see the progress of requests, errors, etc.…(Logs/out.log).
* Configuration of the conf directory: There are three files in the conf directory, detailed below:
Configuration of the Entidades.properties file This file is the Entidades template. It is an optional file that configures an extra data source needed for the bidirectional conversion between XML and flat formats to be complete and correct. When this file is not defined, or the data sought is not found, depending on the direction of the transformation performed, the fields of the flat format will be filled with zeros or the corresponding labels of the XML formats will be left empty. Specifically, it allows you to provide both the entity and branch office of the presenter in the plain format of standard 19, as well as the BICs of the originators of the transfer ISO standard and the creditors of the direct debit ISO standard. As many entities as necessary can be listed. The file will contain exclusively relationships between BIC numbers and the pair of "entity + office" numbers they correspond to. It will be used exclusively for Spanish entities, since the "entity + office" number indicated will be searched in positions 4 to 11, counting from 0, of the IBAN accounts (starting with "ES") corresponding to the party whose BIC or "entity + office" is to be reported. Location example: ES0001234567000000000000 Initial file contents: \#Example \#bic.0=ABCDEFGHXXX \#entyof.0=01234567 bic.1= entyof.1= bic.2= entyof.2= \\
Entidades properties (Optional) This file is the Entidades template. It is an optional file that configures an extra data source needed for the bidirectional conversion between XML and flat formats to be complete and correct. When this file is not defined, or the data sought is not found, depending on the direction of the transformation performed, the fields of the flat format will be filled with zeros or the corresponding labels of the XML formats will be left empty. Specifically, it allows you to provide both the entity and branch office of the presenter in the plain format of standard 19, as well as the BICs of the originators of the transfer ISO standard and the creditors of the direct debit ISO standard. As many entities as necessary can be listed. The file will contain exclusively relationships between BIC numbers and the pair of "entity + office" numbers they correspond to. It will be used exclusively for Spanish entities, since the "entity + office" number indicated will be searched in positions 4 to 11, counting from 0, of the IBAN accounts (starting with "ES") corresponding to the party whose BIC or "entity + office" is to be reported. Location example: ES0001234567000000000000 Initial file contents: \#Example \#bic.0=ABCDEFGHXXX \#entyof.0=01234567 bic.1= entyof.1= bic.2= entyof.2=
log4j2.properties
--- # 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/sepa/requirements-and-installation/installation.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.