What the ediblockchain folder contains

The ediblockchain folder contains a script to compile all the maps in the example, compileall.bat

The blockchain folder contains the config folder, journal, maps, and templates. The config folder contains a configuration file which may be expanded in the future. The journal folder contains the json templates for the block chain information file and actual block chain file.

The journal folder also contains some control block definitions for the block chain service maps. The maps folder contains the map source for the block chain requests and processing. The templates folder contains some json document and control block definitions for the participants to use to make requests and pass documents to the block chain service. Viewing the templates will help understand the mapping and block chain service requests.

The edifiles folder contains the EDIFACT standard being used and will contain all the EDI documents communicated between each participant.

The buyer, carrier, and supplier folders identify an EDI participant and contain maps and data to create edi documents and make block chain requests. The map source in each participant folder contains a top-level map (aBuyerNewOrder, aSupplierNewOrder, aCarrierNewOrder). The last output card controls the block chain service requests, and triggers for the next participant.

The buyer folder it the main execution folder. The map source file is BuyerOrderMaps.mms and the top-level map aBuyerNewOrder will start the new order and trigger the other participants processing.