Page History
...
Setting up session replication consists of the following steps:
More information regarding Tomcat Session Replication can be found at http://tomcat.apache.org
...
| Code Block | ||
|---|---|---|
| ||
<web-app>
<distributable/>
<!-- System Event and Debug classes -->
<listener>
<listener-class>com.hof.servlet.SysSessionListener</listener-class>
</listener>
|
To enable session replication, add the following to the ClusterManagement servlet in the web.xml file.
| Code Block | ||
|---|---|---|
| ||
<init-param>
<param-name>SessionReplication</param-name>
<param-value>true</param-value>
</init-param>
|
| Anchor | ||||
|---|---|---|---|---|
|
Modifications to server.xml
Changes need to be made to the server.xml file in the Yellowfin/appserver/conf directory.
Add the additional XML entry within the “<host>” XML block.
| Code Block | ||
|---|---|---|
| ||
<Cluster className="org.apache.catalina.ha.tcp.SimpleTcpCluster"/> |
The IP address “228.0.0.4” is a multicast address that session replication messages will be received on. This does not need to be modified, but a Linux/Unix server may need to register a valid multicast route to receive broadcasts on this address. This can be done by running the following command on the console:
| Code Block | ||
|---|---|---|
| ||
sudo route add -net 224.0.0.0 netmask 224.0.0.0 dev eth0 |
This syntax may be different for different flavours of Linux or Unnis. This example uses “eth0” as the network device that will be used for this route.
...