Build and Run
For each Entity from config file, i.e. table or file, anonymization job with mapping and other metadata need to be build. It is enough to run the command line utility
evl anon build <config_file>
[-p|--project <project_dir>]
[--parallel [<parallel_threads>]]
[-v|--verbose]
That build all the files in build/ project subdirectory. There you can find evd and evm files in appropriate folders. EVD means EVL Data definition file and it defines the structure of the source/target; field names, data types and other attributes. EVM means EVL Mapping file and it defines how each field is mapped. Although both these files are generated, it is sometimes good to check how they are look like for debug purpose.
It generates also a file in run/anon/ subdirectory, where you can find one evl file per each Entity.
These files can be then run to anonymize the data. For example for three tables, party_addr, party_cont and party_rel it would be fired by these commands:
evl run/anon/party_addr.evl evl run/anon/party_cont.evl evl run/anon/party_rel.evl
Once such evl file exists for an Entity, there no need to build jobs again. It check each run if the config file has changed or not for given Entity and run ‘evl anon build’ command automatically.
Note: There is no need to run ‘evl anon build’ every time the config file is updated. It is done automatically once the job is fired.
The build command also generates a workflow file for given source in workflow/anon/ subdirectory. You can run the anonymization for all the Entities from that source. For example having source defined by configs/some_source.csv, you can run
evl run workflow/anon/some_source.ewf
and it will run all anonymization jobs in one or several parallel threads. It depends on the value defined by --parallel option.
If one or more anonymization jobs in a workflow fail, then you can the restart the whole workflow by:
evl restart workflow/anon/some_source.ewf
or continue from those last failures:
evl continue workflow/anon/some_source.ewf