BDT Command Syntax
The CipherTrust Batch Data Transformation utility runs at the command line with the following syntax:
bdt [-c <configfilepath>] [-e] [-f] [-h | -ld <type> | -ls <type> | -t [<transformation_id>]
| -v] [-p <policyfilepath> | -central <centralized_policyfile>] [-sv] [-table
<tableName>] [-r <transformation_id>][-rb <transformation_id>]
Command Options
| Option | Description |
|---|---|
-c,--configfile <configfilepath> | Location of the BDT configuration file. Replace <configfilepath> with the path to bdt.config. If omitted, the default file bdt/conf/bdt.config is used. |
-e,–-encryptPassword | Set the CADP-JCE library password and CT-VL password, encrypt them, and store in bdt.config. Use this option the first time you run BDT. You can also use it whenever you want to change the passwords. BDT prompts you to enter the passwords at the console. |
-f,--populatePropertyFile | Populates the bdt.properties file. Use this option to configure the minimum required parameters of the default crypto library. It also allows you to configure log file path and log level. |
-h,--help | Display the BDT command syntax and information about how to use it. |
-ld <type> | list destination objects. Object types [tables, columns] |
-ls <type> | list source objects. Object types [tables, columns] |
-p,--policyfile <policyfilepath> | Location of the BDT policy file. Replace <policyfilepath> with the path to bdt.policy. |
-central <centralized_policyfile> | This configuration is applicable if the BDT policy is configured in CM. Provides name of the BDT Policy in CM. |
-sv,–-skipvalidation | Run BDT without first checking the bdt.config and bdt.policy files for correctness. It is advisable to run transformation with skip validation option only when policy and configuration are already validated.Caution: Use only for testing. Do not use it in a production environment. |
-t,–-transform [<transformation_id>] | Validate bdt.config and bdt.policy, then transform the input file and store the results in the output directory. If this option is omitted, BDT does not perform the data transformation. Running without -t is useful when you only want to set passwords or validate configuration files.You can optionally include the transformation ID here. When provided as a value to this option the specified ID overrides the ID field value that is set in the policy file. |
-v,–-validate | Validate bdt.config and (optionally) bdt.policy. Use this option when you want to check the files without actually transforming the data. The policy file is validated if the -p option is included in the command. If you are running with -t, you do not need to also include -v. The -t option includes an implicit -v. |
--table <tableName> | List columns for this table. This option must be accompanied by -ls or -ld option. General syntax: bdt.bat -ls (or -ld) columns --table <tableName> -p <policyfile> |
-r <transaction_id> | Restart a transformation run at the point of a failed transaction. Only uncommitted records are transformed. |
-rb, --rollback<transaction_id> | Roll back a failed row during in-place transformation. |
