The File I/O receiver stamps the outgoing XML messages with a unique message group identification, YantraMessageGroupID before it is sent to the next component in the service definition framework. Once the end of the file is reached, an EOF message is created with the same message group ID. This EOF message is useful if special processing needs to be done at the end of each file.
If you are using the Sterling Selling and Fulfillment Foundation File IO adapter component, the same unique message group ID is added and the message header is appended to each message by default.
The following are the rules for creating EOF messages when using a third party component and integrating with Sterling Selling and Fulfillment Foundation:
<EOF YantraMessageGroupID="Mandatory" />
The steps involved in creating EOF messages and processing the messages in a JMS queue or a database is explained in detail with a sample XML file as an input to the File I/O adapter.
The following figure shows the service framework with a File IO component.
<Items Attr1="Value1" Attr2="Value2" Attr3="Value3" >
<Item ItemId="Item1" />
<Item ItemId="Item2" />
<Item ItemId="Item3" />
</Items>
If the input files are non-XML files then the root node attributes does not get included in the EOF node. It would contain the attributes given below:
<EOF YantraMessageGroupID="file1.txt.001" FileName=""
FileSize="" LastModifiedTime="" />