bdd

The bdd configuration type publishes a modified version of bdd.conf to all BDD nodes. This updates the configuration of the entire cluster.

To update the cluster configuration, edit a copy of $BDD_HOME/BDD_manager/conf/bdd.conf on the Admin Server, then run:

./bdd-admin.sh publish-config bdd <path>

Where <path> is the absolute path to the modified copy of bdd.conf. Note that it's recommended to edit a copy of bdd.conf to preserve the original in case the changes need to be reverted.

Important: When making changes to your cluster's configuration, always use the post-install version of bdd.conf in $BDD_HOME/BDD_manager/conf/, and not the original one used during the installation. The post-install version contains a number of new properties added by the installer, which will be lost if you use the original one.

When the script runs, it makes a backup of the original bdd.conf in $BDD_HOME/BDD_manager/conf on the Admin Server. The backup is named bdd.conf.bak<num>, where <num> is the number of the backup; for example, bdd.conf.bak2. This file can be used to revert the configuration changes, if necessary.

The script then copies the modified version of bdd.conf to all BDD nodes in the cluster. When it completes, the cluster must be restarted for the changes to take affect.

Note: When bdd runs, any component log levels you've set on specific nodes using the set-log-levels command will be overwritten by the DGRAPH_LOG_LEVELS and ENDECA_SERVER_LOG_LEVEL properties in the updated file.

For more information on updating your cluster configuration, see Updating bdd.conf.