Application Server Upgrade Considerations - Application Server - English - Foundation 22.1 - OnBase - external

Due to the discontinuation of Microsoft .NET Core version 2.2.0, issues may occur during an upgrade from a version of OnBase prior to Foundation EP2 to OnBase Foundation EP2 or later. After upgrading, you must run the Repair operation either using the installer or through the Add/Remove Programs function in Windows.

As of OnBase 18, the default database connection method for the Application Server and other Core-based applications is ADO.NET connection strings. The Application Server no longer supports ODBC connections to connect to the OnBase database. If you are upgrading from version 17 or earlier, you must update data source connections in the Application Server to use connection strings. In addition, any applications that connect to the database using the Application Server must also be updated to reference the name of the Application Server's data source connection string instead of an ODBC data source name.

As of OnBase 18, the Application Server Proxy has been deprecated. A reverse proxy configuration is recommended instead. If you are upgrading from a solution that depended on the Application Server Proxy, you should update the solution to use a reverse proxy. See the Application Server documentation on Reverse Proxy Configuration for more information.

If the Application Server being upgraded was manually installed in version 16 or earlier, ensure that the following settings are configured in IIS:

When upgrading the Application Server, it is considered a best practice to de-register any Application Server DLLs from the Global Assembly Cache (GAC) before installing the new version. If any GAC registration had been performed manually in the previous version of the solution, that registration will need to be performed manually in the upgraded version as well. This ensures that the GAC references the upgraded versions of the Application Server components.

Beginning in OnBase 18, the Unity Scheduler Service is required for all OnBase deployments. An instance of the Unity Scheduler Service must be installed and running to ensure that necessary maintenance tasks are automatically performed on the OnBase system. When upgrading any OnBase component to version 18 or later, any existing instance of the Unity Scheduler from a previous version must also be upgraded to version 18 or later. For more information on the Unity Scheduler Service, see the Unity Scheduler module reference guide.