Problem

Extract from "Financial_Exchange_2.8.x_ImplementationGuide_allOS_en" : Implementation > Electronic Signature > Extending support to other formats

This topic explains how to use the parser exit to create your own parser implementation. This determines how the payment details are displayed in the Electronic Signature UI.

Payload parser :
Payload files contain information such as number of payment operations, payment amount, account information, and so on. The parser provides methods to allow parsing of the payload files and retrieve the information.
Axway provides sample parsers for the implementation of the CFONB160, CFONB320 and SEPA file formats in order to show how to extend the file format support.

Modifying the parser exit :
The parser sample is located in <Electronic Signature_install_dir>\samples\parser\ and is an example of implementing the CFONB160 file format. The build_sample_parser.xml file is used to compile the sample and the source code is placed in the src directory.

Resolution

The repository mentionned in the documenation is false. All files are located in "devKit" folder.

For example, "build_sample_parser.xml" is located under "...\ElectronicSignature\devKit\parser".

And "..\ElectronicSignature\devKit\parser\src\com\axway\fex\es\samples\parser" contains :
- Cfonb160DebitParserSample.java
- Cfonb160ParserSample.java
- Cfonb320ParserSample.java
- SepaCreditTransferParserSample.java