DevOps Edition for Continuous Integration 10.5 | Service Development Help | Working with Flat Files | Testing Flat File Schemas | Creating a Launch Configuration for a Flat File Schema
 
Creating a Launch Configuration for a Flat File Schema
Use the following procedure to create a launch configuration for testing a flat file schema.
* To create a launch configuration for a flat file schema
1. In the Service Development perspective, select Run > Run Configurations.
2. In the Run Configurations dialog box, select Flat File Schema and click .
3. In the Name field, specify a name for the new launch configuration.
4. On the Flat File tab, in the Integration Server list, select the Integration Server on which the flat file schema for which you want to create a launch configuration resides.
5. In the Flat File Schema field, click Browse to navigate to and select the flat file schema, then click OK.
Tip: If you select the flat file schema in Package Navigator view and then select Run > Run Configurations, Designer populates the Integration Server and Flat File Schema fields automatically.
6. On the Input tab, in the Skip whitespace list, select true if you want Designer to ignore whitespace at the beginning of a record.
Note: If the flat file schema specifies a fixed length parser, Designer always preserves whitespace when processing a flat file document. For fixed length parsers, the Skip whitespace value is ignored.
7. In the Encoding list, select the encoding for the flat file that you will be testing.
8. Next to the File field, click the Browse button to navigate to and select the flat file that you want this launch configuration to use when testing the flat file schema.
9. Optionally, click the Common tab to specify general information about the launch configuration and to save the launch configuration to a file.
10. Click Apply.
11. Click Run to test the flat file schema now. Otherwise, click Close.

Copyright © 2017-2019 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.