Building Your Event-Driven Architecture : Service Development Help : Working with Flat Files : Creating Flat File Schemas
Creating Flat File Schemas
 
Creating the Flat File Schema
Specifying a Record Parser
Specifying a Record Identifier
Defining the Schema Structure
Setting a Default Record
Allowing Undefined Data
Creating an Area
Specifying a Floating Record
Editing a Flat File Schema
You can use Designer to create a flat file schema that Integration Server can use as a blue print for parsing and creating flat files.
Building a flat file schema is a process that involves the following basic stages:
Stage 1
Create the flat file schema. During this stage, you create the new flat file schema on the Integration Server where you will do your development and testing. For more information, see Creating the Flat File Schema.
Stage 2
Define the record parser and specify a record identifier for the flat file schema. During this stage, you associate a record parser with the flat file schema that will process flat files inbound to the Integration Server. You also specify how you want the record to be identified after it is parsed. For more information about defining the record parser, see Specifying a Record Parser. For more information about specifying a record identifier, see Specifying a Record Identifier.
Stage 3
Define the structure.During this stage, you specify the hierarchical structure of the flat file by creating and nesting record definitions or record references. For more instructions, see Defining the Schema Structure.
Stage 4
Set properties for the flat file schema.During this stage, you set up the ACL (access control lists) permissions, configure a default record, add areas, and allow undefined data for your flat file schema or dictionary.
Stage 5
Test the flat file schema.During this stage, you can use the tools provided by Designer to test the flat file schema. For more information, see Testing a Flat File Schema.
Note:  
When validation is enabled, Integration Server can generate errors for the Ordered, Mandatory, Validator, and Undefined Data properties. To enable validation, you must set the validate variable of the convertToValues service to True. For more information about this service, see webMethods Integration Server Built-In Services Reference.
Copyright © 2016 - 2016 Software AG, Darmstadt, Germany.

Product LogoContact Support   |   Community   |   Feedback