Migrate Profiles Between Environments

In this page, you will learn how to transfer profiles from one environment to another.

This process includes exporting .profile files in MC package form, pre-TFS commit manipulations, and importing the package in the destination environment either via Message Center Editor or via  IWS. You can use IWS as an alternative to import packaged profiles.

This functionality requires Monitoring Tool v1.0.0.126 or higher and IWS v1.0.1.662 or higher.

Export Profiles

To export profiles:

  1. Launch the EJM Monitoring Tool.

    EJM Monitoring Tool
  2. Select the Activities tab.

    EJM Monitoring Tool - Activities tab
  3. Select profiles for migration (multiple selection is allowed).

    EJM Monitoring Tool - Selected Profiles
  4. Right-click the group of selected profiles and then select Export Profile(s).

    Export Profiles right-click option

    The system downloads the profile data and displays the Export Dialog box.

    Export Dialog box
  5. In this step, you can clear the check boxes for unnecessary profiles to exclude them from the export.
    File preview is available in the right pane.

    Export Dialog box - Clear Check Boxes for Unneeded Profiles
  6. Click Next
    You see the final dialog box, where you can enter the name for your MC package, provide an informative description, and select an export store folder for the package.

    Export Dialog box - Package Description and Store Folder

    The export will have similar contents as follows:

    Documents Library for Export Example

     

    • tpe folder – contains all data.

    • export.conf - Migration Wizard metadata – this file is used by IWS for importing (can be missing). Note: This file must be deleted before you copy the folder to TFS. 

    • eagle_iws_service_data_empty package – "fake" stream package used for importing by MCE data files without streams.

    • _*main.pkg package – main package, contains links to all data files and packages. This is the file you use to import exported data later. 

Commit to TFS

Assuming you are storing in source control (in this case, TFS), follow these steps:

  1. Before committing to TFS, rename one of the .pkg files to avoid a conflict of names.

  2. Rename eagle_iws_service_data_empty.pkg to my_test_stream_package.pkg (for example).

  3. Open the *main.pkg file find the line with the old file name:
    <include>  <package>eagle_iws_service_data_empty</package></include>

  4. Enter the new name:
    <include>  <package>my_test_stream_package</package></include> 

  5. Delete the export.conf file. 

  6. As a result, your export folder should look like this:

    Documents Libarary for Export to my_test_stream_package
  7. Commit these three items to TFS.

Import Profiles with Message Center Editor

To import profiles with Message Center Editor:

  1. Open Message Center Editor, go to Message Center Streams tab and click Import Stream to launch the import stream wizard.

    Eagle Message Center Editor - Import Stream option

    You see the Import Stream wizard. 

  2. Under Select package to import on server, navigate to the folder and select the main package file.

    Import Stream wizard - Select package file box

     

    Import Stream wizard - Import stream package page
  3. Preview the content of the package you are about to import. You can choose to exclude some files on this stage. To do that, clear the check box next to their names.

  4. If you are prompted with information about eagle_iws_service_data_empty already existing, just click Yes to overwrite it. This stream is always used to import sources without streams links.
    You will also see csv-0.rsf file marked as missing in the list. It refers to eagle_iws_service_data_empty fake stream, so just ignore this message.

  5. Click Next.

  6. Click Next and choose the Create stream(s) option. Click Next.

  7. Click Finish.
    The process of import starts shortly.

    Import Stream wizard - Finish page
  8. To check your newly added profile(s) go to the Monitoring Tool - Activities tab.