Billing High Availability and Clustering


Connected Services Framework
Connected Services Framework 3.0 - Billing Standard Business Event Send comments on this topic.
Billing High Availability and Clustering
See Also

The Billing Standard Business Event (BillingSBE) is designed for scale-out and can be deployed across multiple servers. In a multiple server configuration, some or all of your BillingSBE servers can be deployed behind network load balancers. The BillingSBE also supports asymmetric configuration, that is, configurations in which the Batched Delivery Service is disabled on some of your servers. When the BillingSBE is deployed for high availability, you must ensure that the settings in BillingSBE configuration files remain consistent on all of your BillingSBE servers. For more information, see the Microsoft Connected Services 3.0 BillingSBE Planning and Deployment Guide.

Asymmetric Configuration and Billing Event Propagation 

In a multiple server configuration, both the BillingSBE Web Service and the Batched Delivery Service are installed on each server, however, you can selectively disable the Batched Delivery Service on some servers. To disable the Batched Delivery Service, you set the <ProcessMessages> parameter to false in the Microsoft.ConnectedServices.DeliveryService.exe.config configuration file. By disabling the Batched Delivery Service on some of your servers, you can dedicate these servers to receive raw billing events from VAS systems, transform them and store them in the BillingSBE database. The other servers in your installation, those on which the Batched Delivery Service is enabled, can be used to deliver the transformed events to your billing systems.

You can also choose to dedicate one or more of your BillingSBE servers to processing raw billing events from specific VAS systems. You can direct traffic from VAS systems that emit a large number of raw billing events to specific BillingSBE servers by ensuring that subscriptions to these VAS systems are only created in sessions that have these servers as the BillingSBE participant. In some cases, you may want to dedicate a BillingSBE server to receiving a specific type of raw billing event from a VAS system, while directing other raw billing events from the same VAS system to other servers. You can also disable the Batched Delivery Service on these dedicated BillingSBE servers to improve bandwidth.

Note. Although you can dedicate a BillingSBE server to the front-end processing of raw billing events from specific VAS systems, you cannot dedicate BillingSBE servers to delivering transformed events either from specific VAS systems or to specific billing systems. All of the BillingSBE servers on which the Batched Delivery Service is enabled collaborate to deliver transformed events to all of the billing mediation systems in your configuration.

Deploying the CSF Core Components for High Availability with the BillingSBE

Depending on the number of raw billing events that must be handled by your configuration, you may want to consider the following strategies for deploying the Session component:

  • Deploy the CSF core components and the BillingSBE on different servers.
  • Dedicate one or more CSF Session servers to hosting sessions for the BillingSBE.
  • Create sessions for VAS systems that source a large number of events on dedicated CSF Session servers.  In extreme cases, you may even want to dedicate a Session server to a specific kind of raw billing event from a VAS system and direct other billing events from that system to a different Session server.

You specify the Session endpoint to which a VAS delivers raw billing events in the subscription file that you supply when you subscribe to a VAS system by using the BillingSBE MMC Snap-in, or in the message body of the BillingSBE CreateSubscription admin message.

The BillingSBE Database and High Availability 

The BillingSBE database is a SQL Server 2005 database. For more information about high availability and SQL server 2005, see the SQL Server 2005 home page, on the Microsoft Web site, at

See Also

© 2016 Microsoft