About Load Balancing

After configuring and activating your Silver Fabric Tomcat Component, you can access the applications running on the Tomcat Servers. You can also add load balancing to your Component , if required.

You can use load balancing for proxying requests from clients and routing them to engines running the appropriate component. Load balancing is achieved through mappings between relative URLs and components.

VirtualRouter

VirtualRouter is load balancer for HTTP-enabled components. An instance of VirtualRouter runs by default on each Silver Fabric broker, and can also run externally. Additionally, VirtualRouter maintains HTTP Session mappings between clients and Tomcat servers by examining the standard JSESSIONID cookie. For more information about using VirtualRouter, see the TIBCO Silver Fabric Installation Guide

Custom External Load Balancer

You can create a custom load balancer to distribute requests across your component. Accommodating the dynamic nature of Silver Fabric allocation requires a mechanism to update the routing list of the custom balancer when the Silver Fabric allocation changes. Notification of activation or deactivation events can occur in the following ways:

  • ServerHook events
  • SNMP traps
  • Web Service calls

For more information on configuring and using these methods refer to the Silver Fabric Developer's Guide.