Two way replication – keyed files
We are rolling out a new credit card switch where the app will run on two iSeries in different locations each handling roughly half of the nation’s transactions for load balancing. The vendor sold us a concept that includes MIMIX to replicate the files so that if on site were down, those units could fail over and operate on the remaining site. As we get further into implementation, we now discover that they know this will not work for the files in IFS (that make up the db for a JAVA version of the switch, and that the native iSeries files need to use "keyed file" replication, which I guess means the files are forced to keep all record keys the same to there is not repeated duplication. The only admin I speak to that has MIMIX experience groaned loudly when I ask about keyed duplication and indicated it can be a nightmare.
Does anyone have experience with this that has a HAPPY ENDING? Is keyed two way replication going to cause me a large amount of PAIN?
Software/Hardware used:
Software/Hardware used:
ASKED:
February 24, 2009 5:49 PM
UPDATED:
February 25, 2009 8:09 PM
Answer Wiki:
Your "two-way" replication is also know as "bi-directional"
I can recommend looking at two products:
IBM's Change Data Capture <a href="http://www-01.ibm.com/software/data/infosphere/change-data-capture/"> -here</a>
and Vision Solutions Replicate 1 <a href="http://www.visionsolutions.com/Products/Systems-Data-Management-replicate1.aspx"> here</a>.
I know they both support bi-directional transfers. I can't answer the rest of your questions.
Regards
Mike
To see all answers submitted to the Answer Wiki: View Answer History.
RSS - Discussions Help
Discuss This Question:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
