Question
Pegasystems Inc.
HK
Last activity: 1 Oct 2015 23:11 EDT
Rule and Work Schema Segregation on PRPC 6.3
I have a customer I am working with that has a life insurance application built on PRPC 6.3 deployed across multiple countries.
Currently, the Rules and Work related tables (like assignment tables, attachment tables, etc.) are shared across different countries. But the work tables (pc_work) and work history tables are mapped to country specific class groups and physically are different database tables. Also, the JVM node are configured separately for each country which means each country has its own specific set of dedicated JVM node.
The Question is ..
Can we separate all work related tables for each country into different work schema so that the no work related tables are shared across countries. The JVM node configuration can determine the work schema location at runtime. \
What is the best possible option to achieve it in Pega 6.3 SP1
Thanks in advance
Message was edited by: Kip Jackson Removed customer specific references.
Accepted Solution
Variations of this have been done in the field using database aliases. Basically, every cluster has a different database user. Each user 'sees' a single schema which is actually made up of tables from separate schemas (country-specific work table and now-unique assignment and queue tables). PRPC is unaware of the underlying schema split -- everything looks and acts like single schemas.
Be warned that aliasing in Oracle is done via synonyms, which do not play well with PRPC 7 upgrade jobs -- you might need to clone and migrate the rules out to each schema to get them to upgrade later.
Pegasystems Inc.
US
Hi Frank -
I am moving your question to the Product Support area as it is more likely to get an answer there. This area is for help with using the Mesh itself.
Thanks!
Pegasystems Inc.
JP
Pega7 introduced split schema to separate rules and data, so it is possible to configure single shared rule schema and dedicated data schema for each country. I think it would be difficult to achieve clean separation of work related data for each country with PRPC 6.3, unless you have dedicated PRPC instance for each country.
Accepted Solution
Variations of this have been done in the field using database aliases. Basically, every cluster has a different database user. Each user 'sees' a single schema which is actually made up of tables from separate schemas (country-specific work table and now-unique assignment and queue tables). PRPC is unaware of the underlying schema split -- everything looks and acts like single schemas.
Be warned that aliasing in Oracle is done via synonyms, which do not play well with PRPC 7 upgrade jobs -- you might need to clone and migrate the rules out to each schema to get them to upgrade later.