Interchange Mappings
There are multiple ways to import records into OneData:
Using an import job. Import data directly from the source system using a scheduled or ad hoc import job. Create the job and job steps in
Data Interchange > Manage Import Jobs on the Menu toolbar.
You can schedule data quality cleansing and data quality matching jobs through the Job Scheduler. For more information about the Job Scheduler and import jobs, see Implementing webMethods OneData.
Using an interchange mapping. Define an interchange mapping to map columns from the source to the target. You can access the interchange mapping import feature directly from the
Data Interchange menu on the Menu toolbar, or while viewing data in Data Manager by clicking,
Import > Data Object Import or
Import > Conceptual Object Import on the Command toolbar. To view the existing data in
OneData from the Interchange Mapping screen, click the shortcut on the Command toolbar,
Go To Data Manager.
You must define at least one interchange mapping to perform customer consolidation. OneData uses the interchange mapping to compare data between the Consolidation (Staging) table and the Gold table when creating a new Gold record or linking to an existing one.
You can define additional interchange mappings to load data from external sources, such as a remote database table, a delimited file, an XML file, REST API, or JMS API into the Consolidation (Staging) table. The number of interchange mappings you need depends on the number of external data sources.
When OneData executes the interchange mapping, it loads data from the source into the Consolidation (Staging) object. It then executes the cleansing and matching process. The Consolidation (Staging) to Gold Interchange Mapping populates data from the Staging object to Gold Object when Gold records are created or updated and is executed when cleansing and matching are run separately.
When you define the interchange mapping for a data quality cleansing or data quality matching, OneData creates a default cleansing or matching job. Default jobs cannot be modified or deleted. For existing interchange mappings, if a default job does not yet exist, OneData creates a default cleansing or matching job when the batch cleansing or batch matching job is executed.