VirtualApp Data
Structures
The
VirtualApp
managed object contains the
ExportVApp
method, which returns an
HttpNfcLease
. The
HttpNfcLease
contains the info and state properties, where
info is of type
HttpNfcLeaseInfo
and state is of type
HttpNfcLeaseState
. The
HttpNfcLeaseInfo
data object has several properties, one
of which is the
deviceUrl
of type
HttpNfcLeaseDeviceUrl[]
. The
HttpNfcLeaseState
has four different
states—done
,
error
,
initializing
and
ready
.
The following class diagram shows the UML
representation of the data structures used in the VirtualApp API.
VirtualApp Class Diagram
The VirtualApp API data structures are the
following:
- VirtualApp—A managed object that is a collection of virtual machines (and potentially other VirtualApp containers) that are operated and monitored as a unit.
- HttpNfcLease—A managed object returned when you callVirtualApp.ExportVApp. It represents a lease on the virtual application. While you hold the lease, you block the operations that alter the state of the virtual application.
- HttpNfcLeaseInfo—A data object that holds information about the lease, such as the virtual application covered by the lease, and the device URLs for up/downloading images.
- HttpNfcLeaseState—An enumeration that is a list of possible states of a lease.
HttpNfcLeaseDeviceUrl
—A data
object that provides a mapping from logical device IDs to upload/download URLs.