The following upgrade notes pertain to users upgrading to Responder 10.2.1d from version 10.0.3 or earlier:
- As of Responder 10.0.3, you may turn on the Telemetry service to gather statistical information on the processing of Responder data. To take advantage of telemetry you will need to install the Telemetry Service, as well as enable this feature in the Responder applications, as it is disabled by default. If you are upgrading, you will have to add this manually to enable it. Configuration is required for new installations and upgrades. Refer to the Configuring ArcFM Solution online help for configuring information. This file is available in the ArcCatalog Help menu or in the ArcFM Solution folder in the Start Menu if you perform the Administrator installation.
- As of Responder 10.0.2, custom FilterFinders written for Responder Explorer trees will no longer support vbs format. If you have written any custom FilterFinders for trees, they will have to be converted to use dvf. See the developer help at Responder Overview > Responder Customizations > Filters for more information. Note that custom filter finders written on the grids will still support vbs.
- As of Responder 10.0.2, if you are an Oracle user and plan to use the new Line Display Service, you must ensure that the server running the new service has the "Oracle Services for Microsoft Transaction Server" component installed as part of the Oracle Client installation. This component can be found in the Custom install portion of the Oracle installer.
- As of Responder 10.0.1 SP1, Responder Settings previously found in ArcMap.exe.config are now to be configured in Miner.Responder.Explorer.exe.config.
- As of Responder 10.0.1 SP1, Remoting settings previously found in ArcMap.exe.config are now to be configured in ArcMapRemotingConfig.xml. These settings include the destination Responder Server. The old ArcMap.exe.config file will be backed up (for reference) by xupdate as ArcMap.exe.config.bakxx.
- As of Responder 10.0.1 SP1, you may turn on additional caching to improve the performance of Responder services. With this configuration, Responder will open each feature class in the geometric network when the services start up and hold references to the open feature classes for the life of the process. This minimizes schema locks to improve performance. This setting is enabled by default in a new install, but if you are upgrading from a version prior to 10.0.1 SP1, you will have to add this manually to enable it in the following three files: Miner.Responder.DataServices.exe.config, Miner.Responder.PredictionServices.exe.config, and Miner.Responder.QueryWindowsService.exe.config. Find the <geodatabase> tag in any database connection section you use and add the text featureClassCaching =’true’ between geodatabase and before the >.
- As of ArcGIS 10, the GDB_Objectclasses table no longer exists (it has been replaced with multiple new tables). Because of this, the XY Event Layer SQL script ‘02-ArcJoinViews.sql’ changed significantly. Customers who are implementing Responder for the first time or customers who are just upgrading from a previous version to 10 must open this script and update it to use their datasets and table names. See the notes in that script for the list of feature class names that the script assumes exist in your data. If these have different names in your database, then you will need to find and replace those names in the script. Also note that each feature class name in the script is prefixed by the owner ‘ARCFM’. If your data has a different owner for these feature classes, then this also may need to be updated in the script. For example, the first part of the script creates or replaces rx_incident_devices_svc_view. It assumes the view is using a feature class called ARCFM.SERVICEPOINT. If your dataset and feature class combination for a Service Point feature is instead SDE.ServPoint, you will need to find all instances of ARCFM.SERVICEPOINT in the query and replace them with SDE.ServPoint.
- As of Responder 9.3.1 SP1, Responder no longer includes OASyS PubSub technology in favor of Responder Refresh technology. Responder Refresh technology does not require the configuration process that OASyS PubSub technology needed or any additional configuration.
Important notes regarding the 10.2.1d installers:
- If upgrading to ArcFM Desktop 10.2.1d from 10.0.2 or earlier, users should delete all files in their patch directories.
- If upgrading to Responder 10.2.1d from a release PRIOR to 9.3 Rev2, please contact Tech Support for some additional upgrade information.
- If upgrading to Responder 10.2.1d from a prior release that utilized OASyS PubSub technology, and you want to keep utilizing OASyS PubSub, you must request these installers from Tech Support. If you want to use Responder Refresh, no further configuration or action is necessary.
Switch order upgrade notes:
There were significant enhancements made to the way switch orders are handled in Responder versions following 9.3.1 SP1. Note that if you are upgrading from 9.3.1 SP1 or later, you can skip this section.
- Switch order ‘Created’ and ‘Approved By’ names on the switch order will be removed on upgrade, because they are stored differently in releases after 9.3.1 SP1.
- The first time a switch order is opened (if it existed prior to an upgrade from a release before 9.3.1 SP1) and closed, the form will show a ‘dirty data’ message requesting a save. After saving, this issue will no longer occur.
- Already executed Tag/Ground removal steps will not show which Tag/Ground was removed. This is only if a switch order existed prior to an upgrade from a release before 9.3.1 SP1 and is still in the incident grid at the time of upgrade.