Installing Macromedia Flash Remoting Updater Release 1

This document contains installation instructions for Macromedia Flash Remoting Updater Release 1. This includes updates to the Flash Remoting MX server environment and the Flash Remoting Components used in Flash MX.

This Updater is for Flash Remoting MX for .NET and Java and the Flash Remoting Components. For updates to Flash Remoting MX within ColdFusion MX, see the ColdFusion Support site at http://www.macromedia.com/support/coldfusion to get the appropriate Updater. For updates to Flash Remoting MX within JRun 4, see the JRun Support site at http://www.macromedia.com/support/jrun to get the appropriate Service Pack.

For the Macromedia Flash Remoting Updater Release 1 Release Notes, see http://www.macromedia.com/go/flashremotingupdater_releasenotes

The Flash Remoting Updater Release 1 includes the following:

Flash Remoting Components — Install the Flash Remoting Components to use Flash Remoting in the Flash MX IDE.
Flash Remoting MX application server files — Install the Flash Remoting MX application server files to run Flash Remoting on your Web application server.

The Flash Remoting MX Components Updater Release 1 includes the following updated files used by Flash MX:

• Flash Remoting ActionScript libraries
• NetConnection Debugger utility
• HTML help files

The following sections describe how to install the Flash Remoting Components Updater Release 1:

Installing Flash Remoting Components (Windows)
Installing Flash Remoting Components (Macintosh)

Installing Flash Remoting Components (Windows)

Use the instructions in this section to install the Flash Remoting Components Updater Release 1 for Flash MX in a Windows environment.

To install the Flash Remoting Updater Release 1 components for Windows:

1. Close Flash MX.
2. Locate your Flash MX application's root directory. The default installation directory is C:/Program Files/Macromedia/FlashMX.
3. Make a backup copy of your Flash MX root directory and all its contents.
4. Delete the flash_root/FlashRemotingHelp directory and all its contents. The Updater replaces this directory with a new set of HTML help files.
5. Unzip the FlashRemotingCmpntsUpdater_r1_en.zip file (or your localized version) into the Flash MX root directory.
6. If your extraction utility asks if it should overwrite existing files, select Yes for all files.

Use the instructions in this section to install the Flash Remoting Components Updater Release 1 for Flash MX in a Macintosh environment. When you download the FlashRemotingCmpntsUpdater_r1_en.zip file (or your localized version), your extraction utility expands the contents to the Users/username/Desktop directory.

To install the Flash Remoting Updater Release 1 components for the Macintosh:

1. Close Flash MX.
2. Locate your Flash MX application's root directory. The default installation directory is Applications/Macromedia Flash MX.
3. Make a backup copy of your Flash MX root directory and all its contents.
4. Delete the flash_root/FlashRemotingHelp directory and all its contents. The Updater replaces this directory with a new set of HTML help files.
5. Copy the extracted files into your Flash MX root directory using the command-line cp utility. For example:
   

   cp -r * /Applications/Macromedia\ Flash\ MX/

   NOTE: Do not drag and drop the folder onto the existing Flash MX root directory. This replaces existing directories and all their contents.

The following sections describe how to install the Flash Remoting MX Updater Release 1 application server files:

Installing Flash Remoting MX (.NET)
Installing Flash Remoting MX (Java)

Installing Flash Remoting MX (.NET)

The Flash Remoting MX .NET Updater Release 1 ZIP file includes a single DLL file. This section describes how to install the DLL.

To install Flash Remoting MX Updater Release 1 for .NET:

1. Extract the contents of the flashremoting-net-updater-r1.zip file to a temporary location.
2. Stop your .NET server.
3. Locate the Flash Remoting bin directory for your .NET server. The default location is C:/inetpub/wwwroot/flashremoting/bin.
4. Replace the existing flashgateway.dll file in the bin directory with the one you extracted from the flashremoting-net-updater-r1.zip file.
5. Search for the flashgateway.dll file. You might have multiple copies of it. Replace all existing copies.
6. Restart your .NET server.

The Flash Remoting MX J2EE Updater Release 1 ZIP file (flashremoting-java-updater-r1.zip) includes two EAR files, two WAR files, and a JAR file. You use only one of these files to upgrade your J2EE application server with the Updater Release 1. Which file you use depends on your application server and your preferred method of deployment. The following table describes these files:

The following sections describe how to install each of these files.

1. Extract the contents of the flashremoting-java-updater-r1.zip file to a temporary location.
2. Optional. If you want to make changes to the deployment descriptor, such as changing the servlet mapping:
   1. Extract the contents of the WAR file using the JAR utility. For example:
      

      jar -x flashgateway.war

   2. Edit the web.xml deployment descriptor in the WEB-INF directory with your own settings.
   3. Repackage the WAR file using the JAR utility. For example:

      jar -cvf flashgateway.war *

3. Undeploy the current WAR file containing Flash Remoting using your application server's documentation. This step may be optional. For more information, see your application server's documentation.
4. Stop your application server. This step may be optional.
5. Deploy the flashgateway.war (or flashgateway-samples.war) file using your application server's deployment utility.
6. If you stopped your application server, start it.

1. Extract the contents of the flashremoting-java-updater-r1.zip file to a temporary location.
2. Optional. If you want to make changes to the deployment descriptors, such as changing the servlet mapping or the context root:
   1. Extract the contents of the EAR file using the JAR utility. For example:
      

      jar -x flashgateway.ear

      The extracted files include the flashgateway.war file and application deployment descriptor in the standard EAR file layout.

   2. Edit the application.xml deployment descriptor in the META-INF directory.
   3. Extract the contents of the flashgateway.war file using the JAR utility. For example:
      

      jar -x flashgateway.war

      The extracted files include the flashgateway.jar file and web.xml deployment descriptor in the standard WAR file layout.

   4. Edit the web.xml deployment descriptor in the WEB-INF directory.
   5. Repackage the WAR file using the JAR utility. For example:

      jar -cvf flashgateway.war *

   6. Repackage the EAR file using the JAR utility. For example:

      jar -cvf flashgateway.ear *

3. Undeploy the current EAR file containing Flash Remoting using your application server's instructions. This step may be optional. For information on undeploying enterprise applications, see your application server's documentation.
4. Stop your application server. This step may be optional.
5. Deploy the flashgateway.ear (or flashgateway-samples.ear) file using your application server's deployment utility.
6. If you stopped your application server, start it.

1. Extract the contents of the flashremoting-java-updater-r1.zip file to a temporary location.
2. Stop your application server. This step may be optional. For more information, see your application server's documentation.
3. Locate the existing flashgateway.jar file in your application server's directory structure.

   If you only use Flash Remoting in a single Web application, the JAR file is likely in the Web application's web_app_name/WEB-INF/lib directory. If you use Flash Remoting in more than one application on your server, the JAR file is likely in a global directory such as /lib. For more information, see your application server's documentation.

4. Replace the existing flashgateway.jar file with the one you extracted from the flashremoting-java-updater-r1.zip file.
5. Add the following servlet definition to your Web application's web.xml file:
   

   <servlet>
    <servlet-name>FlashGatewayServlet</servlet-name>
    <display-name>Flash Remoting MX Servlet</display-name>
    <description>Servlet-based plugin to Flash Remoting</description>
    <servlet-class>flashgateway.controller.GatewayServlet</servlet-class>
    <init-param>
     <param-name>LOG_LEVEL</param-name>
     <param-value>Error</param-value>
     <description>Controls the level of information logged.</description>
    </init-param>
    <init-param>
     <param-name>DISABLE_JAVA_ADAPTERS</param-name>
     <param-value>false</param-value>
     <description>When set to true, this setting disables the Java Service Adapters in the gateway.</description>
    </init-param>
    <load-on-startup>1</load-on-startup>
   </servlet>

6. Add the following servlet mapping to your Web application's web.xml file:

   <servlet-mapping>
    <servlet-name>FlashGatewayServlet</servlet-name>
    <url-pattern>/gateway</url-pattern>
   </servlet-mapping>
   		  

7. If you stopped your application server, start it. If you did not stop your application server, you might be required to restart it. For more information, see your application server's documentation.