Custom Schema File

The custom schema file stores all the custom table and functional object definitions. The custom schema file works in combination with the core schema file to store the tables and functional objects that are available for migration, where the core schema file contains the application core schema tables and functional objects while the custom schema file contains the customized (customer-specific) schema tables and functional objects. Furthermore, the object definitions in the custom schema file override the object definitions in the core schema file, so if both files contain different definitions for the same table, the table definitions in the custom schema file will override the table definitions in the core schema file. All of the tables and functional objects listed in the two files are displayed in the Select Tables/Functional Objects page of the Migration Tool.

If a table or functional object that is listed in the core schema or custom schema file does not appear in the Select Tables/Functional Objects page, this may mean:

• The objects have been hidden via the Manage Migration Objects List. For more information about managing migration objects, see Manage Migration Object List.
• The objects have been previously compared and you selected the Hide/Filter previously compared objects check box.

By default, the Migration Tool only references the core schema file. To set your Migration Tool to point to a custom schema as well, select Administration > Change Configuration Settings, and then click Change to select your custom schema XML file. After you have configured the Migration Tool to reference the custom schema file, the configuration is saved to the migrationWizard.properties file.

For more information about the core schema file, see Schema File.