Replication of Queue Agent Tables between Data Centers
We are using several queue agents to process some work objects in the background. We are using the default pr_sys_queue and pr_sys_lock table for Queue Agent processing. The issue I am looking for is a solution to replication between (2) data centers. Please correct my line of thinking if I am incorrect in any way. But, my thought is if I have a large number of work objects in queue at Data Center One using the pr_sys_queue & pr_sys_lock table....and ....we have to move to Data Center Two for whatever reason - 1) doesn't normal Pega operations use the two tables mentioned? 2) so if we replicate them to another data center, I would expect to see issues?
What issues can I expect and is there another way to avoid the pitfalls?
I think this is best left to the DBA staff to replicate the data between data centers. This would include all the Pega RULES and DATA schema tables. This is done at the data base level and is transparent to Pega,
Jim, in order for us to work with our DBAs to replicate the tables we need a better understanding on what tables are required to be replicated to support a multiple data center deployment. Do any such documentation exist on PDN?