...
- Follow the steps documented under Downloading & Installing to install a copy of on each machine.
- Edit <frevvo-home>/frevvo/tomcat/config/server.xmlin each installation to:
- Setup the AJP jvmRoute
- Uncomment the <Cluster> element
- Edit <frevvo-home>/frevvo/tomcat/bin/setenv.bat on windows or setenv.sh on linux to add cluster setenv parameters.
- Edit <frevvo-home/frevvo/tomcat/conf/Catalina/localhost/frevvo.xml
- Uncomment the <Manager> element for DeltaManager.
- Ensure that the form server's database configured in <frevvo-home/frevvo/tomcat/conf/Catalina/localhost/frevvoin frevvo.xml is the same database used for ALL cluster nodes.
...
To enable single sign on in a cluster, uncomment the following parameter in each of the the <frevvo-home>/frevvo/tomcat/config/server.xml configuration files of all cluster nodes.
...
frevvo.instances.maxIdle is now set to 8 hours. See this in cache-clustered.xml in frevvo.war. frevvo.instances.maxIdle controls for how long (in millis) using/editing forms/flows are kept. I have changed this value to 1728000000 to match web.xml, which is configured to 8 hours.
...
- retry (default 60secs) - "Connection pool worker retry timeout in seconds. If the connection pool worker to the backend server is in the error state, Apache will not forward any requests to that server until the timeout expires. This enables to shut down the backend server for maintenance, and bring it back online later. A value of 0 means always retry workers in an error state with no timeout."
- ping (not set by default)- "Ping property tells webserver the web server to send a CPING request on ajp13 connection before forwarding a request. The parameter is the delay in seconds to wait for the CPONG reply. This features has been added to avoid problem with hung and busy Tomcat's and require ajp13 ping/pong support which has been implemented on Tomcat 3.3.2+, 4.1.28+ and 5.0.13+. This will increase the network traffic during the normal operation which could be an issue, but it will lower the traffic in case some of the cluster nodes are down or busy. Currently this has an effect only for AJP. By adding a postfix of ms the delay can be also set in milliseconds."
...
Additional form server nodes can be dynamically hot swapped (added and removed) to/from a cluster. Once you have signaled one of the servers in your cluster to stop, that server will immediately start rejecting new form requests; wait for existing activities such as rule execution to complete and only then shutdown the node. Your servlet container (ex:Tomcat or WLS, etc) should handle this function correctly.
...
Depending on a customer's specific usage you can increase this to a higher value by editing <frevvo-home>\tomcat\conf\Catalina\localhost\frevvo.xml. Edit the 1st line of frevvo.xml as shown here to change 40000 ms (40 seconds) to whatever you need.
...