|
|
|
|
|
|
|
|
|
|
- Overview
- Configuring the history of versions
- Version history
The history of setup versions is an advanced feature of the network setup. This feature is used to keep on the reference server one or more earlier versions of the application. This allows the user to go back to an earlier version if a problem occurs. The history of versions is also used to install on the server the next upgraded version of an application without sending it to all the customers. This is used to distribute a version to the "beta testers" before it is made available to everyone. Note: Version history only applies to LAN installations. The history of versions is not available for the network setups by IP. Configuring the history of versions The history of version is configured when installing the reference version of the application. The following plane is displayed during the setup: To enable the history of versions, all you have to do is check the corresponding box. Two parameters can be configured: - The number of versions that will be stored (in addition to the current version). If this parameter is equal to 0, the number of versions stored is unlimited.
- The global size of the history of versions (in MB). If this parameter is equal to 0, the disk space used to store the history of versions will be unlimited. The approximate size of a version is specified for information.
If the two limit parameters are specified, the lowest of the two limits is used. The history of versions is managed via the Control Center of Network Applications (WDAdminExe.exe). The Control Center of Network Applications is installed in the INSTALL subdirectory of the reference setup of the application. The tab for managing the versions is as follows:
1: Version currently viewed by client workstations. 2: List of versions present in the reference installation. The help for the history of the selected version is proposed (if it is available) in the right section of the window. 3: Available operations for each version: - Prohibit a version: The selected version will be prohibited. The users can no longer go back to this version. The client computer deployed in this version will be forced to update when the application is started for the next time.
- Authorize a version: The selected version will be authorized. A user can choose to change the current version installed on his computer via the "?" menu (for more details, see The? menu). This option allows a user to go back to the earlier version if a problem occurs (if this earlier version operated properly).
- Force version: The selected version will be forced on all client workstations the next time the application is launched, even if they are in a more recent version.. This option is used to make the version installed on the client computers "move forward" or to make the beta testers "go back" to an "official" version.
- Release version: This option cancels the effects of "Force version".
4: Activates a version. When updating the reference version, you have the ability to request the activation of the version from the setup wizard. 5: Deletes an older version. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|