The next step is to provision global settings. Global settings are located in three sections: globals, datasets, and metrics.
Each one is provisioned in three steps:
1. Generate a template for the section.
2. Edit the template.
3. Import the template into configuration.
The default globals templates for on-premises deployments are added to the ./cloudbiling-prem.local/templates/globals.tpl file during deployment if it does not exist.
Also metric/region/location templates are part of the delivery bundle and are available immediately after deployment in the ./cloudbiling-prem.local/templates/ directory.
They can be either edited there and imported, or they can be generated again by the admin tool.
To generate the template, run the admin utility with the template command.
brsctl.py template -t globals -f
The entire globals section is contained in one template. You must generate and import a separate template for each dataset and metric in the datasets and metrics sections.
You must configure the name and access credentials for the s3 bucket, sftp destination, and tenant Configuration Manager (CME) and Genesys Info Mart (GIM) credentials. BDS expects to be able to use the same service account credentials for each tenant's CME and each tenant's GIM instance.
A metric template must be imported for each metric supported by BDS.
A dataset template must be imported for each dataset that BDS extracts.
The etc directory of the BDS installation contains pre-defined region and location templates. They can be edited and imported, or admin utility's template command can be used to regenerate the templates.