Managing Master Data with webMethods OneData 10.5 | Managing Master Data with webMethods OneData | Implementing webMethods OneData | Importing Data into Objects | Importing Data
Importing Data
You can import data into OneData multiple ways: from a delimited file, remote database, or an XML file, using the following mechanisms:
*Import job. Import data directly from the source system using a scheduled or ad hoc import job. Create the job and job steps by clicking Administer > Job Center on the Menu toolbar.
*Data Interchange Mapping. Define an interchange mapping to map columns from a source system to fields in OneData. With an interchange mapping, you define the relationship between the source and destination fields once and reuse these mappings as often as needed for import jobs. You can also use interchange mappings for data quality cleansing and data quality matching jobs.
Access the interchange mapping import feature directly from the Data Interchange > Configuration > Interchange Mapping 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. For more information about interchange mappings, see Working with Interchange Mappings.
For information about interchange mappings for data quality jobs, see webMethods OneData Consolidation MDM Guide.
The import feature is limited to users that have the appropriate security privileges for an object.
For more information about user privileges, see Administering webMethods OneData.
To import data from a remote database, you must have already configured the database connection within OneData. To import data from an XML or delimited file, ensure that the files exist in the FTP location.
For more information on configuring connections and FTP locations, see Administering webMethods OneData.
Import profiles are a way to save an import mapping definition so that you can reuse it the next time you import data from a file with the same mappings.
When working with mappings, to map a date in the source file to a timestamp column in the destination object, ensure that the date format in the source file exactly matches the date format defined in the user preferences, or the import may not work successfully. The date to timestamp conversion is performed during the import. For more information about imports, see Using an Interchange Mapping in Data Manager.
When importing data into temporal objects, if the primary key is a concatenated historical date and a qualified date, the End Data must be specified in the import file. If the end date is not provided, an error is returned. For temporal objects with a parent-child relationship, the effective date of the records of the child object cannot extend beyond the effective dates of the parent records.
If a reference key violation occurs during the import process, the values and line numbers of the rejected records are recorded in the log file. For other import errors, the log file records the error description and the line number of the record.

Copyright © 2011-2019 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.