If your integration tool does not have a catalog or metadata repository to store all mappings used across the organization, this tool can be used to document the mappings and allow them to be stored in a content and/or knowledge management system.

Use an appropriate naming convention for holding metadata about the mapping contained in the tool. For example: mapping_<source>_<dataobject>_<target>.xlsx will categorize this spreadsheet as a mapping specification between a source and target system for a specific data object.

This tool should be used by a business systems analyst and/or a data steward as input to integration specifications.

This tool can also be used by an integration specialist or application developer hand coding a data map if the integration tool being used does not offer a visual mapping capability, or the mapping is too complex to put into a visual tool.

Also In

Select and Implement an ESB Solution

Vendor Evaluation

Also In

Optimize the Organization’s Data Integration Practices

Ensure the organization’s data accurately flows to the critical downstream IT and business processes through effective data integration.

Related Content


Get Access

Get Instant Access
To unlock the full content, please fill out our simple form and receive instant access.