File schemas can be used to define the contents one or more files that you intend to write to (publish) or read from (subscribe) in IBM® Rational® Integration Tester tests. For files that are made up of a number of records, a file schema can save users from having to write to or read from a file over and over again (that is, creating a publisher or subscriber for each record in the file). The file schema lets Rational Integration Tester iterate over the entire file, reading the wanted records according to the way the file is defined.
The file schema is used with the File Contents resource (created in the Logical View of Architecture School), which defines the file that contains the records to be processed. For more information about working with files in Rational Integration Tester, refer to Working with File transport.
The following example illustrates how to create a file schema that defines a file contents resource.
Conditions are used to help Rational Integration Tester understand the structure of the file that is being processed. If available for a condition, you can select a field within the record to use for matching the condition in the Value field.
In the example file schema that is shown below, the file contains a header record, a number of account records, and a trailer (footer) record. Within each account record, one or more account detail records can appear.
Record definitions can be moved and deleted by using the Remove Record, Move Up, and Move Down buttons. Conditions cannot be moved, but they can be deleted by using the Remove Condition button.
When finished, or at any time, you can click the Preview button to apply the file schema to the file to be processed, ensuring that the structure of the file is defined properly.
A preview of the file to be processed is displayed.
For All Available Bytes and Swift type records, no further information is required.
Field | Description |
---|---|
Update outbound message with packet details below | You can update outbound messages with the length of the remaining data for delimited records. To include this information in outbound messages (that is, when publishing), select the Update outbound message with packet details option. |
[Delimiters] | Select one of the following delimiters:
If you choose Other, you must specify a delimiting character. |
Process last empty packet | Valid when reading records. Select this option if the record ends with the delimiter you specified previously and you want to process one more packet as an empty string (""). Clear this option if the delimiter indicates that there are no more packets. |
Write token with last packet | Valid when writing records. Select this option if you want the packetizer to write a final delimiter character at the end of the file. |
Field | Description |
---|---|
Update outbound message with packet details below | You can update outbound messages with the length of the remaining data for delimited records. To include this information in outbound messages (that is, when publishing), select the Update outbound message with packet details option. |
Fixed Length | Select this option if the packets in the record are all the same length. Specify the number of characters in each packet. |
Token | Select this option if the packets are separated by tokens. Specify one or more characters for the token. |
Offset | Select this option if the packet length is determined by an offset. Specify the number of characters in the offset. |
Prefix | Select this option if the length of the packets is contained in a Prefix. The following
additional information is required:
|
Field | Description |
---|---|
Update outbound message with packet details below | You can update outbound messages with the length of the remaining data for delimited records. To include this information in outbound messages (that is, when publishing), select the Update outbound message with packet details option. |
Start Token | Specify one or more characters for the token that begins a record. |
End Token | Specify one or more characters for the token that ends a record. |
Field | Description |
---|---|
Update outbound message with packet details below | You can update outbound messages with the length of the remaining data for delimited records. To include this information in outbound messages (that is, when publishing), select the Update outbound message with packet details option. |
Select the ISO 8583 Schema | Select a Data Format Description Language schema that you have previously uploaded to the Schema Library. |
Field | Description |
---|---|
Update outbound message with packet details below | You can update outbound messages with the length of the remaining data for delimited records. To include this information in outbound messages (that is, when publishing), select the Update outbound message with packet details option. |
Start Token | Specify one or more characters for the token that begins a record. |
End Token | Specify one or more characters for the token that ends a record. |
End Token Data Length | The number of characters of data that can follow the end token. |
Field | Description |
---|---|
Update outbound message with packet details below | You can update outbound messages with the length of the remaining data for delimited records. To include this information in outbound messages (that is, when publishing), select the Update outbound message with packet details option. |
Remove newline character from the end of each record | Select a Data Format Description Language schema that you have previously uploaded to the Schema Library. |