Mapping Validation
When you develop a mapping, you must configure it so that the Data Integration Service can read and process the entire mapping. The Developer tool marks a mapping as not valid when it detects errors that will prevent the Data Integration Service from running the mapping.
The Developer tool performs the following types of validation:
- •Connection validation
- •Expression validation
- •Object validation
- •Parameter validation
- •Synchronization validation
Connection Validation
The Developer tool performs connection validation each time you connect ports in a mapping and each time you validate a mapping.
When you connect ports, the Developer tool verifies that you make valid connections. When you validate a mapping, the Developer tool verifies that the connections are valid and that all required ports are connected.
The Developer tool performs the following connection validations:
- •At least one input object and one output object are connected.
- •At least one mapplet input port and output port is connected to the mapping.
- •Data types between ports are compatible. If you change a port data type to one that is incompatible with the port it is connected to, the Developer tool generates an error and invalidates the mapping. However, you can change the data type if it remains compatible with the connected ports, such as Char and Varchar.
Expression Validation
You can validate an expression in a transformation while you are developing a mapping. If you do not correct the errors, error messages appear in the Validation Log view when you validate the mapping.
If you delete input ports used in an expression, the Developer tool marks the mapping as not valid.
Object Validation
When you validate a mapping, the Developer tool verifies that the definitions of the independent objects, such as Input transformations or mapplets, match the instance in the mapping.
If any object changes while you configure the mapping, the mapping might contain errors. If any object changes while you are not configuring the mapping, the Developer tool tracks the effects of these changes on the mappings.
Parameter Validation
To validate mapping parameters in the Developer tool, view the mapping with resolved parameters and validate the mapping.
When you resolve mapping parameters, the Developer tool generates a run-time instance of the mapping that shows the resolved parameters at run-time. Validate the run-time instance of the mapping to validate the mapping parameters. You can validate mapping parameters that use the default parameter values in the mapping, a parameter set, or a parameter file.
Synchronization Validation
You can validate run-time synchronization of dynamic sources and targets.
If you configure a dynamic mapping that uses data sources that are set to synchronize at run time, you can preview the run-time instance of the mapping to validate the synchronization. To preview the run-time instance of the mapping, view the mapping with resolved parameters. When you view the mapping with resolved parameters, the Developer tool generates a run-time instance of the mapping that reflects run-time changes in dynamic sources and targets. Validate the run-time mapping to validate data source synchronization.