Migrate Out Data Model and Configuration Components - Precisely_EnterWorks - EnterWorks - 11.0

EnterWorks Guide
Product type
Software
Portfolio
Verify
Product family
EnterWorks
Product
Precisely EnterWorks
Precisely EnterWorks > EnterWorks
Version
11.0
Language
English
Product name
Precisely EnterWorks
Title
EnterWorks Guide
Copyright
2024
First publish date
2007
Last updated
2025-01-07
Published on
2025-01-07T07:44:20.997000
Note: The migration flow should always be from DEV to QA then to PROD. Development changes and enhancements should always be performed in DEV, migrated to QA and tested, then migrated to PROD. Following this process enables migration to properly identify the components to update, as well as providing the most reliable migration and deployment experience.
Warning: These instructions only discuss how to use the migration tool. For a detailed description of when you should migrate components, which components should be migrated together, when you should use the overwrite option, how migration of the data model fits in the EnterWorks deployment process, and how to migrate EPX, see Deployment and Migration Best Practices.

To migrate the EnterWorks components out of an EnterWorks environment in preparation for migrating them into a target EnterWorks environment:

  1. On the source environment, log into the Classic UI as an administrator.
  2. Open the Feature bar, open the Migration folder, and select Migrate Out. The Migrate Objects Out page will appear.
  3. Edit the options:
    • Migration Zip File Name: The name of the zip file that will hold the migrated out components. A time-based number will be appended to the file name to ensure that the filename is unique.
    • Migration Specification File Name: The name of the specification file that will be generated by the migrate out process. This file will contain key-value pairs that identify the components you selected to be migrated and it will be used to tell EnterWorks how to migrate in the components. A time-based number will be appended to the file name to ensure that the filename is unique.
    • Migration Specification File on Server: (Optional) You can use the dropdown menu to select an already existing migration specification file. If you do, EnterWorks will use the migration specification file to prepopulate the list of objects that will be migrated out. When you get to the step in the migration process when you specify the objects to migrate out, you can change any of the prepopulated choices. Any changes you make will not be saved back to the existing migration specification file. The changes will be reflected in the new migration specification file.
  4. Click Next.
  5. The Select Objects to Migrate page will appear. It consists of lists of all the migratable components.
    On the first row of the page you can:
    • Select All: Check or Uncheck to select or deselect all the components in the migration file.
    • Show All / Hide All: to expand or collapse all the lists.
    On each list you can:
    • Expand or collapse a list by selecting + or – to the left of the list's name.
    Select the components you want to migrate out.
  6. When you have finished selecting the components to migrate, scroll to the bottom of the list and select Migrate.
  7. Check the Job Monitor to see the progress of the migration. You may need to refresh the Job Monitor tab one or more times before the Status shows Completed.
  8. Two migration files will have been created in: 
    
            <drive>:\Enterworks\shared\migration

    They are:

    • <your-file-name>.zip: This contains the migrated out objects.
    • <your-file-name>.msf: This is the migration specification file.
  9. To download the log file for the migrate out procedure, in the Job Monitor, click the job's Download Log File icon .