CLM failover force application cache flush
we are working thru our DR scenarios and there is confusion over the process.
I see the doc at https://jazz.net/help-dev/clm/index.jsp?re=1&topic=/com.ibm.jazz.install.doc/topics/c_ha.html&scope=null
which discusses cold and idle failover scenarios, but (in my 5th day here) there seems to be some expectation that (with one database) we can start the DR site apps 'quickly' by sending some 'flush' signal to the production CLM apps & WAS.
I am not aware of this scenario being supported, single replicated DB with multiple app sites and near 'hot' failover.
can anyone point me to any different doc than the above..
thanks
|
One answer
|
and we may have found a bug. It appears during DR someone created a CLM project. On revert back to production landscape, the RM component of the CLM application still references the DR RM server applications string..
from jts/registered applications
Prod =
https://server/jts/applicationAdmin?owningApplicationKey=ec018cb6-92bf-4484-8c1a-7ec782e2993e#action=com.ibm.team.process.editProjectArea&itemId=_UUh4EFd5EeOQrZ8XvRoE5w
notice the application keys are different. I need to look at the config on the DR site
Comments I'm guessing that we missed a step on the config of the prod/DR machines that synchs the application IDs...
is that here?
heading:
Synchronizing the configuration files for the primary and backup servers
Ralph Schoon
commented Dec 12 '13, 10:03 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Sam, you might want to contact support on this.
thanks.. on the list of things to do |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.