Create a Package for an App Volumes Application

A package stores one or more programs required for the application to run. You can create a package for an application either immediately after creating the application or at a later point in time.

When you create a package, you provide the metadata such as name, storage, path, template, and description of the package. You can select a package stage that indicates the state of delivery of a package. For information about the package stages, see Lifecycle of an App Volumes Package.

You can configure when a package must be delivered to the end user by using the delivery modes: Classic and On-demand. For more information about the package delivery modes, see Understanding Package Delivery Modes in App Volumes.

In the following screenshot, the On-demand delivery mode is chosen when creating a package.

Prerequisites

• You must have already created an application.

  To create an application, see Create an App Volumes Application.

• You must have uploaded the template for packages to the datastore.

  To upload a template, see Upload Templates.

• If you want to configure the package delivery mode as On-demand, ensure that you are aware of the required criteria and the behavior of the application package when delivered to the end user.

  For information about the criteria and characteristics, see Understanding Package Delivery Modes in App Volumes.

Procedure

1. From App Volumes Manager, go to INVENTORY > Applications.

2. Select an application and click Create Package.

3. On the Create Package page, provide package details such as Name, Base Package, Storage, Path, Template, Stage, and Description.

   • When a package is created, the filename of the volume created on the datastore is the same as the package name. Ensure that the volume filename is unique in the datastore directory.
   • Base package acts as reference when you opt to create a version of a package by using an existing version as base. Note: You cannot use the Create functionality to create an MSIX app attach format in Omnissa App Volumes. As a result, this format is not listed in the Base Package dropdown box.

4. Select the package Delivery mode.

   • By default, the package delivery mode is Classic.

     If you select the default value, you cannot change the delivery mode to On-demand until you complete package capture.

   • If you configure the package delivery mode to On-demand, you can edit the delivery mode to Classic regardless of the package status.

     When a package is delivered as on-demand, the attachment occurs only when the end user launches the application.

   • If you have selected the Do not deliver for these assignments at startup or login option on the Assign Application page, then the assignment option overrides the package delivery option selected in this task.

     For more information about the command-line delivery behavior, see Command-line Delivery of Applications in App Volumes.

5. Click Create.

6. On the Confirm Create Package window, select one of the options and click Create.

   Option	Action
   Perform in the background	The package gets created for the application in the background and you can perform other tasks. Note: Status of the package is Creating.
   Wait for completion	You must wait until the package is created for the application. You cannot perform any other tasks until the package gets created.

Results

The newly created package details are displayed in the Packages tab.

As soon as a package is created, a Launch Links table is displayed in the application details page. This table is empty until the application is packaged successfully. For more information about this table, see Launch an App Volumes Application with an App Link.

What to do next

Package an App Volumes Application