Table of Contents

Search

  1. Preface
  2. Introduction to High Availability
  3. Set Up the High Availability Environment
  4. Configure JMS Discovery
  5. Configure RMI Connections
  6. Configure the Operation Console
  7. Configure an HTTP Load Balancer
  8. Configure the Dashboard and Reports
  9. Appendix A: Troubleshooting High Availability
  10. Appendix B: High Availability Log Messages
  11. Appendix C: Port Number Reference
  12. Appendix D: Glossary

High Availability Guide

High Availability Guide

Configuring Tomcat for Sticky Sessions

Configuring Tomcat for Sticky Sessions

Configure properties in the file
<
DIH
InstallationDir/
DataIntegrationHub
/tomcat/conf/server.xml.
Each item that needs to be changed is marked with an "INFA change cluster" XML comment in
server.xml
. Search for this string to find the required locations.
  1. Create a backup of the file
    server.xml
    and call it
    server.xml.bak
    .
  2. Enable AJP connector by removing the comment indicator from the line
    <connection port="18009" enableLookup="false" redirectPort="18443" protocol="AJP/1.3"/>
    .
    This opens a socket that the load balancer uses to forward requests.
  3. Change the value of the attribute
    jvmRoute
    on the element
    Engine
    to the physical computer name, for example,
    Tomcat-A
    . The value of the
    jvmRoute
    attribute must be unique for each Tomcat instance, therefore, use the computer name. Otherwise, the load balancer cannot consistently route the requests and sessions to the correct machine.
    Failure to edit
    jvmRoute
    might cause unexpected results.

0 COMMENTS

We’d like to hear from you!