XI - File Content Conversion

...Previous

                       Developments on Integration Directory. 

1.       Configuration of Sender File Adapter   

Here specify Message Protocol as ‘File Content Conversion’.  

Document Name and Namespace correspond to the message type from the Integration Repository. 

Recordset Name defines the root node under which rest of the XML will be created. 

Recordset Structure defines the name and occurrence of each sub-node in Recordset Structure. In this example we have only one occurrence of sub-node Emp_Header and Emp_Summary and unbounded occurrences of sub-node Emp_Weekly_Det. 

Key Field Name and Key Field Type helps in differentiating different substructures. In this case Key =1 implies Emp_Header node, Key = 2 implies Emp_Weekly_Det node and Key = 3 implies Emp_Summary node.

Additional Parameters are given below. 

• <node>.fieldFixedLengths – comma-separated ordered list of field lengths in the particular node
• <node>.endSeparator – identifies end of record
• <node>.fieldNames – comma-separated ordered list of field names in the particular node
• <node>.keyFieldValue – Value of the key field
• <node>.keyFieldInStructure – ‘ignore’ (without quotes) indicates that the Key field should not be generated in the resulting XML whereas ‘add’ (without quotes) indicates that it should be added.

2.       Configure Receiving File Adapter  

3.       Configure Receiver Agreement  

4. Configure Sender Agreement. 

5.       Configure Interface Determination. 

6.       Configure Receiver Determination.

On Executing the Scenario we will get the output file in XML Format.