Destiny Auto Update Overview

The auto-update process is for minimal revisions and updates. You can configure Destiny to automatically install updates at a time you choose, eliminating the need for manual hot-patching. It is a quick, hands-free way to automatically keep your Destiny installation up to date.

Important: Auto-update does not replace the Destiny upgrade process.

This process includes the following main steps:

Find and schedule updates

  1. Destiny checks periodically for updates by connecting to the auto-update server at https://destinyupdate.follettdestiny.com and sends its current version number to the server. If an update is available, Destiny:
    • Downloads a zip file containing the update. There may be multiple updates contained in a single download.
    • Displays a notification that the update is available in a green bar at the top of the page.
    • Displays a link to a pop-up describing the contents of the update.
  2. The server administrator can only see the:
    • ASP Administrator for Follett Destiny Cloud
    • Super Administrator for a consortium
    • Destiny Administrator for a district

    If you enabled email notifications for auto-update, Destiny sends an email.

    If you configured a scheduled time for the auto-update, Destiny creates a scheduled job.

    Note: To configure notification and automatic installation of updates, log in as the server administrator and edit the Auto Update Settings on the Options sub-tab of the Setup page.
  3. The auto update process begins when either:
    • The scheduled time arrives.
    • The server administrator starts the update manually.

Destiny runs the auto-update

  1. The auto-update process prevents new jobs from starting, and Destiny does one of the following:

    • Gives current jobs 30 minutes to finish. Waits an additional 30 minutes if any jobs are still running after the initial 30 minutes. If any jobs are not finished at this time, the update fails and an email notification (if configured) is sent. The notification bar appears again, and if an auto-update scheduled time is enabled, Destiny creates another scheduled job.

    • If all jobs are complete, the auto-update process continues.

  2. Destiny creates an empty Job Summary file (a blank HTML file) in the DistrictResources folder. This file is later populated with information by the auto-update process.
  3. Destiny starts a separate Java process to execute the auto-update. Then, Destiny changes the status of the Auto Update job to Completed in the Destiny Job Manager, even though the separate auto-update process is still running.
  4. The auto-update process executes the update contained in the zip file and logs the results into the empty Job Summary file created earlier.
  5. After Destiny restarts, view the results of the auto-update process by opening the Job Summary file in the Job Manager.

For a printable version, see Destiny Auto Update Overview.