| Re: Scalability with hw load balancing Scott, You won't have any issues with the way you are setting this up. I've set scalability on about 3-4 customers with a mix of active-active and active-failover and it will work. The way you distinguish each tier instance is via the glog.properties. Make sure your load balancer is set to persistence for the cookie session otherwise you'll get bounced from one web server to the other by your LB in which you'll be asked to continuously re-login. The admin guide is very vague, unless it was recently updated so take your time when configuring it. I am almost 99% sure that what is in the admin guide for active-failover is not correct. Furthermore if you failover to the 2nd app server you need to take the first app server out of the pool otherwise you will have issues with integration. If you are planning on using 5.5 CU-3 or above I would recommend you have it set to active-active. I am not sure if you know this but OTM does not support multiple reports instances in an active-active or active-failover mode. You’ll need to do this manually.
__________________ MavenWire Hosting Admin
Over 7 years of OTM experience
The Oracle OTM / G-Log GC3 Experts Offering Incubator and Production OTM instances www.mavenwire.com |