Run the example using the flow command server process (flowcmdserver)

To run the example, deploy locally or to ftp server and use the flow command server process (flowcmdserver).

1. Create a server definition where the runtime is installed, if you do not have a server local definition or ftp execution definition to deploy to, in Design Server.
2. In Design Server, deploy the created package to the server definition. For example, deploy to c:\ftpserver\deployment directory.
3. Execute the flow using the flow command server. The below command is for EBA EURO1/STEP1 e1s1_pacs_009.xml message.

   flowcmdserver.exe --dir c:\ftpserver\deployment\flows
   --flow eba_e1s1_validation_flow.json
   --var "INPUT_FILE=C:\ftpserver\deployment\tools\mx_service\data\e1s1_pacs_009.xml"
   --audit "C:\ftpserver\deployment\tools\mx_service\data\e1s1_pacs_009_adt.json" -ad
   

   The results will be in C:\ftpserver\deployment\flows as validation_result.xml or validation_result.json depending on the value of the REPORT_FORMAT variable.
4. Use the following command to execute with the variable VALIDATION_TYPE value defined in the Flow settings in Design Server (extended or schema).

   flowcmdserver.exe --dir c:\ftpserver\deployment\flows
   --flow eba_e1s1_validation_flow.json
   --var "INPUT_FILE=C:\ftpserver\deployment\tools\mx_service\data\e1s1_pacs_009.xml"
   --var "VALIDATION_TYPE=schema"
   --var "REPORT_FORMAT=json"
   --audit "C:\ftpserver\deployment\tools\mx_service\data\e1s1_pacs_009_adt.json" -ad
   

5. The flow will report status similar to:

     ***Starting flow command server
   
   	  Flow UUID:      85eabe2c-2302-4543-b347-9e18d65c6816
   	  The flow audit file is:         "C:\\ftpserver\\deployment\\tools\\mx_service\\data\\e1s1_pacs_009_adt.json"
   	  Flow completed successfully
   	  Elapsed time: 3048ms
   

6. Examine the flow output result file validation_result.xml and the audit file e1s1_pacs_009_adt.json.