This section is DEPRECATED.
| Table of Contents |
|---|
From Agnos Framework 2.x, it’s possible to use an .ini file to generate a set of binary data files (i.e. the persisted model) that are used by the framework to initialize internal structures (i.e. the instanciated model). Framework 3.2.x now provides a standard component, AgnosGE, that is optionnaly integrated at Level3.
INI File Structure
[Config] section
The following key is used:
...
Note: AID shall be set to a value so that the section is parsed like [A0000000041010:2] where AID = A0000000041010 andd KernelId = 2
INI File Configuration
Contact
Contact configurations use only 2 files:
Whereas TERMINAL file reflects the EMV Level2’s contact ICS, PROCESSING file contains all the processor/acquirer parameters like TACs, floor limit, etc…
...
Contactless configurations use either 3 files (TLV binary format) or 5 files (RAW binary format): The configuration files in Agnos are:
Whereas TERMINAL is limited to declare whether or not the terminal supports EMV contactless, and PROCESSING contains supported AID (contact and contactless in dual mode), most of the business parameters are declared using ENTRY_POINT file.
...
All possible tags are presented in the Configuration Model section.