Exporting Composed OVF into distribution format

An OVF package can be represented as a set of files, or as a single file using the TAR format. If the OVF package is the single file format, the extension of that file should be .ova (open virtual appliance or application).

For OVF TAR archives, the files shall be in the following order inside the archive:

If the manifest or certificate files are present, they shall either both be placed after the OVF descriptor file, or both be placed at the end of the archive.
For deployment, the ordering restriction ensures that it is possible to extract the OVF descriptor from an OVF TAR file without scanning the entire archive.
The TAR format used shall comply with the USTAR (Uniform Standard Tape Archive) format as defined by the POSIX IEEE 1003.1 standards group.

Are the files to be packaged along with the envelope and other optional files? (Required for local file references but optional for http or https protocols).
Are any of the files resource translation bundles? (They need to be ordered first in the file list).
Do you want to have a manifest file created? (Which will cause the file digests to be calculated).
Do you want the file sizes calculated (or recalculated)
 

The following diagram illustrates the dialog where you indicate you file processing options.