Accessibility
Adobe
Sign in Privacy My Adobe

Flex Documentation

Flex 1 Updater 2 Installation Instructions

The Macromedia Flex 1.0 Updater 2 includes performance and reliability improvements, enhanced documentation for Flex ActionScript and MXML API Reference, and more. Updater 2 also includes all updates from Updater 1.

This document contains the following information about the Flex 1.0 Updater 2:

About Updater 2

This section provides a summary of changes in Updater 2 and provides an overview of the installation process.

Summary of Changes in Updater 2

Flex 1.0 Updater 2 includes the following updates:

  • Bug fixes and updates to many areas of Flex, including the following:
    • Usability — Improved usability of drop shadows, rounded corners, text alignment, and alpha style settings for containers and controls
    • Components — Added the HSlider and VSlider controls to the standard Flex control set
    • Scalability — Expanded support for large data models
    • Performance — Included byte code optimization, tabbing performance improvements, and style optimizations
    • Documentation — Updated Developing Flex Applications book and updated Flex ActionScript and MXML API Reference (documentation updates are available as a separate download)
  • Updated Flash Debug Player (ActiveX, Netscape, and stand-alone versions)
  • Updated command-line debugger (fdb)
  • Updated sample applications (Flex Explorer, Flex Store, and Occassionally Connected Client)
  • Updated the Flex web applications:
    • Flex base application (flex.war)
    • Flex Profiler (profiler.war)
    • Samples (samples.war)
  • Updated Flex component SWC files for use in the Macromedia Flash MX 2004 IDE (FlexforFlash.zip)

For specific bug fixes and compatibility issues, see the Flex 1.0 Updater 2 Release Notes.

Overview of Updater 2 Installation

The type of Flex installation you have determines how you install Updater 2. There are two types of Flex installations: integrated and nonintegrated.

  • Integrated — You installed the JRun Java application server in addition to Flex. You installed the integrated version of Flex if you had no pre-existing application server prior to installing Flex.
  • Nonintegrated — You deployed the flex.war file onto an existing Java application server. This installation might also include web applications that have been packaged with Flex and deployed to any number of application servers.

The Flex 1.0 Updater 2 installer updates files in their current locations within the Flex application tree. It also writes all the new files to the {flex_install_dir}/flex_updater2 directory. The Updater also copies original versions of all updated files to the {flex_install_dir}/flex_updater2/backup directory. If you are running an integrated version of Flex, the Updater inserts new files into the deployed Flex WAR files flex.war, samples.war, and profiler.war. If you are running a nonintegrated version, you must redeploy the Flex web applications onto your web application server.

This document uses the following variable locations:

  • {flex_install_dir} — The location of your Flex installation. The default location in Microsoft Windows is C:/Program Files/Macromedia/Flex, and /root/Macromedia/Flex in a UNIX system.
  • {flex_app_root} — The top level of web applications that use Flex. An example of a {flex_app_root} directory is C:/jrun4/servers/default/myFlexApp. Web applications using Flex typically run on Java application servers in an open file structure, although they can be in a WAR file. In the latter case, expand the WAR file in order to carry out the instructions in this document. The top-level directory of that WAR file is the {flex_app_root} directory.

Installing Updater 2

The process of installing Updater 2 depends on whether you installed the integrated or nonintegrated version of Flex. The Updater 2 installer detects which version of Flex you are running and installs the appropriate files, but you must still take additional steps to ensure a proper update. If you created new web applications that use Flex, you must also manually update the Flex files in those custom applications.

The following sections describe how to install Updater 2 on the integrated and nonintegrated versions of Flex 1.0 and how to update custom Flex applications.

Before you begin

You may need to do the following before you begin your update of Flex:

  • Depending on the type of installation you have and the type of Java application server, you may be required to stop your server before the update.
  • Delete generated Flex files. Find the {flex_app_root}/WEB-INF/flex/generated directory and delete all files and folders in it. This clears files that might not be backward compatible with the new version of Flex.

Installing Flex 1.0 Updater 2 for a Nonintegrated Flex Installation

In the Flex installation directory, Updater 2 inserts new files into the samples.war, profiler.war, and flex.war web applications. Each new file is also copied to the {flex_install_dir}/flex_updater2 directory. These files are stored in an open directory format so that you can manually copy them to your deployed Flex applications if necessary.

To install Updater 2 on a nonintegrated installation, you first run the Updater 2 installer. To complete installation, you must redeploy the Flex WAR files (flex.war, profiler.war, and samples.war) onto your application server. In addition, if you have created your own Flex applications as WAR or EAR files, you must copy the new files into those applications.

To install Updater 2 for a nonintegrated Flex installation:

  1. Run the Updater 2 installer and follow the onscreen instructions. Depending on your operating system, you will execute one of the following files:
    • flex-updater2-win.exe (Windows)
    • flex-updater2-sol.bin (Solaris)
    • flex-updater2-lin.bin (Linux)
    The Updater 2 installer inserts new files into the WAR files located in {flex_install_dir} and copies new versions of tools, Debug Flash Player, and other files to {flex_install_dir}. The Updater 2 also backs up all files it changes to the {flex_install_dir}/flex_updater2/backup directory.
  2. Find the updated WAR files in the {flex_install_dir} directory. These are:
    • flex.war
    • profiler.war
    • samples.war
  3. Redeploy the new WAR files either using your application server's deploy utility or extracting the contents to the {flex_app_root} directory. Overwrite existing files if you are prompted to do so. Redeploying these WAR files does not overwrite your existing *.mxml, *.as, or other Flex application files that you have written.
  4. If you have deployed custom Flex applications, you must update these applications using the instructions in Updating Custom Flex Applications.

Installing Flex 1.0 Updater 2 for an Integrated Flex Installation

To install Updater 2 on an integrated installation, you first run the Updater 2 installer. The installer updates files in the following open directories:

/flex/jrun4/servers/default/flex
/flex/jrun4/servers/default/profiler
/flex/jrun4/servers/default/samples
      

These open directories correspond to the Flex WAR files (flex.war, profiler.war, and samples.war). If you have created your own Flex applications as WAR or EAR files, you must manually copy the new files into those applications.

To install Updater 2 for an integrated Flex installation:
  1. Run the Updater 2 installer and follow the onscreen instructions. Depending on your operating system, you will execute one of the following files:
    • flex-updater2-win.exe (Windows)
    • flex-updater2-sol.bin (Solaris)
    • flex-updater2-lin.bin (Linux)
    The Updater 2 installer inserts new files into the WAR files running on JRun and copies new versions of tools and Flash Debug Player to {flex_install_dir}. The Updater 2 also backs up all files it changes to the {flex_install_dir}/flex_updater2/backup directory.
  2. If you have deployed custom Flex applications, you must update these applications using the instructions in Updating Custom Flex Applications.

Updating Custom Flex Applications

Use the instructions in this section to update custom Flex applications after you have run the Updater 2 installer.

To update custom application WAR or EAR files:

  1. Expand the contents of the application's WAR or EAR file into an open directory structure.
  2. Replace the following files in the {flex_app_root}/WEB-INF/flex/ directory of your Flex application. These files are located in the {flex_install_dir}/flex_updater2/common/WEB-INF/flex/ directory.
    frameworks/mx.swc
    frameworks_debug/mx_debug.swc
    mxml-manifest.xml
    jars/flex.jar
    jars/commons-httpclient.jar
    jars/flashgateway.jar
      
  3. Repackage the application as a WAR or EAR file.
  4. Redeploy the web application onto your Java application server.

Installing Other Tools in Updater 2

The Flex 1.0 Updater 2 includes several updates to Flex tools, including:

  • Flash Debug Player — The Updater 2 installer copied the new version of this Player to the {flex_install_dir}/bin directory. To install a new Player, use the instructions in your Flex documentation. The new version is 7,0,35,5. You can check the Player version by examining the output of the getVersion() ActionScript method.
  • fdb command-line debugger — To use the new fdb debugger, you must install the Flash Debug Player that comes with Updater 2. The Updater 2 installer installed the other necessary files.
  • FlexforFlash.zip — If you create custom component SWC files from the Flash MX 2004 IDE for use in Flex, you must install the updated FlexforFlash.zip file. For more information, see the Flex 1.0 Updater 2 Release Notes.

Verifying the Updater 2 Installation

When you finish installing Updater 2 and redeploying your Flex web application, restart your web application server. To verify that the upgrade succeeded, examine the INFO entries in the server log files or on the console. The Flex version number should be 80569.125138 or later. The version appears in the server output as the following:

06/24 09:13:12 INFO Macromedia Flex Build: 80569.125138

Uninstalling Updater 2

The Updater 2 installer backs up all files into the {flex_install_dir}/flex_updater2/backup directory.

To uninstall Updater 2:

  1. Redeploy the following WAR files from the {flex_install_dir}/flex_updater2/backup directory onto your application server:
    flex.war
    profiler.war
    samples.war
  2. If you have custom Flex applications, copy the following files out of the {flex_install_dir}/flex_updater2/backup directory and back into your Flex web applications.
    jars/flex.jar
    jars/commons-httpclient.jar
    jars/flashgateway.jar
  3. If your web applications are not in open directory structures but are deployed as WAR or EAR files, you must extract the WAR or EAR files into an open directory structure before you can copy these files into them.

  4. Copy the following files from the {flex_install_dir}/flex_updater2/backup/lib directory to the {flex_install_dir}/lib directory.
    frameworks/mx.swc
    frameworks_debug/mx_debug.swc
    mxml-manifest.xml
      
  5. If necessary, reinstall Flash Debug Player using the backed up version of Flash Debug Player from the {flex_install_dir}/flex_updater2/backup/bin directory.

Getting Started

 

Application Development

 

Security

 

Downloads

 

Documentation

 

Community Resources