SBR provides a common database framework to host database solutions for native or custom applications. The major functionalities of the SBR infrastructure include:
- A common framework to host a generic database that can be used by multiple and different custom applications and for many built-for-purpose databases for some other applications such as PCA or GLA
- A common configuration and maintenance system to enable users to configure and manage databases for various types of applications, and a common control for database audit
- A common communication mechanism to allow various applications to communicate with different generic or built-for-purpose databases using the DSR ComAgent routing services and a common stack event library
- A common High Availability (HA) policy management and Resource/Sub-resource management for various database
- A common set of Alarms, Events, KPIs, and Measurements for database usages that are applicable for all applications
An SBR Database consists of several fields:
- A user-configured Database Name
- A Database Type (Session, Binding, or Universal)
- The name of the Resource Domain that contains the SBR Server Groups
- The Number of Server Groups that define the capacity of the SBR database
- The Place Association that uses the SBR database
- The Owner Application that shows which application has the privileges to write, read, and manage the configured SBR database
Note: An SBR database must be configured after configuring SBR server groups, resource domains, and binding region, application region, or mated sites place associations.
To use an SBR database, it must register to the local ComAgent for the registered resource (identified by the resource IDs) as resource providers to be used by registered resource users (applications) for the same registered resource. Registering to a ComAgent as a resource provider requires configuring the SBR server topology and the SBR database on the page, as well as preparing the configured SBR database on the page.
Once the SBR database is configured and prepared, it is registered to ComAgent as a ComAgent provider for the assigned resource ID and the assigned sub-resource IDs. Then, the SBR database can be enabled by activating applications that own and use the SBR database.
While multiple applications may use the same SBR database, the database can have only one owner application associated with it.
The life cycle of a SBR database is related to the application that owns the database:
- While a SBR database can be configured without an owner application being specified at the configuration, the SBR database can't be prepared or enabled without an owner application being configured
- After the owner application is activated and configured in the SBR database configuration, the SBR database can be prepared and then be enabled.
- The SBR database can be used by the owner application and other custom applications.
- The SBR database can be deleted only if the SBR database is configured with no owner application specified. The owner application field in the SBR database configuration is None.
For further information on configuring an SBR Database, refer to Configuration.
For further information on maintaining an SBR Database, refer to Maintenance.