CSV Connector

Version 21.0.7884


CSV Connector


The CSV Connector can convert Comma-Separated Values (CSV) files into XML and also generate CSV files from XML.

Overview

XML is the primary format that ArcESB uses to manipulate data within a flow. Thus it is useful to convert CSV files into XML as a staging step for further processing within the flow, or to convert XML to a CSV file after the XML has been manipulated. Both of these operations can be accomplished with the CSV connector.

For details on converting CSV into XML please see the Converting CSV to XML section; for details on converting XML into CSV please see the Converting XML to CSV section.

Connector Configuration

This section contains all of the configurable connector properties.

Settings Tab

CSV Settings

Settings related to the core operation of the connector.

  • Connector Id The static name of the connector. All connector-specific files are held in a folder by the same name within the Data Directory.
  • Connector Description An optional field to provide free-form description of the connector and its role in the flow.
  • First line is header information Whether the CSV file contains a row of headers providing names or context to the values in the file.
  • Record Name The name of elements representing a row in the CSV file when converting to XML. Please see Converting CSV to XML for more details.

Local Folders

Settings that determine the folder on disk that files will be processed from, and where they will be placed after processing.

  • Input Folder (Send) The connector can process files placed in this folder. If Send Automation is enabled, the connector will automatically poll this location for files to process.
  • Output Folder (Receive) After the connector finishes processing a file, the result will be placed in this folder. If the connector is connected to another connector in the flow, files will not remain here and will instead be passed along to the Input/Send folder for the connected connector.
  • Processed Folder (Sent) After processing a file, the connector will place a copy of the processed file in this folder if Save to Sent Folder is enabled. This copy of the file will not be passed along to the next connector in the flow.

Other Settings

Settings not included in the previous categories.

  • Log Subfolder Scheme By default, logs for transactions processed by the connector will be stored in the Logs subfolder for the connector. For connectors that process many transactions, it may be desirable to further divide the logs based on the datetime they were generated. When this setting is set to Daily, logs generated on the same day will be grouped in a subfolder;; when this setting is set to Weekly, logs generated in the same week will be grouped in a subfolder; and so on.

  • Log Messages Whether the log entry for a processed file will include a copy of the file itself.
  • Save to Sent Folder Whether files processed by the connector should be copied to the Sent folder for the connector.

Automation

Settings related to the automatic processing of files by the connector.

  • Send Whether messages arriving at the connector will automatically be processed.

Converting CSV to XML

When a CSV file is transformed into XML, the resulting XML has the following structure:

<Items>
 <Record>
  <field_0></field_0>
  <field_1></field_1>
  <field_2></field_2>
 </Record>
</Items>

Each row (record) in the original file becomes a child of the root element ‘Items.’ The name of all record elements is determined by the Record Name setting option. Each record element then has child elements corresponding to the values in each row of the input file.

Some CSV files include a line of header information that provides context to the values in the file.
When the First line is header information setting is enabled, this header line will be parsed, and the parsed headers will be used as the element names for the value elements (the children of the record elements).
Otherwise, the value elements will be given generic names such as field_0, field_1, etc.

Converting XML to CSV

To convert XML to a CSV file, the input XML must have a ‘flat’ structure. This means that, disregarding the root element, the depth of the XML structure is 2. For example:

<Items>
 <film>
  <title>Citizen Kane</title>
  <year>1941</year>
  <runtime>119</runtime>
 </film>
 <film>
  <title>Sharknado</title>
  <year>2013</year>
  <runtime>86</runtime>
 </film>
</Items>

The XML will be interpreted as follows: Children of the root element will be treated as records (rows) within the resulting file, and children of each record element will be treated as the values in each row. If the First line is header information option is enabled, a header row will be inserted into the resulting CSV file with the names of each value element to provide context to the values. In the above example, this header row would consist of title, year, and runtime.

CSV Transformation: Using the XML Map Connector

Many data transformation flows use the CSV Connector in conjunction with the XML Map Connector.

Often, data enters an Arc flow in CSV format and should exit the flow in some other format (e.g. a database insert, an EDI file, an insert into a CRM or ERP data source, etc), or vice versa. Arc uses a single streamlined approach to these data transformation requirements:

  • Model the input format as XML
  • Model the output format as XML
  • Use the XML Map Connector to map between the input XML and the output XML

Thus the CSV Connector is commonly adjacent to an XML Map Connector in the flow:

When CSV files are the input to the flow, the CSV Connector converts a CSV file to XML and then passes that XML off to the XML Map Connector to be transformed; when CSV files are the output from the flow, the CSV Connector receives XML from the XML Map Connector and converts it into a CSV file.

The CSV Connector includes an Upload Test File feature to simplify the process of mapping the XML that represents a CSV file.

Upload Test File

An XML Map Connector requires a sample XML structure for both the Source/Input for the mapping and the Destination/Output for the mapping. The Upload Test File feature makes it easy to use the CSV Connector to generate a Source or Destination XML template.

In the Input tab of the CSV Connector, the More dropdown button includes the Upload Test File option. Select this option and browse to a sample CSV file on disk to instruct the connector to generate an internal XML model of this sample file.

Then, when an XML Map Connector is connected to this CSV Connector in the flow (and the flow changes are saved), the XML Map Connector can detect this internal XML model and use it as a Source File (if the CSV Connector is before the XML Map Connector in the flow) or a Destination File (if the CSV Connector is after the XML Map Connector in the flow).

Note that the structure of this Test File should be representative of all future files. In other words, all of the CSV files processed by the CSV Connector (and then the XML Map Connector) should have the same columns as the selected Test File. It may be necessary to set up multiple CSV Connectors and multiple XML Map Connectors to handle distinct CSV structures.

CSV Operations

In addition to the Operations provided with ArcESB, connectors may provide operations that extend functionality into ArcScript. Operations specific to the functionality of the CSV Connector are listed below.

csvListRecords

Loops over every record in a specified CSV file or string.

Required Parameters

  • file: The path to the CSV file.

Optional Parameters

  • data: If the CSV data exists as a string rather than stored in a CSV file use this parameter instead of file.
  • columns: The comma-separate list of columns to include in the output (if unspecified, all columns will be included).
  • requireheader: By default, the first row of data is interpreted as column headers; pass false to this parameter to use generic column names (e.g. c1, c2, c3).

Output

Any script within a csvListRecords operation will execute multiple times: once for each record/row found in the input CSV file/data. Within the operation, individual CSV values are accessible using the csv formatter. This formatter takes a column name as a parameter, and outputs the value in that column for the current record.

For example, imagine the CSV input data contains a set of items purchased in an order, and the name of the item is held in the ‘ItemName’ column. The following script generates XML containing each ‘ItemName’ value in an <Item> element:

<ItemList>
  <arc:call op="csvListRecords?file=myFile.csv">
    <Item>[csv('ItemName')]</Item>
  </arc:call>
</ItemList>