Updating Specific Clocks Within a Clock Type

You can configure updates for specific clock type’s as well specific clocks within these clock types. For example, if you had several clocks of the type Biometric you could configure an update so that only clocks of this type download any updates. Furthermore, if a different update for a specific clock within the Biometric type is required, you can configure an additional update just for this specific clock.

To update specific clock(s) within a clock type:

  1. Ensure the wbsynch.softwareupdates.type setting in the settings.conf file of each clock has been set to the correct type name.
  2. Determine the system download directory by checking this registry parameter:

    /system/clocks/DOWNLOAD_DIR

  3. Create sub-directories in the system download directory with the type name specified in the parameter wbsynch.softwareupdates.type for each clock type you want to update. For example, Biometric.
  4. Create a sub-directory within the clock type directory specified in step 3 to match the clock's specific name as specified in wbsynch.webservice.serverName parameter of the clock's settings.conf file. For example WB9000-Cafeteria.
  5. Create an update directory named update.a-b-c-d.dir, where a-b-c-d represents the version of the update as provided by Infor.
  6. Place the fix pack or hot fix file provided by Infor in the update directory named update.a-b-c-d.dir in this location: /<system download directory>/Biometric/WB9000-Cafeteria/<update.a-b-c-d.dir>/.
  7. If you want to retain or apply any custom configuration settings or copy custom files to the clock(s), see Configuration Updates for the Clock.
  8. Copy the update directory to the directory specified in step 4 on the application server.
    Note: Repeat this step for each application server node in a clustered environment.
  9. Once the update directory has been copied to the system download directory as specified by the registry parameter, place an empty text file named update.ready in the system download directory or in every directory that contains files that must be downloaded by your clocks. If there is no update.ready file, then your clocks do not see the directory and do not start processing the upgrade.
    Note: Repeat this step for each application server node in a clustered environment.
  10. The above-specified clock in the specified clock type will automatically download and apply the update on the next scheduled update as configured in the clock's settings.conf file.