Skip to main content
Jump to: navigation, search

Difference between revisions of "RAP/RWT Cluster"

< RAP
(Schedule)
m (Run)
Line 13: Line 13:
 
We are currently working to make transparent session [http://en.wikipedia.org/wiki/Failover failover] possible for RAP applications.
 
We are currently working to make transparent session [http://en.wikipedia.org/wiki/Failover failover] possible for RAP applications.
  
=== Run ===
+
=== Configuration ===
* provide a <code>web.xml</code> that looks like the one below:
+
In order to run an RWT application in a cluster configuration, an additional servlet filter must be registered. The <code>web.xml</code> should look like the one below:
 
   <?xml version="1.0" encoding="UTF-8"?>
 
   <?xml version="1.0" encoding="UTF-8"?>
 
   <web-app version="2.4"  
 
   <web-app version="2.4"  
Line 37: Line 37:
 
     </servlet-mapping>
 
     </servlet-mapping>
 
   </web-app>
 
   </web-app>
* set the <code>lifecycle</code> system property to <code>org.eclipse.rwt.internal.lifecycle.SimpleLifeCycle</code>
+
In addition a different life cycle must be selected. To do so, set the <code>lifecycle</code> system property to <code>org.eclipse.rwt.internal.lifecycle.SimpleLifeCycle</code>
  
 
=== Development Snapshots ===
 
=== Development Snapshots ===

Revision as of 09:00, 5 June 2011

| RAP wiki home | RAP project home |

Warning2.png
Support for Transparent Session Failover in RWT is work in progress and details outlined below may change without prior notice


Load balancing

Load balancing to distribute workload across multiple nodes in a cluster works with RAP out of the box since version 1.0.

One thing to mind though when setting up a load balancer for RAP applications is that it must be configured to use stcky sessoins (aka session affinity). This entails that once a session is started, the same server serves all requests for that session.

For information on how to set up load balancing, refer to the servlet container documentation. E.g. Tomcat


Transparent Session Failover

We are currently working to make transparent session failover possible for RAP applications.

Configuration

In order to run an RWT application in a cluster configuration, an additional servlet filter must be registered. The web.xml should look like the one below:

 <?xml version="1.0" encoding="UTF-8"?>
 <web-app version="2.4" 
   <context-param>
     <param-name>org.eclipse.rwt.entryPoints</param-name>
     <param-value> the class name of your entry point goes here </param-value>
   </context-param>
   <listener>
     <listener-class>org.eclipse.rwt.internal.engine.RWTServletContextListener</listener-class>
   </listener>
   <servlet>
     <servlet-name>rwtServlet</servlet-name>
     <servlet-class>org.eclipse.rwt.internal.engine.RWTDelegate</servlet-class>
   </servlet>
   <filter-mapping>
     <filter-name>org.eclipse.rwt.internal.engine.RWTClusterSupport</filter-name>
     <servlet-name>rwtServlet</servlet-name>
   </filter-mapping>
   <servlet-mapping>
     <servlet-name>RWTServlet</servlet-name>
     <url-pattern>/</url-pattern>
   </servlet-mapping>
 </web-app>

In addition a different life cycle must be selected. To do so, set the lifecycle system property to org.eclipse.rwt.internal.lifecycle.SimpleLifeCycle

Development Snapshots

Development takes place in HEAD, if you are interested you may want to directly check out the source from the source code repository. To run the tests you will have to add Jetty 7.4 and the H2 embedded database (version 1.1) to your target platform.

Nightly builds are also available and can be downloaded from the build server.

Schedule

We plan to ship the first version with milestone 1 of RAP 1.5 which will be available end of August 2011.

Back to the top