Understanding SnAppShot

SnAppshot records the changes that occur on a workstation as an application is installed. As the installation proceeds, snAppShot captures the differences between the workstation's pre-installation configuration state and the workstation's post-installation state, compares the two pictures, and creates an application installation package that consists of two Application object template (.aot or .axt) files, one or more application source (.fil) files, and one file definition (filedef.txt) file.

Application Object Templates

You use the Application object template file to create the Application object in Novell eDirectoryTM. Both Application object template (.aot and .axt) files contain the same information, which is used to populate the Application object property fields during creation of the object:

The .aot file is a binary file that cannot be edited; the .axt file is a text file that can be modified with a text editor. If you need to modify the Application object template after snAppShot has created it, you should modify the .axt file and use it to create the Application object. Otherwise, you should use the .aot file because data from the .aot file is imported more quickly.

Application Source Files

SnAppShot also tracks all of the application files that are copied to the workstation. These files, which become the application source files, are copied to a network source location, renamed numerically starting with 1, and given a .fil file extension (for example, 1.fil). Novell Application LauncherTM uses these source files when installing the application to the workstation.

Application File Definition File

To map the .fil files to their original files, snAppShot creates a file definition (filedef.txt) file. This text file not only maps the .fil files to the original files, but also specifies the target location and name to be used when installing the files to the workstation. For example:


SnAppShot Limitations

Please be aware of the following before using snAppShot: