Migrator » Features
| Below the major functional Migrator areas are listed for a brief overview. For a more detailed introduction a special PDF document is available in the Downloads page once logged in. Please visit the Customer Area to sign-up first if you do not have a login yet. |
|
Migrator - Projects |
|
 |
Within a project both the source and the target database systems are specified (if applicable) to retrieve corresponding structural information for tables and fields. Also all important settings for later SQR program generation are defined here, like naming conventions for import and export scripts, destination folders for storage. The most important settings are the actual program templates for each the export and import scripts for SQR. |
Migrator - Tables |
|
|
All information collected from any source/target database system is stored within the Migrator's own repository and is shared across all projects. Since each project defines it's source/target systems with a so called "Save Name", every table is keyed by this as shown in the "DB-Name" column. Each table may also contain additional information with regard to it's actual type (Table/View), row count etc. |
Migrator - Fields |
|
|
The Fields view displays all fields associated with the currently selected table. However, buttons for navigation as well as filtering are available. The tabular display contains columns for field properties like key, type, length, decimal position, description and default value. If applicable, information like description and default values are also collected from PeopleSoft repository, but are free to be customized by the user at any time. The term "Fields" is used equally to "Columns" within the Migrator. |
Migrator - Programs |
|
|
By design for each table (or datafile) that needs to be migrated/interfaced, a program entry within the Migrator is created (either automatically or manually). Each program defines important settings for both the export and import script generation. The settings influence the actual program generation, such as naming conventions, data import rules (Update/Insert), data file's value separator etc. After each SQR generation of a program copies of the generated SQR programs are stored. |
Migrator - Mappings |
|
|
Mappings are the most important part of any migration process. For each field on both the source and target side a mapping should be defined. The code generation automatically takes care of most data type conversions, but sometimes the default may not be sufficient. Then custom SQR code may be attached to either to the export and/or import side to e.g. perform special conversion, procedure calls or other plain SQR code. Special color coding is applied for each mapping dependent on mapping status or datatype differences. |
Migrator - Code Blocks |
|
|
Code blocks, which are directly related to programs, offer a flexible way to inject custom SQR code to pre-defined locations in the export and/or import script upon generation. Each code block is attached to either a specific mapping or a Code Type, which is a pre-defined location within the SQR program template. Custom code types may also be maintained within the Migrator options. As an example a code block may be defined to specify include statements for custom SQR files by using the Code Type "IncludesTop". Within the Migrator Options also global code blocks for pre-defined code types may be defined which are triggered on table/field names and - if applicable - automatically added to mappings automatically. |
