There are two options for distributing Adobe AIR:.Stand-alone Adobe AIR Runtime distribution—Use this AdobeAIR Runtime Installer if you plan to distribute the Adobe on individualsystems, on an intranet, or via an enterprise setting. See the nextsection,.Bundled deployment of Adobe AIR Runtime Installer files—thisis also known as a “sidecar installation.” Use this to include theAdobe AIR installer on a CD, DVD, USB, or DMG. This option letsusers install an AIR application and the runtime simultaneously.See.In addition to the files for each of these two options, the AdobeAIR download site also includes the following:.A link to this documentation.The AIR Redistribution Helper (ARH) utility, which you canuse to streamline the install process. See.The OSID Generator application has been replaced by the ARHutility. The OSID Generator program is still supplied for developerswho have existing installation code. If you are developing a newinstaller, use ARH instead. The OSID Generator helps you discoverthe file path to an installed AIR application, given the applicationID and publisher ID of the application.
![]()
See.TheAdobe AIR logo. You may download the logo and use it in accordancewith the Adobe AIR Runtime Distribution License Agreement you acceptedand the “Includes Adobe AIR Logo Usage Guidelines” found at. Note:This is like the seamless install feature, whichalso lets a user install Adobe AIR and an AIR application simultaneously.However, the seamless install feature installs from a web page,not from a disk.Download the bundled runtime installer from the runtimeredistribution download site. For Mac OS, this is a DMG file. ForWindows, this is a ZIP file. For Linux, this is a tar.bz2 archive.Extract the contents of the file to a directory, which this documentrefers to as thebundled runtime installer directory.OnLinux, extract the file using the following command:tar xvf AIRLinuxinstallerfiles.tar.bz2.Rename the Adobe AIR installer to match your applicationname. For example, on Mac OS or Linux if your application is namedMyApp 2.0, rename the installer MyApp 2.0 Installer.
Important:Use the-eulaAcceptedoptiononly if your organization has agreed to the Adobe AIR end-user licenseagreement. You can only specify the-eulaAcceptedoptionif the organization has agreed to the Adobe AIR end-user licensefor all users of the computer. You can only specify the-eulaAcceptedoption for deployment within an intranet.Ifyou donotinclude the-eulaAcceptedoptionand Adobe AIR is installed during a silent installation, Adobe AIRwill later present the Adobe AIR end-user license agreement to eachuser of the machine. Users see the end-user license agreement (withthe option to accept it) upon first running an AIR application.Ifused, specify the-eulaAcceptedoption immediatelyafter the ‑silentoption.pingbackAllowed— Allows the installer to check forupdates to the AIR runtime and report a successful install to Adobeover the Internet. No identifying information is transmitted.location—The optional-locationoptionprovides the location (an absolute file system path) to installthe AIR application. The default location is the standard applicationinstallation location.desktopShortcut—The optional-desktopShortcutoptioncauses the installer to install a desktop shortcut for the installedAIR application. If you do not specify this option, no desktop shortcutis installed.programMenu—The optional-programMenuoptioncauses the installer to install a program menu shortcut for theinstalled application (on Windows).
If you do not specify this option,no program menu shortcut is installed.path—Thepathoption specifies thepath to the AIR file to install.The AIR application installerinstalls the correct version of Adobe AIR on the target computer,as required by the AIR application to be installed. For example,if the AIR application to be installed requires the AIR 1.1 runtime,and the end user’s computer has only AIR 1.0 installed (or no versionof AIR installed), the installation process installs the AIR 1.1runtime along with the AIR application. The version of the AIR applicationinstaller must be compatible with the version required by the AIRapplication.Youcannotuse the silent installer optionto update aninstalledAIR application.
Mar 06, 2018 like and sub if worked comment so others can see.
This is because theAIR installer cannot determine whether the version to be installedis newer than the installed version, and it would pose a security riskto downgrade the application.To install or update the runtimeonly, use the-silentoption without specifyingapathor any other options. The OSID generator application has beensupplanted by the ARH utility. You can use ARH to detect and uninstallAIR applications directly.An OSID, oroperating system identifier, is a platform-specificidentifier for an installed application.
The OSID Generator applicationreports the OSID of an AIR application. The OSID for an applicationis the same on every computer. The OSID generator uses the applicationID and either the publisher ID string, or, if a publisher ID isnot used, an empty string.
Note:Prior to AIR 1.5.3, every application was assigned a publisherID that was based on the certificate used to apply the applicationsignature. While a publisher ID is no longer assigned automatically,applications published before AIR 1.5.3 can still use one.
Once you have an Adobe® AIR™ Runtime Distribution License Agreement with Adobe® Systems Incorporated, you may redistribute the Adobe AIR installer and installer files. This guide provides instructions on configuring and using the runtime installer.
Obtaining permission to redistribute the runtime
To obtain permission to redistribute Adobe AIR, read the Adobe AIR Runtime Distribution Agreement and apply for a license: Adobe® AIR™ Runtime Distribution .
Also, be sure to read the Adobe AIR FAQ page, which contains important information on the runtime distribution and license terms: Adobe® AIR™ Runtime Distribution FAQ .
Important: You may distribute Adobe AIR with your product only if you follow the Adobe AIR Runtime Distribution License Agreement application process and are then approved by Adobe. Otherwise, users can download and install Adobe AIR from the adobe.com site.
Installer files and options
There are two options for distributing Adobe AIR:
In addition to the files for each of these two options, the Adobe AIR download site also includes the following:
Using the stand-alone runtime installer
Once Adobe has approved your request to distribute Adobe AIR, you can include the stand-alone runtime installer file on individual systems or on an intranet. For Windows, this installer is an EXE file. For Mac OS, this is a DMG file. For Linux, this is an RPM, DEB, or BIN file. Administrative users can run this file to install Adobe AIR.
Important: The Adobe AIR Runtime Distribution Agreement does not allow you to distribute the Adobe AIR installer from your web site. However, you can use the Adobe AIR seamless install feature on your web site, which downloads and installs the Adobe AIR Runtime on end-user system as part of the AIR application installation. For details, see Distributing, Installing, and Running AIR applications and Updating AIR applications .
If you need to redistribute Adobe AIR using an enterprise deployment tool, contact Adobe for available options: [email protected].
Using the bundled runtime installer
You can include a bundled installer on a CD, DVD, USB, or DMG. The user can use this installer to simultaneously install your AIR application and install or update the Adobe AIR installer (as needed).
Note: This is like the seamless install feature, which also lets a user install Adobe AIR and an AIR application simultaneously. However, the seamless install feature installs from a web page, not from a disk.
You can deploy the contents of the bundled runtime installer directory on a CD, DVD, USB, or DMG and instruct the user to double-click the renamed installer file.
You can also call the AIR installer from a bootstrapper application. A bootstrapper application is a native application that manages multiple processes (such as the installation of many files and applications). You can also use a bootstrapper application to manage the process of downloading all files and calling the appropriate installer commands when downloaded. The bootstrapper application can provide a custom user interface (for example giving users options to install other files or applications). The ARH utility can be used to initiate most of the AIR-related tasks of the installation.
You can use a tool to bundle all of the files into a self-extracting executable file. A bootstrapper application can load this self-extracting executable file and run the installer.
For Linux, support for bundled runtime installation was added in AIR 2.
Note: On Mac OS, take care to preserve the symbolic links when repackaging the installer files. Do not unpack or repack the files on a file system that does not support symbolic links.
Silent installation
Generally, the AIR Installer presents its own user interface while installing the runtime and the AIR application. The silent installation feature lets you install an application without presenting or interacting with the AIR Installer interface.
You can use silent mode to install Adobe AIR using an enterprise deployment tool (such as Microsoft SMS, IBM Tivoli, or any deployment tool that allows silent installations that use a bootstrapper).
To run the Adobe AIR installer silently, start the Adobe AIR installer with the following command-line options:
Silent uninstallation
You can silently uninstall an AIR application using the ARH utility.
While ARH is the recommended method, you can also use the following methods:
On Mac OS, use rm -rf to remove the AIR application installation directory.
On Windows:
On Linux, pass the application ID and publisher ID for the application to the package manager (such as RPM or Debian), as in the following:
Runtime installer exit codes
The Adobe AIR installer outputs the following exit codes:
The AIR installer automatically creates log files in the following locations:
Using the ARH utility
The AIR Redistribution Helper (ARH) utility is a small executable that you can use as part of a custom installer.
To check whether the runtime is installed:
ARH exits with code 0 if the runtime is installed. It exits with code 1 if the runtime is not installed.
To get the installed AIR version number:
To install an application:
-location — the install location.
-desktopShortcut — if present a desktop shortcut icon is added.
-programMenu — if present, an entry is added to the program menu (Windows only).
file — the AIR file to be installed.
To uninstall an application:
appid — the application identifier specified in the application descriptor.
pubid — Required if and only if the application specifies a publisher ID. Publisher IDs are deprecated as of AIR 1.5.3. Only applications created prior to AIR 1.5.3 should use a publisher ID.
To query the state of an installed application:
appid — the application identifier specified in the application descriptor.
pubid — the publisher ID, if used by the application.
To locate an installed application:
To obtain an installed application's version (as a string):
appid — the application identifier specified in the application descriptor.
pubid — the publisher ID, if used by the application.
To update the current user's runtime state:
Updates the current user’s registry and configuration settings to reflect the fact that the application has been installed for that user. This command must be run from a non-elevated process (in other words, using the user’s account, not a separate administrator account).
![]()
If the updateUserState command is not performed, the AIR in-browser will not be able to detect the AIR application.
Using the OSID Generator application
The OSID generator application has been supplanted by the ARH utility. You can use ARH to detect and uninstall AIR applications directly.
An OSID, or operating system identifier , is a platform-specific identifier for an installed application. The OSID Generator application reports the OSID of an AIR application. The OSID for an application is the same on every computer. The OSID generator uses the application ID and either the publisher ID string, or, if a publisher ID is not used, an empty string.
Note: Prior to AIR 1.5.3, every application was assigned a publisher ID that was based on the certificate used to apply the application signature. While a publisher ID is no longer assigned automatically, applications published before AIR 1.5.3 can still use one. Such an application still uses the same publisher ID even after being updated to AIR 1.5.3 or later.
In AIR 1.5.3, or later, both the application ID and the publisher ID, if used, are specified in the application descriptor file.
For AIR applications published before AIR 1.5.3, you can determine the publisher ID by reading the contents of the publisherid file, which is in the META-INF/AIR directory in the installed AIR application.
On Mac OS, the OSID Generator application returns a bundle identifier. To find the application, pass the OSID as the inBundleID parameter of the LaunchServices LSFindApplicationForInfo() function. The object passed as the outAppURL parameter of the LSFindApplicationForInfo() function is set as a pointer to the application.
On Windows, the OSID Generator application returns a globally unique identifier (GUID). This GUID is the upgrade GUID as well as the component GUID of the component containing the main application executable. You can use these to locate the installed application:
On Linux, OSID returns the name of the native package for the application.
![]() Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |