Deploy air application

Hi there,
I built an air application. Now I have to deploy it to my
client who might not have AIR runtime installed and not access
internet. I need some help about how to deploy in this situation.
Thanks in advance.

Looks like you will need to distribute the AIR Runtime with
your app.
You can find out the information about redistribute AIR
Runtime here:
http://www.mikechambers.com/blog/2008/04/07/redistributing-the-adobe-air-runtime-installer /
-ted

Similar Messages

  • Deploying AIR applications with flex & BlazeDS

    I have a Flex app which needs to run on the server in the
    background. I was thinking of turning into an AIR app since it
    really doesn't need to run on the browser. But how could I deploy
    this.
    I am sending my entire flex project as a .war file to deploy
    on the server and am using BlazeDS to work with some java backend
    code. But all of the tutorials for AIR seem to assume some sort of
    manual install method and I just want to bundle it with my current
    project. Is this possible? And if so, how is this done?

    I actually do send the PNG as a byteArray to Java from Flex
    via a remote object method. The reason I need Flex is because I
    specifically want to use the charting software package from Flex
    charting. The Flex look and feel out of the box for the interface
    and the chart is far superior to what I could create in Java.
    Here is a quick over view of what happens in the application:
    1. launch java app
    2. Java then launches a Flex instance for each report defined
    in the database
    3. java pushes live data to each Flex instance from database
    4. after Flex plots data, it sends ByteArray of the png to
    remote java method
    5. java saves png to file locally on the server
    How would you simplify this process? I'd really appreciate
    your take on this.

  • Deploying Air Application with Zend AMF Dataservices to remote server?

    I cannot find anything to guide me through getting this set up.. it's frustrating because I feel this is probably the whole point of Air!
    I have an Air project in Flash Builder which is set up with the Data/Services panel, using a custom php model file.
    It's working fine on localhost, but I do not know what is necessary to have it work while the app is running locally but connecting to a remote server (can get it working as a flex app in browser hosted remotely, though)
    I uploaded the Zend framework and my custom php files to the net
    I changed the amf_config.ini file .. the webroot and the zend_path, I assume, should be different depending whether it's localhost or on a server, so I changed the one online to be match where the files are.
    I found in the _super_Database.as it was referencing the Zend gateway.php locally, so I changed that to be an absolute link to where I put gateway.php on the server.
    But I'm not sure what to do next... I assume I only need the Zend framework and the php files I'm using online, but then there is no link to my Database.php anywhere other than as a symbolic link from services/Database.php to the bin-debug folder.. but I don't know how exactly to put that on the server and then compile my app... and I can't find any explanations anywhere.
    Anyone know how to go about this?

    Hello everyone,
    Exact the same problem here. I've build an Air app with PHP in the backend. On my localhost it works fine...  but, when i am tranfer it to the remote server it just won't work.
    I have changed settings in amf_config.ini and in gateway.php, and I have changed the settings in super class of my flash file, so it knows where to find the new gateway.php.
    Can someone please help a hand... (mmm it is almost Christmas .... )
    Thanks., Erik

  • I want to deploy AIR application in production environment. Will the licence for AIR is free?

    Please let me know the licence details. Shall i have to pay any thing if i want to use in production environment.

    Just after the 2012 Macs were released there were a lot of crashes involving those machines that Chrome got the blame for. By the time I got my hands on a 2012 MBA Chrome had been updated at least twice (plus it was never clear which version of Chrome was implicated, assuming it was the cause to begin with). All I can say now is that I've not replicated the issue with the last two versions of Chrome.

  • 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

  • Deploy Adobe Air Application

    Hello everybody.
    I have a question. I would like to deploy on many computers an application from Adobe Air.
    How can I deploy my adobe air application in silence ? I wanna do a batch but I don't know how can I specify to automatically choose "Install" in my batch
    And "Continue" for it
    Thanks a lot for your help

    First, you'll want to sign our distribution agreement which you can find here: http://www.adobe.com/special/products/air/runtime_distribution1.html
    The process is easy, and should only take a few minutes.  Once done, you'll receive links and documentation that will describe how to deploy AIR via the command line.
    An alternative is to create your own installer for your AIR 3 application, this could be as simple as a batch file.  You can find more details in this article:
    Installation and deployment options in Adobe AIR 3
    Chris

  • Silentely deploy an air application

    Hi,
    AIR is already installed on my computer. I run a v3.
    Now I want to silentely install an air application (not air itself) on many computers so double clicking the air file is not an option. Anyone knows how to silentely answers the questions asked during the install ?
    I also get the message saying the publisher is unknown. Is there a way to skip this step without digitally signing the application ?
    Thanks

    Does this thread help at all?
    http://forums.adobe.com/thread/414547

  • AIR runtime and AIR applications built using Captive Runtime still need Admin Privilege to Install

    I am working on a small project to install AIR application(native .exe & .dmg) with AIR runtime without needing the Administrator privilege so I used Captive runtime but the installation is still asking for admin privilege
    I bundled AIR application with AIR runtime using Captive runtime from flash builder 4.6, then I packaged this into a .MSI using Advanced Installer. Now when I install it for a user without admin privilege it prompts me for Admin credentials.
    Can you please tell me if
    1. I need AIR distribution license to install AIR runtime without Admin privilege
    2. Do I need a different installer
    3. Am I missing any step here
    Thank you

    If you're installing to a location where Windows requires elevated privileges, like Program Files, you'll need to have admin privileges to continue.  Are you using an AIR based native installer or have you taken the application with the captive runtime and rolled this up in your own installer?
    Here's a section from the Installation and deployment options in Adobe AIR 3 article that might help:
    Installation privileges
    When designing an installer, one has the option to choose from approaches that may or may not require administrative privilege. For example, a drag-and-drop install on Mac OS X requires no special privilege; users can always copy the application into their own application folders, for which they have the necessary permissions. On the other hand, if registry keys must be written to the machine-specific portion of the registry on Windows, installation of that application will require administrative privilege to do so.
    The two installer formats directly supported by AIR, AIR files and native installers, have always required administrative privilege. This was a design decision made in part to simplify the implementation of the AIR installers: If administrative privilege is assumed to be available, implementation is possible if the registry can be written to, and so on. It was also selected because, in many enterprises, this is the desired behavior: administrators can use the privilege requirement to gate software installation.
    All the same, there are scenarios where supporting installation without requiring administrative privileges is desirable, or even necessary. This can now be achieved using custom installers; you simply need to author an installer that operates correctly with only standard user privilege. In practice this can be easy to achieve; a simple install-by-copy to a writable location (that is, in the user's own folder) will suffice. Should you author a more complex installer, you should keep in mind that the addition of certain operations during the install process will in turn reintroduce the requirement for administrative privileges.

  • 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">
    <!-- Adobe AIR Application Descriptor File Template.
        Specifies parameters for identifying, installing, and launching AIR applications.
        xmlns - The Adobe AIR namespace: http://ns.adobe.com/air/application/2.0
                The last segment of the namespace specifies the version
                of the AIR runtime required for this application to run.
        minimumPatchLevel - The minimum patch level of the AIR runtime required to run
                the application. Optional.
    -->
        <!-- A universally unique application identifier. Must be unique across all AIR applications.
             Using a reverse DNS-style name as the id is recommended. (Eg. com.example.ExampleApplication.) Required. -->
        <id>com.MyCompany.Application</id>
        <!-- Used as the filename for the application. Required. -->
        <filename>Production Control System</filename>
        <!-- The name that is displayed in the AIR application installer.
             May have multiple values for each language. See samples or xsd schema file. Optional. -->
        <name>Production Control System</name>
        <!-- An application version designator (such as "v1", "2.5", or "Alpha 1"). Required. -->
        <version>2.1.3</version>
        <!-- Description, displayed in the AIR application installer.
             May have multiple values for each language. See samples or xsd schema file. Optional. -->
        <!-- <description></description> -->
        <!-- Copyright information. Optional -->
        <!-- <copyright></copyright> -->
        <!-- Publisher ID. Used if you're updating an application created prior to 1.5.3 -->
        <!-- <publisherID>My Company</publisherID> -->
        <!-- Settings for the application's initial window. Required. -->
        <initialWindow>
            <!-- The main SWF or HTML file of the application. Required. -->
            <!-- Note: In Flash Builder, the SWF reference is set automatically. -->
            <content>[This value will be overwritten by Flash Builder in the output app.xml]</content>
            <!-- The title of the main window. Optional. -->
            <!-- <title></title> -->
            <!-- The type of system chrome to use (either "standard" or "none"). Optional. Default standard. -->
            <systemChrome>none</systemChrome>
            <!-- Whether the window is transparent. Only applicable when systemChrome is none. Optional. Default false. -->
            <transparent>true</transparent>
            <!-- Whether the window is initially visible. Optional. Default false. -->
            <!-- <visible></visible> -->
            <!-- Whether the user can minimize the window. Optional. Default true. -->
            <!-- <minimizable></minimizable> -->
            <!-- Whether the user can maximize the window. Optional. Default true. -->
            <!-- <maximizable></maximizable> -->
            <!-- Whether the user can resize the window. Optional. Default true. -->
            <!-- <resizable></resizable> -->
            <!-- The window's initial width in pixels. Optional. -->
            <!-- <width></width> -->
            <!-- The window's initial height in pixels. Optional. -->
            <!-- <height></height> -->
            <!-- The window's initial x position. Optional. -->
            <!-- <x></x> -->
            <!-- The window's initial y position. Optional. -->
            <!-- <y></y> -->
            <!-- The window's minimum size, specified as a width/height pair in pixels, such as "400 200". Optional. -->
            <!-- <minSize></minSize> -->
            <!-- The window's initial maximum size, specified as a width/height pair in pixels, such as "1600 1200". Optional. -->
            <!-- <maxSize></maxSize> -->
        </initialWindow>
        <!-- We recommend omitting the supportedProfiles element, -->
        <!-- which in turn permits your application to be deployed to all -->
        <!-- devices supported by AIR. If you wish to restrict deployment -->
        <!-- (i.e., to only mobile devices) then add this element and list -->
        <!-- only the profiles which your application does support. -->
        <!-- <supportedProfiles>desktop extendedDesktop mobileDevice extendedMobileDevice</supportedProfiles> -->
        <supportedProfiles>extendedDesktop</supportedProfiles>
        <!-- The subpath of the standard default installation location to use. Optional. -->
        <!-- <installFolder></installFolder> -->
        <!-- The subpath of the Programs menu to use. (Ignored on operating systems without a Programs menu.) Optional. -->
        <!-- <programMenuFolder></programMenuFolder> -->
        <!-- The icon the system uses for the application. For at least one resolution,
             specify the path to a PNG file included in the AIR package. Optional. -->
        <!-- <icon>
            <image16x16></image16x16>
            <image32x32></image32x32>
            <image48x48></image48x48>
            <image128x128></image128x128>
        </icon> -->
        <!-- Whether the application handles the update when a user double-clicks an update version
        of the AIR file (true), or the default AIR application installer handles the update (false).
        Optional. Default false. -->
        <customUpdateUI>true</customUpdateUI>
        <!-- Whether the application can be launched when the user clicks a link in a web browser.
        Optional. Default false. -->
        <!-- <allowBrowserInvocation></allowBrowserInvocation> -->
        <!-- Listing of file types for which the application can register. Optional. -->
        <!-- <fileTypes> -->
            <!-- Defines one file type. Optional. -->
            <!-- <fileType> -->
                <!-- The name that the system displays for the registered file type. Required. -->
                <!-- <name></name> -->
                <!-- The extension to register. Required. -->
                <!-- <extension></extension> -->
                <!-- The description of the file type. Optional. -->
                <!-- <description></description> -->
                <!-- The MIME content type. -->
                <!-- <contentType></contentType> -->
                <!-- The icon to display for the file type. Optional. -->
                <!-- <icon>
                    <image16x16></image16x16>
                    <image32x32></image32x32>
                    <image48x48></image48x48>
                    <image128x128></image128x128>
                </icon> -->
            <!-- </fileType> -->
        <!-- </fileTypes> -->
        <!-- iPhone/iPad -specific capabilities -->
        <!-- <iPhone> -->
            <!-- A list of plist key/value pairs to be added to the application Info.plist -->
            <!-- <InfoAdditions>
                <![CDATA[
                    <key>UIDeviceFamily</key>
                    <array>
                        <string>1</string>
                        <string>2</string>
                    </array>
                    <key>UIStatusBarStyle</key>
                    <string>UIStatusBarStyleBlackOpaque</string>
                    <key>UIRequiresPersistentWiFi</key>
                    <string>YES</string>
                ]]>
            </InfoAdditions> -->
        <!-- </iPhone> -->
    </application>

  • How do i update Installed AIR Applications? // General Questions

    Hi,
    first of all, i'm completly new to AIR. However, i made my way through your product documentation and i'm now able to deploy AIR and a AIR Application (SFDC Chatter) and register it.
    Works fine so far, but some questions:
    - How can i update installed AIR applications? If i just try to re-install it, the installer will fail with exit code "9"
         -> How can i update them directly? If this is not possible
          -> How can i uninstall AIR applications in a large enterprise environment?
    - Where is the ARH Tool that is described in your product documentation?
    - When installing AIR as SYSTEM User (I'm using SCCM) where is the logfile?
    - Do you recommend updating AIR on a regular base? Are "older" applications compatible with newer AIR Versions?
    Thanks for your replies!
    Ben

    Hi Ben,
    I'd recommend taking a good look at our captive runtime option that is available in AIR 3.0 and higher.  While you have to roll your own installer (and updater) this could be as simple as a zip/batch file combination.  It also allows you to use the runtime that you prefer and not be dependent on what the user installs or uninstalls.  You do have to be mindful of security implications, but it's definitely the way I'd go.
    http://www.adobe.com/devnet/air/articles/air3-install-and-deployment-options.html
    http://help.adobe.com/en_US/air/build/WSfffb011ac560372f709e16db131e43659b9-8000.html
    As for updating, it should be as simple as increasing your app descriptors version number and installing again.  This article explains how you can also use our update framework: http://www.adobe.com/devnet/air/articles/air_update_framework.html
    The ARH tool can be found here:
    Mac: http://airdownload.adobe.com/air/distribution/latest/mac/arh
    Win: http://airdownload.adobe.com/air/distribution/latest/win/arh.exe
    Linux: http://airdownload.adobe.com/air/distribution/latest/lin/arh
    Thanks,
    Chris

  • Adobe Air Application only works using Super Administrator account on Windows XP

    Good day
    i really need some help. I developed air application that uses remote service, sql lite etc. It is working on my computer WIndows XP sp2. To test, i even created a guest account and it works fine. But when i deployed it to our client, the application doest work. Only the login page appears. I ask the it personnel there and ask if there are any restriction on the account of the user and said there is none because they are using Domain account. But when the super administrator is logged in, it works
    Your help will greatly apprciated

    Your help me, I iwill greatly apprciated
    HELP MALAYSIA
    Date: Thu, 21 Oct 2010 20:54:19 -0600
    From: [email protected]
    To: [email protected]
    Subject: Adobe Air Application only works using Super Administrator account on Windows XP
    Good day
    i really need some help. I developed air application that uses remote service, sql lite etc. It is working on my computer WIndows XP sp2. To test, i even created a guest account and it works fine. But when i deployed it to our client, the application doest work. Only the login page appears. I ask the it personnel there and ask if there are any restriction on the account of the user and said there is none because they are using Domain account. But when the super administrator is logged in, it works
    Your help will greatly apprciated
    >

  • What are the System Requirements for Web Server hosting Adobe Air application

    Working on a project that is using Adobe Air . The Adobe support site has system requirements for the client side application, but for the server side, what are the system requirements?
    Using a Windows server, would expect to have approx. 100 concurrent connections at any given time.

    Adobe AIR applications are installed on the end user's computer. They are not hosted on a web server. You can deploy an AIR file, which is the installer file for an AIR application, via your web server.

  • Problems updating/installing air application

    Hi,
      We have an Adobe Air application that uses the Air update mechanism for newer versions. It seems to work fine for most of the customers  but on some computers when it tries to install the new version it cannot. The only clue we have are some errors we found in the Install.log in in Adobe/Air/logs:
    [2012-07-09:12:14:50] Error occurred during msi install operation; beginning rollback: [ErrorEvent type="error" bubbles=false cancelable=false eventPhase=2 text="1603" errorID=0]
    [2012-07-09:12:14:50] Rolling back install of C:\Users\pop.radu\AppData\Local\Temp\fla73EA.tmp\setup.msi
    [2012-07-09:12:14:50] Rollback complete
    [2012-07-09:12:14:50] Got an unexpected fatal error while in stateInstalling: [ErrorEvent type="error" bubbles=false cancelable=false eventPhase=2 text="1603" errorID=0]
    We have checked other discussions on this problem and most of the solutions were using an uninstall tool to remove the app and then install it again. However, we would like to know if there is another way to solve this since we don't want  our customers to uninstall and reinstall the application manually each time a newer version of the app appears.
    Does anyone know if there is a way to do this?
    Thanks,
    Radu

    Hi Radu,
    The next step would be to enable MSI logging and take a look at what is failing with MSI.  Unfortunately, MSI is very fragile at times and we do see this problem.  Sometimes its simply a file/folder/registry permission issue.  Other times it's more severe, like a missing .msi database file.  Because this is an upgrade, I suspect what is happening is that MSI is looking for the old version's .msi database file so that it can run its "uninstall" routine.  If the old msi can't be found, it will bail out and the upgrade will fail.
    The only solution, other than locating the old msi database file (doubtful) is to run the Microsoft cleanup utility.
    Thanks,
    Chris
    Ps.  If you haven't already, I'd recommend taking a look at the captive runtime solution in AIR 3.x.  http://www.adobe.com/devnet/air/articles/air3-install-and-deployment-options.html

  • Unable to export AIR application in FlashBuilder 4

    Hi,
    I have just finished an AIR application created in Flash Builder 4 / SDK 4.1.
    But  I have systematically a problem while exporting the application with  the Flash Builder wizard / button Export to a validated version.
    When I double click on the generated .air file, I've got the error :
    'This application cannot be installed because the installation program has not be configured correctly'.
    Thanks in advance for your help.
    Sophie

    Hi,
    First of all, thanks for your answer.
    I am working on a Windows XP server - Version 2002 - SP2.
    To avoid the following error message, Could not generate timestamp: Connection timed out: connect
    I set java.net.useSystemProxies=true in [Adobe Flash Builder 4 folder]\jre\lib\net.properties
    Here's my Application-app.xml file :
    <?xml version="1.0" encoding="utf-8" standalone="no"?>
    <application xmlns="http://ns.adobe.com/air/application/2.0">
    <!-- Adobe AIR Application Descriptor File Template.
        Specifies parameters for identifying, installing, and launching AIR applications.
        xmlns - The Adobe AIR namespace: http://ns.adobe.com/air/application/2.0
                The last segment of the namespace specifies the version
                of the AIR runtime required for this application to run.
        minimumPatchLevel - The minimum patch level of the AIR runtime required to run
                the application. Optional.
    -->
        <!-- A universally unique application identifier. Must be unique across all AIR applications.
             Using a reverse DNS-style name as the id is recommended. (Eg. com.example.ExampleApplication.) Required. -->
        <id>com.akka.dgac.ClientLourdNA</id>
        <!-- Used as the filename for the application. Required. -->
        <filename>ClientLourdNA</filename>
        <!-- The name that is displayed in the AIR application installer.
             May have multiple values for each language. See samples or xsd schema file. Optional. -->
        <name>Client Lourd NA</name>
        <!-- An application version designator (such as "v1", "2.5", or "Alpha 1"). Required. -->
        <version>1.0</version>
        <!-- Description, displayed in the AIR application installer.
             May have multiple values for each language. See samples or xsd schema file. Optional. -->
        <!-- <description></description> -->
        <!-- Copyright information. Optional -->
        <copyright>Copyright 2011, Akka Technologies</copyright>
        <!-- Publisher ID. Used if you're updating an application created prior to 1.5.3 -->
        <!-- <publisherID></publisherID> -->
        <!-- Settings for the application's initial window. Required. -->
        <initialWindow>
            <!-- The main SWF or HTML file of the application. Required. -->
            <!-- Note: In Flash Builder, the SWF reference is set automatically. -->
            <content>ClientLourdNA.swf</content>
            <!-- The title of the main window. Optional. -->
            <title>Outil de rédaction d'un rapport d'audit Navigation Aérienne</title>
            <!-- The type of system chrome to use (either "standard" or "none"). Optional. Default standard. -->
            <!-- <systemChrome></systemChrome> -->
            <!-- Whether the window is transparent. Only applicable when systemChrome is none. Optional. Default false. -->
            <!-- <transparent></transparent> -->
            <!-- Whether the window is initially visible. Optional. Default false. -->
            <!-- <visible></visible> -->
            <!-- Whether the user can minimize the window. Optional. Default true. -->
            <!-- <minimizable></minimizable> -->
            <!-- Whether the user can maximize the window. Optional. Default true. -->
            <!-- <maximizable></maximizable> -->
            <!-- Whether the user can resize the window. Optional. Default true. -->
            <!-- <resizable></resizable> -->
            <!-- The window's initial width in pixels. Optional. -->
            <!-- <width></width> -->
            <!-- The window's initial height in pixels. Optional. -->
            <!-- <height></height> -->
            <!-- The window's initial x position. Optional. -->
            <!-- <x></x> -->
            <!-- The window's initial y position. Optional. -->
            <!-- <y></y> -->
            <!-- The window's minimum size, specified as a width/height pair in pixels, such as "400 200". Optional. -->
            <!-- <minSize></minSize> -->
            <!-- The window's initial maximum size, specified as a width/height pair in pixels, such as "1600 1200". Optional. -->
            <!-- <maxSize></maxSize> -->
        </initialWindow>
        <!-- We recommend omitting the supportedProfiles element, -->
        <!-- which in turn permits your application to be deployed to all -->
        <!-- devices supported by AIR. If you wish to restrict deployment -->
        <!-- (i.e., to only mobile devices) then add this element and list -->
        <!-- only the profiles which your application does support. -->
        <!-- <supportedProfiles>desktop extendedDesktop mobileDevice extendedMobileDevice</supportedProfiles> -->
        <!-- The subpath of the standard default installation location to use. Optional. -->
        <installFolder>bin-release</installFolder>
        <!-- The subpath of the Programs menu to use. (Ignored on operating systems without a Programs menu.) Optional. -->
        <!-- <programMenuFolder></programMenuFolder> -->
        <!-- The icon the system uses for the application. For at least one resolution,
             specify the path to a PNG file included in the AIR package. Optional. -->
        <!-- <icon>
            <image16x16></image16x16>
            <image32x32></image32x32>
            <image48x48></image48x48>
            <image128x128></image128x128>
        </icon> -->
        <!-- Whether the application handles the update when a user double-clicks an update version
        of the AIR file (true), or the default AIR application installer handles the update (false).
        Optional. Default false. -->
        <!-- <customUpdateUI></customUpdateUI> -->
        <!-- Whether the application can be launched when the user clicks a link in a web browser.
        Optional. Default false. -->
        <!-- <allowBrowserInvocation>true</allowBrowserInvocation> -->
        <!-- Listing of file types for which the application can register. Optional. -->
        <!-- <fileTypes> -->
            <!-- Defines one file type. Optional. -->
            <!-- <fileType> -->
                <!-- The name that the system displays for the registered file type. Required. -->
                <!-- <name></name> -->
                <!-- The extension to register. Required. -->
                <!-- <extension></extension> -->
                <!-- The description of the file type. Optional. -->
                <!-- <description></description> -->
                <!-- The MIME content type. -->
                <!-- <contentType></contentType> -->
                <!-- The icon to display for the file type. Optional. -->
                <!-- <icon>
                    <image16x16></image16x16>
                    <image32x32></image32x32>
                    <image48x48></image48x48>
                    <image128x128></image128x128>
                </icon> -->
            <!-- </fileType> -->
        <!-- </fileTypes> -->
    </application>
    Thanks in advance for your help.
    Sophie

  • Newbie asks: Will an AIR Application work with CFCs on Standalone PC if ColdFusion is not installed?

    I am a ColdFusion developer who is absolutely new to Flex.
    I would like to create a Flex/AIR application that will run on standalone PCs that are not connected to the Internet. As such, I need to develop a truly standalone application with the entire front and back end installed on the PC.
    I will need to create the services that the SWF files will use to fetch and write data to the database. I would prefer to use my CF skills to write those services in ColdFusion. When I deploy the application as a standalone Windows application, would CF have to be installed on the target PCs, or is the AIR runtime able to use the services (the CFC files) that were created with ColdFusion?
    If the answer is that CF would have to be installed, I would have to create the services in something other than CF. If that's the case, what would you suggest that I use to create the services? I would be looking for something with the smallest possible footprint that will work on truly standalone PCs.

    I am a ColdFusion developer who is absolutely new to Flex.
    I would like to create a Flex/AIR application that will run on standalone PCs that are not connected to the Internet. As such, I need to develop a truly standalone application with the entire front and back end installed on the PC.
    I will need to create the services that the SWF files will use to fetch and write data to the database. I would prefer to use my CF skills to write those services in ColdFusion. When I deploy the application as a standalone Windows application, would CF have to be installed on the target PCs, or is the AIR runtime able to use the services (the CFC files) that were created with ColdFusion?
    If the answer is that CF would have to be installed, I would have to create the services in something other than CF. If that's the case, what would you suggest that I use to create the services? I would be looking for something with the smallest possible footprint that will work on truly standalone PCs.

Maybe you are looking for

  • Error in scenario for client Java Proxy

    2006-04-28 15:30:49 Success Java proxy runtime (JPR) is transferring the request message to the messaging System 2006-04-28 15:30:49 Success Application attempting to send an XI message synchronously using connection JPR. 2006-04-28 15:30:49 Success

  • Creating the index at end of book

    I am  looking at how to finish my first cook book and realize one of the last touches is to create an index of the  terms mentioned in the book. I'm not done yet, so the pages are shifting around a lot as I finish up, so I see there is no point in do

  • Error with stored procedure block datasource

    Hi all, I tried to base a datablock on a stored procedure in order to get better runtime performance. I work with Forms Builder 6i with patch 17 , and our database is oracle 8.1.7.1.4 But when compiling I got errors. Here are what I did : create or r

  • How to stop sharing of recent contacts

    our family has 5 apple devices ranging from iPads, iPhones to iMac; all of which share the same iCloud account to share calendar, contacts, photos etc. I've tried a Family sharing set up, but realized afterwards that contacts are not shared so my kid

  • Vision m softw

    hi guys, im pretty sure im gonna buy the 60gb zvm but am just waiting for it to come to ireland, im just wondering can anyone help me with some querys )i have over 600 cds so what is the best prog of getting them on to the player that wont restrict m