Deploying Air package via Air installer

I am attempting to deploy a .air package as part of the Adobe AIR installer as detailed by the Adobe deployment documentation.
Adobe AIR 1.5.1 is stored under \\server\My Installs\Package\1.5.1 and the package is \\server\My Installs\Package\
I have configured a file called .airinstall.cfg (using Command Prompt as Windows Explorer will not allow leading dots) and the contents of the file are as follows:
..\package.air
However, upon running Adobe AIR Installer under an admin account (also tried using it renamed as package.exe) the egg timer appears briefly, disappears, then nothing happens. Neither AIR nor the package are deployed. I have tried changing the contents of the .airinstall.cfg file to the full path
\\server\My Installs\Package\package.air
However, this leads to the same issue. If I remove the .cfg file then the Adobe AIR Installer launches as expected.
Clearly there is something wrong with my .airinstall.cfg file, but checking the docs again I'm not sure what.

Hi,
AIR file internally is a zip file, and if you upload this file on any web server, by default it will show up as zip file only.
To make the AIR file to open up with AIR installer, you need to set the MIME type of AIR file in the web server configuration.
There are many articles on net which talks about adding AIR MIME type in web servers.
I googled and found many articles, adding link to some of the articles
http://www.davidtucker.net/2008/01/08/update-your-air-mime-type/
http://blogs.adobe.com/ashutosh/2009/02/setting_the_correct_mime_type.html
Hope this will solve your problem.
Thanks
Praful
Adobe RoboHelp Team

Similar Messages

Is there a way to deploy Adobe Air package via Group Policy or SCCM?

Is there a way to deploy Adobe Air package via Group Policy or SCCM?

hi,
I guess you can try the following options
Remove the all the entry from the TOC of your project or create a new blank TOC and select that while AIR file generation
Remove the all the entry from the index of your project or create a new blank index and select that while AIR file generation
Remove the all the entry from the glossary of your project or create a new blank glossary file and select that while AIR file generation
THis will ensure that TOC/Index/Glossary page is not shown,
There is no way to hide Favorite or RSS from the AIR Help. Again, you can try looking at the Unipane Template provided in the AIR SSL Dialog.
Hope this helps
-Praful Jain

Packaging an AIR application in a native installer

Hi! I'm trying to create a native installer of my AIR Application, because (I think) it's the only way make the native processes working. But I have a problem: I used the following command to pack: "adt -package -storetype pkcs12 -keystore myCert.pfx -target native -storetype pkcs12 -keystore myCert.pfx myApp.exe myApp-app.xml", but I get the error: "File myApp-app.xml is not a valid AIRI or AIR file". In the Flash Builder I use as additional compiler arguments: "-locale=pt_PT,en_UK,fr_FR,de_DE,ro_RO,es_ES -allow-source-path-overlap=true -source-path=assets" and I add the source path "src/locale/{locale}/". What is the sintax for packing my AIR application in a native installer? Thanks in advance.

Hi again! Thanks for the reply. I based myself on the link to see what command syntax I should use to pack my Air Windowed Application and it was the command that I presented in the previous post.
adt version "2.0.1.12090"
                                              My Descriptor File
<?xml version="1.0" encoding="utf-8" standalone="no"?>
<application xmlns="http://ns.adobe.com/air/application/2.0">

    
    <id>com.MyCompany.Application</id>
    
    <filename>Production Control System</filename>
    
    <name>Production Control System</name>
    
    <version>2.1.3</version>
    
    
    
    
    
    
    
    <initialWindow>
        
        
        <content>[This value will be overwritten by Flash Builder in the output app.xml]</content>
        
        
        
        <systemChrome>none</systemChrome>
        
        <transparent>true</transparent>
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
    </initialWindow>
    
    
    
    
    
    
    <supportedProfiles>extendedDesktop</supportedProfiles>
    
    
    
    
    
    
    
    <customUpdateUI>true</customUpdateUI>
    
    
    
    
        
        
            
            
            
            
            
            
            
            
            
            
        
    
    
    
        
        
    
</application>

Use adt to package an air installer success, but install this air file "sorry , an error has occured

hi everyone, i am using a bat file to package an air file ,
this application runs on windows 7 32 bit,
it need to call another windows application , so i google and then find i need to add -target native when package , so i added.
the bat file is like below:
========================================
@echo off
:: AIR application packaging
:: More information:
:: http://livedocs.adobe.com/flex/3/html/help.html?content=CommandLineTools_5.html#1035959
:: Path to Flex SDK binaries
set PATH=%PATH%;C:\AdobeAIRSDK\bin
:: Signature (see 'CreateCertificate.bat')
set CERTIFICATE=yeahCert.pfx
set SIGNING_OPTIONS=-storetype pkcs12 -keystore %CERTIFICATE% -tsa none
if not exist %CERTIFICATE% goto certificate
:: Output
if not exist air md air
set AIR_FILE=air/jonnson.air
:: Input
set APP_XML=application.xml
set FILE_OR_DIR=-C bin .
echo Signing AIR setup using certificate %CERTIFICATE%.
call adt -package %SIGNING_OPTIONS% -target native %AIR_FILE% %APP_XML% %FILE_OR_DIR%
if errorlevel 1 goto failed
echo.
echo AIR setup created: %AIR_FILE%
echo.
goto end
:certificate
echo Certificate not found: %CERTIFICATE%
echo.
echo Troubleshotting:
echo A certificate is required, generate one using 'CreateCertificate.bat'
echo.
goto end
:failed
echo AIR setup creation FAILED.
echo.
echo Troubleshotting:
echo did you configure the Flex SDK path in this Batch file?
echo.
:end
pause
======================================================
after run this bat , the air file is successfully built , but when i want to install this air , it says "sorry ,an error has occured ..... bla bla installer file is damaged....bla bla "
but when i remove the red part -target native in the command above then run it again , the new packaged air file can install successfully, but the application can not call other windows apllication anymore, nativeprocess.issupported always returns false when running
so seems like the problem is all about -target native , deos anyone know whats wrong ?
this problem really bothers me long time , any help will be appreciated. thanks in advance!

Nice! I swear I tried that URL (substituting "mac" for "win" and "MAC" for "WIN" in the one relaxatraja posted), but I guess I missed something.
Ironically, it doesn't include a binary either, but a simple alias works:
alias pfi='java -jar /path/to/PFI/lib/pfi.jar'
And it did indeed produce an ipa without error. I don't have my hardware with me, but I'll be able to test it tonight. Meanwhile, I think I'm in business. Thank you all!

Adobe Air installation status issue via silent installation

I installed adobe air silently, then installed an adobe air applicaiton silently. Everything works, and I can launch the application. However, if I use the status check via air.swf file it has the "available but not installed" and it can't retrieve the version of my air application. Once I double click on "any" .air file, it launches the non-silent installer, and I don't have to even install or update the app, just lanching the iapp nstaller non-silently seemed to correct something. From then on air.swf statu now returns "installed" and it can read the version of my app. Can anyone tell me what's going on and how can I correct this?

Ok, I understand. So before we continue, we really need to figure out what the exact error is. Can you, on at least 2 systems, generate the MSI logs we'll need? Here's a document that explains how to enable logging and where to find the logs once they've been created:
How to enable Windows logging
Once you've enabled logging, try installing again. Grab the newly created msi logs and either post here or email me at [email protected] I'll examine the logs and see if we can find a common issue between the systems.
Thanks,
Chris

Air package installation issue: Grey screen, black dots.

Hi,
    I am new to this forum, and to air development in general, but loving it! I turned to air for a recent project in which I needed support for UDP, and have been pleased with the DatagramSocket.   However, I am currently installing my software, on sit, and under a very tight deadline and I am (all of a sudden) experiencing problems.
   My apps have all been created using Flash CS5 on snowleopard, and debugged with the air runtime. I have 8 pcs with clean installs of win7 and 1 running XP. My setup process included installing AdobeAIRInstaller.exe version 2.0.4.13090. After setup, I've continued by installing the .air packages which I created with Flash. The packages are signed with an "home-made" certificate. When I finally launce my .exe however, all I can see is a grey screen (at the intended resolution of my ap) with 4 or 5 black/grey dots, cycling - as if they are a load bar.
   I should add that I used this same process in te shop to test my files on a PC with identical specifications and setup. I have disabled windows firewall, and the machines have flash player 10 installed. I have no virus software running. The air apps do not rely on any local media, but they do contain calls to amfphp, as well as dynamically loading content from a web server. I believe that the IP configuration for the server is correct, and the programs work from my machine (leopard) in debug mode.
   Any hints? Is this a 'feature' that I'm not aware of, or perhaps something windows-specific? As I mentioned, I am on very tight schedule, so any help is GREATLY appreciated.

Hi,
Would it be possible to get access to your project or sample code that reproduces the issue? Please feel free to email me at [email protected], if you zip your file up please remove the extension so it can get past our email filter.
Couple of other questions. Are you seeing this problem occur under when running the app under Flash CS5? Have you tried using a network traffic monitor to see what might be going on behind the scenes? Are the cycling black dots part of your UI or do you believe this is something Flash is producing?
Thanks,
Chris

Which files to use when packaging Air 3.6 with installer.

I've been publishing Air files without the installer for some time.
My publisher wants Adobe 3.6 along with the installer, which is new to me.
The Windows I believe I can set the output as: Windows Installer - then just send them the .exe file.
But I don't have a Mac to test on so can I just set the output as: Application with runtime embedded - and then just send the .exe file?

mac file extensions are usually .app not .exe

Deployment of an Adobe AIR application in an enterprise environment

Dear Team members,
first of all my apologies for posting this thread in more than one forum (see Installations Issues) but the argument is very important to us and I don't know where discuss it.
I would like to post a question to you regarding deployment doubts that we are trying to address.
My company is working on the new version of our primary application previously built as a J2EE application with some reporting functions with Flex, and we want to use AIR in order to leverage its possibilities:
Seamless integration with existing application functionalities (implemented as standard JEE web application pages) thanks to the integrated HTML capabilities
Improved integration of the user interface with the desktop
Native processes to provide additional functionalities
Our application is targeted to pharmaceutical industry, subject to FDA regulations, and it affects more than 5000 users for each customer, so we have some specific requirements affecting the deployment and distribution of the software:
Allow to run multiple versions of the software on the same client machine (to support test and acceptance activities in addition to the production environment)
Minimize the effort of the initial setup on each client
Manage the version upgrades without manual activities on each client
Keep the test/acceptance and production environments strictly aligned to improve effectiveness of formal validation (ideally, an application once validated should be transported in production without any source code modification, recompilation or repackaging)
The current browser-based strategy is perfectly fit to these requirements, and in the shift towards a desktop-based strategy we need to continue satisfying them as much as possible. We evaluated the standard distribution strategy of Adobe AIR applications, and noticed several attention points in this scenario.
The first issue we encountered is the back-end services endpoint discovery problem. Simply hardcoding a server URL in the packaged application could be a viable solution for public internet-accessible applications, but we need to support multiple customers in their intranet, and each one typically requires multiple environments for the application (acceptance, production, etc.). Maintaining dozens of different packages of the AIR application to support all these customer environments clearly is not the solution. Neither we want to force thousands of different users to enter and maintain the correct server location in their local preferences.
So, we thought to use a badge hosted in the back-end application to run the local AIR application: using the underlying API, we could activate the application specifying also the network location of the back-end services. We could also rely on the badge to install the application (and the AIR runtime if necessary)… however, application packaged as native installers cannot be installed, upgraded, or launched by the badge API (and we need to package ours as native to use native processes).
We also noticed that multiple versions of an AIR application cannot be installed side-by-side in a client machine, and that the installation and upgrade of the application can be performed only when the local user has administrative rights on the machine (using standard or native packages), forcing us to rely on external software distribution systems in some customer scenarios (introducing additional complexities in the release cycle).
At this point, in our opinion the standard deployment strategies of Adobe AIR applications are unfit for enterprise environments. In the enterprise world, many of the applications have migrated to a completely browser-based solution, while others enhanced their client layer to comply with the requirements, for example installing only a thin portion of the client code and allowing to connect to multiple server versions/environments with it (e.g. the SAP GUI universal client). Without smarter deployment and distribution tools, AIR applications currently are a step back compared to web applications in terms of manageability.
So, we are trying to develop a solution to address these problems, with some concepts similar to JStart: install on the client machine a launcher application capable of being activated from a web page, dynamically locate, download and run the actual client bytecode, transparently enforce client software updates, and supporting multiple applications (and multiple versions of the same application). However, we are facing many technical problems due to internal architecture of AIR and we already spent a considerable amount of effort trying to find a solution. We are now thinking to return on the choice of AIR, going back to Flex.
What is the position of Adobe on this argument? Is Adobe aware of these issues and are there any plans on this topic? Any advice?
Thank you in advance

For those following along, Oliver Goldman will be answering this post in future articles on his blog.
Many great comments and questions here. I’m working on some follow-up posts to address these; nothing I could cram into this comment field would really do your query justice. - Oliver Goldman
Pursuit of Simplicity
Chris

Distribute Adobe Air Runtime via Apple Remote Desktop

I've be researching whether or not it's possible to distribute the Adobe Air framework via Apple Remote Desktop, but I haven't found any solutions. The Adobe Air Admin guide has this to say:
Enterprise deployment
IT administrators can install Adobe AIR and AIR applications silently using standard desktop deployment tools. IT administrators can deploy the following:
•Silently install Adobe AIR using tools such as Microsoft SMS, IBM Tivoli, or any deployment tool that allows silent installations that use a bootstrapper
No mention of Apple Remote Desktop, or any other Apple-related Enterprise deployment methods. Is this possible, or must Mac software vendors bundle the Adobe Air framework with their pkgs (and jump through the necessary licensing hoops) in order for clients to get an Adobe Air app and all it's dependencies (i.e. the Adobe Air framework) distributed to a network of Apple machines.
Thanks!

Thanks for the interest in AIR. You are correct that you would have to wrap everything (runtime and application) up in a .pkg for installation via ARD. Another alternative would be to get the AIR Runtime installer on to the remote system, and then execute it via ssh.
Chris

Maximum size of an .air package

hi forum,
are there any limitations / recomendations for a maximum size
of an .air package?
i'm currently developing on an air application which will be
distributed via cd/dvd. the app will have access to an fixed amount
of image data (about 1,5 gb), i'm not shure whether its better to
keep the data outside of the .air app installer an write an
postroutinie which autmatically copies the data from cd to
harddisk, or simply include the whole data whithin the .air file?
last version would save a lot coding but i don't know if ther
are limitations in the size of an .air packege

quote:
Originally posted by:
vectorhog2
I'm also making an air project to distribute on cd or dvd.
I've managed to create an air file that's about 500M which installs
on windows. Anything larger will give an error. I have not
experienced any file size issues on the Mac.
Does anyone have any info on how to write a post-routine
which automatically copies the data from cd to hard-disk?
David
hi david,
thanx for your reply. think we have the same problem. here
are my ideas to resolve this problem:
1) writing a post-routine:
as far as i know there is no standard post-routine function
implemented in air. so we have to fake it. maybe this way:
- create a prefereces.dat where you store all the application
preferences (serialized data) in
- create a "firstRun"-flag inside this file with the value of
"false"
- in the application init() method check this value
- if set to "true" - run the application
- if set to "false" call a "copyContent()" method
- this method should prompt for a "toc.xml" (open a file
dialog) which is stored on the cd
- this toc.xml should keep all infos which content should be
copied
- now the user has to manualy go to the cd-drive an select
the file. (you shoud check the file schema, whether its "your"
provided file)
- for later use- save the native path of the toc.xml in the
flag "toc-path" inside the preferences.dat.
- now copy all files (asynchronus) listed in the toc.xml
(excluding the files in the "local-toc.xml", see below)
- for "aborting proccess issues" you should also write a
local empty "local-toc.xml" to the users hdd
- for each copied file you should write an the associate
entry from the cd's toc.xml to this local-toc.xml
- this is important because if for some reasons the whole
process fails (by user or system), we do not have to copy the whole
stuff again
- if all files ar copied correctly, set the firstRun flag to
"false" - run the application
- if not, exit the application
- next time the app starts, it looks for the firtsRun flag
again.
- if its still set to "true" (cause the copy process wasnt
successfull first time), the app matches the local-toc.xml with the
toc.xml from the cd (read the path from the toc-path flag first, if
not valid - do a new file dialog prompt)
- now the "rest" of the content will be copieed
- this procces loops till everything is well copied :+)
2.) write a "real" installer
- write a real installer with an installer build tool e.g.
NSIS
3.) hack air
- try the new air wrapper tool
"shu-player"
- it wraps the air package in a single .exe
- this a tool like mdm zinc for flash
4.) hope
- .... that adobe provides post-routines in the next release
of air :+)
well, hope this helps - this are just ideas which havent been
realized.
i'll keep you to date whether one solution works ...
regards,
jan viehweger

Is there any way to export a desktop AIR package when desktop is not supported by an ANE?

I have a third party ANE that I need to use. The ANE has a target for Android, but when I add it in Build Path->Native Extensions an error shows up "This ANE does not support Desktop(Mac) platform". Now, my app is targeting android, but to make it easy for others in my company to play builds without having a device, I've been using the "Export Release Build->Signed AIR package for installation on desktop" option. The problem is, since I've added the ANE, I'm no longer able to hit the "finish" button because it's greyed out due to the error (even though the checkbox to include the ANE is unchecked in the export settings. The only way I've found to work around this is to remove the ANE temporarily and comment out references to it to build the desktop package, which is not optimal. Any other suggestions?
Thanks!

Rather than commenting it out, you could define a compiler parmeter:
[code]
-define=CONFIG::includeAndroidANE,true
[/code]
Then, in your code, wrap any references to the problem code in the config statement
[code]
CONFIG::includeAndroidANE
import the.problem.package.ProblemExtensionClass;
[/code]
And:
[code]
CONFIG::includeAndroidANE
   if(ProblemExtensionClass.isSupported()) {
        var v:ProblemExtensionClass = new ProblemExtensionClass();
         v.init();
         v.doSomethingThatIsntSupportedOnAMac();
[/code]
Then, when you compile for Mac, you just need to set CONFIG::includeAndroidANE,false;
This is what OSMF does to support different versions of the player, and also what SWIZ do to support different versions of Flex.
All good.
G

Packaging Linux AIR app as a native package (.deb)?

Ok, so I've been tasked with packaging an AIR app in a system package. We got a redistrubution license for AIR so I think we are good in that respect but I run into an unfortunate predicament when trying to do a silent install from a deb:
Both AIR runtime and AIR applicaiton generate a native package (.deb in this case) during install. So even though I can run silent install from my own deb, it fails to install as it cannot install a deb during installation of a deb. I am assuming that even if I could somehow grab the generated deb file, it would be against the license agreement to do so.
So, any thoughts as to how to get this accomplished? Is there an alternative distribution of an app that comes as a native ".deb" file? Or is there a command line option that disables a native package management install? ( I can seem to find no information on any command line options for the bin installer)
Thanks.
-M

Ok, so I've been tasked with packaging an AIR app in a system package. We got a redistrubution license for AIR so I think we are good in that respect but I run into an unfortunate predicament when trying to do a silent install from a deb:
Both AIR runtime and AIR applicaiton generate a native package (.deb in this case) during install. So even though I can run silent install from my own deb, it fails to install as it cannot install a deb during installation of a deb. I am assuming that even if I could somehow grab the generated deb file, it would be against the license agreement to do so.
So, any thoughts as to how to get this accomplished? Is there an alternative distribution of an app that comes as a native ".deb" file? Or is there a command line option that disables a native package management install? ( I can seem to find no information on any command line options for the bin installer)
Thanks.
-M

Packaging an AIR application in a .EXE file using ADT

Hi All,
I have to package a .AIR file in .exe file with ADT.
Is it possible setting a default installation path in exe file using ADT tool?
I would like to create a .exe file where user can't interact with installation wizard to set a particular path.
Does it exist a particular option?
Would you suggest an example?
(...adt -package -target native ??? myApp.exe myApp.air)
Thanks in advance
Gianni

Hi All,
I have to package a .AIR file in .exe file with ADT.
Is it possible setting a default installation path in exe file using ADT tool?
I would like to create a .exe file where user can't interact with installation wizard to set a particular path.
Does it exist a particular option?
Would you suggest an example?
(...adt -package -target native ??? myApp.exe myApp.air)
Thanks in advance
Gianni

Possible Solution: Allow native code packaging with AIR using ADT?

Packager / ADT are providing huge benefits for AS3 developers targetting mobile as we all know. We also know that we'd like as much access to the native libs for the various platforms as we can possibly get. Two cases in point, in-app purchasing and access to Apple's iAd network. Discussions about these requirements over the last few days with a colleague of mine have resulted in him coming up with a very strong idea for providing adhoc access to native libraries. He has posted his suggestion, (which involves a feature request to Adobe), on Adobe AIR Ideas at Labs. I really encourage as many people as possible to read his suggestion to get the discussion warmed up. If you think the proposal is worthy, please make sure you vote it up so that it registers on Adobe's radar. I believe this would really benefit all of us working with AIR for mobile. Here is the link.
Peter Robertson

manicjames wrote:
I have packaged my AIR app into a Native .exe installer using ADT. If the user does not have air installed and they are connected to the internet, the AIR runtime is automatically installed.
Is it possible to package the AIR runtime into the exe so that if the user is not online the AIR runtime is installed?
I have experimented with the sidecar install and .air file but ideally I want to only have the one file(.exe). I already have a distribution licence from Adobe.
This isn't available at this time, but I think it's a great idea. You might want to add a feature request for this over at ideas.adobe.com and bugbase.adobe.com, or review and vote for these current feature requests if they provide for what you're looking for:
Portable AIR Apps
Create portable AIR apps
If you decide to add a new request, please post back with the URL so others can cast their votes and add comments.
Chris

Compressing an AIR Package

The AIR package I've created is around 50MB in size and set
to grow larger with subsequent updates to the application. Is there
a way to compress this file but still use the seamless install
badge, etc to deploy the application. Another approach I've
considered is compressing directories within the application in
order to reduce file size and then decompress them on the first run
of the application.

AIR files are ZIP files. This has made me wonder if you could
use some more advanced ZIP compression... Haven't had time to test
myself.
For what it's worth, this was enlightening to me when I read
it on Oliver Goodman's blog:
http://blogs.adobe.com/simplicity/2008/05/notes_on_the_air_file_format.html

Deploying Air package via Air installer

Similar Messages

Maybe you are looking for