> 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/puesta-en-marcha-del-producto.md). # Product startup Once the product's operation has been examined in detail, a quick guide for startup is provided below, with references to the sections where each item has been explained in detail. **On the signing workstations:** 1. Install the certificates with which the user will sign in Editran/FF and all those in its certification path (CA authority and intermediate certificates). The certificates for signing must necessarily include a private key, that is, be in PKCS#12 format (extension .*pfx* or .*p12*). It is highly recommended to install them enabling secure protection so that they ask for the password before use. Once installed, check with EnviarDN.exe, with a web browser or with *certmgr.msc* of Windows, that they all appear in the machine's personal certificate store, that they have a private key and that all the certificates in each one's certification path are also installed and show correct status, see **7.2.** 2. Install the product choosing the option *Compact* with which the component is installed *UserFF* and the set of most commonly used viewers. In general, on signing workstations the module *AdminFF* whose purpose is to perform/modify the product configuration. 3. Add the user who will use Editran/FF in the Security tab of the Editran/FF directory options. To do this, with an administrator user on the machine, select the Editran/FF installation directory and right-click -> Properties -> Security -> Edit -> Add, in the window that appears, add the user or users who are going to use the product, setting the Full control permission. 4. Have the license in the installation directory. The product license consists of two files: *license.dat* and *license.publick.* 5. Collect with *EnviarDN.exe* the data from the personal certificates with which the user will sign. 6. Alternatively to the use of *EnviarDN.exe*, from a web browser or by executing *certmgr.msc* of Windows, export to .*cer* the certificates with which each user will sign (export without the private key). 7. Send or take the information or files obtained, either with 4) or 5), to the administration machine. **On the server workstation:** 1. Install all the CA certificates of the certificates that will be used for signing and also those whose signatures will be validated. These certificates can be downloaded from the CAs' websites. 2. If the workstation has a version of the product installed earlier than the one going to be started up: stop and uninstall the services associated with the product, back up the profiles, and finally uninstall the product. 3. Install the product choosing the option *Typical* with which the components are installed *AdminFF, UserFF* and the set of most commonly used viewers. 4. Add the user who will use Editran/FF in the Security tab of the Editran/FF directory options. To do this, with an administrator user on the machine, select the Editran/FF installation directory and right-click -> Properties -> Security -> Edit -> Add *right-click -> Properties -> Security -> Edit -> Add*, in the window that appears, add the user or users who are going to use the product, setting the Full control permission. 5. Have the license in the installation directory. The product license consists of two files: *license.dat* and *license.publick.* 6. If a product version update is being performed, copy the file *path* from the previous version into the new version directory and make a backup copy of the old files .*cfg* of profiles in another directory. Finally run *MigraPerfiles.exe* to update the profiles to the format corresponding to the version, see **7.9.** 7. If the installation is being performed for the first time, run *AdminFF.exe* and click the menu *“Help->About* *AdminFF…”* to do what is described in **4.2** regarding the location of profiles. It is important to remember that the indicated location must also be accessible from each signing workstation. 8. In the menu *Administrator -> General settings* of *AdminFF,* configure everything necessary (see **4.1.1.1** of this manual) 9. Create and/or modify the user, application profiles and their relationships, see **4.2.** The data from the signers' personal certificates needed for the user profiles will already be accessible on this machine (files generated on the signing workstations with *EnviarDN.exe* or certificates exported in format .*cer*), and will be incorporated as explained in **4.2.1.** **It is important to remember that all the directories indicated in the application profile for the files to be signed, the signatures, the sending directory, etc., must be shared for users of the signing workstations**. Once configuration is complete, make a backup copy of the profiles files in another directory.*cfg* of profiles in another directory. Typical installation example regarding the parameters that require a choice: Users * One or two users of type **Local Administrator**. It is recommended that the **associated certificates** to these users have **private key secure protection enabled and ask for the password for use** (these parameters are configured during the installation of the certificates on the server or administration workstation). These users will be the only ones who can create, modify or delete the product profiles. * A user of type Local and Automatic to which a **certificate that does not have secure private key protection enabled or request a password for use** (these parameters are configured during certificate installation on the server workstation). * Two users of type Local to which up to three personal certificates with private key, valid for signing, issued by any recognized CA, will be associated. In this case it is highly recommended that the **certificates have secure private key protection enabled and ask for the password for use** (these parameters are configured during certificate installation on the signers' workstations). Application * Purpose -> Sign * Signing mode -> XADES\_DETACHED\_INTERNA\_IMPLICITA * Data directory → the one containing the files to be signed; they will all have the same format and content type. * Signatures directory → the one where the obtained signatures will be left. * Move/reject → directory to which the files that the signing user decides to remove from the circuit will be moved, provided the corresponding permission has been granted. * Send -> Directory to which the files will be moved once they all reach the required number of signatures and all of them are correct. Signatures will be marked to mean that this is what will be sent to the other end (with the proposed signing mode, the signature file includes the signed file). * Template -> \[EditranFF installation directory]/XAdES/templates/pln-di-i-BES.xml * Validation of required signatures -> Users/Groups * Viewer → the one corresponding to the format of the files to be signed. * Enablement → Yes and automatic enablement if the recipient of the signatures has Editran/FF in a Windows environment, otherwise choose No. Group in the application * Mandatory number of signatures → 2 Once the three elements are configured, associate the three users with the application and add the two who do not have the Automatic property to the group. During association with the application, each user will be granted the permissions as appropriate: permission to enable the application, to move/reject files, HR viewer to see full content in the case of Transfers, etc. 10. If the automatic first-signature functionality and/or the sending of notifications of new files available is going to be used, install and start the Editran/FF service (see **7.10**) 11. If signing is going to be done or signatures are going to be verified with any of the XAdES modes, also start the process *Editran* *Signature Services* with XAdES/bin/start\_xades.bat or install and start it as a Windows service (see **7.12**. item *wrapper*) with a user account that has read, write and execute permissions on the directories. **Again on the signing workstations:** 1. Copy the file “*path”* from the server workstation installation into the signing workstation installation directory. 2. If in *AdminFF* has been configured the “Server connection” tab from the “General settings” menu, also copy the file “*cnx.cfg”* from the profiles directory into the signing workstation installation directory. 3. If any of the applications in which the user is involved uses any of the XAdES signing modes, edit “XAdES\bin\\*start\_xades.bat”* and “XAdES\bin\\*stop\_xades.bat”* to modify, if necessary, the value of “set XADES\_PATH=”. Likewise, run “XAdES\bin\\*configuracion\_xades.bat*” if the port on which the Java process for XAdES signatures should start or any other default configuration value needs to be modified. 4. Run *UserFF.exe*, enter the user alias, select one of the associated certificates, enter its password, and check that the connection is made to the profile files server and to the signing files server as follows: select in the tree “*Applications -> Signing of* *files -> \[Application\_name] -> \[User\_name]*” and check that the corresponding file list for each application appears in the right panel. If so, the connections to the servers will have been made correctly. These connections are made automatically if it has been configured in \*\*4.1.1.\*\*1 and if the configuration file “*cnx.cfg”* (if this is not possible an error is shown), otherwise they must be prepared manually. If any of the applications in which the user is involved uses any of the XAdES signing modes, check in *XAdES/logs/out.log* that the Java process for XAdES signing is running. --- # 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/puesta-en-marcha-del-producto.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.