Support Article
Need to have Split Schema with no Plan.xml in weblogic
SA-16941
Summary
User's onboarding application is being upgraded to Pega7.1.8/KYC 7.12 with split schema. Plan.xml deployment is mandatory for split schema(as per Pega upgrade guide). Plan.xml deployment is not allowed in user's environment as the wrapper software (DAP) used for all deployments across enterrpise is not engineered to deploy Plan.XML. User is looking for alternate solution to achieve split schema upgrade with no Plan.xml. The following settings in prconfig.xml didn't work because Pega was not able to find the rule schema.
<env name="database/databases/PegaRULES/defaultSchema" value="RULES_SCHEMA_NAME"/>
<env name="database/databases/PegaDATA/defaultSchema" value="DATA_SCHEMA_NAME"/>
Error Messages
Getting below error in logs
Invalid table name as pr4_base is queries with no schema name...like below
select pzPVStream from .pr_base where pxObjclass = ?
Steps to Reproduce
1. Perform Pega7.1.8 split schema install/upgrade in weblogic with no plan.xml
Root Cause
How to question on custom deployment by user.
Resolution
Perform the following local-change:
If you review the Plan.xml bundled with the PRPC distribution image you can see the following sections –
<variable-definition>
<!-- Modify the following variables by filling in the value element-->
<variable>
<name>defaultDataSchema</name>
<value>mydataschema</value>
</variable>
<variable>
<name>defaultRulesSchema</name>
<value></value>
</variable>
<!-- Modify the above variables -->
… .. ..
… .. ..
<module-override>
<module-name>prweb.war</module-name>
<module-type>war</module-type>
<module-descriptor external="false">
<root-element>web-app</root-element>
<uri>WEB-INF/web.xml</uri>
<variable-assignment>
<name>defaultDataSchema</name>
<xpath>/web-app/env-entry/[env-entry-name="prconfig/database/databases/PegaDATA/defaultSchema"]/env-entry-value</xpath>
<operation>replace</operation>
</variable-assignment>
<variable-assignment>
<name>defaultRulesSchema</name>
<xpath>/web-app/env-entry/[env-entry-name="prconfig/database/databases/PegaRULES/defaultSchema"]/env-entry-value</xpath>
<operation>replace</operation>
</variable-assignment>
</module-descriptor>
The above means that you will need to update the web.xml under prpc.ear/prweb.war/WEB-INF to replace the element “/web-app/env-entry/[env-entry-name="prconfig/database/databases/PegaDATA/defaultSchema"]/env-entry-value” with “mydataschema”.
If you search for the <module-override>/<uri> element values you will be able to locate all the deployment descriptors under the PRPC EAR file that needs to be modified.
Published January 31, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.