Integration Server 10.3 | Flat File Schema Developer's Guide | Concepts | How Is a Flat File Schema Used to Parse Records?
 
How Is a Flat File Schema Used to Parse Records?
 
Record Parsers
Record Identifiers
Extractors
Undefined Data
Default Records
To parse a flat file, use the pub.flatFile:convertToValues service in the WmFlatFile package. This service uses a flat file schema to parse flat files inbound to the Integration Server. The convertToValues service uses a record parser (Delimited, Fixed Length, or Variable Length) to parse the records in a flat file. For more information about the pub.flatFile:convertToValues service, see the webMethods Integration Server Built-In Services Reference.
After each record in a flat file has been parsed, each record must be identified. This is done using the record identifier. Identifying the record provides the definition of that record, as defined in the flat file schema using the flat file schema editor. The field values then are pulled from the record using the extractors defined in the flat file schema.
If the record cannot be identified (known as undefined data) and you have selected a default record, the field values are extracted from the record using the definition of the default record. If the record cannot be identified and you have not selected a default record, the field values are not extracted from the record. You can also format flat file data to meet the requirements of your back–end system or application using the Format Service property in the Flat File Structure tab of the flat file schema editor. For information about how to specify field format services, see Format Services.
Finally, the parsed record is placed in the output data based on the structure defined in the flat file schema. This process is repeated until all records in the flat file have been parsed.