Specifying a Record Parser

Service Development Help : Working with Flat Files : Creating Flat File Schemas : Specifying a Record Parser

Specifying a Delimited Record Parser for the Schema

Specifying a Fixed Length Record Parser for the Schema

Specifying a Variable Length Record Parser for the Schema

Integration Server can exchange all types of flat files but can process only certain types of flat files. Integration Server can process flat files in which:

The records in the flat file are defined using one of the following methods:

Delimiter. Each record in the flat file is separated by a delimiter.

Fixed length. Each record is a fixed number of bytes (for example, mainframe punch or print records).

Variable length. Each record is preceded by two bytes that indicate the length of the record. Records in the flat file can have different lengths.

EDI document type. This option is only for viewing existing EDI flat file schemas.

Note:

If you are using the webMethods Module for EDI to process EDI documents, you should use the wm.b2b.edi services to create your flat file schemas. This help system does not provide information about creating EDI flat file schemas for use with the webMethods Module for EDI. For more information and steps, see the webMethods Module for EDIINT Installation and User’s Guide . The EDI Document Type option is displayed for you to view existing EDI flat file schemas.

Each distinct record structure has a record identifier. If no record identifier is present, the record is parsed using a default record definition. For more information about default records, see Setting a Default Record.

If the flat file contains record identifiers, the record identifiers must be located in the same location in all records in the file.

Integration Server then can identify fields in these records based on either:

Delimiters. Each field is separated by a delimiter, and you can specify the Nth delimited field in a record to represent the record identifier. This can be used only when a field delimiter (and, if necessary, subfield delimiter) has been specified.

Byte position. Each field is defined by 1) the number of bytes from the beginning of the record and 2) the field length. This can be used regardless of whether a field delimiter has been specified.