Set-up Pack for Supply Chain for ITX Design Studio

Edit online

Before you begin

  • Build the maps ccx12, x12segment, and x12ttval in ITX Design Studio on Windows, with Linux selected as the target platform, in the <DTXHOME>\packs\supplychain_edi_v10.2.x\x12\compliance\mapsandschemas folder.
  • Create a compliance folder structure like the one in Windows. Either copy the entire x12, edifact, or rail folder from the Design Studio pack install (refer to Step 1) or create and copy folders and files individually (refer to Step 2 and Step 3). The map execution folder structure is the same across all pack components. The compliance check configuration file should be copied to /maps/compliance/data folder. The /systems folder is used for Launcher systems defined using the ITX Integration Flow Designer.

    Example, <bind_mount_dir> = /tmp/itx-ls/x12Compliance/data

    mkdir -p <bind_mount_dir>/input

    mkdir -p <bind_mount_dir>/maps/compliance/data

    mkdir -p <bind_mount_dir>/maps/compliance/mapsandschemas

    mkdir -p <bind_mount_dir>/systems

    mkdir -p <bind_mount_dir>/output

Procedure

  1. Copy the entire x12/compliance folder to the <bind_mount_dir> location under /maps folder. This will copy the compliance check output file structure.

    Example, <bind_mount_dir> = /tmp/itx-ls/x12Compliance/data

    cp -R <Windows_install>/x12/compliance /tmp/itx-ls/x12Compliance/data/maps

    Note: Make sure the folders have Write permission. If not, use chmod +777 to change the permission.
  2. Create output folders individually in output folder under <bind_mount_dir> location.

    Example, <bind_mount_dir> = /tmp/itx-ls/x12Compliance/data

    mkdir -p /tmp/itx-ls/x12Compliance/data/output/fa/inbound

    mkdir -p /tmp/itx-ls/x12Compliance/data/output/fa/outbound

    mkdir -p /tmp/itx-ls/x12Compliance/data/output/ta1/inbound

    mkdir -p /tmp/itx-ls/x12Compliance/data/output/ta1/outbound

    Example, <bind_mount_dir> = /tmp/itx-ls/railCompliance/data

    mkdir -p /tmp/itx-ls/railCompliance/data/output/rail/reject

    mkdir -p /tmp/itx-ls/railCompliance/data/output/fa/inbound

    mkdir -p /tmp/itx-ls/railCompliance/data/output/fa/outbound

    mkdir -p /tmp/itx-ls/railCompliance/data/output/ta1/inbound

    mkdir -p /tmp/itx-ls/railCompliance/data/output/ta1/outbound

    Example, <bind_mount_dir> = /tmp/itx-ls/edifactCompliance/data

    mkdir -p /tmp/itx-ls/edifactCompliance/data/output/edifact/reject

    mkdir -p /tmp/itx-ls/edifactCompliance/data/output/fa/inbound

    mkdir -p /tmp/itx-ls/edifactCompliance/data/output/fa/outbound

    Note: Make sure the folders have Write permission. If not, use chmod +777 to change the permission.
  3. Copy files from the Windows mapsandschemas to the Linux mapsandschemas folder.
    1. Copy all the compiled maps from the Windows mapsandschemas to the Linux <bind_mount_dir>/maps/compliance/mapsandschemas folder.
      ccx12.lnx
      x12json.lnx
      putdatax.lnx
      x12audit.lnx
      x12aud2.lnx
      seg5010.lnx where 5010 is the standard version
      ttv5010.lnx where 5010 is the standard version
    2. Copy compliance check files to the Linux <bind_mount_dir>/maps/compliance/mapsandschemas folder.
      edicc.ini contains edisvu.so location
      errcodes.txt
      x12cfg.xsd
      x12codes.txt
      x12struct.txt
    3. Update the edicc.ini file for edisvu.so location. Ensure CR/LF end of line characters are converted to NL. The exitlib setting N/A or NA (Not Applicable) identifies the ITX install folder.
      exitlib=N/A
      The edisvu.so module can be found with the container install or in the Windows pack install folder platform_support/LINUX.
    4. Copy compliance check configuration from the Windows data folder to the Linux <bind_mount_dir>/maps/compliance/data folder.
      x12defaultconfig.xml
      x12fullconfig.xml
      x12fullconfig.json.dat *X12U component only