Learn about Billing Data Service architecture
Billing Data Service (BDS) operates as a CronJob, which runs once a day, consisting of a sequence of steps that collect various data from sources -- such as Genesys Info Mart, GVP RS, and Configuration -- and transforms that data into usage statistics that track your consumption of Genesys services, which is used for billing purposes. Files are securely transferred to Genesys back-office using SFTP.
Autoscaling is not supported.
For information about the overall architecture of Genesys Multicloud CX private edition, see the high-level Architecture page.
See also High availability and disaster recovery for information about high availability/disaster recovery architecture.
Architecture diagram — Connections
The numbers on the connection lines refer to the connection numbers in the table that follows the diagram. The direction of the arrows indicates where the connection is initiated (the source) and where an initiated connection connects to (the destination), from the point of view of Billing Data Service as a service in the network.
The connection numbers refer to the numbers on the connection lines in the diagram. The Source, Destination, and Connection Classification columns in the table relate to the direction of the arrows in the Connections diagram above: The source is where the connection is initiated, and the destination is where an initiated connection connects to, from the point of view of Billing Data Service as a service in the network. Egress means the Billing Data Service service is the source, and Ingress means the Billing Data Service service is the destination. Intra-cluster means the connection is between services in the cluster.
|Connection||Source||Destination||Protocol||Port||Classification||Data that travels on this connection|
|1||Billing Data Service||Pushgateway||HTTP||9091||Intra-cluster||BDS-specific monitoring metrics are available through PushGateway. A monitoring tool connection can scrape those metrics from PushGateway.|
|2||Billing Data Service||Genesys Web Services and Applications||HTTP||80||Intra-cluster||Obtains information on voicemail boxes configured in the tenant’s configuration.|
|3||Billing Data Service||Voice Platform Configuration Server||TCP||8888||Intra-cluster||Verifies necessary configurations required to connect to Voice Platform Reporting Server in a tenant's primary region.|
|4||Billing Data Service||Consul||HTTPS||443||Intra-cluster||Connection to Consul in a tenant's primary region.|
|5||Billing Data Service||Voice Platform Reporting Server||TCP||1433||Intra-cluster||Connection to the Voice Platform Reporting Server's database (GVS RS DB) to extract metrics information in a tenant's primary region.|
|6||Billing Data Service||Genesys Info Mart||TCP||5432||Intra-cluster||Connection to the Genesys Info Mart's database (GIM DB) to extract metrics information in a tenant's primary region.|
|7||Billing Data Service||Voice Platform Configuration Server||TCP||8888||Egress||Verifies necessary configurations required to connect to Voice Platform Reporting Server in a tenant's non-primary region(s).|
|8||Billing Data Service||Consul||HTTPS||443||Egress||Connection to Consul in a tenant's non-primary region(s).|
|9||Billing Data Service||Voice Platform Reporting Server||TCP||1433||Egress||Connection to the Voice Platform Reporting Server's database (GVS RS DB) to extract metrics information in a tenant's non-primary region.|