If B2B receives inbound file name as ABC.txt; then we want to customize the generated 999 file name as ABC_999.tx.B2B does not support this format out-of-box as of now however you may send custom filename from back-end in eventName header and enable the "Preserve Filename" in your FILE/FTP/SFTP channel. So what all you have to do is that instead of allowing B2B to handle 999, generate 999 from back-end and in the eventName header set the filename like -
I am trying to find out the way to do FA generation from BPEL. is there doc can you pls point me to?This logic you may incorporate in the same process which receives the inbound 834. In the process which receives 834 from B2B, add below logic -
1. Generate FA payload at BPEL using a XSLT (you may use 997 XSD). Here input will be inbound 834 message and output will be 997 payloadThanks Anuj, if i understand correctly, this is good for generating positive FA.
1. Do I need to write separate logic in SOA Error handler to generate negative FA if there is any validation errors?Yes, if you are going to do any validations at SOA layer. If FA is not really important for your/your partner's org then you may simply generate positive FA if inbound request is received successfully at SOA layer (which means it would have passed the structure validation at B2B layer).
2. Is there a standard xslts to generate positive FA as well to generate negative xslt from SOA layers?I am not aware about any such XSLT but you may create a simple one by yourself. XSLT input will be of type of inbound message (for example 850.xsd) and output will be of type FA (997.xsd)