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 |
| 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 -e ITX_LS_LICENSE_ACCEPT=true -it -d -v /tmp/itx-ls/data:/data localhost/ibm-itx-ls:20260625docker run -e ITX_LS_LICENSE_ACCEPT=true -v /tmp/itx-ls/x12Compliance:/data --name itx-ls -d localhost/ibm-itx-ls:20260625Compliance 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>