[nick.polites]

For the reports server you can get a bit creative by using an alias for the report like reports.company.com and have it pointing in your dns to reports1.company.com. When you fail over to reports2.company.com you just change your DNS to point to reports2. Keep in mind that OAS which is used for reports has a clustering ability by default so it will detect and use both reports instances if they have the same report server component name. Reports2 will need to be turned off until you need to fail over to it.

"Nick, I'm not clear on your comment that if we failover to the 2nd app server, we would need to take the first app server out of the pool. Do you mean if we're directing traffic at the app servers via the LB? Otherwise, this would be handled by OTM SCA, wouldn't it?"


SCA will fail you over to the 2nd app server but I have seen at a customer's site when they failed over to the 2nd one that some processes within weblogic, specifically agents, hung until you removed the 1st application server from the pool. This will make more sense when you configure this but I was told by development, this is the only way to truly failover the instance. It is not an automatic process but one which you will need to intervene. That is why I was suggesting active-active instead.

Keep in mind that OTM does not alert you when you have failed over to the 2nd application server so you will need to setup a 3rd party monitoring application to check this. I have integrated scripts with Nagios to do this, if you are interested we at Mavenwire can implement this for you. Please PM me if you are interested and I'll get you in contact with someone to start the process.