Managing Master Data with webMethods OneData 10.5 | Managing Master Data with webMethods OneData | Implementing webMethods OneData | Importing Data into Objects | Job Steps in Import Jobs | Working with Job Steps in Import Jobs
Working with Job Steps in Import Jobs
Use the following procedure to create job steps for an import job.
* To create a job step in an import job
1. On the Menu toolbar, click Manage Import Job.
OneData displays the existing jobs.
2. Click the Edit icon corresponding to the job that you want to edit.
3. In Manage Job Steps, click Manage Job Step.
4. Click Add Import Job Step to add a new step.
5. Define the following job step details:
Table 3. Job Step Field Descriptions
Job Step Name
Enter a job step name.
Job Step Description
Enter a description of the job step (optional).
Destination Object
Select the object type as data object or conceptual object. Then select the object from the field (populated with objects from the current repository in which you are logged in).
Job Type
Shows the type of the import job.
Update existing entries
Applicable only for data objects. Select this option to update existing entries (in addition to insert) based on the primary key or alternate key specified.
Note: If selected, you can choose an alternate primary key in the next screen.
Enforce partial commit
If selected, commits changes in the database at the end of the import process. The job commits the inserted or updated records during the import, regardless of whether job succeeded or failed.
Currently OneData processes the records in batches of 100, though the commit is performed only at the end of the import process. This batch size can be configured through the OneData property, onedata.interchangeexecution.batchsize.
Fast Load
If selected, bypasses workflow validations to improve performance.
Note: Requires ADMIN role privileges.
Interchange Mapping
Applicable only for import jobs in Nova mode. Select an interchange mapping for import. For information about interchange mappings, see Working with Interchange Mappings.
Note: If you are using SQL Server, you must select an interchange mapping to save the job step.
6. Complete the database or FTP details corresponding to the type of import job:
Import Job Type
Connection Details
Remote Data base Type
*Remote entity list. Select a source table from the remote database.
*Enforce where clause on remote entity. (Optional) Specify any condition to control the data that is imported.
XML/XSD Import
*FTP Source. The FTP destination defined in the job.
*Import from source XML file. Select the XML source file.
*XSD file for source XML file. Select the corresponding XSD file for the selected XML source file.
Delimited File Import
*FTP User Name. The FTP destination defined in the job.
*Import from file. The FTP username defined in the job.
*Delimiter. Select the source file from Available files at selected source or specify a File Name if the source file does not exist.
*Delimiter. Select the delimiter used in the source file. For delimiters other than tab and comma, select Other and specify the delimiter in the text field.
*Text Qualifier. Specify the text qualifier used in the source file.
*Header row present at line. Specify the line number of the header in the source file. Default value is 1.
*Start import at row. Specify the line number from which the import should start. Default value is 2.
7. Click Next and map the columns between the remote table and source table.
Note: If the Destination Object is a conceptual object, then you must select the related objects for import and select an alternate primary key before mapping the columns. While selecting an alternate primary key, the default is the primary key of the destination object.
8. In the Column Mapping screen, map the columns between the source and destination objects. To see the job step details, expand the Import Job Step.
The file contents and columns display for delimited file import jobs. The job uses the delimiter to detect the number of columns in the source file. If the column names in the delimited file are the same as the physical column names in the object, the columns are automatically mapped in the Import Mapping screen. You can change the mappings, if necessary.
Table 4. Import Column Mapping Field Descriptions
Remote Source Mapping
Select the source column from the Source Mapping Column.
Destination Object <Object_Name_Mapping>
*Destination Table Mapping. Select the destination table for the selected source column.
*Column Mapping. Select the corresponding OneData destination column.
*Description Column Mapping. Select the OneData column to display as a reference column. You can only select a value if the DECODE option is selected.
*Default Value. Specify a default value to populate in the destination column if the source column is null.
9. Click Save.

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.