![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
TIBCO BusinessConnect EDI Protocol powered by Instream uses the file FlatFileInitialDetector.csv, present in the EDI_HOME/config directory, for initial detection of a TEXT file to associate certain characteristics with the guideline as well as with trading partner information defined in the BusinessConnect configuration.The file FlatFileInitialDetector.csv provides general structural information for the incoming document; for example, it defines the key elements that are required, as well as optional elements such as MessageGroup, MessageType, Sender and Receiver ID/Qualifiers that are used to match the operation defined for the TEXT protocol, as well as for trading partner configuration. You will create a new entry in the file FlatFileInitialDetector.csv if there is a new definition associated with the TEXT guidelines and your TEXT document.Each entry in the file FlatFileInitialDetector.csv is associated with a TEXT document by matching the key entry value and any other optional element values entered in the file FlatFileInitialDetector.csv . The runtime engine goes through the list of entries mentioned in the file FlatFileInitialDetector.csv and checks if any one of its entries matches the TEXT document. The matching entry from the file FlatFileInitialDetector.csv is then used to give information to the BusinessConnect engine about:
• For more details about the file FlatFileInitialDetector.csv and its use, see Chapter 7, Type Detection.
1.
2. The Instream conversion engine compares the contents of the TEXT file with each entry in the file FlatFileInitialDetector.csv and tries to find a match.
3. Checking the key value: First it checks to see if the data file matches the key value defined in the file FlatFileInitialDetector.csv .
4. Checking the optional values: If the key value matches, the engine checks other optional field values if they exist, and matches against them.
− If the entry is a match, then the engine enters an appropriate value for MessageGroup and MessageType to identify the operation of the TEXT document, and tries to see if a value for Sender/Receiver ID and/or Sender/Receiver Qualifier is defined in any of the Field columns to match the trading partner identity.
− If there is no match, it will fail to get the MessageGroup and MessageType identification; identifying the operations would not be possible, and the right guidelines would not be matched.
− If MessageGroup and MessageType values are matched, but the Sender/Receiver ID/Qualifier values are not matched, then the BusinessConnect runtime engine would use the partner’s or host's default ID/Qualifier to match and the validation would try to proceed.
5. Checking the configuration fields: The configuration fields are SenderId, SenderDomain, ReceiverId, ReceiverDomain, MessageType, and MessageGroup. If MessageGroup is not identified, it is assumed to be TEXT.The configuration fields can be identified through the FlatFileInitialDetector.csv file.
6. Checking the configuration validation: The Preprocess process checks the configuration validation information against the Sender and Receiver configurations created in the repository using the TIBCO BusinessConnect console. Either the host or the trading partner could act as a sender or as a receiver.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |