Migrating configuration files in M3 UI Adapter

Use this procedure to import configuration files such as personalizations and scripts to the M3 UI Adapter database.

Note: You must create a zip file of the data files to migrate.
  1. In LifeCycle Manager, locate the M3 UI Adapter application.
  2. Right-click the M3 UI Adapter application > Manage Application.
  3. Click Advanced.
  4. Under the Migrate function, click Browse. Select the zip file containing the files to migrate.
  5. Click Import to migrate the data files to the database.

    The migrated files can be viewed from M3 H5. From the application menu of H5, select Administration Tools > Administration Tools > Personalizations tab. For more information about the Personalizations tool, see information about admin activities for M3 H5 in the M3 Core Administration Guide.

Migrating mne data files from an earlier version of M3 UI Adapter

If you want to migrate data files from a previous installation of M3 UI Adapter, you must access the contents of the mne_data folder, and then package them into a single zip file. When creating the zip package, you must zip the subfolders but exclude the top level mne_data folder. The mne_data folder contains these subfolders:

The same structure for creating the zip file should be followed even if you want to migrate only one category of data files. For example, if you want to import only the user settings files, then the zip package must contain the User Settings as the top folder.

When importing Customizations, however, you have the option to change the way contents are organized. (This change must be performed before creating the zip file.) Customizations contain a list of folders, for example:


If you retain this structure, then all the IDs in the list (except GLOBAL_CUSTOMIZATIONS) will be added as a type User after the migration. You would then need to identify the IDs that represent Roles, and then change their type to Role by using the Personalizations tool in M3 H5. However, what you can do instead is to put files of the same type in a new folder. The new structure must be such that the new folders are now directly under Customizations. The new list of folders under Customizations can look like this:


The Global folder contains the global customizations, the Role folder contains the role-based customizations, and so on.