Blaze. DS / Home / Blaze. DS 4. 0 Installation Guide. Blaze. DS 4. 0 Installation Guide. Contents. Blaze. DS 4.
Installation Guide. Installing Blaze.
Using BlazeDS with Spring. BlazeDS is deployed as a set of JAR files as part of your web. The instructions in this document assume that you use the BlazeDS turnkey server. If you are using one of the alternative.
DS with integrated Apache Tomcat application server (turnkey)Installing Blaze. DS with J2. EE web applications. Additional server- specific configuration. Running Blaze. DS from a compressed WAR file. Upgrading Blaze. DS 3. Blaze. DS runs in a J2. EE web application and is available in ZIP files for the following configurations: Blaze.
- JoseRamonLeon / spring-flex forked from. and copyright 'dist' contains the Spring BlazeDS Integration distribution jar files 'src' contains the Spring BlazeDS Integration distribution. They are using the org.
- BlazeDS 3 Installation Guide Authors: BlazeDS 3. Expand the flex.war file using winzip or the JAR utility. Copy the following jar files from c:\temp\BlazeDS\WEB-INF\lib to ColdFusion8/wwwroot/WEB-INF/flex/jars.
Deploying BlazeDS jar files. Tagged: crud application using flex and blazeds, crud application using flex and java, flex based crud. You are currently browsing the archives for the Flex and BlazeDS category. Setting up BlazeDS. Another goal of this BlazeDS endeavor was to avoid using the BlazeDS turnkey system. The BlazeDS turnkey system contains a few WAR files in the root directory.
![Using Jar Files Blazeds Using Jar Files Blazeds](http://rohitsethiya.files.wordpress.com/2014/02/new-bitmap-image.jpg?w=620&h=348)
DS with integrated Apache Tomcat application server (turnkey) Blaze. DS web applications Blaze. DS runs on the following platforms: These installation instructions refer to root directory where you unzip the Blaze. DS ZIP file as install_root. Blaze. DS includes the following Web Application Archive (WAR) files: blazeds. The primary Blaze. DS WAR file: use this as a starting point for building your Blaze.
DS application. blazeds- spring. An additional Blaze.
DS WAR file: use this as a starting point for building Blaze. DS applictions using the Spring framework. Sample Blaze. DS applications. Samples Blaze. DS application that integrates with the Spring framework. Simple monitoring application for Blaze.
DS deployments. Each WAR file is a separate, stand- alone web application. If you are using the J2. EE web application option, you must have an existing J2. EE application server or servlet container available and understand web application deployment. If you do not have an existing J2. EE server or are not familiar with WAR file deployment, use the integrated Tomcat configuration to get started. Note: for more information on the Blaze.
DS Spring integration see http: //www. Installing Blaze.
DS with integrated Apache Tomcat application server (turnkey)The Blaze. DS with integrated Tomcat ZIP file contains the following files and directories under the installation root: blazeds_turnkey_readme. Contains license information. Blaze. DS web application, used as a starting point for new applications.
Blaze. DS web application using Spring framework, used as a starting point for new application using the Spring framework. Blaze. DS sample applications. Samples Blaze. DS application that integrates with the Spring framework. Simple monitoring application for Blaze. DS deployments. /docs - Contains the Blaze.
DS Javadocs./tomcat - Contains an installation of Apache Tomcat that includes blazeds, samples, and ds- console web applications expanded and deployed in the default server./resources - Contains Flex SDK source code, fully commented configuration files, as well as directories and files used for security, clustering, Flex Ajax Bridge and manually creating HTML wrappers. Flash Player installers are in the Flex SDK ZIP file./sampledb - Contains a sample HSQLDB database used with the integrated Apache Tomcat application server (turnkey)To install Blaze. DS in the integrated Tomcat configuration: Read the Blaze. DS Release Notes for known issues and any late- breaking information. Unzip the blazeds- turnkey- 4. Make sure that the machine you are installing on has a Java Development Kit (JDK) installed, JAVA_HOME environment variable set and (Windows only) the PATH environment variable updated to include JAVA_HOME/bin.
For Windows you can test your JDK environment variable configuration as follows: a. From a command prompt, type: cd JAVA_HOME/bin b. Next type: java - version c. The version of the JDK will be returned. If an error is returned, you must correct your environment variable settings before proceeding. To start Blaze. DS on Microssoft Windows, open a command window, navigate to install_root/tomcat/bin, and enter the catalina start command. On OS X, UNIX, and Linux, enter ./catalina start.
Optionally, on Windows you can navigate to the install_root/tomcat/bin in Windows Explorer and double- click the startup. Running the Test Drive applications with the integrated Tomcat install. In addition to the Blaze.
DS WAR file, the Blaze. DS download includes a version of Tomcat (6. Blaze. DS. There are two test drive applications: Samples. Samples- spring. To run the test drive applications after downloading and expanding the integrated Tomcat install: Start Tomcat (startup.
The Blaze. DS sample applications use an HSQLDB database that is installed in the install_root/sampledb directory. To start the sample database: Open a command prompt and go to the install_root/sampledb directory. Run startdb. bat (Windows) or startdb. Unix- based systems). Open a browser and access one of the following sample home pages: http: //localhost: 8. Take the test drive! Installing Blaze.
DS with J2. EE web applications. The Blaze. DS J2.
EE web application option installs the following files and directories under the installation root: readme. Contains an overview of important information. Blaze. DS web application, used as a starting point for new applications.
Blaze. DS web application using Spring framework, used as a starting point for new application using the Spring framework. Blaze. DS sample applications. Samples Blaze. DS application that integrates with the Spring framework. Simple monitoring application for Blaze. DS deployments. license. Contains license information./resources - Contains Flex SDK source code, fully commented configuration files, as well as directories and files used for security, clustering, Flex- Ajax Bridge and manually creating HTML wrappers. Flash Player installers are in the Flex SDK ZIP file.
To install Blaze. DS as a J2. EE web application: Read the Blaze. DS Release Notes for known issues and any late- breaking information. Unzip the Blaze. DS ZIP file. Deploy the blazeds, samples, samples- spring. For example, for Tomcat, copy the WAR files to the webapps directory and restart the server.
The Blaze. DS sample applications use an HSQLDB database that is installed in the install_root/sampledb directory. To start the sample database: Open a command prompt and go to the install_root/sampledb directory. Run startdb. bat (Windows) or startdb. Unix- based systems). Perform additional application- server specific configuration, as described in Additional server- specific configuration. Running the Test Drive as a J2. EE web application.
In addition to the Blaze. DS WAR file, the Blaze.
DS download includes a series of web applications fully configured with Blaze. DS. There are two test drive applications: To run the test drive after the install: Start your application server. The Blaze. DS sample applications use an HSQLDB database that is installed in the install_root/sampledb directory. To start the sample database: Open a command prompt and go to the install_root/sampledb directory. Run startdb. bat (Windows) or startdb. Unix- based systems). Open a browser window.
Access one of the sample application home pages by opening the one of the following URLs in a browser (the host name and port number of the deployed war file depends on the configuration of your web application): http: //host. Name: port. Number/samples/ http: //host. Name: port. Number/samples- spring/ # Take the test drive!
Additional server- specific configuration. You may need to perform additional configuration steps for the following application servers: * Tomcat 6 * Web. Sphere 6 * JBoss * Running from a compressed WARTomcat. To use Blaze. DS with Tomcat, follow these steps after deploying the Blaze. DS WAR files. These steps are not necessary for the integrated (turnkey) Tomcat installation.
Increase the maximum memory to at least 5. MB. This is achieved by specifying the maximum heap size for the JVM in the JAVA_OPTS variable: - Xmx. Optional) To enable custom authentication, locate the Tomcat security resource libraries under install_root/resources/security/tomcat.
Put flex- tomcat- common. Place flex- tomcat- server. Edit the catalina. Find the common. loader property and add the following path to the end of the list: ${catalina. Add < Valve class. Name="flex. messaging.
Tomcat. Valve"/> tag to the Context descriptors. For example, for the Blaze. DS samples WAR: < Context path="/samples" doc. Base="$\{catalina. Valve class. Name="flex. Tomcat. Valve"/> < /Context> You will now be authenticated against the current Tomcat realm.
Usually, the default for this authentication stores user information in conf/tomcat- users. See the Tomcat documentation for more information on realms.
See the documentation for more information on Blaze. DS custom authentication. You may also need to update the active < login- command> in /WEB- INF/flex/services- config. Blaze. DS WAR file.
For Tomcat, ensure that the Tomcat. Login. Command is active in the < security> section: < security> < login- command class="flex. Tomcat. Login. Command" server="Tomcat"/> ..
Optional) To use the JMSAdapter with the Message Service, you must install and configure a JMS provider (such as active. MQ or open. JMS) for use with Tomcat. Restart Tomcat. Configuring Active.
MQ 4. 1. 1 with Tomcat 6. These instructions create a configuration that matches what is distributed with Blaze. DS. You should be able to integrate Apache Active. MQ 4. 1. 1 with earlier versions of Tomcat and you should also be able to integrate newer versions of Active. MQ with Tomcat 6. These instructions require that you have a valid Apache Ant installation.
Complete the following steps to integrate Active. MQ with your own installation of Tomcat 6. Download Active. MQ 4. Download and install the Active.
MQ distribution following the instructions provided on the Active. MQ website. Active. MQ ships with an example that contains the JAR files and configuration settings that work with a web application deployment. Build the example by opening a command prompt, changing to the activemq_root/example directory and running the following command to build the example: ant war In the tomcat_root/lib directory, create a new directory called activemq. Copy the contents of the activemq_root/example/target/activemq- web/WEB- INF/lib directory to this new directory.
Open the catalina. Modify the common. Modify your Blaze.