Upgrading Responder Mobile

This section walks you through upgrading Responder Mobile after installing the latest version. Schneider Electric provides batch scripts to update your configuration files to use the latest version.

Responder Mobile releases prior to 10.1 provided new configuration files, which required users to re-configure a number of XML files. Responder Mobile now supplies batch scripts which automate this process. These batch scripts preserve your existing configuration files and append changes that support new functionality, thus eliminating the need to manually re-configure after each new release.

After installing the Responder Mobile components do the following:

Steps 1-4 are required only on machines with the Responder Mobile Client installed.

Look for the ResponderMobile.exe.Config file in an AppData folder of a mobile user. For example: C:\Users\[user name]\AppData\Roaming\Miner and Miner\Responder.

Open this file and remove the following section (your TaskOwner value may be different):

<taskConfiguration>
    <taskLoginConfiguration TaskOwner="33" />
  </taskConfiguration>

Save and copy this file to your Responder Mobile Client installation location, typically C:\Program Files (x86)\Miner and Miner\ArcFM Mobile\Bin.

Return to the AppData folder and remove the ResponderMobile.exe.config file.

In addition, for any user that has the ResponderMobile.exe.config file in their AppData folder, delete the file prior to running the batch script.

Run the installed batch script to automatically update the configuration file. If you are installing Responder Mobile for the first time, this step is not necessary. Just double-click the batch script to execute. The script will create a backup of your original file before performing the upgrade:

Mobile Web: C:\inetpub\wwwroot\MobileServices\Developer Resources\10.0.3 - 10.1.0 Upgrade Scripts\UpgradeMobile.bat
Mobile Client: C:\Program Files (x86)\Miner and Miner\ArcFM Mobile\Developer Resources\10.0.3 - 10.1.0 Upgrade Scripts\UpgradeResponderMobileClient.bat

All releases may not require upgrade scripts for all components mentioned above. The directory will contain only the scripts necessary for the corresponding release.

There are a few cases in which you may need to manually configure these files (rather than using the batch script):

The batch script fails. Some customizations to the configuration files may cause the upgrade script to fail.
You have a release version older than 10.0.3. This functionality was introduced with 10.1 and only supports upgrades from 10.0.3 to 10.1 and beyond.
Batch scripts frighten you. Really, there's nothing to fear. These are friendly batch scripts.

If you need to update manually, first back up your original configuration files. You may wish to use these files to copy your previous configurations into the current configuration files.

Copy these files from the Developer Resources folders and paste them over your (backed-up!) original configuration files.