Creating a VAA
The AppZeroTM Creator is used to build a VAA. It features a wizard-based graphical user interface that steps a user through the process of defining which files and registry keys an application needs to run. Once identified, they are included in the VAA file along with defined properties. VAA properties can be modified as needed and include: network identities such as hostnames, IP and MAC addresses; and machine properties such as a system ID. The Creator controls all the files that make up a VAA.
Any tool that is usually used to install an application onto a machine can be used to install into the VAA including the use of a package manager, TAR or ZIP archive. The installation process is executed in the context of the VAA. Therefore, the files from the installation are placed in the VAA file set instead of in the file space of the underlying operating system.
The finished VAA
When finished, a VAA is a single compressed and encrypted file that includes all elements of an application and its dependencies that are required for execution. Elements include:
- Binaries, executables, and registry keys that are shipped and installed with the application
- Scripts created to extend the capabilities of the software
- Configuration settings created during installation and setup
- System files and libraries may also be included
The skill level required is equivalent to an operations application specialist.
Creating a VAA for an installed application
If the application to be packaged is already installed, configured, and running on a machine, AppZero's intelligent application discovery assists in the file and registry selection process. The user executes the application with AppZero in "learn mode". The Creator monitors access sequences and patterns to identify which files should be placed in the VAA. Items can later be added to the VAA by a simple copy. This approach is typically used when a fresh install is not possible and requires knowledge of the target application.
Creating a VAA for an application that is not yet installed
For applications that are not yet installed, the user begins by creating a "baseline" VAA. A snapshot of the system is taken before the application is installed. After installation, the VAA is created by referencing the original snapshot, and capturing changes that are made to the system. If the application is configured beyond its basic install, those changes are also captured.
At runtime
The AppZero Director provides the isolation and control that enables an application to run in the context of a VAA, merging the underlying OS view with components in the VAA at runtime. The configuration of the baseline OS, registry entries, directories and files are parameterized and resolved at runtime by the Director.
For more details, review our VAA Overview & Use Cases white paper.
