Creating Conceptual Object Export Jobs
OneData conceptual objects are a logical representation of the relationship between multiple data objects (tables and views). A conceptual object export job exports the data in a conceptual object to either a file or a messaging object.
The export job saves data in XML format. When you export data to a file, you can send the file through email or save it to an FTP location. For information about the XML output options, see
Export Formats.
When the job exports the data, the incremental changes are detected based on changes at any level of the conceptual object. Whenever there is a change at one level, the job exports all the nodes under it.
To write the output file to a FTP location, you must first configure the FTP location. For more information about configuring FTP connections, see Administering webMethods OneData.
To create a conceptual object export job
1. On the Menu toolbar, click Data Interchange > Manage Export Job.
OneData displays the existing jobs.
2. Click Add a Job and complete the following fields:
Field | Description |
Name | Enter a name for the job. |
Description | Enter a description of the job. |
Job Type | Select Conceptual Object Export Job. |
Export Type | Default is the only export type allowed. It identifies full load and incremental load. |
Notification | |
Notification Recipients | Click the Select A Value icon to select the users or user groups to receive notifications. To search on a user or user group, enter the name in the search criteria field and click the Search Value icon or press Enter. To clear the values, click the Clear Value icon. |
Export data for all job steps... from this date till this date | Enter a date range to limit the records exported. For information about date fields in export jobs, see Job Date Ranges. |
Execution Options | Select the Rollback on Failure to roll back all changes in the remote database when the job fails. |
Log Exports | Select whether OneData creates a log of the export job. For information about the logging options, see Job Log Options. |
3. Define the conceptual object export job specific properties:
Field | Description |
Conceptual Object | Select an object from the list of available conceptual objects. |
XML output format | Define the XML format. For information about the XML formatting options, see Export Formats. |
Output for columns with zero-length values | Define how OneData handles empty columns in the XML output. For information about the options, see Export Formats. |
4. Choose whether to send the XML output of the job to either a file or a message object.
Field | Description |
Write to file |  File Name (Optional): Enter a file name. OneData overwrites the file every time the job runs. If you omit a file name, OneData generates the file name and creates a new file every time the job runs. E-mail Recipient(s): Enter the email addresses to receive the output file. Separate multiple emails with a comma. FTP Destination: Select a FTP destination. The job writes the output file to the selected FTP destination. |
Write to message object | Destination Message Object: Select a messaging object. The job sends the output to the selected messaging object. Header Information Option: Specify the information to include in the message output: Exclude: Excludes the job execution information from the JMS message. Include in message body: Includes the job execution information in the JMS message body. Include in message header: Includes the job execution information in the JMS message header. For more information about messaging objects, see Administering webMethods OneData. |
5. Click Save.
6. Create job steps to specify the data that is included in the export job. For information about creating a job step, see Adding Job Steps. 