The default database connection method for OnBase servers and applications requires ADO.NET connection strings. An ODBC connection is still required for the OnBase Client and the OnBase Configuration module.
A connection string contains the information required to connect to a database, and each connection string has a unique identifying name for that data source connection. This unique data source name is referenced by other applications to connect to the database configured in the connection string.
Data source connection strings are configured in the configuration file of the application used to connect directly to the database. For example, the connectionStrings element in the Application Server web.config file contains a data source connection string for each database that the Application Server accesses. Other applications using the Application Server, such as the Unity Client or Web Server, access the database by referencing the unique data source name from the relevant connection string.
You can use the Web Application Management Console to create, modify, and delete data source connection strings to connect to the OnBase database. This utility also allows you to encrypt all of the connection string information in the configuration file for security purposes.
ADO.NET and connection strings are Microsoft .NET Framework concepts, but each database provider (such as SQL Server or Oracle) has its own implementation of ADO.NET. For more information on building a valid connection string or using additional options, see your database provider's documentation on connection strings.
It is important to note the following considerations for connection strings:
-
It is strongly recommended to use integrated security instead of a database account for authentication. To use integrated security, the Windows user connecting to the database must be the same user that is running the connecting server or service (such as the Application Server). This user must also be configured with the configgp role in the database.
-
It is strongly recommended to encrypt the connection strings. If they are not encrypted, all data source connection information is visible in the configuration file, including the database user names and passwords in the connection strings.
See the following sections to configure connection strings: