Specifications

CHAPTER 15

304

Deployment checklist

The deployment checklist contains some common system configuration issues that customers have found when

deploying Flex applications for production. It also contains troubleshooting tips to diagnose common deployment

problems.

Application assets

When deploying a Flex application, you must make sure you also deploy all the assets that the application uses at

run time. These include files that are used by the wrapper to support deep linking or history management, as well

as files that are loaded by the application such as resource bundles or RSLs.

In the case of wrapper code, you will probably be cutting and pasting it from the HTML templates included with

the SDK into your JSP or ASP or PHP pages.

Check that the following assets are deployed with your application if you use those assets in your Flex applications:

Feature Assets to Deploy

Wrapper files If you use a wrapper, be sure to include it in the deployment process. The wrapper can be any

file that returns HTML, such as PHP, ASP, JSP, or ColdFusion. At a minimum, this file must include

In addition, if you use dynamic pages to query databases or perform other server-side actions

for your Flex application, be sure to deploy those as well. This is especially important if you use

the data wizard in Flex Builder to generate these pages.

Version detection To support version detection in your HTML wrapper, you must add the code based on the Flex

wrapper templates to your wrapper, as well as deploy the AC_OETags.js file. This file defines

several methods used for version detection.

For more information, see “Creating a Wrapper” on page 311.

Express Install To support Express Install, you must include the following files:

• AC_OETags.js

• playerProductInstall.swf

For more information, see “Using Express Install” on page 333.