OnBase is not context aware; in the event of a failover, Client users will experience a Database Connection Error informing them that the connection to the database was lost. Users will have to close the OnBase Client module and log on again to access to OnBase.
After a failover, it may be necessary to log on to OnBase using a different data source because the original data source points to a specific database server. Alternatively, if a network alias is being used for the primary database server, the alias would need to be modified to redirect connections to the failover database server. In the case of SQL Server database mirroring, the SQL Native Client data source can be configured to include the name of the mirror server, thereby allowing users to use the same data source when logging on to the OnBase Client module.
For the OnBase Web Client, it is not necessary to restart the application pool and/or IIS after a failover. If a different data configuration is being used, the web.config file needs to be modified before restarting. Any processing Client workstations need to be restarted. If the Client is running as a service, the service can be configured to restart automatically on the Recovery tab of the service.