> 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/connect-v2.1-en/instalacion/migracion/perfiles.md). # Profile migration Two command-line applications are distributed with the Connect installation to automatically create contacts and channels from the profiles of presentations and sessions existing in the Editran installation. The input with the information that will be incorporated into the Connect database will be the text files with the profiles dumped using the commands **igaperfi.exe** and **ediperfi.exe**. These files can be obtained automatically from the Editran 5.2.2 installation using the previous commands or can be obtained manually, for example, if you want to make a selection of the sessions to include. ## Requirements The initial configuration of the Editran Connect application must have been completed and the Connect services (Editran Connect Base) must be running. In addition, the sessions must have the local and remote code name field configured and two different remote codes must not share the same name. To migrate specific profiles, the files must have the following names: * salidaP for the sessions file obtained when running ```bash ediperfi -r --a --osalidaP. ``` * salidaG for the presentations file obtained when running ```bash igaperfi -r --a --osalidaG. ``` The names of the salidaP and salidaG files must not contain any extension accompanying them such as ".txt" and they must be located in: `\ /bin.` ## Usage 1. Open a CMD terminal. 2. Go to the path `*\/utils*`, where the files are located *migraContactos.bat* and *migraCanales.bat*. 3. In the terminal, first run *migraContactos.bat*: 1. *migraContactos.bat -f* if you want to use a specific profiles file. *Use the modifier --f/-f1/-f2 depending on the contents of the file:* * *--f for files that contain the local profile and the session(s),* * *-f1 for files that contain only the local profile and* * *--f2 for files that contain only sessions.* 2. *migraContactos.bat -e* if you want to migrate all Editran profiles. 4. After that, the following will be executed *migraCanales.bat* 1. *migraCanales.bat -f* if you want to use a specific profiles file. 2. *migraCanales.bat -e* if you want to migrate all Editran profiles. 5. Check the files *conflictosREMOTOS.txt* and *conflictosCANALES.txt* located in the path *\ /log/migrar* 6. Once the conflict files have been reviewed, the problems found must be resolved by modifying the indicated profiles and re-running the migration. In the case of having migrated all Editran profiles, you can: 1. Modify the profiles in the files *salidaP* and *salidaG* and run the program again with the specific profiles file option (*-f*). 2. Modify the profiles in Editran and run the program again with the option to migrate all profiles (*-e*). 7. It is necessary to modify the Editran profiles with Connect integration scripts in the pre-transmission (.\utils\EC\_PREVTX.bat), post-transmission (.\utils\EC\_POSTTX.bat) and exception (.\utils\EC\_EXCTX.bat) programs for sending/receiving. This configuration can be done from the Editran applications *modiperfi* or Modi*Connect.exe\* (run and follow the on-screen instructions)*. The migrated channels will not be functional until the Editran profiles are modified. \*ModiConnect.exe is a new Connect utility to facilitate the task of modifying Editran profiles to update them with Connect integration scripts. ## Important matters 1. The program attempts to translate the profiles to the new Connect format as best as possible, but this is not always possible and conflict files will be generated. For the file *conflictosREMOTOS.txt* it gives an explanation detailed enough about the problems when migrating. For the file *conflictosCANALES.txt* no specific information can be offered due to Connect's different operation. 2. *migraContactos.bat* will not perform the migration if it detects serious errors when checking the Editran profiles. 3. *migraCanales.bat* will try to migrate all possible channels. Those that could not be migrated are indicated in the conflict file log. 4. If the checks of *migraContactos.bat* are not met for some profile, contacts will begin to be created in Connect ignoring those that return an error. In the *conflictosREMOTOS.txt* file you can consult those that have returned an error. 5. User scripts from presentation profiles are imported into Connect channels and will be executed after Connect's own integration scripts. The migration program attempts to find the absolute paths of the scripts when these are relative in the Editran profiles; otherwise the Editran path will be used and it must be edited from Connect. 6. If a channel is modified from Connect it must be maintained exclusively from Connect from then on and its modification from the Editran applications should be avoided. This is because profile configuration from the Editran applications is not synchronized with Connect and changes made from those other applications do not automatically reflect in Connect's configuration. 7. If any command has been executed with --e, **do not** use this argument again unless the salidaP and salidaG files are deleted. 8. The name that the local codes will have will be the first one found alongside the first profile that has the local code, that is, if the local code "111222333" appears in two profiles and each has a different local name parameter value, Connect will use the value of the one that appears first in the profiles file. ## Possible errors 1. Not specified *-e* or *-f*. The application will inform the user how to perform the execution. 2. The Connect services are not running and an attempt has been made to use the profiles migrator. In this case the program will warn that it was not possible to connect to the remote server (Connect). 3. Numbered errors. These are internal program errors (bug) and the exact cause cannot be indicated. Report the problem to the Connect provider so it can be analyzed by the development team. ## Example of importing profiles from Editran First the following will be executed *migraContactos.bat -e.* ![Execution of migraContactos.bat -e.](https://64653979-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvdpBggYaSLH9X3nOAiMG%2Fuploads%2Fgit-blob-c5d323d0e9569857767a7a73050c742229690c8a%2Fimage179.png?alt=media) And then the following will be executed *migraCanales.bat -e.* ![Execution of migraCanales.bat -e.](https://64653979-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvdpBggYaSLH9X3nOAiMG%2Fuploads%2Fgit-blob-3e1d6229718f98b077cec425b6c5cca36c64bc1c%2Fimage180.png?alt=media) Next, the corresponding logs should be reviewed to check if there were contacts or channels that could not be added. ![Verification of contact migration.](https://64653979-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvdpBggYaSLH9X3nOAiMG%2Fuploads%2Fgit-blob-107a0e23b087f46617dd8bc2dcc0a749076eca47%2Fimage181.png?alt=media) ![Verification of channel migration.](https://64653979-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvdpBggYaSLH9X3nOAiMG%2Fuploads%2Fgit-blob-94009bf81f30bb4c9f2d088febdb08e203fd2e0b%2Fimage182.png?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 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/connect-v2.1-en/instalacion/migracion/perfiles.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.