3.22. <ServiceDatabase xxxxxx>

A Service Database holds information about services and subscriptions. Examples of services are data plans and pre-paid packages offered by hotspot services. Service attributes can be data and time quota, bandwidth limitations, pre- and post-paid requirements. Some services may also place restrictions to re-subscribing the service and have special requirements to the action taken when quota is exceeded.
When a user subscribes to a service, a Service Database also keeps track of per-user subscription state. For example, if a user currently has no active session, there is no entry in a Session Database, but any resources applicable for a service that the user has subscribed to, is tracked by a subscription entry in a Service Database.
If you are running multiple instances of Radiator which all provide the same service, for example a hotspot service, you must specify an external Service Database for each Radiator, and you must ensure that all instances of Radiator use the same Service Database. If you fail to do this, Radiator will not be able to correctly track usage. This requirement is similar to SessionDatabase, see Section 3.17. <SessionDatabase xxxxxx> for more information.
See goodies/README.hotspot and goodies/hotspot.cfg for a configuration sample.

3.22.1. Identifier

This optional parameter assigns a name to the Service Database, so it can be referred to in other parts of the configuration file, such as the ServiceDatabase parameter in AuthBy HOTSPOT.
# Allow other parts of configuration to refer to this Service Database
Identifier xxxxxx

3.22.2. Tenant

This optional parameter assigns a name to the Service Database. For example, if the same SQL database is used with multiple Service Databases that need to be disjoint, these databases should be configured with different Tenant value. This parameter defaults to default.
# We use one database for multiple hotels
Tenant hotspot-hotel1