Files

The files listed below are the mandatory files to be delivered in the app process.

App File

.app is the filename extension for AppWave-Enabled application files. It is an application that was mastered with AppWave and must adhere to all of the App Mastering Acceptance Criteria.

App means that applications can be streamed from the AppWave and then run locally on the desktop without installation. This option also allows applications to be run on locked-down desktops. There are no conflicts with other applications, no writing to the system areas of their registry or modifying shared dlls. Application data such as Configuration and license information is stored locally on the hard disk, and is separate from the executable itself.

.aw File

The AppWave Template file offers a model for mastering an application, and contains branding information and information on which filter to run on the installer for the application. It must respect all of the “Acceptance criteria”.

The AppWave Template file (.AW) is created by the PADE Product Manager and is used to add Instant AppWave Mastering support to a server.

MD5 File

Message-Digest algorithm 5 (MD5) is used to check the integrity of files. The .aw and the .app files must come together with the associated md5 message digest file. Each time one of the two files needs to be changed, the .md5 file must be changed too.

.msi installer File

MSI files are database files, used by Windows Installer. They contain information about an application which is divided into features and components, and every component may hold files, registry data, shortcuts etc. The MSI file also contains the UI that is to be used for installing, and various other data such as any prerequisites to look for, custom actions to execute, the order of the installation procedure, whether to support Administrative installations, etc. MSI files are the current recommended way of doing installations on Windows.

The  .msi files provided must have the ability to run in Unattended mode.

.stp File

STP File is created after the author masters the application and can be found in the output folder. This file is the outer layer that encapsulates the other application components. It is encrypted and stores the files, folders, and registry settings needed to reproduce the application being mastered on the end users machine.

The .stp file includes:

File Type

Description

Aib (application installation blueprint)

This file contains all the files’ metadata (filename, file path, file size, etc) and registry information (registry keys and values) for the mastered application.

Stc (streaming content file)

The code and other configuration information that comprises most of the application.

Tok (token)

Token Files are comprised of security data and general information about the mastered application

Ico

icon file

htm

EULA file

None of the files contained in the .stp file need to be altered or deleted.

Studio File

The Studio or .tca file is the project file in the AppWave Browser.The .tca contains the registry and folder and files structure captured during a software installation along with resources, launch points, and registry settings required to run a product.It also contains information about the product such as the version, name, and editions. Every time a user needs to master an App, a .tca file is created.