Compliance Components

Refer to the following table for the compliance components:

Component	Map and Schemas
edifact component	ccedf, edfsegment, edfttval
iata-api component	ccapi, apisegment, apittval
iata-pnr component	ccpnr, pnrsegment, pnrttval
rail component	ccrail, railsegment, railttval
tt-edifact component	ccttedf, ttedfsegment, ttedfttval
X12 component	X12 (ccx12.mms), x12segment, x12ttval
x12u component	x12u (ccx12u.mms), x12segment, x12ttval, x12conv

The compiled maps along with input and output folder structures must be saved to the volume, or a host directory, bound to the /data/maps location in the container file system. The container mount location should be identified when creating the folder structures needed for compliance execution. The <bind_mount_dir> refers to folder specified in volume (-v) option on the docker run commands:

docker run -u root --name itx-ls -it -d -v /tmp/itx-ls/data:/data

docker run -v /tmp/itx-ls/x12Compliance:/data --name itx-ls -d itx-ls

Compliance configuration file with container mount location /tmp/itx-ls/x12Compliance:/data.

/tmp/itx-ls/data/maps/x12/compliance/data/x12defaultconfig.xml

<FileOutput>  
            <FileDirectory>/data/data/x12Compliance</FileDirectory>
</FileOutput>