Creating a VAA

AppZero Creator

Virtual Application Appliances (VAAs) are created using AppZero™ Creator, an interactive utility that packages an application with all required files.  The skill level needed is equivalent to an IT operations application specialist.  The time required of course varies with the complexity of an application but averages 2-4 hours.

A wizard-based graphical user interface that steps the user through the process of defining which files should be included in the VAA file set and what properties it should have,  Properties defined in VAA creation can be modified as needed and include: network identities such as hostnames, IP and MAC addresses; and machine properties such as a system ID.

When finished, a VAA includes all elements of an application and its dependencies that are required for execution in a single compressed and encrypted file.  Elements include:

• Original binaries and executables that are shipped and installed with the application
• Codes and scripts created to extend the capabilities of the software
• IT generated configuration files created during installation and setup
• System files and libraries used by the application during execution

The VAA file set

The VAA file set provides per-file control over how processes running within a VAA access both its own files and those that are host-based.   The user creates rules during creation of the VAA by selecting files and directories from a list of all files available on the host system.   For each selected file or directory, the user can determine whether or not this element should be included in the VAA.

The user can also "hide" files so that the VAA won't see them, even if they are in the underlying host.  AppZero allows the user to control where new files will be created by applications running in a VAA - either within the VAA or on the host system.  The user has control of the search order that applications running in a VAA will use when looking for a file or directory (host then VAA, or VAA then host).

Here's an example:  An IT admin wishes to encapsulate a web browser for deployment to all users in an organization.   The admin may choose not to include the browser's configuration/options file in the VAA file set, so that the browser's behavior is not pre-defined.  He or she may elect to have new files that the browser creates get created in the host system so that the VAA doesn't get modified with temporary cache files or other files that are specific to a user or session.   For security reasons, the admin may elect to always have the browser ignore any certificates that are installed in the host by "hiding" that host directory from the VAA,  so that even if files are there, the browser is unable to see or access them.

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 selection process.  The user executes the application.  The Creator monitors access sequences and patterns to identify which files should be placed in the VAA.  The intelligent discovery output defines the VAA file set.

Creating a VAA for an application that is not yet installed

For applications that are not yet installed, the user creates a "baseline" VAA that describes the set of properties and an empty file set.   This baseline file set could include all the common files that should be included with a class of VAA , for example,  all files in /var/www for a web server.

After the baseline VAA is created, any tool that is usually used to install an application on a system, 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.

At runtime

The configuration of the baseline OS, registry entries, directories and files are parameterized and resolved only at runtime.