Compliance Check Execution

Edit online

Procedure

  1. Test the map with valid data by issuing this command: 
    curl -X  PUT "http://localhost:8080/tx-rest/v2/run/ccx12”
    If you get a message Map completed successfully, go to /tmp/itx-rs/data/x12Compliance/x12 and locate a file that ends with .in extension. If not, check the map folders to make sure they are created in the correct location.
  2. Test the map with invalid data by issuing this command: 
    curl -X  PUT "http://localhost:8080/tx-rest/v2/run/ccx12?input=1;FILE;../data/x12_invalid.txt”
    If you get a message Map completed successfully, go to /tmp/itx-rs/data/x12Compliance/x12/reject folder and locate a file that ends with .log.
  3. If you see the following message in the container JSON response, there could be issues with the output file structure.
    “message”: “FAIL function aborted map: Map terminated due to map framework problem”

    With this situation, the compliance check maps will generate a map framework trace in the mapsandschemas folder. With V2 execution, this is found within the container and will need to be retrieved. One way is to use the docker cp command.

    1. Find the link in the container JSON response. For example, "Settings": "/tmp/6c64-f72a-1350-b233/compliance/mapsandschemas/
    2. Create a folder to copy the files from the container. For example, /home/x12Results
    3. Issue the docker copy command: 
      docker cp itx-rs:tmp/6c64-f72a-1350-b233 x12Results
    4. Navigate to the /home/x12Results/6c64-f72a-1350-b233 and the mapsandschemas folder.
    5. Open the edilog.xml and search on sendoutput to verify output locations. With the example below the output folder structure /data/x12u/ta1/output is not defined. 
      <SendOutput>
<Send>
	<Command>/data/x12u/ta1/outbound/20240918-192651_ta1.out</Command>
	<Execute>FILE adapter called to process output type TA1OUT - Result: E9000 The TX File adapter was unable to locate the target output directory structure. Ensure that the configuration input has the correct location and that directory exists.
 	** SEND FAILURE ** </Execute>
	<FrameworkErrorOccurred>Send output to file failed</FrameworkErrorOccurred>
</Send>
</SendOutput>
  4. If you see the following message, that means there is something wrong with the edisvu shared library location.

    Return code/text: -99999/Adapter not found structure failed. DLL path: ./ Check the edicc.ini file to make sure that it correctly specifies the edisvu shared library

    1. Make sure the edicc.ini is transferred in ASCII mode. The removal of extra carriage-return when transferring the file is required.
  5. Finally, if you are still experiencing problems, try to restart the container by issuing the command: 
    docker restart itx-rs