Importing a migration file

Use the following instructions to import configuration changes by using Import Configuration.

Important: Do not manually make changes to the application configuration during the import. Doing this can corrupt the data or result in errors. If this occurs, you must re-export the data before you attempt the import again.

Before you begin

  • If an import, export, or validate process is currently running on the system, you must wait until processing is complete before you submit another import, export, or validate job.
  • The source and target environments must have the same version and patch level of OpenPages®.
  • Ensure that any dependencies that are not included the migration file are imported first. For example, if you are migrating profiles and the profiles use reports on the dashboard, import the reports manually before you import the profiles.

Procedure

  1. Log on to the target OpenPages application as a user with the ImportConfiguration permission and read and write to the Migration Documents folder.
  2. Click Open Administration menu Administration menu > System Migration > Import Configuration.
  3. Select the migration file (.jar or .xml).
    • If the migration file is on your local system, click Local drive, and then click Add file.
    • If the migration file is in the repository, click Server repository, and then click the file that you want to import.
    The Review Items pane shows the items that will be imported, if those items are supported by the environment migration user interface. If you are importing other items, such as role templates, the items are not displayed, but they are imported. For more information, see Supported migration items.
  4. Click Import.

Results

Note: If you imported Views, the priority order of the imported Views might have a conflict with the priority order of the existing Views. Review and update the priorities to resolve any conflict.

If The requested operation could not be completed is displayed, check the migration file. The file must be either a migration JAR file or an ObjectManager XML file.

If Completed With Errors is displayed, review the status messages on the History tab for information about the errors and review the Environment migration best practices. You must fix the errors before you import the migration file.