RRC, Oracle, WAS (6.1.26) Failover on windows 2003
hi,
I'm working on a failover for RRC, at the moment I've got two seperate machines configured to connect to LDAP, and the same Oracle database. They have been setup using the same DNS alias.
So all appears happy (security certificates withstanding), at the jazz end of the business, I seem happy to be able to switch off one, and runup the 2nd and jazz apepars to handle everything happily with no hangovers.
RDM doesnt appear to be so happy, with the login to rrc hanging.....
Before I get to far into debugging this, is anyone doing a similar setup anywhere, that has accomplished a failover setup, and can point me at any useful technotes/white papers?
I'm working on a failover for RRC, at the moment I've got two seperate machines configured to connect to LDAP, and the same Oracle database. They have been setup using the same DNS alias.
So all appears happy (security certificates withstanding), at the jazz end of the business, I seem happy to be able to switch off one, and runup the 2nd and jazz apepars to handle everything happily with no hangovers.
RDM doesnt appear to be so happy, with the login to rrc hanging.....
Before I get to far into debugging this, is anyone doing a similar setup anywhere, that has accomplished a failover setup, and can point me at any useful technotes/white papers?
One answer
Ok, spooted the deliberate mistake, WAS server has the same (as tomcat) jfs index files burried inside the server profile. Delete the files (as per tomcat) associated with the indices, start the server, the indices get rebuilt, allowing yo uto switch (almost) seemlessley between primary server and DR server...Happy days..