Depending on design choice, data store tables may be created in the same (local) UnifiedLogon database with other entities (users, user groups, companies application, configuration, etc.), or in a separate (remote) database, which may be on the same or on a different server.
With local database deployment, UnifiedLogon automatically creates additional API view in its database to access data store records.
With remote database deployment, UnifiedLogon automatically creates additional API view to access data store records in both local UnifiedLogon database and remote data store database. The view in local database references data store table using full database name, which includes server name, database name and schema name. The view in remote database references data store table as its own local table.
The screenshot below shows data store properties page. If property Remote Database remains blank, then the data store is created in the UnifiedLogon local database. Otherwise, the data store is created in a remote database.
The next screenshot shows remote database properties page. If data source is not selected, then local UnifiedLogon database is used to simulate remote database. Otherwise, selected data source specifies how to connect to the remote database. UnifiedLogon Database Prefix property should include reference to UnifiedLogon database. This reference is used to generate system views to publish auditing information back to UnifiedLogon database.
The next screenshot shows data source properties page. Data source specifies connection string to the remote database, logon credentials, as well as Database Prefix property value. Connection to the remote database and database prefix are used to create remote objects accessible from the local UnifiedLogon database, as well as to manage data schema in remote database.
Data stores created in Arnica UnifiedLogon may be used by other Arnica Platform applications, as well as any other custom application.