Support Article
prpcUtils export including schema changes in product rule
SA-23199
Summary
Pega deployment using prpcUtils fails. Database user configured does not have privileges to execute the DB schema changes, thus the exported product rule file must not contain any schema changes. The product rule exported has the 5.4 compatibility check box selected, but prpcUtils still includes schema changes in the exported product rule file.
Error Messages
Not Applicable
Steps to Reproduce
Export product rule with 5.4 compatibility check using prpcUtils.
Root Cause
A defect in Pegasystems’ code or rules. The 5.4 compatibility check box property from the product rule is not used during the export process from the command line.
Resolution
Perform the following local-change:
Modify the prpcUtils.xml file to specify the -m command line argument during export. With this change, schema changes will always be excluded from the export.
<java classname="com.pega.pegarules.pub.PegaRULES" failonerror="true" fork="true" dir="${load.temp.dir}">
<classpath refid="prpc.base.path"/>
<jvmarg value="${jvm.arg.mem.max}"/>
<sysproperty key="com.pega.pegarules.bootstrap.properties.url" value="file:///${prbootstrap.config}" />
<sysproperty key="pegarules.config" value="${pegarules.config}" />
<arg value="com.pega.pegarules.deploy.internal.util.ExportImpl" />
<arg line="-p "${export.archive.productkey}""/>
<arg line="-o "${export.archive.full.path}""/>
<arg line="-U "${exportRAP.username.arg}""/>
<arg line="-P "${exportRAP.password.arg}""/>
<arg line="-m"/>
</java>
Published May 21, 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.