jump to navigation

Flash swf deployment checklist / document August 21, 2010

Posted by Tournas Dimitrios in Flash.

I upload my flash file to server and always forget to do one thing or the other. Is there a solution to flash deployment problem? Of course, Yes. Nothing can be better that maintaining a checklist for the deployment of SWF file. Following points can be used as a checklist to make sure that you don’t miss anything while deploying flash swf.

Steps and checklist for flash swf deployment on the server:

  1. SWF wrapper files: Wrapper files provide functionality like Version detection, History Management, Deep linking and Express install besides adding embed or object tag in swf file. If you are using default files generated by publishing from flex or flash then remember to upload these files:
    • AC_OETags.js                         (Provides functionality to add swf to html using embed or object tag, Version detection)
    • playerProductInstall.swf            (Required for express install and version detection feature to work)
    • history.js                                   ( required for Deep linking, History Management)
    • history.css                                 (Deep linking, History Management)
    • historyFrame.html                      (Deep linking, History Management)
  2. Flash player version check that the correct flash player version is specified in the HTML wrapper.
  3. Modules: If you have used modules in your application remember to upload them at the required location.
  4. RSL files: Use the same relative path that was used in compiler settings while uploading signed RSL (SWZ) and unsigned RSL (SWF) files to your domain. If uploading the SWZ file for the first time then verify url by accessing it through browser. A File Save dialog box should appear. If fails to access then the SWZ file extension may not be permitted on your webserver. For that add the extension to your webserver to make it accessible. Optimize your custom RSL files before deployment.
  5. Css swf files: Deploy your stylesheet files, compiled css files to swf files to your domain.
  6. Localization files: If you are using multiple languages support at runtime then you must also deploy your modules containing localization resources.
  7. Crossdomain security files: Upload your security files and also update the wildcard access to your specific domains if required.
  8. Updates to crossdomain: Adobe keeps on changing crossdomain policy files structure from time to time with the release of new flash player versions. So keep them updated.
  9. Asset files: Upload you run time asset files like SWF, Sound, Video, Images etc.
  10. Data files: Upload your data files like Text and XML files.
  11. Verify access of webservices: If you are using webservices or HTTP services then verify the links and their functionality.
  12. View Source files: If you are providing view source functionality for your flash application then you must upload the source view HTML, SWF, CSS, XML file, and ZIP file of the source code. Also maintain the directory structure generated by flex builder.


No comments yet — be the first.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s