DataFlux Data Management Studio 2.5: User Guide

XML Input Node

An XML Input node specifies an XML file as an input in a data job. It reads selected pieces of XML and presents them collectively as rows in a table. If the XML source file contains multiple tables, use one XML Input node per table.

The XML nodes support reading XML files and writing XML output. Because XML is traditionally hierarchical, the nodes select certain portions of the XML presented in the XML Input node and present the information in tables for processing. A separate XML Input node is needed for each table in the XML source file. Once complete, you can output the information back into XML using the XML Output node.

NoteNote: For Profiles, use the XML Input node to extract your data into a text file or database, and then profile that text file or database. See also the usage note: Handling Large XML Files with XML Input Nodes or XML Output Nodes.

The properties dialog for this node includes the following elements:

Name - Specifies a name for the node.

Notes - Enables you to open the Notes dialog. You use the dialog to enter optional details or any other relevant information for the node.

XML input file - Specifies the full path to the XML input file. Select one of the following processing options:

Use XQuery from file - Specifies the location of the XQuery file.

Use XMLMap from file - Specifies the location of the XMLMap file. You can use SAS XMLMapper software or you can write a custom XQuery to convert the source XML into a compatible XML map. This node will work with either XMLMap version 1.9 or XMLMap version 2.1. Version 1.9 XMLMaps can be created by the SAS 9.2 SAS XML Mapper. Version 2.1 XMLMaps can be created by the SAS 9.3 XML Mapper. For information about obtaining the SAS XML Mapper, see How can I obtain a copy of the SAS XML Mapper?. For information about essential settings needed to use SAS XML Mapper, see How can I make the SAS XML Mapper work with the XML data job nodes?.

You also need to specify values for the following related fields:

No XQuery or XMLMap - Specifies that neither an XQuery nor an XMLMap file is used.

Additional Options - Enables you to set more optional parameters for the XML Input node. The following options are available:

Maximum number of rows to return - Specifies the maximum number of rows to process. When left _null, all rows are processed. The default is 0.

Number of rows per RowSet - Specifies the number of rows to place in each returned RowSet. The default value is 100.

Maximum number of queued RowSets - Specifies the maximum number of queued RowSets. The default value is 2.

Additional classpaths - Specifies additional Java© classpaths to search.

The Fields section of the properties dialog includes the following elements:

Fields Table - Enables you to define each field in your text file, including field name, field type, and field length. The following field types are available:

STRING - An ordered sequence of text or symbols

INTEGER - A number from the set of integers

REAL - The set of real numbers expressed as decimals

DATE (MDY) - Date in the order of month, date, and year

DATE (DMY) - Date in the order of date, month, and year

DATE (YMD) - Date in the order of year, month, and date

BOOLEAN - True or false

You can click Add to define a new field and use the up and down arrows to change the order of fields. Finally, you can click Delete to remove field definitions.

Import - Displays the Open dialog and enables you to restore a file layout from a .dfl file that you have exported.

Export - Displays the Save As dialog and enables you to store a given file layout that can be shared for parsing other input files. In this case you can set the text qualifier and the delimiter and store the file layout to create. The Export option lets you save the file layout as a .dfl file.

You can also access the following advanced properties by right-clicking the XML Input node in the data job:

Documentation Feedback: yourturn@sas.com
Note: Always include the Doc ID when providing documentation feedback.

Doc ID: dfU_PFInput_XML.html