Migrating Repository Objects

When you install Uniface 10, it creates a new Repository into which you can import and automatically migrate your sources.

For Enterprise Edition users, you can configure another supported database as your Repository, using Uniface to generate scripts for creating tables in the appropriate DBMS.

Caution: Do not run Uniface 10.4 against an earlier Repository, and do not use earlier meta model definitions in Uniface 10.4.

Uniface provides an automatic migration path when importing XML export files from supported Uniface versions. This is only possible when the XML file or files meet the following criteria:

  • They were created in Uniface 9.6, 9.7, 10.3, 10.2, or 10.1.

  • They were created using formal Uniface export facilities:

    • Export Repository Objects form. In Uniface 10, this is available from Main Menu ( ≡ )> Export; in Uniface 9 from Utilities >Export.
    • $ude("export") ProcScript function
    • Actions > Export in Uniface 10.3, although this will not include global object libraries .
Note:  Uniface 10 refuses to import XML files that are produced in earlier versions, or using Uniface 9 data copying facilities (Tools > Convert Data), /cpy on the command line, or $ude ("copy").

When importing and migrating XML files, Uniface does the following:

  • Checks the Repository version from which the XML file was exported.
  • Imports the XML file, if the import file was generated by an export command from a valid Repository.
  • Migrates the imported data to the new Repository structure.
  • Writes summary information about both import and migration actions to the log file, including any possible import and migration errors encountered.

The following topics describe the Migration Utility and the actions it performs, how to prepare and migrate to Uniface 10, the issues you may encounter during migration, and the steps to take to solve these issues.