The following upgrade considerations have been compiled by OnBase subject matter experts. These upgrade considerations are general and applicable to most OnBase solutions and network environments and should be considered each time an upgrade is performed.
Carefully consider the impact of making any changes, including those listed below, prior to implementing them in a production environment.
For additional general information about upgrading OnBase, refer to the Upgrade Guidelines reference manual , and visit the Hyland Community at: https://www.hyland.com/community.
- Create Backups
-
When upgrading your ArcGIS solution, some existing files are overwritten by the upgrade process. Before upgrading, it is recommended that you save backup copies of the following:
-
All web.config files (WebAPI, GIS Service, etc.)
- Update Configuration Files
-
Configuration files created using OnBase 15 or earlier must be updated to work with version Foundation 22.1. To update a configuration file to work with version Foundation 22.1, follow these steps:
- Open the ArcGIS Configuration Utility.
- Click Import from the ribbon.
- Browse to the configuration file you would like to update, then click Open.
- Click the OnBase Mapping option on the ribbon.
- Click Save from the ribbon.
- Convert Silverlight Applications
-
The Silverlight version of the Integration for Esri is no longer supported as of version 17. This is in conjunction with Esri's support of the ArcGIS API for Silverlight. See the Integration for Esri product page on Hyland Community for more information.
If your Integration for Esri solution made use of the Silverlight version of the integration, you must convert your existing Silverlight web mapping applications into JavaScript applications in order to use those applications with OnBase Foundation 22.1.
- Using Geocoders with Feature Layers for Esri REST API
-
As of OnBase Foundation EP1, using the default Esri geocoders with the OnBase Feature Layers for Esri REST API is no longer supported. Documents that were geocoded by these geocoders in a previous version can still be displayed using OnBase Feature Layers for Esri REST API, but if any of the address Keyword Values of those document are updated, the document will no longer be displayed on the map.
Other interfaces are not affected by this change. It is still possible to use geocoders in conjunction with Unity Mapping or Web Mapping in OnBase Foundation 22.1.
Documents indexed with latitude and longitude coordinates directly (that is, documents indexed using a Single-Line geocoder) are also unaffected and can still be displayed on the map as expected.
Documents indexed using custom geocoders (that is, geocoders using a non-Esri customized geocoder service) are still supported for use with OnBase Feature Layers for Esri REST API.
- Configure a Viewer URL
-
As of OnBase Foundation EP5, using the built-in viewer that was previously supplied with the sample map application is no longer supported. In order to open and display documents in the sample map application, you must configure the viewerURL setting in the GIS Service web.config file.
- Configure the GIS Service web.config File
-
As of OnBase Foundation EP5, the following configuration files have been removed from the software:
-
CORS.config
-
MapConfiguration.config
-
PooledUser.config
-
GIS Sample Application web.config
The settings contained in the above files have been migrated into the GIS Service web.config file. Depending on your system's configuration, you may need to reconfigure your GIS Service web.config file to ensure your solution works as intended.