Jump to: navigation, search

Configuring BDS for on-premise deployment

This page describes steps you must take to configure Billing Data Server (BDS) in on-premise deployments.

By default, BDS is configured to run in online mode, wherein it stores extract and transform data on S3, and then transfers the resulting files to the IT department using Secure File Transfer Protocol (SFTP). This page describes how to configure premise mode, which stores files only in a local path. For more information about how BDS works in premise deployments, see the BDS User's Guide.

Procedure: Configure BDS for on-premise deployments

Purpose: Use the steps in this procedure to configure the BDS application.


Ensure that your environment meets the requirements set out on the Configuration prerequisites page.


  1. Create the tenant template in the ./cloudbilling-prem.local/templates/ folder. Use the following format to name the template:
    tenant_<short_tenant_name>.tpl, that is, '''tenant_acme.tpl'''
    Use the bundled ./cloudbilling-prem.local/etc/gvars.py file for the initial configuration. See Global variables for parameter descriptions.
  2. Execute the following command to launch BDS in configuration mode
    An interactive prompt appears.
  3. Execute the following commands to create encryption keys:
    python /usr/lib/python2.7/site-packages/keyczar/keyczart.py create --location=/vagrant/etc/crypto --purpose=crypt --name="BRS keyset"
    python /usr/lib/python2.7/site-packages/keyczar/keyczart.py addkey --location=/vagrant/etc/crypto --status=primary
    ls /vagrant/etc/crypto 1  meta
  4. Execute the following commands to encode the passwords with the generated encryption key:
    brsctl.py encrypt
    utils.py:__zk_lock_get: Connected to Zookeeper at
    Password: AM1agMm0Thl9KOCUP1qlTqufDy1SwQaHF-Ne-lGr9FhZQoBZ0hD0iBuDZrzFzQcONQSNvQvrJZn1
  5. Execute the following command to exit configuration mode:
  6. Execute the following command to import the configuration templates and reset all configuration values, including the current ETL timestamps:
    ./cloudbilling-prem.sh reset
  7. Check the output for any errors below the line “Main run, should not produce any errors below this message”.
  8. If the following error appears: “Cannot read file /vagrant/templates/tenant_*.tpl”, re-import the configuration templates.
  9. Execute the following command to launch configuration mode:
    ./cloudbilling-prem.sh config
  10. Execute the following commands to verify that the templates are loaded:
    ./brsctl.py dataset -l
    ./brsctl.py metric -l
    ./brsctl.py location -l
    ./brsctl.py tenant -l

Additional configuration steps for BDS are described in the following sections:

Retrieved from "https://docs.genesys.com/Documentation:BDS:Dep:Config:9.0.0 (2019-10-22 10:35:42)"
This page was last modified on April 12, 2019, at 13:05.


Comment on this article:

blog comments powered by Disqus