Validating Configuration and Policy Files
Perform the following steps to validate the BDT config and policy files.
Validating Configuration Files
If the config file is named as bdt.config and assuming the file is stored in the expected default location, then to validate bdt.config alone use -v with no other options:
./bdt.sh -v
If your config file is named differently, then to validate config files use the -c option,
./bdt.sh -v [-c configfilepath]
Note
-cis optional. If not provided, the default configuration filebdt/conf/bdt.configis validated.Replace
bdt.shwithbdt.batin the Windows environment wherever using commands withbdt.sh.
Validating Policy Files
If you want to only validate the policy files but not perform any other operation, you can specify which files to validate by adding -p for local policy file and -central for central policy.
For example, to validate the files configfilepath and policyfilepath, use the following command:
./bdt.sh -v [-c configfilepath] [-p <policyfilepath> | -central centralized_policyfile]
Note
-cis optional. If not provided, the default configuration file bdt/conf/bdt.config is validated.-pand-centralare optional. If not provided, the policy file is not validated.Replace
bdt.shwithbdt.batin the Windows environment wherever using commands withbdt.sh.