The File Inbound endpoint is used to read comma-separated files (CSV). With this files objects are transformed into the UT XML format and stored in the UT database. Each line of the file stands for an object and is first tranformed into a simple XML format. Based on the messagequantity parameter this format has one of the following structures:
Messagequantity=One Message per Line:
<row>
<field>value1</field>
…
<field>valueN</field>
</row>
Messagequantity=One Message per File:
<rows>
<row>
<field>value1</field>
…
<field>valueN</field>
</row>
<row>
<field>value1</field>
…
<field>valueN</field>
</row>
…
</rows>
Forward, using XSLT, the format is converted into UT XML format. The XSL file can be determined via the Service Point with the XSL file parameter. By clicking on the icon beside, it will open a text editor to modify the XSL file. It is important to pay attention to the separator, which must match the separator in the CSV file. By default, the separator is set to semicolon. After the file was successfully imported into geodatabase, the CSV file is moved into the archive path and then deleted from the original directory. To avoid this scenario, no parameter must be entered in the archive path. From here it is also possible to import multiple files at a time. This is done using the wildcard filter.
Example:
The following files should be read from C:\ drive
Test1.csv, Test2.csv, Test3.csv
This can be defined by specifying a "*" wildcard pattern in the file name:
C:\Test*.csv
The following table provides an overview of the File Inbound Parameter:
Parameter |
Value |
Required |
|---|---|---|
Name |
Name of the Service Endpoint. |
X |
Type |
Type of the Service Endpoint. The value is preset with “File Inbound” and cannot be changed. |
X |
Description |
Description of the Service Endpoint. |
|
Path |
Path to the CSV file or files. Here a wildcard filter can be specified. Example: C:/Test*.csv |
X |
Archive Path |
Path in which the CSV file is to be moved. |
|
Delimiter |
Symbol, used to separate values in the CSV file. |
X |
First line is header |
Supported values are: •false •true |
X |
Header as XML names |
Supported values are: •false •true |
X |
File Encoding |
Encoding of the file to be read. Supported values are: •ISO-8859-1 •UTF-8 •UTF-16 •US-ASCII |
X |
Quantity of Messages |
Via this ComboBox it is specified if either one Message per Line or one Message per File is to be sent to the target system. |
X |
XSL Parameter |
Optional parameters that can be used in the transformation into the UT XML format. |
|
XSL file |
The XSL file defines the transformation process that converts incoming XML data into UTI XML format, enabling the data to be processed effectively. |
X |
Target version |
The SDE Version of stored data. |
X |
Outbound endpoint |
Additionally redirects the message to an outbound endpoint. |
|
