Jump to: navigation, search


After the initial provisioning of Global settings, you must provision the location and tenant for configuring the Billing Data Server (BDS) for deployment.

New location / location update

To generate the new location template, use the admin tool:

brsctl.py template -t location -f location_new.tpl

Or, copy one of the existing location templates in the etc directory of BDS to a new file. Edit the template by providing the following information:

  • Correct region code
  • Location code and name
  • Switch name(s) and Genesys Voice Platform (GVP) host name, port, and Configuration Management Environment parameters

Then use the admin tool to provision the new location:

brsctl.py config -i location_new.tpl

To update the existing location, use the --force option when provisioning.

New Tenant

To provision a new tenant, always generate a template using the admin utility:

brsctl.py template -t tenant -f tenant_new.tpl

Most options in the tenant template are self-explanatory. The following notes describe the less obvious options:

  • production_date: Genesys recommends you provision a tenant before it goes to production. The provisioned tenant, even if enabled, is not processed if the production date is in the future. Processing begins only after the production date.
  • extract_watermark, transform_watermark, load_watermark: The initial values of the three watermarks must be set to the same date, which is earlier than the production date.
    Default values are already earlier than any valid production date:
    • extract_watermark: 2015-07-01
    • transform_watermark: 2015-07-01
    • load_watermark: 2015-07-01
  • Location-level GVP settings are pre-populated from global settings when the template is generated. They must be changed only if this tenant is using a different instance of GVP. However, if the regional default setting changes, the settings for the provisioned tenants are not updated automatically. See Modifying Existing Tenant on how to make changes to the provisioned tenant.

The completed template can be provisioned by using the config command of the admin utility:

brsctl.py config -i tenant_new.tpl

Modifying an Existing Tenant

See Operation if you only need to enable/disable processing for the tenant at any level. For more complex configuration changes, use the tenant command of the admin utility:

brsctl.py tenant -t tenant_name -f filename.tpl

This command reimports the tenant template. The current watermark values are lost and must be adjusted.

Edit the file, and then reprovision the tenant:

brsctl.py config --force -i filename.tpl

After provisioning the location and tenant, you must schedule BDS execution as described in Operation.


Comment on this article:

blog comments powered by Disqus
This page was last modified on December 19, 2018, at 09:43.