Data tier - System database

The OneContact system database stores all system wide configurations and runtime state.

 

Functions

  • Store OneContact system configurations:
    • Instances
    • Applications & component locations and configuration.
    • Maintenance tasks
    • Sites and associated configurations
    • Storages
    • Licenses
    • Alarms
    • Configuration Parameters
  • System state
  • Application state
  • Runtime information (system wide) necessary to other OneContact Server components

 

Relations to others modules

  • BaseService - uses the system database to read components location and parameters and to store system state.
  • OneAdmin - uses the system database to read and write the system configurations.
  • Notifier - uses the system database to store specific runtime information: registrations done in a system context.
  • Timer - uses the system database to store specific runtime information: system timers.
  • Script Engine - uses the system database to store specific runtime information used in the script engine recovery process (in case of failure).
  • OneProxy - uses the system database to read configuration information.

 

System_database.png

 

Performance and Scalability

  • Can be scaled vertically by adding CPU’s, memory and disks to SQL Server machine.
  • The overall usage of the system database is quite low when compared to other OneContact databases. The runtime information stored in this database is reduced.

 

Redundancy

Failover cluster

 

Deployment

  • Requires Microsoft SQL Server 2016.
  • Only one database per OneContact system.
  • There’s no dependency to other OneContact databases; it can be deployed in a separate SQL Server instance.