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).

Create a server definition where the runtime is installed if you do not have a server local definition or ftp execution definition to deploy in Design Server.
In Design Server, deploy the created package to the server definition. For example, deploy to c:\ftpserver\deployment directory.
Execute the flow using the flow command server. The below command is for TARGET2 Securities t2_sec_pacs_009.xml message.
```
flowcmdserver.exe --dir c:\ftpserver\deployment\flows --flow t2_sec_validation_flow.json --var "INPUT_FILE=C:\ftpserver\deployment\tools\mx_service\data\t2_sec_admi_005.xml" --audit "C:\ftpserver\deployment\tools\mx_service\data\t2_sec_admi_005_adt.json" -ad
```
The results will be in C:\ftpserver\deployment\flows as validation_results.xml or validation_results.json depending on the value of the REPORT_FORMAT variable.

This command will execute with the variable VALIDATION_TYPE value defined in the Flow settings in Design Server (only schema is supported).

To change, the following command can be used:
```
flowcmdserver.exe --dir c:\ftpserver\deployment\flows --flow t2_sec_validation_flow.json --var "INPUT_FILE=C:\ftpserver\deployment\tools\mx_service\data\t2_sec_admi_005.xml" --var "REPORT_FORMAT=json" --audit "C:\ftpserver\deployment\tools\mx_service\data\t2_sec_admi_005_adt.json" -ad
```

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\\t2_sec_admi_005_adt.json"
Flow completed successfully
Elapsed time: 3048ms

Examine the flow output result files validation_results.xml and the audit file t2_sec_admi_005_adt.json.