> 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/instrucciones-para-la-instalacion.md). # Installation instructions The procedure to follow to install the Editran/SEPA module, on any operating system, will be to download the corresponding file from the Editran website and then unzip it, obtaining the following folder structure: ``` |SEPA |--conf |--doc |--lib |--logs |--scripts |---utils ``` In addition, the user environment must be prepared in order to run JAVA applications. The following explains exactly how to proceed depending on the operating system. ## UNIX The client will receive or will download from the Editran website a file `.tar` with the package for their OS and will save the file in the directory where it is to be installed. They may create a new directory or leave it in the directory where Editran is installed. In any case, the product will create the SEPA subdirectory with the new software. Assuming the OS is Solaris and that by default we are going to install it in the same directory as Editran (for example in `/opt/editran`), the following steps will be followed: 1. Leave the file in `/opt/editran` 2. Go to `/opt/editran` and unzip and extract the software, running: ``` tar -xvf sepa-unix.V#.##-YYYY-MM-DD.tar ``` 3. If it is not already defined, include in `.profile` or `.chsrc` (depending on the shell) the environment variables: * `JAVA_HOME` = \[Java installation path] * Add to the `PATH` variable `$(JAVA_HOME)/bin` 4. Edit the file `SEPA/scripts/EntornoSepa` to define: * The path contained in variable `DIR_SEPA` with the location of the SEPA installation directory (without using relative paths). ``` # ----------------------------------------------------------- # ------------ INSTALLATION DEFINITIONS ------------------ # ----------------------------------------------------------- DIR_SEPA=/opt/editran/SEPA ``` * The variable `PATH` with the installation directory of the Editran product and the Java installation directory (without using relative paths). ``` # Editran bin directory and Java installation directory PATH="/opt/editran/bin:/path/to/java:$PATH" # ----------------------------------------------------------- ``` * Edit the scripts: * `checkLic.sh` * `PRVEMISEPA.sh` * `PSTEMISEPA.sh` * `PSTRECSEPA.sh` * `SEPA.sh` To adjust the path of the EntornoSepa file to its location in the installation (without using relative paths). ``` # ------------ INSTALLATION DEFINITIONS ------------------ ENT_SEPA=/opt/editran/SEPA/scripts/EntornoSepa # ----------------------------------------------------------- ``` ## Windows The client will receive or will download from the Editran website the compressed file `.zip` with the distribution for Windows. When unzipped in the desired destination directory, a subdirectory called SEPA will be created with the new software. Once the extraction is finished, the following actions must be performed: 1. Edit the file `SEPA/scripts/EntornoSepa.bat` to define: * The path contained in variable `DIR_SEPA` with the location of the SEPA installation directory (without using relative paths). ``` rem ------------------------------------------------------------- rem INSTALLATION DEFINITIONS rem ------------------------------------------------------------- set DIR_SEPA=C:\SEPA ``` * The variable `PATH` with the bin directory of the Editran product installation and the Java installation directory (without using relative paths). ``` # Editran bin directory and Java installation directory set PATH="C:\editran\bin;\path\to\java;"%PATH% # ----------------------------------------------------------- ``` * Edit the scripts: * `checkLic.bat` * `PRVEMISEPA.bat` * `PSTEMISEPA.bat` * `PSTRECSEPA.bat` * `SEPA.bat` To adjust the path of the EntornoSepa file to its location in the installation (without using relative paths). ``` rem ------------------------------------------------------------- rem INSTALLATION DEFINITIONS rem ------------------------------------------------------------- set FENTORNO=C:\SEPA\scripts\EntornoSepa.bat rem ------------------------------------------------------------- ``` 2. Access: **Control Panel → System and Security → System → Advanced system settings → Advanced options → Environment variables.** In the window displayed, the following environment variables will be defined and modified: * `JAVA_HOME`: You must define `JAVA_HOME` as an environment variable with the path where the Java you want to use is installed and modify the variable `PATH` so that it includes the path where Java is installed. ![Photo](https://620397458-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYRsCBWELAyzw5mj5JFUW%2Fuploads%2Fgit-blob-256085d285dfd4feefac00a421d830958c401872%2Fimage.avif?alt=media) For example, the Java installation is located in `C:\Program Files\Java\jre1.8.0_25`. The variable would need to be configured `JAVA_HOME` as follows. ![Foto](https://620397458-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYRsCBWELAyzw5mj5JFUW%2Fuploads%2Fgit-blob-aa4df9c8508cd9d5faf1ffd35c9f36cf0a387690%2Fimage.avif1.avif?alt=media) * `PATH`: Modify the variable `PATH` by adding at the beginning `%JAVA_HOME%\bin`, separating it with a semicolon (`;`). ![Foto](https://620397458-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYRsCBWELAyzw5mj5JFUW%2Fuploads%2Fgit-blob-b4b2f2e70e798fb2c8d96a133a7cb570ea18f3e1%2Fimage%20\(2\).avif?alt=media) --- # 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/instrucciones-para-la-instalacion.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.