Your production environment determines how you deploy your application. One option is to package your application and assets in a BlazeDS web application, and then create a single WAR file that contains the entire web application. You can then deploy the single WAR file on your production server.

Alternatively, you can deploy multiple BlazeDS applications on a single web application. In this case, your production server has an expanded BlazeDS web application to which you add the directories that are required to run your new application.

When you deploy your BlazeDS application in a production environment, ensure that you deploy all the necessary parts of the application, including the following:

• The compiled SWF file that contains your client-side application
• The HTML wrapper generated by Flex Builder or created manually if you use the mxmlc compiler
• The compiled Java class and JAR files that represent your server-side application
• Any run-time assets required by your application
• A BlazeDS web application
• Updated BlazeDS configuration files that contain the necessary information to support your application