Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

prpcUtils export.migration.xml unable to find classes

SA-17647

Summary



prpcUtils export for "Migration Export" does not work for classes specified in the xml file, that use the Data-Admin-DB-Table class mapping of their parent class.  prpcUtils export exports zero row.


Error Messages



Not Applicable.


Steps to Reproduce



Extract any rules updated since a specific timestamp:

1. Create an xml document to export an archive of rules or work or data previously committed to the database:

a. Create an xml file with the following contents:

<?xml version ="1.0" encoding="UTF-8" ?>
<ExportClassList>
<Database dbname="PegaRULES">  * Note, the dbname must match the name of the tables Database name as it relates to the source environment
<Class name="Rule-" column="PXCOMMITDATETIME"/>  *Note, the Class Name you wish to export instances from (parent or child) and the column containing a date/time indicating when the instance was created and/or updated.
</Database>
</ExportClassList>

b. Save the file, such as ‘exportClasses.xml’ 

2. Configure the prpcUtils.properties file to export rules updated after the timestamp.

a. Open the ../scripts/utils/prpcUtils.properties file.
b. Configure the connection. Replace the examples below with your system values:
# Connection Information
pega.jdbc.driver.jar=/home/users/path/to/driver/ojdbc6.jar
pega.jdbc.driver.class=oracle.jdbc.OracleDriver (for Oracle)
pega.database.type=oracledate (for Oracle)
pega.jdbc.url=
jdbc:oracle:thin:@<server>:<port>:<databasename>
pega.jdbc.username=username
pega.jdbc.password=password
c. Set the rules schema name to the original Source rules schema:
rules.schema.name=RulesSchema
d. Set the data schema name to the original Source data schema. If necessary, uncomment this line:
#data.schema.name=DataSchema
e. Specify the path and name of the archive file to create with the exported instances:
# FULL PATH TO ARCHIVE (REQUIRED):
export.archive.full.path=/home/path/to/export/file/exported-Aug-5.zip
f. Set the export.migration.xml to the path of the xml document created in step 1.
export.migration.xml=/home/users/administrator/exportClasses.xml
g. Set the export.migration.date to the time-stamp of the last extraction. Use the format "YYYY MM DD hh mm ss S a" and enclose the date in double quotes.
For example, for March 15, 2015 04:42:00:0 PM
export.migration.date="2015 03 15 04 42 00 0 PM"
h. Save and close the prpcUtils.properties file.

3. Open a command prompt and navigate to the scripts or utils directory.
4. Run prpcUtils.bat export to generate the archive file with the new rules.


Root Cause



A defect in Pegasystems’ code not recognizing child classes when there is no Data-Admin-DB-Table instance for the Class name provided in the xml file used for export.

If the parent class is mapped in the DB-Table and that class was used, the utility would export those instances and all of the child classes, not just the one specified in the xml file.


Resolution



Apply HFix-25287 to the system that you are exporting from.  There is no restart of the server required as prpcUtils automatically starts up its own engine and the change will be present.

 

Suggest Edit

Published January 31, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us