Term | Description |
Version Path | A required document that you create in the AUT Catalog to define and upload an install executable file for a new version of Notes, to prepare for deploying it to AUT servers.
A Version Path defines:
- Type of client kit (platform). For example, for a Notes client StandardAllClient-Win32,StandardNotesClient-Win32, orBasicNotesClient-Win32. Or, for an HCL Client Application Access (HCAA) client,HCAA-Win32.
- Version(s) to upgrade from;
- Version to upgrade to.
For example, a Version Path document could define an upgrade of Notes StandardNotesClient-Win32from 10.0.1 to 10.0.1 FeaturePack 1. |
Version Map | A required document that you create in the AUT Catalog that lists at least one Version Path to apply to a set of users. Selecting a Version Map in the Client Upgrade -> AUT tab in a Desktop Settings policy is required to upgrade clients of a group of users.
A Version Map can list multiple Version Paths. For example, a Version Map that lists the following two Version Paths allows both Notes standard and basic clients to be upgraded:
- Upgrade StandardNotesClient-Win32 from 10.0.1 to 10.0.1 FeaturePack 1
- Upgrade BasicNotesClient-Win32 from 10.0.1 to 10.0.1 FeaturePack 1
|
Install manifest | An XML file that describes an install executable file that is provided with the web download kit for a new Notes or HCAA version. It provides information such as the release number, the type of client, the language, and the name of the install executable file. When you create a Version Path document, you can import the install manifest so the install executable file information is populated for you.
Here's an example of install manifest content for Notes:
<?xml version="1.0" encoding="utf-8"?><manifest appid="{3E1B33CC-8C2E-4EED-B6A2-3BB3EE0ACFF1}" name="StandardAllClient-Win32" version="Release 10.0" lang="en"> <packages> <package name="setup10.0.exe" size="81830632" hash="sg+3qzEtiK7djQ23+Glcjs4TI24="/> </packages></manifest> |