F5 and WebLogic

In setup 2, the F5 is inserting a cookie on the client's browser that maps them to a specific pool member for as long as the cookie's expiration. In setup 1, the user will not be persistent to any machine.

 

 

You'd choose Setup 2 if you needed to send subsequent requests to the same apache server. If the servers behind the Apache boxes manage this persistence on their own via JSESSIONID for instance, you might not need the cookie. Here's a question - if your first request goes to Apache 1 and your second goes to Apache 2, what's the impact? How about if a user has logged in on apache 1 and they then get sent to apache 2?