Setup for Design Server V2-based flow executions

Edit online

Design Server packages are used to deploy to the V2 based flow executions and are defined using the maps and files in a project. When the package is deployed or compiled, it is saved to the volume, or a host directory, bound to the /data/catalog location in the container file system.

The following information is related to the Design Server project x12Compliance.zip. The main execution map is ccx12. Modify the ccx12 map and input card three, ConfigInfo, to use the x12rsconfig.xml file or the x12fullconfig.xml file. The x12fullconfig.xml file contains additional configuration settings for the compliance checking process. The *config.xml file selected will need to be downloaded, modified, and replaced in the Design Server project. The FileDirectory needs to be updated to follow the container mount location.

<FileOutput>
<!-- This section will send output to files. Reference file x12rsconfig.sh -->
	<FileDirectory>/data/data/x12Compliance</FileDirectory>
</FileOutput>

The FileDirectory defined in the x12 configuration file should point to the container file system and mount location.

With container mount location /tmp/itx-rs/data and package name x12Compliance.

<FileOutput>
	<!-- This section will send output to files. Reference file x12rsconfig.sh -->
	<FileDirectory>/data/x12Compliance</FileDirectory>
</FileOutput>

The compliance check output folder structure must also be defined for the container file system and mount location /data.

A script file is located in the x12Compliance project, relative to the map location. The script contains example commands to create the output file structure for the container package deployment to the rest container depending on the server definition in Design Server for deployment.

With container mount location /tmp/itx-rs/data.

/tmp/itx-rs/data/maps/x12Compliance/compliance/data/x12rsconfig.sh

mkdir -p /tmp/itx-rs/data/x12Compliance/x12/reject

mkdir -p /tmp/itx-rs/data/x12Compliance/fa/inbound

mkdir -p /tmp/itx-rs/data/x12Compliance/fa/outbound

mkdir -p /tmp/itx-rs/data/x12Compliance/ta1/inbound

mkdir -p /tmp/itx-rs/data/x12Compliance/ta1/outbound

As an alternative to using the predefined output structure, you can remove the <FileOutput> component from the *config.xml file. This will cause compliance checking to default to card output. Using card output requires that each output card of interest be identified with the map execution. The example below would override output card 5 in the ccx12 map for valid data and card 9 for the x12 acknowledgement.

curl -X  PUT "http://localhost:8080/tx-rest/v2/run/ccx12?output=5;FILE;/data/x12compliance/x12ValidData.out, output=9;FILE;/data/x12compliance/x12Ack.out"

After deploying the package and modifications, restart the container.