Accessibility

Flex Documentation

Flex 1.5 Installation Instructions

This document describes how to install Macromedia Flex 1.5. You can choose between a full Flex 1.5 installation or an upgrade to an existing Flex 1.0 installation. If you already have a Flex 1.0 installation, completing a full installation of Flex 1.5 lets you do a side-by-side comparison of Flex 1.0 and Flex 1.5.

This document contains the following information about Flex 1.5:

For information about what's new in Flex 1.5, compatibility issues, known issues, and bug fixes, see the Flex 1.5 Release Notes.

Important: Uninstall Flex 1.5 Beta

The Flex 1.5 installer does not support installing over a Beta version of Flex 1.5. You must uninstall any installation of the Flex 1.5 Beta before you install the released version. If you have a Flex 1.5 Beta installed and you attempt to install the released version to the same location, the installer prompts you to enter a different location.

Completing a full Flex 1.5 installation

This section contains instructions for completing a full installation of Flex 1.5. These instructions are intended for new Flex users and users who want to create a full installation instead of upgrading a Flex 1.0 installation. For more information, see the following subsections:

Overview

Flex is a J2EE web application that you can install as a Web Application Archive (WAR) file to any supported Java application server. Flex includes the following WAR files:

  • flex.war — The primary Flex WAR file
  • samples.war — Sample Flex applications
  • profiler.war — Debugging application for use with Flex

Each WAR file is a separate, standalone application. Do not install the samples.war file or profiler.war file in the same application directory as the flex.war file. Instead, install them as separate applications on your server with their own directory structures and contexts.

If you install the licensed version of Flex, you must have a Java Application Server already installed. You then deploy the Flex WAR file to your server and start building Flex applications.

If you install Flex without a license key, you have the option of installing Flex to an integrated Java Application Server (JRun 4.0). Select the Macromedia Flex with Integrated JRun4 installation option in the installer if you do not already have a Java Application Server installed. You also have the option of deploying the Flex WAR files to a Java application server, if you have one installed already.

For more information on Flex server requirements, see Flex requirements.

Flex requirements

Flex requires the following:

  • System
    • Intel Pentium processor or SPARC
    • 256 MB RAM (512 MB recommended)
    • 400 MB hard drive space
    • Macromedia Flash Player 7.0.14 or later
  • One of the following application servers:
    • Macromedia JRun 4 Updater 2
    • IBM WebSphere 5
    • BEA WebLogic Server 7 and 8.1
    • Tomcat 4.1.29 and later
    • Oracle 10g AS (newly supported)
  • One of the following operating systems:
    • IBM AIX 5.2 in conjunction with WebSphere 5 (newly supported)
    • Microsoft Windows 2000 Server
    • Microsoft Windows 2003 Server
    • Microsoft Windows 2003 Standard Server
    • Microsoft Windows XP Professional
    • Red Hat Enterprise AS 2.1 and 3.0
    • Sun Solaris 8
    • Sun Solaris 9
  • One of the following Java versions:
    • Sun 1.3.x
    • Sun 1.4.x
    • IBM 1.3 for use with WebSphere
    • IBM 1.4 for use with WebSphere
    • BEA JRockit 1.4 for use with Weblogic
    • Note: Double-byte operating systems require a double-byte version of the Java Runtime Environment (JRE).

Installing Flex in Windows

This section contains two installation procedures: one for systems that have a Java Application Server already installed, and one for systems that do not.

To install Flex on a system with an existing Java application server:

  1. (Optional) Create a new server instance on your Java application server.
  2. Double-click the flex-15-win.exe file.
  3. Follow the onscreen instructions for completing a full installation of Flex. In the Install Options window, select the Macromedia Flex (default) option. This window appears only if you entered an invalid serial number or no serial number.

    The installer writes the following files to the default installation folder, C:/Program Files/Macromedia/Flex: 

    /flex.war

/profiler.war

/samples.war

/dochome.htm
/flex_app.ico
/license.htm
/Macromedia_Flex_1.5_InstallLog.log
/readme.htm
/xd.css

/bin/..
/extras/..
/lib/..
/resources/..
/UninstallerData/..
  4. When the installer finishes, find the flex.war file at the top level of the default installation folder.
  5. Depending on your application server configuration, either copy the flex.war file to the application server's deployment directory or extract the contents of the flex.war file to a \flex directory within the application server's deployment directory. In either case, /flex will be your context root.

    Note: On BEA WebLogic Server, you must extract the contents of the Flex WAR files.

    If you must deploy an expanded war file; use WinZip, jar, or another archiving utility to extract the contents of the flex.war file. For example, from the /flex directory, enter the following command: 

    jar -xvf "C:/Program Files/Macromedia/Flex/flex.war"
  6. Repeat the Step 5 for the samples.war file, also located in the top-level installation folder. If you must deploy an expanded war file, create a \samples directory to define an application with a context root of /samples.
  7. Repeat Step 5 for the profiler.war file, also located in the top-level installation folder. If you must deploy an expanded war file, create a \profiler directory to define an application with a context root of /profiler.
  8. Optionally, specify the JVM for the Flex tools in flex_install_dir\bin.

    On Microsoft Windows, the JVM used by the Flex tools in flex_install_dir\bin is defined by the java.home parameter in the flex_install_dir/bin\jvm.config file. By default, java.home is set to the following:

    java.home=../UninstallerData/jre2

    Note: On UNIX, Flex determines the location of your JVM from the setting of your PATH environment variable.

    If you want to use a different JVM, set java.home to a different path, or set it to blank. If set to blank, Flex determines the location of your JVM by looking in the following locations, in the specified order:

    1. The path specified by the JAVA_HOME environment variable
    2. The bin directory for java.dll
    3. The relative path ..\jre
    4. The Windows registry

    For more information, see the comments in the flex_install_dir\bin\jvm.config file.

  9. Start or restart your application server. For more information, see your web application server's documentation.
  10. To configure Flash Player debugging or profiling for Flex, copy the /Flex/bin/mm.cfg file to the client computer's home directory. To determine the location of your home directory on a Windows computer, enter the following command at the command prompt: 
    echo %HOMEDRIVE%%HOMEPATH%

    There are additional steps to using the Profiler. For more information, see Developing Flex Applications.

    For additional information on identifying your home directory, see Configuring Flex.

  11. Install Flash Player 7. For more information, see Installing Flash Player.
  12. Verify the installation. For more information, see Verifying the Flex Installation.

To install Flex in a Windows system with no pre-existing Java Application Server:

  1. Double-click the flex-15-win.exe file.
  2. Follow the onscreen instructions for completing a full installation of Flex. In the Install Options window, select the Macromedia Flex with Integrated JRun4 option. This window appears only if you entered an invalid serial number or no serial number.

    The installer writes the following files to the default installation folder, C:/Program Files/Macromedia/Flex: 

    /dochome.htm
/flex_app.ico
/license.htm
/Macromedia_Flex_1.5_InstallLog.log
/readme.htm
/xd.css

/bin/...
/extras/..
/jrun4/bin/..
/jrun4/lib/..
/jrun4/servers/default/default-war/..
/jrun4/servers/default/flex/.. (exploded flex.war application)
/jrun4/servers/default/profiler/.. (exploded profiler.war application)
/jrun4/servers/default/samples/.. (exploded samples.war application)
/lib/..
/resources/..
/UninstallerData/..

    The /Flex/jrun4 directory contains the development version of the JRun 4 Application Server and deployed versions of the Flex applications.

  3. When the installer finishes, start the JRun 4 server. To start JRun, see Starting and stopping JRun.
  4. Optionally, specify the JVM for the Flex tools in flex_install_dir\bin.

    On Microsoft Windows, the JVM used by the Flex tools in flex_install_dir\bin is defined by the java.home parameter in the flex_install_dir/bin\jvm.config file. By default, java.home is set to the following:

    java.home=../UninstallerData/jre2

    Note: On UNIX, Flex determines the location of your JVM from the setting of your PATH environment variable.

    If you want to use a different JVM, set java.home to a different path, or set it to blank. If set to blank, Flex determines the location of your JVM by looking in the following locations, in the specified order:

    1. The path specified by the JAVA_HOME environment variable
    2. The bin directory for java.dll
    3. The relative path ..\jre
    4. The Windows registry

    For more information, see the comments in the flex_install_dir\bin\jvm.config file.

  5. To configure Flash Player debugging or profiling for Flex, edit the home_directory/mm.cfg file. The installer copied that file to your home directory during installation. In Microsoft Windows 2000 and Windows XP, the default home directory is C:/Documents and Settings/user_name where user_name is your system user name.

    There are additional steps to using the Profiler. For more information, see Developing Flex Applications.

    For information on identifying your home directory, see Configuring Flex.

  6. Install Flash Player 7. For more information, see Installing Flash Player.
  7. Verify the installation. For more information, see Verifying the Flex Installation.

Starting and stopping JRun 4

This section describes how to start and stop the integrated JRun Java Application Server.

To start the integrated JRun 4 server:

  1. Select Start > Programs > Macromedia > Macromedia Flex > Start Integrated Flex Server.
or
  1. Open a Command Prompt window.
  2. Change directories to the /Flex/jrun4/bin directory.
  3. Enter the following command: 
    jrun -start default

With the integrated JRun server, the Flex applications are accessible using the following URLs: 

http://localhost:8700/flex
http://localhost:8700/profiler
http://localhost:8700/samples

To stop the JRun server, enter the following command: 

jrun -stop default

For more information on JRun 4, see the JRun 4 documentation.

Installing Flex in Linux, Solaris, or AIX

This section contains two installation procedures: one for systems that have a Java application server already installed, and one for systems that do not. The second procedure installs a JRE and the JRun 4 Java Application Server for use with Flex; the procedure does not apply to installations on AIX because JRun 4 is not supported on that operating system.

To install Flex on a system with an existing Java application server:

  1. (Optional) Create a new server instance on your Java application server.
  2. Start the Flex installer using the appropriate command for your operating system:
    • Linux: 
      ./flex-15-lin.bin
    • Solaris: 
      ./flex-15-sol.bin
    • AIX: 
      java -cp flex-15-install.jar install -i console
      Optional: If you have X-Windows installed, you can include the -i gui switch to run the installer with the GUI interface.
  3. Follow the onscreen instructions for completing a full installation of Flex. In the Install Options window, select the Macromedia Flex (default) option. This window appears only if you entered an invalid serial number, or no serial number.

    The installer writes the following files to the default installation folder, /root/Macromedia/Flex: 

    /flex.war
/profiler.war
/samples.war

/flex_app.ico
/dochome.htm
/license.htm
/Macromedia_Flex_1.5_InstallLog.log
/readme.htm
/xd.css

/bin/..
/extras/..
/lib/..
/resources/..
/UninstallerData/..
  4. When the installer finishes, find the flex.war file at the top level of the installation folder.
  5. Depending on your application server configuration, either copy the flex.war file to the application server's deployment directory or extract the contents of the flex.war file to a /flex directory within the application server's deployment directory. In either case, /flex will be your context root.

    Note: On BEA WebLogic Server, you must extract the contents of the Flex WAR files.

    If you must deploy an expanded war file, use jar or another archiving utility to extract the contents of the flex.war file. For example, from the /flex directory, enter the following command: 

    jar -xvf /root/Macromedia/Flex/flex.war
  6. Repeat Step 5 for the samples.war file, also located in the top-level installation folder. If you must deploy an expanded war file, create a /samples directory to define an application with a context root of /samples.
  7. Repeat Step 5 for the profiler.war file, also located in the top-level installation folder. If you must deploy an expanded war file, create a /profiler directory to define an application with a context root of /profiler.
  8. If your UNIX system does not have a monitor (it is headless), you must do one of the following, depending on your environment:
    • X-windows with any supported JRE: You must set the DISPLAY environment variable.
    • JRE 1.4.x: Locate the <headless-server> line in the /jrun4/servers/server_name/application_name/WEB-INF/flex/flex-config.xml file for the flex.war and samples.war applications, and set its value to true, as the following line shows: 
      <headless-server>true</headless-server>
  9. Start or restart your application server. For more information, see your web application server's documentation.
  10. To configure Flash Player debugging or profiling for Flex, copy the /Flex/bin/mm.cfg file from your Linux/Solaris computer to the home directory on a Windows client. To determine the location of your home directory on a Windows computer, use the following command at the command prompt: 
    echo %HOMEDRIVE%%HOMEPATH%

    There are additional steps to using the Profiler. For more information, see Developing Flex Applications.

    For additional information on identifying your home directory, see Configuring Flex.

  11. Install Flash Player 7. For more information, see Installing Flash Player.
  12. Verify the installation. For more information, see Verifying the Flex Installation.

To install Flex in a Linux/Solaris system with no pre-existing Java Application Server:

  1. Start the Flex installer using the appropriate command for your operating system:
    • Linux: 
      ./flex-15-lin.bin
    • Solaris: 
      ./flex-15-sol.bin
    • AIX:

      This option is not available on AIX.

    Optional: If you have X-Windows installed, you can include the -i gui switch to run the installer with the GUI interface.

  2. Follow the onscreen instructions for completing a full installation of Flex. In the Install Options window, select the Macromedia Flex with Integrated JRun4 installation option. This window only appears if you entered a Trial serial number, an invalid serial number, or no serial number.

    The installer writes the following files to the default installation folder, /root/Macromedia/Flex: 

    /dochome.htm
/flex_app.ico
/license.htm
/Macromedia_Flex_1.5_InstallLog.log
/readme.htm
/xd.css

/bin/...
/extras/..
/jrun4/bin/..
/jrun4/lib/..
/jrun4/servers/default/default-war/..
/jrun4/servers/default/flex/.. (exploded flex.war application)
/jrun4/servers/default/profiler/.. (exploded profiler.war application)
/jrun4/servers/default/samples/.. (exploded samples.war application)
/lib/..
/resources/..
/UninstallerData/..

    The /Flex/jrun4 directory contains the development version of the JRun 4 Application Server and deployed versions of the Flex applications.

  3. When the installer finishes, start the JRun 4 server. To start JRun, see Starting and stopping JRun.
  4. If your system does not have a monitor (it is headless), you must do one of the following, depending on your environment:
    • X-windows with any supported JRE: You must set the DISPLAY environment variable.
    • JRE 1.4.x: Locate the <headless-server> line in the /jrun4/servers/server_name/application_name/WEB-INF/flex/flex-config.xml file for the flex.war and samples.war applications, and set its value to true, as the following line shows: 
      <headless-server>true</headless-server>
  5. To configure Flash Player debugging or profiling for Flex, copy the /Flex/bin/mm.cfg file from your UNIX computer to the home directory on a Windows client. To determine the location of your home directory on a Windows computer, use the following command at the command prompt: 
    echo %HOMEDRIVE%%HOMEPATH%

    There are additional steps to using the Profiler. For more information, see Developing Flex Applications.

    For additional information on identifying your home directory, see Configuring Flex.

  6. Install Flash Player 7. For more information, see Installing Flash Player.
  7. Verify the installation. For more information, see Verifying the Flex Installation.

Starting and stopping JRun 4

This section describes how to start and stop the integrated JRun Java Application Server.

To start the JRun 4 server:

  1. Change directories to the /Flex/jrun4/bin directory.
  2. Enter the following command: 
    ./jrun -start default

With the integrated JRun server, the Flex applications are accessible using the following URLs: 

http://localhost:8700/flex
http://localhost:8700/profiler
http://localhost:8700/samples

To stop the JRun 4 server:

  1. Change directories to the /Flex/jrun4/bin directory.
  2. Enter the following command: 
    ./jrun -stop default

For more information on JRun 4, see the JRun 4 documentation.

Installing Flash Player

Flex requires that you run Flash Player 7. Flex supports Flash Debug Player and standardFlash Player. Flash Debug Player displays debugging information during runtime and generates profiling information so that you can more easily develop applications.

Note: Before you install Flash Player, you should uninstall your existing Flash Player. Flex includes the Flash Player uninstallation utility (uninstall_flash_player.exe) in the {flex_install_dir}/bin directory.

The following table describes the standard Flash Players. Click a link in this table to go to the Flash Player download site for the download file and instructions.

Standard Flash Player Description
ActiveX Player An ActiveX Flash plug-in for Microsoft Internet Explorer.
NS Player A Flash plug-in for Netscape Navigator.
Mac OS Player A Flash player for Mac OS X.
Stand-alone Player An executable application that lets you run Flash files in a separate window so that they feel more like stand-alone applications. The stand-alone player does not support HTTP authentication or the use of a web proxy, which is required for some Flex applications.

The following table describes Flash Debug Player:

Flash Debug Player Description
ActiveX Debug Player An ActiveX Flash plug-in for Microsoft Internet Explorer that includes enhanced error reporting and supports the Flex Debugger and ActionScript Profiler.
Netscape/Mozilla Debug Player A debug player for Netscape Navigator or Mozilla that includes enhanced error reporting and supports the Flex Debugger and ActionScript Profiler.
Stand-alone Debug Player An executable Flash application that lets you run Flash files in a separate window so that they feel more like stand-alone applications. This version includes enhanced error reporting and supports the Flex Debugger and ActionScript Profiler applications. The stand-alone player does not support HTTP authentication or the use of a web proxy which is required for some Flex applications.

To install the ActiveX Flash Debug Player for Microsoft Internet Explorer:

  1. (Linux/Solaris only) Copy Flash Debug Player installation file, "Install Flash Player 7 AX.exe", from the {flex_install_dir}/bin directory on your Linux/Solaris system to a Windows computer.
  2. Run the following file: 
    Install Flash Player 7 AX.exe

To install the Netscape or Mozilla Flash Debug Player:

  1. (Linux/Solaris only) Copy Netscape/Mozilla Debug Player installation file, "Install Flash Player 7.exe", from the {flex_install_dir}/bin directory on your Linux/Solaris system to a Windows computer running Netscape or Mozilla.
  2. Run the following file: 
    Install Flash Player 7.exe

To run the stand-alone Flash Debug Player:

  1. (Linux/Solaris only) Copy the stand-alone Flash Debug Player, "SAFlashPlayer.exe", from the {flex_install_dir}/bin directory on your Linux/Solaris system to a Windows computer.
  2. Run the following file: 
    SAFlashPlayer.exe

Verifying the Flex installation

After you install Flex, you should verify that the application is running properly on your Java Application Server. If you installed the samples.war file or used the integrated installer, you can request the Flex sample applications, as described below.

If you did not install the samples.war file or use the integrated installer, to verify the Flex installation, you must create a new MXML file and request that file. For more information, see the Flex documentation.

To verify the Flex installation with sample applications:

  1. Open the following URL in your browser: 
    http://<hostname>:<port_num>/samples_context_root

    On a system that had a Java application server already running, you access the Flex application using the application server's port number; for example: 

    http://localhost:8101/samples

    On a system that used the integrated installation option, the default port for Flex applications is port 8700; for example: 

    http://localhost:8700/samples

    The Flex Samples page appears.

  2. Select a sample application to run.

If a page does not display, see the following table for troubleshooting ideas:

    Problem Possible solution
    Port conflicts If you created a new server for the Flex application, ensure that the ports used by that server do not conflict with other servers running on your web application server.
    Web server Ensure that your web server is running.
    Context root Ensure that you are using the correct context root in your request URL. For more information, see Configuring Flex.
    Application server Restart your application server after you deploy the flex.war file.
    Flash Player Ensure that you are running the latest version of Flash Player. For more information, see Installing Flash Player.

Configuring Flex

Client computers store logging and configuration information for Flash Player in their home directory. This section describes how to locate your home directory and change the Flex context root.

Locating your home directory

To configure Flash Player error reporting and profiling for Flex, you must copy the mm.cfg file to the client computer's home directory. The home directory is also the location of the flashlog.txt file which stores trace output, system errors, and warning messages generated by the Flash Debug Player while running a Flex application.

Two Microsoft Windows environment variables define the location of the home directory:

  • HOMEDRIVE — Specifies the drive letter of the path to the home directory. In most Microsoft Windows systems, the default value is C:, the primary hard drive.
  • HOMEPATH — Specifies the path to the home directory, relative to HOMEDRIVE. In Microsoft Windows 2000 and Windows XP, the default is /Documents and Settings/user_name where user_name is your system user name.

To determine the settings of HOMEDRIVE and HOMEPATH for your system:

  1. Open a Command Prompt window.
  2. At the prompt, enter the following command: 
    echo %HOMEDRIVE%%HOMEPATH%

Changing the context root

To change the context root in Java application servers, see your server's documentation. For more information on JRun 4, see the JRun 4 documentation.

Uninstalling Flex 1.5 in Windows

Warning: The uninstaller removes all files under the installation directory. If you need to preserve any files, such as MXML and AS files, please back them up before proceeding with the uninstall.

To uninstall Flex 1.5:

  1. From the Start menu, select Settings > Control Panel.
  2. Double-click the Add/Remove Programs icon.
  3. Select Macromedia Flex 1.5.
  4. Click the Change/Remove button.
  5. Click the Uninstall button in the Uninstall window.
  6. Click the Done button when the process is complete.

Note: You can also run the uninstall executable from {installdir}/UninstallerData/Uninstall Macromedia Flex 1.5.exe to uninstall Flex.

Uninstalling Flex 1.5 in Linux, Solaris, or AIX

Warning: The uninstaller removes all files under the installation directory. If you need to preserve any files, such as MXML and AS files, please back them up before proceeding with the uninstall.

To uninstall Flex 1.5:

  • Run the uninstall script from {installdir}/UninstallerData:
    • Linux/Solaris: 
      ./Uninstall_Macromedia_Flex_1.5
    • AIX (JAR installer): 
      java -cp Uninstall_Macromedia_Flex_1.5 uninstall

Upgrading to Flex 1.5

This section contains instructions for completing an upgrade installation from Flex 1.0 to Flex 1.5.

This document uses the following variable locations:

  • {flex_install_dir} — The location of your Flex installation. The default location is C:\Program Files\Macromedia\Flex in Microsoft Windows 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 that use 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.

For more information, see the following subsections:

Overview

The Flex installer gives you the option to perform a full installation of Flex 1.5, or upgrade an existing installation of Flex 1.0 to Flex 1.5. When you choose to upgrade an existing Flex installation, the Flex 1.5 installer backs up all files to the {flex_install_dir}/backup directory.

For more information on performing a full installation of Flex 1.5, see Creating a full Flex 1.5 installation.

If you are upgrading an existing Flex 1.0 installation, the Flex 1.5 installer detects which version of Flex you are running and installs the appropriate files. If you are running an integrated version of Flex, the installer replaces the deployed Flex WAR files flex.war, samples.war, and profiler.war. If you are running a nonintegrated version, the installer replaces the application WAR files. You must then redeploy the WAR files to your web application server.

If you created and deployed any Flex applications, see Updating existing Flex 1.0 applications to Flex 1.5.

Installing Flex 1.5 for a nonintegrated Flex installation

In the Flex installation directory, the Flex 1.5 installer inserts new versions of the samples.war, profiler.war, and flex.war applications and all other Flex files, and copies original versions of all Flex files to the {flex_install_dir}/backup directory.

To complete the installation, you must redeploy the Flex WAR files (flex.war, profiler.war, and samples.war) to your application server. In addition, if you have your own Flex applications as WAR or EAR files, you must redeploy your applications using the Flex 1.5 WAR files. For more information, see Updating Existing Flex 1.0 Applications to Flex 1.5.

To install Flex 1.5 for a nonintegrated Flex installation:

  1. Run the Flex 1.5 installer and follow the onscreen instructions for upgrading an existing installation. Depending on your operating system, you run one of the following files:
    • flex-15-win.exe (Windows)
    • flex-15-sol.bin (Solaris)
    • flex-15-lin.bin (Linux)
    • java -cp flex-15-install.jar install -i console (AIX)

    When you update an existing installation, the Flex 1.5 installer inserts a new version of the WAR files located in {flex_install_dir} and copies new versions of tools, Flash Debug Player, and other files to {flex_install_dir}. The Flex 1.5 upgrade installer also backs up all Flex 1.0 files to the {flex_install_dir}/backup directory.

  2. Find the following updated WAR files in the {flex_install_dir} directory:
    • flex.war
    • profiler.war
    • samples.war
  3. Redeploy the new WAR files either using your application server's deploy utility or by extracting the contents to the {flex_app_root} directory. Overwrite existing files if you are prompted to do so.
  4. If you deployed custom Flex applications, you must update these applications using the instructions in Updating existing Flex 1.0 applications to Flex 1.5.

Installing the Flex 1.5 for an integrated Flex installation

The Flex installer puts the Flex 1.5 application 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).

To install Flex 1.5 for an integrated Flex installation:

  1. Run the Flex 1.5 installer and follow the onscreen instructions for upgrading an existing installation. Depending on your operating system, you run one of the following files:
    • flex-15-win.exe (Windows)
    • flex-15-sol.bin (Solaris)
    • flex-15-lin.bin (Linux)
    • java -cp flex-15-install.jar install (AIX)
    The Flex 1.5 installer inserts new versions of the WAR files running on JRun and copies new versions of all Flex files, tools, and Flash Debug Player to {flex_install_dir}. The Flex 1.5 upgrade installer also backs up all Flex 1.0 files to the {flex_install_dir}/backup directory.
  2. If you deployed custom Flex applications, you must update these applications using the instructions in Updating existing Flex 1.0 applications to Flex 1.5.


Updating existing Flex 1.0 applications to Flex 1.5

Use the instructions in this section to manually update your existing Flex 1.0 applications after you run the Flex 1.5 installer.

To update existing application WAR or EAR files:
  1. Integrate your existing Flex 1.0 application files into a Flex 1.5 application directory. Typically, you integrate your application into the directory where you deployed the flex.war file.
  2. Test your application on Flex 1.5. For information on migration issues when moving an application from Flex 1.0 to Flex 1.5, see the Flex Migration Guide.
  3. Repackage the application as a WAR or EAR file.
  4. Redeploy the web application to your Java application server.

Installing other tools in Flex 1.5

Flex 1.5 includes several updates to Flex tools, including:

  • Flash Debug Player — The Flex 1.5 installer copied the new version of this player to the {flex_install_dir}/bin directory. To install a new Player, use the instructions in Installing Flash Player. The new version is 7,0,35,29. 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 Flex 1.5. The Flex 1.5 installer installed the other necessary files.

Getting Started

 

Application Development

 

Security

 

Downloads

 

Documentation

 

Community Resources

 
 

 
Choose your region    Products   Downloads   Learn & Support   Company

Copyright © 2024 Adobe Systems Incorporated. All rights reserved.

Terms of Use | Privacy | Cookies