Skip to end of metadataGo to start of metadata
Converting XML document to text format at the receiver side. As of in our normal scenarios we use the File Content Conversions, this document tells you the alternate way to use those FCC possible using some modules of the particular file adapter.
Vikram, if I understand correctly you are able to change input XML payload? If so, solution may be quite easy and you are on the right track. You will just need to specify two recordset structures with recordset 1 handling your 'header' and taking its values from 'Detail' node of your input XML and recordset 2 handling all the 'body' data taking values from 'firstname', 'lastname', 'city'. Define Content Conversion Parameters 14. If you have selected File Content Conversion as the Message Protocol, you can convert an XML document to a text file. Select the Content Conversion tab page. More information: Converting XML in the Receiver File/FTP Adapter to Text Format. Define Variable Substitution for Target Directory/File Name. XI - File Content Conversion.Previous Developments on Integration Directory. 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.
Design your Repository objects, then in your Configuration for specific receiver file adapter we will be going to use suitable Modules in the module tab of communication channel. Though it has the same functionality like File Content Conversion in the message protocol option, this document just shows you an alternative approach to that.
Using the Module
In a real time scenario I have been try using the modules to ZIP the actual message payload, when handling a huge messages, there I came across to use the module which helps me to convert the content with in.
Converting XML document to text format at the receiver side.
What Is Sap Pi 7.0
- You can define Recordset type to be displayed as text with fixed field lengths, user defined separators etc., at the receiver using module StrictXml2PlainBean.
In the actual scenario you need to define File as the Message protocol parameter and in the Module tab enter Module name as AF_Modules/StrictXml2PlainBean and type as Local Enterprise Bean. Below is the screen shot which shows you how to use different available options of File Content Conversion.
Assumptions
Passing the parameters to the module is as easy as assigning the parameters of Recordset structure in normal scenarios. Here x2b is the Module Key from where we can pass the parameters to the Module XML2PlainBean.
Assume Employee is one of the record types, and I am using fieldLengths parameter name.
Same way we can use :
fieldSeparator
fieldLengthExceeded
File Content Conversion In Sap Pi Receiver
beginSeparator
File Content Conversion In Sap Pi At Receiver Position
endSeparator