The sequencer will extract out the contents of the SFT file and restore the application to the end state from the last sequence.
The sequencer user then simply restarts the Monitoring process in the sequencer, and once monitoring restarts, the user performs any updates to the application as necessary.
When discussing the different methods for updates, it is assumed that users are already running an existing version of the application, delivered through Soft Grid.
Soft Grid applications are stored with a unique GUID identifier that is embedded into the SFT file at the time of sequencing.
Simple file and registry changes can be made, along with more complex updates such as a package installer like a service pack.
Once the application updates have been completed, the sequencer user stops monitoring and the sequencer will process all the updates. Once the sequencing is completed, all of the new package files are copied up to the content share.
This article will review the three methods and the associated benefits and considerations.In this configuration, the existing package is copied down to a sequencer workstation.The package is then Opened for Package Upgrade, a function found in the sequencer.The Shortcut Wizard is then re-run, reconfirming that the application still works in Soft Grid. The sequencer will recognize that this package is an update and append an underscore and an increment number to the SFT files (e.g., EXAMPLEAPP. Next, the Soft Grid administrator adds a new Package version into the Soft Grid Management Console, referencing the new SFT file.
This allows the Soft Grid server to manage applications independently of their filenames or content.
On the Soft Grid client, the machine and user settings for each application are managed by the SFT GUID, allowing settings to be managed at the same level.