Jump to: navigation, search

Configuration prerequisites

After Installing Billing Data Server (BDS), the following prerequisites must be met before you configure BDS.

Regions and locations

Within each tenant configuration, define a set of regions and locations in which the tenant is enabled.


In the globals section, define credentials at the top level in the following sections:

  • cme_credentials: the credentials to access all the Configuration Servers.
  • gimdb: the default credentials to access the Genesys Info Mart (GIM) databases.
  • gvpdb: the default credentials to access the Genesys Voice Platform (GVP) Reporting Server.

GVP section

  Each location at the top level has a gvp section with details that define the shared GVP deployment details:

  • Configuration Server parameters
  • GVP Reporting Server database parameters
  • Credentials (inherited from the gvpdb section under the globals section)

Reporting Server database

Globally defined GVP Reporting Server database parameters for each location and default credentials are propagated down to the tenant level, and can be overridden on that level.  

Additionally, each tenant has a shared_gvp flag that defaults to true. In premise deployment, shared_gvp must be set to false.

A shared_gvp_alias parameter is not used to configure a premise tenant, and should be left empty.

MCP configuration

  • Configure the Media Control Platform (MCP) to send the required events to the Reporting Server. Genesys does not validate the configuration, but it is a prerequisite:
  • Validate the availability of the events based on the retention period of the event records, as configured in the Reporting Server:

Database configuration

BDS works with the following DB (db_type) types:

  • sql_server
  • postgre
  • Oracle

BDS uses the following corresponding drivers (driver_name):

  • FreeTDS
  • PostgreSQL
  • OracleODBC-12.1

Business unit billing breakout configuration

Presence of a "business_units" attribute on the tenant level of the BDS configuration triggers generation of additional billing information on a business unit level. This attribute should contain a list of business units names, for example:

   "tenants": {
       "tenant_with_units": {
           "tenant_id": "111",
           "tenant_name": "tenant_with_units",
           "business_units": ["unit_1","unit_2"],

To calculate billing metrics on a business unit level, each metric will require more underlying datasets than is being used now.

For that purpose, additional datasets needed for business unit level calculations specifically are added to a metric definition under a separate "bu_datasets" section. Only if that tenant has business units configured, which is when "business_units" parameter has at least one value specified, those datasets will get extracted:

   "metrics": {
       "<metric_name>": {
           "datasets": [
           "bu_datasets": [

Configuration Management Environment (CME) configuration prerequisites

Configuration folder structure as defined in the configuration database should have billing related configuration objects distributed between folders named as business units. Billable activity will be attributed to the business unit based on the presence of the business unit name in the path to the configuration object linked to that particular activity.

This requirement applies to configuration objects of the types below:

  • DN - should be located in CME under the paths as: Switches/<switch name>/DNs/../<business unit name>/...
  • Agent Login - should be located in CME under the paths as: Switches/<switch name>/Agent Logins/../<business unit name>/...
  • Person - should be located in CME under the paths as: Persons/../<business unit name>/...
  • Agent Group - should be located in CME under the paths as: Agent Groups/../<business unit name>/...
This page was last modified on July 10, 2019, at 09:01.


Comment on this article:

blog comments powered by Disqus