Upgrading Properties Files

Learn the steps to upgrade the Vocera Voice Server and Vocera Voice Server components properties files.

The Vocera uses several files to define default properties and behaviors for Vocera components. Vocera Administrators can customize these files to suit business needs. For example, you might need to define custom behaviors for badges in your environment. If you have customized any of the files listed here, be sure to back them up before you begin any upgrade.

The following files define properties and profiles for Vocera Voice Server and Vocera SIP Telephony Gateway.

Product Properties File
Vocera Voice Server
  • \vocera\server\properties.txt
  • \vocera\config\badge.properties.txt
  • \vocera\config\profiles.txt

Vocera SIP Telephony Gateway

Vocera Client Gateway

\vocera\telephony\vgw\vgwproperties.txt

These files provide default values that are appropriate for most installations.

If you have edited one or both of these files to specify specialized behavior, this topic tells you how to preserve these changes when you migrate to Vocera 5.3.2. If you have not changed the default values in these files, you do not need to perform this task.

To upgrade the property files:

  1. Find your customized Vocera property files from the previous release.
    You copied these files to a flash drive or to a temporary location on a network drive before installing Vocera 5.3.2.
  2. Find the new property files in the locations specified above.
  3. Merge the changed data from the backup files into the new files.
    Several text editors—especially programs designed for editing source code—provide a merge feature. You can also copy and paste the data by hand.
    Note: Vocera 5.3.2 has a new speech recognition engine that does not require the SysRecParms or SysFreqDeptRecParms properties. If you have set these properties, comment them out; Vocera 5.3.2 does not recognize them.
  4. To load the updated properties.txt file, restart the Vocera Voice Server(s).
    If you have a Vocera Voice Server cluster, restart the standby node(s) first. The standby node(s) automatically perform a remote restore. After remote restore is completed on the standby node(s), force a failover on the active node by choosing Cluster > Failover in the Vocera Control Panel.
  5. To load the updated vgwproperties.txt restart the Vocera Client Gateway server(s).
    If you have multiple Vocera SIP Telephony Gatewayservers, restart one server at a time. Wait until the server has started before restarting the next server in the array until all servers have been restarted.