This content has been marked as final. Show 1 reply
Seems your architecture is like Browser => OHS ( DMZ ) => Weblogic => DB OR Browser => HLB( like bigip ) => OHS ( DMZ ) => Weblogic => DB
Cluster is the solution for load balancing however if you are using OHS for redirection to weblogic then OHS does the load balancing in round robin way. using cluster in this way has a benefit of in case of any one of your managed server is down the OHS will divert connection request to any one of the active managed server ( you have to turn on dynamic list on at OHS ).
Failover is something different, if in case any of the any managed server goes down then your user you get the application session from another server but new one, means the the tasks not saved by the users on earlier session will lost. for that yo need to use cluster and then need to enable the session replication. another best option is you can use the coherence web if you are using latest versions of weblogic supporting coherence web. with that you not need to worry on user sessions and you can start any of the managed server anytime without worrying about the user sessions.
another way is, you can use side by side deployment feature in case you don't want shutdown your application completely, with this, old connections and new requests will goes to old application and once new application activated all new requests will come to new application and once all requests on old application will complete that application will retire automatically.