evaluates the rules in the mapping template, it requires the names and properties of the columns available in the source and target tables.
mapgen
uses the column names and properties to determine the ports in the mapping transformations that conform to the rules.
mapgen
also requires the name, object type, repository name, and folder name of the shortcuts to sources, targets, and transformations used in the mapping template. Export the sources, targets, and shortcuts to make them available to
mapgen
.
Export the following objects to the tabledefs folder:
source definition
target definition
shortcut to source definition
shortcut to target definition
shortcut to transformation
lookup source for Lookup transformation
If you do not export shortcuts to targets and transformations,
mapgen
creates the targets or transformations based on the rules for the links to the target or transformation.
Use the following rules and guidelines when you export the source and target definitions and shortcuts to sources, targets, and transformations:
mapgen
looks for all the files in one folder. By default, it looks for the files in the Mapping Architect for Visio table definition folder:
\<
PowerCenterInstallationDir
>\Client\MappingTemplate\tabledefs
If you export the files into a different folder, specify the folder path name when you run
mapgen
.
mapgen
requires all XML files in the folder to be valid PowerCenter XML files that comply with powrmart.dtd.
mapgen
reads all XML files in the directory. To ensure that
mapgen
can read all XML files in the folder, keep only valid PowerCenter XML files in the table definition folder.
Since
mapgen
reads all files in the table definition folder, you can export multiple source definitions to one XML file. For example, the folder can contain one XML file that describes five sources or five XML files that each describe one source definition. Similarly, you can export shortcuts to multiple transformations to one XML file.
mapgen
uses the first definition it finds in the table definition folder. For example, if you have ASources.xml that has a source definition for EMPLOYEE and BSources.xml that also has a source definition for EMPLOYEE,
mapgen
uses the first EMPLOYEE source definition it finds. If the source definitions are from different folders or have different columns and properties,
mapgen
can use the wrong table definition for the mapping.
Create separate folders for table definitions with the same names but different properties to ensure that
mapgen
uses the correct table definition for the mapping. Then supply the appropriate folder name when you run