The only components that need to have sticky sessions are the RWS (htcc) and the RCS (Recording Crypto Server). Also the Speechminer Web if you want to do the load balancing between two of them or more.
The other components only need to have a simple load balancing, when for example a POST is done, it points to the F5 and it redirects the POST to the component. The F5 listen in one port for each "cluster" of component (also it can be recognized by the first part of the URL, for example http://IP/component1): one port for WebDAV, one port for RPS, one port for Interaction Receiver, and the mentioned before that needs extra configuration. Then the F5 simply do a round robin between the members (ip:port of the application), because them don't requires stickyness.
The RCS and RWS "extra" configuration of httpd load balancer is (red):
# Web Services
<Proxy balancer://htcc>
BalancerMember http://htcc1:8080 route=HTCC1
BalancerMember http://htcc2:8080 route=HTCC2
BalancerMember http://htcc3:8080 route=HTCC3
[color=red]Header add Set-Cookie "ROUTEID=.%{BALANCER_WORKER_ROUTE}e; path=/" env=BALANCER_ROUTE_CHANGED
ProxySet stickysession=ROUTEID[/color]
</Proxy>
ProxyPass /api balancer://htcc/api
ProxyPass /internal-api balancer://htcc/internal-api
ProxyPass /ui balancer://htcc/ui
# RCS
<Proxy balancer://rcs>
BalancerMember http://rcs1:8008 [color=red]disablereuse=On connectiontimeout=10000ms route=RCS1_Application_Name[/color]
BalancerMember http://rcs2:8008 [color=red]disablereuse=On connectiontimeout=10000ms route=RCS2_Application_Name[/color]
[color=red]ProxySet stickysession=JSESSIONID[/color]
</Proxy>
ProxyPass /rcs balancer://rcs/rcs
You'll need to "translate" this extra configuration to F5 "language". I've never done it, but httpd and F5 are very used so I think there is a lot of information
